Omron CJ1W-DRM21 Operation Manual
広告
広告
Machine Automation Controller
CJ-series
DeviceNet Units
Operation Manual for NJ-series CPU Unit
CJ1W-DRM21
DeviceNet Units
W497-E1-03
OMRON, 2011
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.
Introduction
Introduction
Thank you for purchasing a CJ-series CJ1W-DRM21 DeviceNet Unit.
This manual contains information that is necessary to use the CJ-series CJ1W-DRM21 DeviceNet Unit for an NJ-series CPU Unit. Please read this manual and make sure you understand the functionality and performance of the NJ-series CPU Unit before you attempt to use it in a control system.
Keep this manual in a safe place where it will be available for reference during operation.
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 introducing FA systems.
• Personnel in charge of designing FA systems.
• Personnel in charge of installing and maintaining FA systems.
• Personnel in charge of managing FA systems and facilities.
For programming, this manual is intended for personnel who understand the programming language specifications in international standard IEC 61131-3 or Japanese standard JIS B3503.
Applicable Products
This manual covers the following products.
CJ-series CJ1W-DRM21 DeviceNet Unit
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 1
Relevant Manuals
Relevant Manuals
There are three manuals that provide basic information on the NJ-series CPU Units: the NJ-series CPU
Unit Hardware User’s Manual , the NJ-series CPU Unit Software User’s Manual , and the NJ-series
Instructions Reference Manual .
Most operations are performed from the Sysmac Studio Automation Software. Refer to the Sysmac Studio Version 1 Operation Manual (Cat. No. W504) for information on the Sysmac Studio.
Other manuals are necessary for specific system configurations and applications.
Read all of the manuals that are relevant to your system configuration and application to make the most of the NJ-series CPU Unit.
NJ-series User’s Manuals
Basic information
2
Introduction to NJ-series Controllers
Setting devices and hardware
Using motion control
Using EtherCAT
Using EtherNet/IP
Using CJ-series Units
Software settings
Using motion control
Using EtherCAT
Using EtherNet/IP
Programming
Using motion control
Using EtherCAT
Using CJ-series Units
Programming error processing
Testing operation and debugging
Using motion control
Using EtherCAT
Using EtherNet/IP
Troubleshooting and managing errors in an NJ-series Controller
Use the relevant manuals for references according to any error that occurs.
Maintenance
Using EtherCAT
Using EtherNet/IP
Using CJ-series Units
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Manual Configuration
Manual Configuration
NJ-series CPU Unit Hardware User’s Manual (Cat. No. W500)
Section
Section 1
Introduction
Section 2
System Configuration
Section 3
Configuration Units
Section 4
Installation and Wiring
Section 5
Troubleshooting
Section 6
Inspection and Maintenance
Appendices
Description
This section provides an introduction to the NJ-series Controllers and their features, and gives the NJ-series Controller specifications.
This section describes the system configuration used for NJ-series Controllers.
This section describes the parts and functions of the configuration devices in the NJseries Controller configuration, including the CPU Unit and Configuration Units.
This section describes where and how to install the CPU Unit and Configuration Units and how to wire them.
This section describes the event codes, error confirmation methods, and corrections for errors that can occur.
This section describes the contents of periodic inspections, the service life of the Battery and Power Supply Units, and replacement methods for the Battery and Power
Supply Units.
The appendices provide the specifications of the Basic I/O Units, Unit dimensions, load short-circuit protection detection, line disconnection detection, and measures for
EMC Directives.
NJ-series CPU Unit Software User’s Manual (Cat. No. W501)
Section 1
Introduction
Section
Section 2
CPU Unit Operation
Description
This section provides an introduction to the NJ-series Controllers and their features, and gives the NJ-series Controller specifications.
This section provides information that is necessary to use the CPU Unit, including how the CPU Unit works and the operations that it performs depending on the status of the CPU Unit.
This section describes how to use I/O ports, how to create the slave configuration and unit configuration and how to assign functions.
Section 3
I/O Ports, Slave Configuration, and
Unit Configuration
Section 4
Controller Setup
Section 5
Designing Tasks
Section 6
Programming
Section 7
Checking Operation and Actual
Operation
Section 8
CPU Unit Functions
Section 9
Communications Setup
Section 10
Example of Actual Application Procedures
Section 11
Troubleshooting
Appendices
This section describes the initial settings of the function modules.
This section describes the task system and types of tasks.
This section describes programming, including the programming languages and the variables and instructions that are used in programming.
This section describes the items and procedures for checking the operation of an NJseries Controller, including offline debugging procedures.
This section describes the functionality provided by the CPU Unit.
This section describes how to go online with the CPU Unit and how to connect to other devices.
This section describes the procedures that are used to actually operate an NJ-series
Controller.
This section describes the event codes, error confirmation methods, and corrections for errors that can occur.
The appendices provide the CPU Unit specifications, task execution times, specifications of individual system-defined variables, data attribute lists, CJ-series Unit memory information, CJ-series Unit memory allocation methods, and version information.
3 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
4
Manual Configuration
Sysmac Studio Version 1 Operation Manual (Cat. No. W504)
Section
Section 1
Introduction
Section 2
Installation and Uninstallation
Section 3
System Design
Section 4
Programming
Section 5
Online Connections to a Controller
Section 6
Debugging
Section 7
Other Functions
Section 8
Reusing Programming
Section 9
Support Software Provided with the
Sysmac Studio
Section 10
Troubleshooting
Appendices
Description
This section provides an overview and lists the specifications of the Sysmac Studio and describes its features and components.
This section describes how to install and uninstall the Sysmac Studio.
This section describes the basic concepts for designing an NJ-series System with the
Sysmac Studio and the basic operating procedures.
This section describes how to create programs with the Sysmac Studio.
This section describes how to go online with a Controller.
This section describes how to debug the programs online on the Controller or debug it offline with the Simulator.
This section describes other functions that are supported by the Sysmac Studio, including security functions and troubleshooting functions.
This section describes how to reuse the programs that you create with the Sysmac
Studio.
This section describes the Support Software that is provided with the Sysmac Studio.
This section describes the error messages that are displayed when you check a program on the Sysmac Studio and how to correct those errors.
The appendices describe the following:
Driver Installation for Direct USB Cable Connection
Specifying One of Multiple Ethernet Interface Cards
Online Help
Simulation Instructions
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit
(Cat. No. W497) (This Manual)
Section
Section 1
Features and System Configuration
Section 2
Nomenclature and Installation
Section 3
Data Exchange with the CPU Unit
Section 4
Remote I/O Master Communications
Section 5
Remote I/O Slave Communications
Section 6
Message Communications
Section 7
Other Functions
Section 8
Communications Timing
Section 9
Troubleshooting and Maintenance
Appendices
Description
This section provides an introduction to the DeviceNet Units and their features. It also describes the operating procedure and the specifications of the DeviceNet Units.
This section describes the nomenclature, functionality and installation of the
DeviceNet Unit.
This section describes the data exchange between the CPU Unit and DeviceNet Unit and the definitions of the device variables for CJ-series Unit.
This section describes the remote I/O communications performed as a DeviceNet master by the DeviceNet Unit.
This section describes the remote I/O communications performed as a DeviceNet slave by the DeviceNet Unit.
This section describes the message communications of the DeviceNet Unit.
This section describes other functionality provided by the DeviceNet Unit.
This section describes the communications timing of the DeviceNet Unit and the performances of the remote I/O communications and message communications.
This section describes the troubleshooting procedure, event logs and maintenance procedure for the DeviceNet Unit.
---
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Manual Configuration
DeviceNet Operation Manual (Cat. No. W267)
Section
Section 1
Introduction
Section 2
Network Configuraion and Wiring
Section 3
Communications Power Supply
Methods
Appendices
Description
This section provides an overview of the DeviceNet network, including features, functionality, and types of connected devices such as Masters and Slaves.
This section describes the DeviceNet network configuration, the wiring method, and details on the connected devices such as connectors.
This section describes the communications power supply methos.
This section provides a list of related products, describes dimensions of the connected devices, and gives a list of corrent consumption of Masters and Slaves.
DRT2 Series DeviceNet Slaves Operation Manual (Cat. No. W404)
Section
Section 1
Smart Slaves and Features
Section 2
Example System Startup
Section 3
Common Slave Specifications
Section 4
Function of All Slaves, General-purpose Slaves, and Environmentresistive Slaves
Section 5
General-purpose Slaves
Section 6
Environment-resistive Slaves
Section 7
Analog Slaves
Section 8
Communications Timing
Section 9
Troubleshooting and Maintenance
Appendix
Description
This section provide a functional overview and descrives the types of Slaves.
This section provides the operating procedures for DeviceNet by using examples.
This section provides specifications and indicator displays that are common to all
Slaves. It also describes the allocation of remote I/O memory for Smsty Salves.
This section provides an overview funcionality provided by DRT2 Sries Slaves and the operating procedure.
This section describes the specificaions and the components, terminal arrangement, basic procedures for wiring, and settings for General-purpose Slaves.
This section describes the specifications, terminal arrangements, basic procedures for wiring and settings for Environment-resistive Slaves (conforming to IP67).
This section describes the specifications, terminal arrangements, wiring methods and settings for Analog Slaves.
This section provides information on the response time and the transmission delay time when the remote I/O communications or message commucnaitions are performred.
This section describes the troublushooting and mentainance procedures to take corrective actions for errors and conduct a routine inspection.
This section provides an overview of explicit messages, a list of commands, and informaion on how to use setting files (EDS files) that are required in the multi-vendor environments. It also gives a list of the device profiles of Slaves and a list of Slaves and connected devices.
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 5
6
Manual Configuration
GT1 Series DeviceNet Multiple I/O Terminal Operation Manual (Cat.
No. 348)
Section
Section 1
Multiple I/O Terminal
Section 2
Hardeare Setup and Operationa
Check
Section 3
Sample Programs
Section 4
Basic I/O Unit Specifications
Section 5
Special I/O Unit Specifications
Section 6
Communications Timing
Section 7
Troublushooting and Maintenance
Appendices
Description
This section describes the features, system configuration, types of Units and funcitons provided by the Multiple I/O Terminals.
This section describes the operating procedures for the Multiple I/O Terminals by using examples.
This section provides sample programs to use the Special I/O Units of the Multiple
I/O Terminals.
This section describes the specifications of the each Basic I/O Unit, terminal arrangements, wiring methods.
This section describes the specifications, terminal arrangements, wiring methods of the each Special I/O Unit.
This section describes the response time and transmission delay time of the remote
I/O commucnaitions functions.
This section describes the troublushooting and mentainance procedures to take corrective actions for errors and conduct a routine inspection.
This section provides the device profiles of Slaves that are required in the multi-vendor environments and gives a list of products including Multiple I/O Terminals and connected devices.
CVM1/CV-series and C200HX/HG/HE/HS DeviceNet Master Units
Operation Manual (Cat. No. W379)
Section
Section 1
Features and System Configuration
Section 2
Master Unit Components and Installation
Section 3
Remote I/O commucanitons
Section 4
Message Communications
Section 5
Software Switches and Status Area
Section 6
Communications Timing
Section 7
Troubleshooting and Maintenance
Appendix
Description
This section describes the features of the DeviceNet and the operating procedure for the DeviceNet Master Unit.
This section describes the component names, functionality and installation of the
DeviceNet Master Units.
This section describes the remote I/O master function provided by the DeviceNet
Master Unit.
This section describes the message commucniations performed by the DeviceNet
Master Unit.
This section describes the details on the software switches used to control the
DeviceNet Unit and the status area.
This section describes the communication timing of the DeviceNet Master Unit and the performances of the remote I/O communciations and message communications.
This section describes the troublushooting and mentainance procedures to take corrective actions for errors and conduct a routine inspection.
This section describes the details on the commands for the message communciations and the completion codes of the message communications.
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Manual Configuration
CS/CJ Series DeviceNet Unit Operation Manual (Cat. No. W380)
Section
Section 1
Features and System Configuration
Section 2
Nomeclature and Installation
Section 3
Allocated CIO and DM Words
Section 4
Remote I/O Master Communications
Section 5
Remote I/O Slave Communications
Section 6
Message Communications
Section 7
Other Functions
Section 8
Communciations Timing
Section 9
Troublueshooting and Maintenance
Appendix
Description
This section provides an overview of the DeviceNet Units and their features. It also describes the operating procedure and the specifications of the DeviceNet Units.
This section describes the nomenclature, functionality and installation of the
DeviceNet Unit.
This section describes the data exchange between the CPU Unit and DeviceNet Unit and the definitions of the CIO and DM words allocated to the DeviceNet Unit.
This section describes the remote I/O communications performed as a DeviceNet master by the DeviceNet Unit.
This section describes the remote I/O communications performed as a DeviceNet slave by the DeviceNet Unit.
This section describes the message communications of the DeviceNet Unit.
This section describes other functionality provided by the DeviceNet Unit.
This section describes the communications timing of the DeviceNet Unit and the performances of the remote I/O communications and message communications.
This section describes the troubleshooting procedure, event logs and maintenance procedure for the DeviceNet Unit.
---
CX-Integrator Ver.2.
@
Operation Manual (Cat. No. W464)
Section
Section 1
Overview
Section 2
Basic Operations
Section 3
Trouting Tables
Section 4
Data Links for Controller Link and
SYSMAC LINK
Section 5
Ethernet
Section 6
DeviceNet
Section 7
CompoNet
Section 8
CompoWay/F
Section 9
NT Link
Section 10
Network Testing
Appendices
Description
This section provides an overview of the CX-Integrator and describes the CX-Integrator menus and connecitions.
This section describes the basic operations used for the CX-Integrator.
This section describes how to set the routing tables. For NJ-series, routing table is created by using Sysmac Studio instead of CX-Integrator.
This section describes how to set data links for Controller Link and SYSMAC LINK networks.
This section describes the operations specific to Ethernet.
This section describes the settings and operations unithe to DeviceNet networks including registeing slaves in the master, I/O allocations, and devide monitoring.
This section describes the basic usage of CompoNet networks and how to set ConpoNet parameters.
This section describes the settings and operations specific to the CompoWay/F system.
This section describes the settings and operations specific to the NT Link system.
This section describes the operations of the network test tool.
This section describes the CPS files for Ethernet, Controller Link, CompoWay/F and
NT Link Networks, and EDS files for DeviceNet Networks.
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 7
Manual Structure
Manual Structure
Page Structure
The following page structure is used in this manual.
Level 2 heading
Level 3 heading
A step in a procedure
Indicates a procedure.
4 Installation and Wiring
4-3 Mounting Units
4-3-1 Connecting Controller Components
The Units that make up an NJ-series Controller can be connected simply by pressing the Units together and locking the sliders by moving them toward the back of the Units. The End Cover is connected in the same way to the Unit on the far right side of the Controller.
1
Join the Units so that the connectors fit exactly.
Hook
Connector
Hook holes
Level 1 heading
Level 2 heading
Level 3 heading
Gives the current headings.
2
The yellow sliders at the top and bottom of each Unit lock the Units together. Move the sliders toward the back of the Units as shown below until they click into place.
Move the sliders toward the back until they lock into place.
Lock
Release
Slider
4
The sliders on the tops and bottoms of the Powe r Supply Unit, CPU Unit, I/O Units, Special I/O
Units, and CPU Bus Units must be completely locked (until they click into place) after connecting the adjacent Unit connectors.
Page tab
Gives the number of the main section.
Special information
Icons indicate precautions, additional information, or reference information.
8
NJ-series CPU Unit Hardware User’s Manual (W500)
Manual name
4-9
This illustration is provided only as a sample. It may not literally appear in this manual.
Special Information
Special information in this manual is classified as follows:
Precautions for Safe Use
Precautions on what to do and what not to do to ensure safe usage of the product.
Precautions for Correct Use
Precautions on what to do and what not to do to ensure proper operation and performance.
Additional Information
Additional information to read as required.
This information is provided to increase understanding or make operation easier.
Note References are provided to more detailed or related information.
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Manual Structure
Precaution on Terminology
In this manual, “download” refers to transferring data from the Sysmac Studio to the physical Controller and “upload” refers to transferring data from the physical Controller to the Sysmac Studio.
For the Sysmac Studio, synchronization is used to both upload and download data. Here, “synchronize” means to automatically compare the data for the Sysmac Studio on the computer with the data in the physical Controller and transfer the data in the direction that is specified by the user.
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 9
Manual Structure
10 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Sections in this Manual
Sections in this Manual
1
Features and System
Configuration
I
Index
2
Nomenclature and Installation
3
Data Exchange with the CPU Unit
4
Remote I/O Master Communications
5
Remote I/O Slave Communications
6
Message Communications
7
Other Functions
8
Communications Timing
9
Troubleshooting and Maintenance
A
Appendices
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 11
1 1 I
2
7
8
9
A
3
4
5
6
CONTENTS
CONTENTS
Introduction ............................................................................................................... 1
Relevant Manuals ...................................................................................................... 2
Manual Configuration ............................................................................................... 3
Manual Structure ....................................................................................................... 8
Sections in this Manual .......................................................................................... 11
CONTENTS............................................................................................................... 12
Read and Understand this Manual ........................................................................ 16
Safety Precautions .................................................................................................. 19
Precautions for Safe Use........................................................................................ 24
Precautions for Correct Use................................................................................... 30
Regulations and Standards.................................................................................... 33
Unit Versions ........................................................................................................... 36
Related Manuals ...................................................................................................... 38
Revision History ...................................................................................................... 39
Section 1 Features and System Configuration
Section 2 Nomenclature and Installation
12 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
CONTENTS
Section 3 Data Exchange with the CPU Unit
3-3 Device Variables for CJ-series Unit (Allocations Setting Table, Slave Detailed Status) . 3-51
Section 4 Remote I/O Master Communications
4-4-2 Settings through Device Variables for CJ-series Unit
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 13
CONTENTS
Section 5 Remote I/O Slave Communications
5-3-2 Settings through Device Variables for CJ-series Unit
Section 6 Message Communications
Section 7 Other Functions
Section 8 Communications Timing
Section 9 Troubleshooting and Maintenance
14 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
CONTENTS
Appendices
A-1 Differences in Available Functions Depending on the CPU Unit (NJ or CJ Series) ..........A-2
A-3 DeviceNet Explicit Message Send Command for Other Manufacturer Nodes .................A-41
Index
Index ................................................................................................ Index-2
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 15
Read and Understand this Manual
Read and Understand this Manual
Please read and understand this manual before using the products. Please consult your OMRON representative if you have any questions or comments.
Warranty and Limitations of Liability
WARRANTY
OMRON's exclusive warranty is that the products are free from defects in materials and workmanship for a period of one year (or other period if specified) from date of sale by OMRON.
OMRON MAKES NO WARRANTY OR REPRESENTATION, EXPRESS OR IMPLIED, REGARDING NON-
INFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR PARTICULAR PURPOSE OF THE
PRODUCTS. ANY BUYER OR USER ACKNOWLEDGES THAT THE BUYER OR USER ALONE HAS
DETERMINED THAT THE PRODUCTS WILL SUITABLY MEET THE REQUIREMENTS OF THEIR
INTENDED USE. OMRON DISCLAIMS ALL OTHER WARRANTIES, EXPRESS OR IMPLIED.
LIMITATIONS OF LIABILITY
OMRON SHALL NOT BE RESPONSIBLE FOR SPECIAL, INDIRECT, OR CONSEQUENTIAL DAMAGES,
LOSS OF PROFITS OR COMMERCIAL LOSS IN ANY WAY CONNECTED WITH THE PRODUCTS,
WHETHER SUCH CLAIM IS BASED ON CONTRACT, WARRANTY, NEGLIGENCE, OR STRICT
LIABILITY.
In no event shall the responsibility of OMRON for any act exceed the individual price of the product on which liability is asserted.
IN NO EVENT SHALL OMRON BE RESPONSIBLE FOR WARRANTY, REPAIR, OR OTHER CLAIMS
REGARDING THE PRODUCTS UNLESS OMRON'S ANALYSIS CONFIRMS THAT THE PRODUCTS
WERE PROPERLY HANDLED, STORED, INSTALLED, AND MAINTAINED AND NOT SUBJECT TO
CONTAMINATION, ABUSE, MISUSE, OR INAPPROPRIATE MODIFICATION OR REPAIR.
16 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Read and Understand this Manual
Application Considerations
SUITABILITY FOR USE
OMRON shall not be responsible for conformity with any standards, codes, or regulations that apply to the combination of products in the customer's application or use of the products.
At the customer's request, OMRON will provide applicable third party certification documents identifying ratings and limitations of use that apply to the products. This information by itself is not sufficient for a complete determination of the suitability of the products in combination with the end product, machine, system, or other application or use.
The following are some examples of applications for which particular attention must be given. This is not intended to be an exhaustive list of all possible uses of the products, nor is it intended to imply that the uses listed may be suitable for the products:
• Outdoor use, uses involving potential chemical contamination or electrical interference, or conditions or uses not described in this manual.
• Nuclear energy control systems, combustion systems, railroad systems, aviation systems, medical equipment, amusement machines, vehicles, safety equipment, and installations subject to separate industry or government regulations.
• Systems, machines, and equipment that could present a risk to life or property.
Please know and observe all prohibitions of use applicable to the products.
NEVER USE THE PRODUCTS FOR AN APPLICATION INVOLVING SERIOUS RISK TO LIFE OR
PROPERTY WITHOUT ENSURING THAT THE SYSTEM AS A WHOLE HAS BEEN DESIGNED TO
ADDRESS THE RISKS, AND THAT THE OMRON PRODUCTS ARE PROPERLY RATED AND
INSTALLED FOR THE INTENDED USE WITHIN THE OVERALL EQUIPMENT OR SYSTEM.
PROGRAMMABLE PRODUCTS
OMRON shall not be responsible for the user's programming of a programmable product, or any consequence thereof.
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 17
Read and Understand this Manual
Disclaimers
CHANGE IN SPECIFICATIONS
Product specifications and accessories may be changed at any time based on improvements and other reasons.
It is our practice to change model numbers when published ratings or features are changed, or when significant construction changes are made. However, some specifications of the products may be changed without any notice. When in doubt, special model numbers may be assigned to fix or establish key specifications for your application on your request. Please consult with your OMRON representative at any time to confirm actual specifications of purchased products.
DIMENSIONS AND WEIGHTS
Dimensions and weights are nominal and are not to be used for manufacturing purposes, even when tolerances are shown.
PERFORMANCE DATA
Performance data given in this manual is provided as a guide for the user in determining suitability and does not constitute a warranty. It may represent the result of OMRON's test conditions, and the users must correlate it to actual application requirements. Actual performance is subject to the OMRON Warranty and
Limitations of Liability.
ERRORS AND OMISSIONS
The information in this manual has been carefully checked and is believed to be accurate; however, no responsibility is assumed for clerical, typographical, or proofreading errors, or omissions.
18 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Safety Precautions
Safety Precautions
Definition of Precautionary Information
The following notation is used in this manual to provide precautions required to ensure safe usage of a
CJ-series DeviceNet Unit. The safety precautions that are provided are extremely important to safety.
Always read and heed the information provided in all safety precautions.
The following notation is used.
WARNING
Caution
Indicates a potentially hazardous situation which, if not avoided, could result in death or serious injury. Additionally, there may be severe property damage.
Indicates a potentially hazardous situation which, if not avoided, may result in minor or moderate injury, or property damage.
Precautions for Safe Use
Indicates precautions on what to do and what not to do to ensure safe usage of the product.
Precautions for Correct Use
Indicates precautions on what to do and what not to do to ensure proper operation and performance.
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 19
Safety Precautions
Symbols
The circle and slash symbol indicates operations that you must not do.
The specific operation is shown in the circle and explained in text.
This example indicates prohibiting disassembly.
The triangle symbol indicates precautions (including warnings).
The specific operation is shown in the triangle and explained in text.
This example indicates a precaution for electric shock.
The triangle symbol indicates precautions (including warnings).
The specific operation is shown in the triangle and explained in text.
This example indicates a general precaution.
The filled circle symbol indicates operations that you must do.
The specific operation is shown in the circle and explained in text.
This example shows a general precaution for something that you must do.
20 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
WARNING
During Power Supply
Do not touch any of the terminals or terminal blocks while the power is being supplied. Doing so may result in electric shock.
Do not attempt to take any Unit apart. In particular, high-voltage parts are present in the Power Supply Unit while power is supplied or immediately after power is turned OFF. Touching any of these parts may result in electric shock. There are sharp parts inside the Unit that may cause injury.
Fail-safe Measures
Provide safety measures in external circuits to ensure safety in the system if an abnormality occurs due to malfunction of the CPU Unit, other Units, or slaves or due to other external factors affecting operation. Not doing so may result in serious accidents due to incorrect operation.
Emergency stop circuits, interlock circuits, limit circuits, and similar safety measures must be provided in external control circuits.
The Controller outputs may remain ON or OFF due to deposition or burning of the output relays or destruction of the output transistors. As a countermeasure for such problems, external safety measures must be provided to ensure safe operation of the system.
The CPU Unit will turn OFF all outputs from Basic Output Units in the following cases. The remote I/O slaves will operate according to the settings in the slaves.
• If an error occurs in the power supply
• If the power supply connection becomes faulty
• If a CPU watchdog timer error or CPU reset occurs
• If a major fault level Controller error occurs
• While the CPU Unit is on standby until RUN mode is entered after the power is turned ON
External safety measures must be provided to ensure safe operation of the system in such cases.
If external power supplies for slaves or other devices are overloaded or shortcircuited, the voltage will drop, outputs will turn OFF, and the system may be unable to read inputs. Provide external safety measures in controls with monitoring of external power supply voltage as required so that the system operates safely in such a case.
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Safety Precautions
21
Safety Precautions
22
WARNING
Fail-safe Measures
Unintended outputs may occur when an error occurs in variable memory or in memory used for CJ-series Units. As a countermeasure for such problems, external safety measures must be provided to ensure safe operation of the system.
Provide measures in the communications system and user program to ensure safety in the overall system even if errors or malfunctions occur in data link communications or remote I/O communications.
If there is interference in remote I/O communications or if a major fault level error occurs, output status will depend on the products that are used.
Confirm the operation that will occur when there is interference in communications or a major fault level error, and implement safety measures.
Correctly set all of the EtherCAT slaves.
The NJ-series Controller continues normal operation for a certain period of time when a momentary power interruption occurs. This means that the NJseries Controller may receive incorrect signals from external devices that are also affected by the power interruption. Accordingly, take suitable actions, such as external fail-safe measures and interlock conditions, to monitor the power supply voltage of the external device as required.
You must take fail-safe measures to ensure safety in the event of incorrect, missing, or abnormal signals caused by broken signal lines, momentary power interruptions, or other causes. Not doing so may result in serious accidents due to incorrect operation.
Voltage and Current Inputs
Make sure that the voltages and currents that are input to the Units and slaves are within the specified ranges.
Inputting voltages or currents that are outside of the specified ranges may cause accidents or fire.
Downloading
Always confirm safety at the destination before you transfer a user program, configuration data, setup data, device variables, or values in memory used for CJ-series Units from the Sysmac Studio. The devices or machines may perform unexpected operation regardless of the operating mode of the CPU
Unit.
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Caution
Application
Do not touch any Unit when power is being supplied or immediately after the power supply is turned OFF. Doing so may result in burn injury.
Wiring
Be sure that all terminal screws and cable connector screws are tightened to the torque specified in the relevant manuals. The loose screws may result in fire or malfunction.
Online Editing
Execute online editing only after confirming that no adverse effects will be caused by deviations in the timing of I/O. If you perform online editing, the task execution time may exceed the task period, I/O may not be refreshed with external devices, input signals may not be read, and output timing may change.
Safety Precautions
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 23
Precautions for Safe Use
Precautions for Safe Use
24
Disassembly and Dropping
• Do not attempt to disassemble, repair, or modify any Units. Doing so may result in malfunction or fire.
• Do not drop any Unit or subject it to abnormal vibration or shock. Doing so may result in Unit malfunction or burning.
Mounting
• The sliders on the tops and bottoms of the Power Supply Unit, CPU Unit, I/O Units, and other Units must be completely locked (until they click into place) after connecting the adjacent Unit connectors.
Installation
• Always connect to a ground of 100 Ω or less when installing the Units. A ground of 100 Ω or less must be installed when shorting the GR and LG terminals on the Power Supply Unit.
Wiring
• Follow the instructions in this manual to correctly perform wiring.
Double-check all wiring and switch settings before turning ON the power supply.
• Use crimp terminals for wiring.
Do not connect bare stranded wires directly to terminals.
• Do not pull on the cables or bend the cables beyond their natural limit.
Do not place heavy objects on top of the cables or other wiring lines. Doing so may break the cables.
• Mount terminal blocks and connectors only after checking the mounting location carefully.
• Be sure that the terminal blocks, expansion cables, and other items with locking devices are properly locked into place.
• Always remove any dustproof labels that are on the top of the Units when they are shipped before you turn ON the power supply. If the labels are not removed, heat will accumulate and malfunctions may occur.
• Before you connect a computer to the CPU Unit, disconnect the power supply plug of the computer from the AC outlet. Also, if the computer has an FG terminal, make the connections so that the FG terminal has the same electrical potential as the GR terminal on the Power Supply Unit. A difference in electric potential between the computer and Controller may cause failure or malfunction.
• If the external power supply to an Output Unit or slave has polarity, connect it with the correct polarity.
If the polarity is reversed, current may flow in the reverse direction and damage the connected devices regardless of the operation of the Controller.
Power Supply Design
• Do not exceed the rated supply capacity of the Power Supply Units in the NJ-series Controller. The rated supply capacities are given in the NJ-series CPU Unit Hardware User’s Manual (Cat. No.
W500).
If the capacity is exceeded, operation may stop, malfunctions may occur, or data may not be backed up normally for power interruptions.
Use NJ-series Power Supply Units for both the NJ-series CPU Rack and Expansion Racks.
Operation is not possible if a CJ-series Power Supply Unit is used with an NJ-series CPU Unit or an
NJ-series Power Supply Unit is used with a CJ-series CPU Unit.
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Precautions for Safe Use
• Do not apply voltages or connect loads to the Output Units or slaves in excess of the maximum ratings.
• Surge current occurs when the power supply is turned ON. When selecting fuses or breakers for external circuits, consider the above precaution and allow sufficient margin in shut-off performance.
Refer to the relevant manuals for surge current specifications. Refer to the NJ-series CPU Unit Hardware User’s Manual (Cat. No. W500) for surge current specifications.
• If the full dielectric strength voltage is applied or turned OFF using the switch on the tester, the generated impulse voltage may damage the Power Supply Unit. Use the adjustment on the tester to gradually increase and decrease the voltage.
• Apply the voltage between the Power Supply Unit's L1 or L2 terminal and the GR terminal when testing insulation and dielectric strength.
• Do not supply AC power from an inverter or other device with a square-wave output. Internal temperature rise may result in smoking or burning. Always input a sinusoidal wave with the frequency that is given in the NJ-series CPU Unit Hardware User’s Manual (Cat. No. W500).
• Install external breakers and take other safety measures against short-circuiting in external wiring.
Turning ON the Power Supply
• It takes up to approximately 10 to 20 s to enter RUN mode after the power is turned ON. During that time, outputs will be OFF or will be the values specified in the Unit or slave settings, and external communications cannot be performed. Use the RUN output on the Power Supply Unit, for example, to implement fail-safe circuits so that external devices do not operate incorrectly.
• Configure the external circuits so that the power supply to the control system turns ON only after the power supply to the Controller has turned ON. If the power supply to the Controller is turned ON after the control power supply, temporary errors may result in incorrect control system signals because the output terminals on Output Units may momentarily turn ON when power supply is turned ON to the
Controller.
• If you transfer data from a backup file on an SD Memory Card to the Controller when the power supply is turned ON, properly select the data groups to transfer. If the data for an unintended data group is transferred to the Controller, it may cause the equipment to operate unpredictably.
Actual Operation
• Check the user program, data, and parameter settings for proper execution before you use them for actual operation.
Turning OFF the Power Supply
• Never turn OFF the power supply to the Controller when the BUSY indicator is flashing. While the
BUSY indicator is lit, the user program and settings in the CPU Unit are being backed up in the builtin non-volatile memory. This data will not be backed up correctly if the power supply is turned OFF.
Also, a major fault level Controller error will occur the next time you start operation, and operation will stop.
• Do not turn OFF the power supply or remove the SD Memory Card while SD Memory Card access is in progress (i.e., while the SD BUSY indicator flashes). Data may become corrupted, and the Controller will not operate correctly if it uses corrupted data. To remove the SD Memory Card from the CPU
Unit while the power supply is ON, press the SD Memory Card power supply switch and wait for the
SD BUSY indicator to turn OFF before you remove the SD Memory Card.
• Do not disconnect the cable or turn OFF the power supply to the Controller when downloading data or the user program from Support Software.
• Always turn OFF the power supply to the Controller before you attempt any of the following.
• Mounting or removing I/O Units or the CPU Unit
• Assembling the Units
• Setting DIP switches or rotary switches
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 25
Precautions for Safe Use
26
• Connecting cables or wiring the system
• Connecting or disconnecting the connectors
The Power Supply Unit may continue to supply power to the rest of the Controller for a few seconds after the power supply turns OFF. The PWR indicator is lit during this time. Confirm that the PWR indicator is not lit before you perform any of the above.
Operation
• Confirm that no adverse effect will occur in the system before you attempt any of the following.
• Changing the operating mode of the CPU Unit (including changing the setting of the Operating
Mode at Startup)
• Changing the user program or settings
• Changing set values or present values
• Forced refreshing
• Always sufficiently check the safety at the connected devices before you change the settings of an
EtherCAT slave or Special Unit.
• If two different function modules are used together, such as when you use CJ-series Basic Output
Units and EtherCAT slave outputs, take suitable measures in the user program and external controls to ensure that safety is maintained in the controlled system if one of the function modules stops. The relevant outputs will stop if a partial fault level error occurs in one of the function modules.
• Always confirm safety at the connected equipment before you reset Controller errors with an event level of partial fault or higher for the EtherCAT Master Function Module.
When the error is reset, all slaves that were in any state other than Operational state due to a Controller error with an event level of partial fault or higher (in which outputs are disabled) will go to Operational state and the outputs will be enabled.
Before you reset all errors, confirm that no Controller errors with an event level of partial fault have occurred for the EtherCAT Master Function Module.
• Always confirm safety at the connected equipment before you reset Controller errors for a CJ-series
Special Unit. When a Controller error is reset, the Unit where the Controller error with an event level of observation or higher will be restarted.
Before you reset all errors, confirm that no Controller errors with an event level of observation or higher have occurred for the CJ-series Special Unit. Observation level events do not appear on the
Controller Error Tab Page, so it is possible that you may restart the CJ-series Special Unit without intending to do so.
You can check the status of the _CJB_UnitErrSta[0,0] to _CJB_UnitErrSta[3,9] error status variables on a Watch Tab Page to see if an observation level Controller error has occurred.
Battery Backup
• The user program and initial values for the variables are stored in non-volatile memory in the CPU
Unit. The present values of variables with the Retain attribute and the values of the Holding, DM, and
EM Areas in the memory used for CJ-series Units are backed up by a Battery. If the Battery is not connected or the Battery is exhausted, the CPU Unit detects a Battery-backup Memory Check Error.
If that error is detected, variables with a Retain attribute are set to their initial values and the Holding,
DM, and EM Areas in memory used for CJ-series Units are cleared to all zeros. Perform thorough verifications and provide sufficient measures to ensure that the devices perform safe operation for the initial values of the variables with Retain attributes and the resulting operation.
Debugging
• Forced refreshing ignores the results of user program execution and refreshes I/O with the specified values. If forced refreshing is used for inputs for which I/O refreshing is not supported, the inputs will first take the specified values, but they will then be overwritten by the user program. This operation differs from the force-set/reset functionality of the CJ-series PLCs.
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Precautions for Safe Use
• You cannot upload or download information for forced refreshing with the Sysmac Studio.
After downloading data that contains forced refreshing, change to RUN mode and then use the Sysmac Studio to perform the operation for forced refreshing.
Depending on the difference in the forced status, the control system may operate unexpectedly.
• Do not specify the same address for the AT specification for more than one variable.
Doing so would allow the same entity to be accessed with different variable names, which would make the user program more difficult to understand and possibly cause programming mistakes.
General Communications
• When you use data link communications, check the error information that is given in ErrSta (Controller Error Status) to make sure that no error has occurred in the source device. Write the user program to use the received data only if there is no error. If there is an error in the source device, the data for the data link may contain incorrect values.
• Unexpected operation may result if inappropriate data link tables are set. Even if appropriate data link tables have been set, confirm that the controlled system will not be adversely affected before you transfer the data link tables. The data links start automatically after the data link tables are transferred.
• All CPU Bus Units are restarted when routing tables are transferred from Support Software to the
CPU Unit. Confirm that the system will not be adversely affected by restarting before you transfer the routing tables.
• Tag data links will stop between related nodes while tag data link parameters are transferred during
Controller operation. Confirm that the system will not be adversely affected before you transfer the tag data link parameters.
EtherNet/IP Communications
• All related EtherNet/IP nodes are reset when you transfer settings for the built-in EtherNet/IP port
(including IP addresses and tag data links settings). Confirm that the system will not be adversely affected by resetting nodes before you transfer the settings.
• If EtherNet/IP tag data links (cyclic communications) are used with a repeating hub, the communications load on the network will increase. This will increase collisions and may prevent stable communications. Do not use repeating hubs on networks where tag data links are used. Use an Ethernet switch instead.
EtherCAT Communications
• Make sure that the communications distance, number of nodes connected, and method of connection for EtherCAT are within specifications.
Do not connect EtherCAT communications to EtherNet/IP, a standard in-house LAN, or other networks. An overload may cause the network to fail or malfunction.
• Malfunctions or unexpected operation may occur for some combinations of EtherCAT revisions of the master and slaves. If you disable the revision check in the network settings, use the Sysmac Studio to check the slave revision settings in the master and the actual slave revisions, and then make sure that functionality is compatible in the slave manuals or other references. You can check the actual slave revisions from the Sysmac Studio or on slave nameplates.
• After you transfer the user program, the CPU Unit is restarted and communications with the Ether-
CAT slaves are cut off. During that period, the slave outputs behave according to the slave settings.
The time that communications are cut off depends on the EtherCAT network configuration. If the
EtherCAT network configuration contains only OMRON EtherCAT slaves, communications are cut off for a maximum of 45 seconds.
Before you transfer the user program, confirm that the system will not be adversely affected.
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 27
Precautions for Safe Use
28
• If the Fail-soft Operation parameter is set to stop operation, process data communications will stop for all slaves when an EtherCAT communications error is detected in a slave. For this reason, if Servo
Drives are connected, the Servos for all axes will be turned OFF. Make sure that the Fail-soft Operation parameter setting results in safe operation when a device error occurs.
• EtherCAT communications are not always established immediately after the power supply is turned
ON. Use the system-defined variables in the user program to confirm that communications are established before attempting control operations.
• If frames sent to EtherCAT slaves are lost due to noise or other causes, slave I/O data is not communicated, and the intended operation is sometimes not achieved. If noise countermeasures are required, use the _EC_InDataInvalid (Input Data Disable) system-defined variable as an interlock condition in the user program.
Refer to the NJ-series CPU Unit Built-in EtherCAT Port User’s Manual (Cat. No. W505) for details.
The slave outputs behave according to the slave settings. Refer to the manuals for the slaves for details.
• When an EtherCAT slave is disconnected, communications will stop and control of the outputs will be lost not only for the disconnected slave, but for all slaves connected after it. Confirm that the system will not be adversely affected before you disconnect a slave.
• If you disconnect the cable from an EtherCAT slave to disconnect it from the network, any current communications frames may be lost. If frames are lost, slave I/O data is not communicated, and the intended operation is sometimes not achieved. Perform the following processing for a slave that needs to be replaced.
Program the _EC_InDataInvalid (Input Data Disable) system-defined variable as an interlock condition.
Set the Impermissible Number of Continuous Timeouts setting in the EtherCAT master to at least
2.
Refer to the NJ-series CPU Unit Built-in EtherCAT Port User’s Manual (Cat. No. W505) for details.
Motion Control
• Confirm the axis number carefully before you perform an MC Test Run.
• The motor is stopped if communications are interrupted between the Sysmac Studio and the CPU
Unit during an MC Test Run. Connect the communications cable between the computer and CPU
Unit securely and confirm that the system will not be adversely affected before you perform an MC
Test Run.
• Always execute the Save Cam Table instruction if you change any of the cam data from the user program in the CPU Unit or from the Sysmac Studio. If the cam data is not saved, the previous condition will be restored when the power is turned ON again, possibly causing unexpected machine operation.
• The positive drive prohibit input (POT), negative drive prohibit input (NOT), and home proximity input
(DEC) of the Servo Drive are used by the MC Function Module as the positive limit input, negative limit input, and home proximity input. Make sure that the signal widths for all of these input signals are longer than the control period of the MC Function Module. If the input signal widths are shorter than the control period, the MC Function Module may not be able to detect the input signals, resulting in incorrect operation.
Battery Replacement
• The Battery may leak, rupture, heat, or ignite. Never short-circuit, charge, disassemble, heat, or incinerate the Battery or subject it to strong shock.
• 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 only an experienced engineer replace the Battery. Make sure that an experienced engineer is in charge of Battery replacement.
• Apply power for at least five minutes before changing the Battery. Install a new Battery within five minutes (at 25
°
C) of turning OFF the power supply. If power is not supplied for at least 5 minutes, the saved data may be lost.
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Precautions for Safe Use
Unit Replacement
• We recommend replacing the Battery with the power turned OFF to prevent the CPU Unit’s sensitive internal components from being damaged by static electricity and to prevent malfunctions. The Battery can be replaced without turning OFF the power supply. To do so, always touch a grounded piece of metal to discharge static electricity from your body before you start the procedure.
After you replace the Battery, connect the Sysmac Studio and clear the Low Battery Voltage error.
• Make sure that the required data, including the user program, configurations, settings, variables, and memory used for CJ-series Units, is transferred to a CPU Unit that was replaced and to externally connected devices before restarting operation.
Be sure to include the routing tables, network parameters, and other CPU Bus Unit data, which are stored in the CPU Unit.
Disposal
• Dispose of the product and Batteries according to local ordinances as they apply.
• The following information must be displayed for all products that contain primary lithium batteries with a perchlorate content of 6 ppb or higher when shipped to or transported through the State of California, USA.
Perchlorate Material - special handling may apply.
See www.dtsc.ca.gov/hazardouswaste/perchlorate.
• The CPU Unit contains a primary lithium battery with a perchlorate content of 6 ppb or higher. Place the above information on the individual boxes and shipping boxes when shipping finished products that contain a CPU Unit to the State of California, USA.
Using the DeviceNet Units
• Enable the scan list to before operating the system.
• When adding a new node to the network, make sure that the baud rate is the same as other nodes.
• Use specified communications cables.
• Do not extend connection distances beyond the ranges given in the specifications.
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 29
Precautions for Correct Use
Precautions for Correct Use
Storage, Mounting, and Wiring
• Do not operate or store the Controller in the following locations. Operation may stop or malfunctions may occur.
• 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
• Take appropriate and sufficient countermeasures when installing the Controller in the following locations.
• Locations subject to strong, high-frequency noise
• 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 lines
• Before touching a Unit, be sure to first touch a grounded metallic object in order to discharge any static build-up.
• Install the Controller away from sources of heat and ensure proper ventilation. Not doing so may result in malfunction, in operation stopping, or in burning.
• An I/O bus check error will occur and the Controller will stop if an I/O Connecting Cable’s connector is disconnected from the Rack. Be sure that the connectors are secure.
• Do not allow foreign matter to enter the openings in the Unit. Doing so may result in Unit burning, electric shock, or failure.
• Do not allow wire clippings, shavings, or other foreign material to enter any Unit. Otherwise, Unit burning, failure, or malfunction may occur. Cover the Units or take other suitable countermeasures, especially during wiring work.
• For EtherCAT and EtherNet/IP, use the connection methods and cables that are specified in the NJseries CPU Unit Built-in EtherCAT Port User’s Manual (Cat. No. W505) and the NJ-series CPU Unit
Built-in EtherNet/IP Port User’s Manual (Cat. No. W506). Otherwise, communications may be faulty.
• Use the rated power supply voltage for the Power Supply Units. Take appropriate measures to ensure that the specified power with the rated voltage and frequency is supplied in places where the power supply is unstable.
• Make sure that the current capacity of the wire is sufficient. Otherwise, excessive heat may be generated. When cross-wiring terminals, the total current for all the terminals will flow in the wire. When wiring cross-overs, make sure that the current capacity of each of the wires is not exceeded.
• Do not touch the terminals on the Power Supply Unit immediately after turning OFF the power supply.
Residual voltage may cause electrical shock.
• If you use reed switches for the input contacts for AC Input Units, use switches with a current capacity of 1 A or greater.
If the capacity of the reed switches is too low, surge current may fuse the contacts.
30 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Precautions for Correct Use
Error Processing
• In applications that use the results of instructions that read the error status, consider the affect on the system when errors are detected and program error processing accordingly. For example, even the detection of a minor error, such as Battery replacement during operation, can affect the system depending on how the user program is written.
• If you change the event level of a Controller error, the output status when the error occurs may also change. Confirm safety before you change an event level.
Restoring and Automatically Transferring Data
• When you edit the restore command file or the automatic transfer command file, do not change anything in the file except for the “yes” and “no” specifications for the selectable data groups. If you change anything else in the file, the Controller may perform unexpected operation when you restore or automatically transfer the data.
Unit Replacement
• If you replace a CPU Bus Unit or Special I/O Unit, refer to operation manual for the Unit for information on the data required for individual Units and redo the necessary settings.
• The absolute encoder home offset is backed up with a Battery in the CPU Unit.
When you change the combination of the CPU Unit and Servomotor, e.g., when you add or replace a
Servomotor, define home again.
To restore the information without changing the CPU Unit-Servomotor combination, remove the absolute encoder home offset from the data to restore.
Task Settings
• If a Task Period Exceeded error occurs, shorten the programs to fit in the task period or increase the setting of the task period.
Motion Control
• Use the system-defined variable in the user program to confirm that EtherCAT communications are established before you attempt to execute motion control instructions. Motion control instructions are not executed normally if EtherCAT communications are not established.
• Use the system-defined variables to monitor for errors in communications with the slaves that are controlled by the motion control function module. Motion control instructions are not executed normally if an error occur in slave communications.
• Before you start an MC Test Run, make sure that the operation parameters are set correctly.
• Do not download motion control settings during an MC Test Run.
EtherCAT Communications
• Do not disconnect the EtherCAT slave cables during operation. The outputs will become unstable.
• Set the Servo Drives to stop operation if an error occurs in EtherCAT communications between the
Controller and a Servo Drive.
• Make sure that all of the slaves to be restored are participating in the network before you reset a Network Configuration Verification Error, Process Data Communications Error, or Link OFF Error in the
EtherCAT Master Function Module. If any slave is not participating when any of these errors is reset, the EtherCAT Master Function Module may access slave with a different node address than the specified node address or the error may not be reset correctly.
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 31
Precautions for Correct Use
Battery Replacement
• Be sure to install a replacement Battery within two years of the production date shown on the Battery label.
• Turn ON the power after replacing the Battery for a CPU Unit that has been unused for a long time.
Leaving the CPU Unit unused again without turning ON the power even once after the Battery is replaced may result in a shorter Battery life.
• When you replace the Battery, use the CJ1W-BAT01 Battery Set.
SD Memory Cards
• Insert the SD Memory Card all the way.
• Do not turn OFF the power supply to the Controller during SD Memory Card access. The files may be corrupted.
If there is a corrupted file in the SD Memory Card, the file is automatically deleted by the restoration function when the power supply is turned ON.
32 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Regulations and Standards
Regulations and Standards
Conformance to EC Directives
Applicable Directives
• EMC Directives
• Low Voltage Directive
Concepts
z
EMC Directive
OMRON devices that comply with EC Directives also conform to the related EMC standards so that they can be more easily built into other devices or the overall machine. The actual products have been checked for conformity to EMC standards.*
Whether the products conform to the standards in the system used by the customer, however, must be checked by the customer. EMC-related performance of the OMRON devices that comply with EC
Directives will vary depending on the configuration, wiring, and other conditions of the equipment or control panel on which the OMRON devices are installed. The customer must, therefore, perform the final check to confirm that devices and the overall machine conform to EMC standards.
* Applicable EMC (Electromagnetic Compatibility) standards are as follows:
EMS (Electromagnetic Susceptibility): EN 61131-2 and EN 61000-6-2
EMI (Electromagnetic Interference): EN 61131-2 and EN 61000-6-4 (Radiated emission: 10-m regulations) z
Low Voltage Directive
Always ensure that devices operating at voltages of 50 to 1,000 VAC and 75 to 1,500 VDC meet the required safety standards. The applicable directive is EN 61131-2.
z
Conformance to EC Directives
The NJ-series Controllers comply with EC Directives. To ensure that the machine or device in which the NJ-series Controller is used complies with EC Directives, the Controller must be installed as follows:
• The NJ-series Controller must be installed within a control panel.
• You must use reinforced insulation or double insulation for the DC power supplies connected to
DC Power Supply Units and I/O Units.
• NJ-series Controllers that comply with EC Directives also conform to the Common Emission Standard (EN 61000-6-4). Radiated emission characteristics (10-m regulations) may vary depending on the configuration of the control panel used, other devices connected to the control panel, wiring, and other conditions.
You must therefore confirm that the overall machine or equipment complies with EC Directives.
The following examples show means of reducing noise.
1
Noise from the communications cable can be reduced by installing a ferrite core on the communications cable within 10 cm of the DeviceNet Unit.
33 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Regulations and Standards
Ferrite Core (Data Line Filter): 0443-164151 (manufactured by
Fair-Rite Products Co., Ltd.)
Impedance specifications
25 MHZ: 156 Ω
100 MHZ: 250
Ω
30 mm 33 mm
13 mm 29 mm
[Contact]
Nisshin Electric Co., Ltd.
2
Wire the control panel with as thick and short electric lines as possible and ground to 100
Ω
min.
3
Keep DeviceNet communications cables as short as possible and ground to 100 Ω min.
34 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Regulations and Standards
Conformance to Shipbuilding Standards
The NJ-series Controllers comply with the following shipbuilding standards. Applicability to the shipbuilding standards is based on certain usage conditions. It may not be possible to use the product in some locations. Contact your OMRON representative before attempting to use a Controller on a ship.
Usage Conditions for NK and LR Shipbuilding Standards
• The NJ-series Controller must be installed within a control panel.
• Gaps in the door to the control panel must be completely filled or covered with gaskets or other material.
• The following noise filter must be connected to the power supply line.
Noise Filter
Manufacturer
Cosel Co., Ltd.
Model
TAH-06-683
Trademarks
• Sysmac and SYSMAC are trademarks or registered trademarks of OMRON Corporation in Japan and other countries for OMRON factory automation products.
• Windows, Windows 98, Windows XP, Windows Vista, and Windows 7 are registered trademarks of
Microsoft Corporation in the USA and other countries.
• EtherCAT is registered trademark and patented technology, licensed by Beckhoff Automation
GmbH, Germany.
• The SD logo is a trademark of SD-3C, LLC.
Other company names and product names in this document are the trademarks or registered trademarks of their respective companies.
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 35
Unit Versions
Unit Versions
36
Unit Versions
A “unit version” has been introduced to manage CPU Units in the NJ Series according to differences in functionality accompanying Unit upgrades.
Notation of Unit Versions on Products
The unit version is given on the ID information label of the products for which unit versions are managed, as shown below.
Example for NJ-series NJ501@@@@ CPU Unit:
ID information label
Unit model Unit version
NJ501 - 1500 Ver.1.
@@
PORT1 MAC ADDRESS:
@@@@@@@@@@@@
PORT2 MAC ADDRESS:
@@@@@@@@@@@@
Lot No. DDMYY
@
xxxx
Lot number and serial number MAC address
The following information is provided on the ID information label.
Item
Unit model
Unit version
Lot number and serial number
MAC address
Description
Gives the model of the Unit.
Gives the unit version of the Unit.
Gives the lot number and serial number of the Unit.
DDMYY: Lot number, @ : For use by OMRON, xxxx: Serial number
“M” gives the month (1 to 9: January to September, X: October, Y: November, Z: December)
Gives the MAC address of the built-in port on the Unit.
Confirming Unit Versions with Sysmac Studio
You can use the Unit Production Information on the Sysmac Studio to check the unit version of the CPU
Unit, CJ-series Special I/O Units, CJ-series CPU Bus Units, and EtherCAT slaves. The unit versions of
CJ-series Basic I/O Units cannot be checked from the Sysmac Studio.
z
CPU Unit and CJ-series Units
1
Double-click CPU/Expansion Racks under Configurations and Setup in the Multiview
Explorer. Or, right-click CPU/Expansion Racks under Configurations and Setup and select
Edit from the menu.
The Unit Editor is displayed for the Controller Configurations and Setup layer.
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Unit Versions
2
Right-click any open space in the Unit Editor and select Production Information .
The Production Information Dialog Box is displayed.
Simple Display Detailed Display
In this example, “Ver.1.00” is displayed next to the unit model.
The following items are displayed.
CPU Unit
Unit model
Unit version
Lot number
CJ-series Units
Unit model
Unit version
Lot number
Rack number, slot number, and unit number z
EtherCAT Slaves
1
Double-click EtherCAT under Configurations and Setup in the Multiview Explorer. Or, rightclick EtherCAT under Configurations and Setup and select Edit from the menu.
The EtherCAT Configuration Tab Page is displayed for the Controller Configurations and Setup layer.
2
Right-click the master in the EtherCAT Configurations Editing Pane and select Display Production Information .
The Production Information Dialog Box is displayed.
The following items are displayed.
Node address
Type information*
Serial number
* If the model number cannot be determined (such as when there is no ESI file), the vendor ID, product code, and revision number are displayed.
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 37
Related Manuals
Related Manuals
The following manuals are related to the NJ-series Controllers. Use these manuals for reference.
Manual name
NJ-series CPU Unit
Hardware User’s Manual
NJ-series CPU Unit Software User’s Manual
Sysmac Studio Version 1
Operation Manual
CJ-series DeviceNet
Units Operation Manual for NJ-series CPU Unit
(This document)
DeviceNet Operation
Manual
DRT2 Series DeviceNet
Slaves Operation Manual
GT1 Series DeviceNet
Multiple I/O Terminal
Operation Manual
CVM1/CV-series and
C200HX/HG/HE/HS
DeviceNet Master Units
Operation Manual
CS/CJ Series DeviceNet
Unit Operation Manual
CX-Integrator Ver.2.
Operation Manual
@
Cat. No.
W500
W501
W504
W497
W267
W404
W348
W379
W380
W464
Model numbers
NJ501@@@@
NJ301@@@@
NJ501-
NJ301-
@@@@
@@@@
Application
Learning the basic specifications of the NJ-series
CPU Units, including introductory information, designing, installation, and maintenance. Mainly hardware information is provided.
Learning how to program and set up an NJ-series
CPU Unit. Mainly software information is provided.
Description
An introduction to the entire NJ-series system is provided along with the following information on the CPU Unit.
• Features and system configuration
• Introduction
• Part names and functions
• General specifications
• Installation and wiring
• Maintenance and inspection
Use this manual together with the NJ-series
CPU Unit Software User’s Manual (Cat. No.
W501).
The following information is provided on a Controller built with an NJ501 CPU Unit.
• CPU Unit operation
• CPU Unit features
• Initial settings
• Programming based on IEC 61131-3 language specifications
Use this manual together with the NJ-series
CPU Unit Hardware User’s Manual (Cat. No.
W500).
Describes the operating procedures of the Sysmac Studio.
SYSMAC-
SE2
---
@@@
CJ1W-DRM21
Learning about the operating procedures and functions of the Sysmac Studio.
Learning about the functions and operating procedures when the CJ-series
DeviceNet Unit is used in an NJ-series system configuration.
Learning about the communications specifications and wiring methods common among the DeviceNet communications networks.
The functions and operating procedures when the CJ-series DeviceNet Unit is used in an NJseries system configuration are described.
The communications specifications and wiring methods common among the DeviceNet communications networks are described.
Please read this manual and familiarize yourself with the functions and characteristics of the
DeviceNet before use.
The types of DRT2 DeviceNet Slaves, the functions, specifications, and operating procedures are described in details.
DRT2-ID/OD/
MD32SL(H)(-1)
DRT2-MD16S
DRT2 Series
DRT1-COM
GT1 Series
Learning about the DRT2
Series DeviceNet Slaves.
C200HW-DRM21-V1
CVM1-DRM21-V1
Learning about the Multiple
I/O Terminal, which is a type of DeviceNet Slave.
Learning about C200H and
CVM1/CV DeviceNet Master Units.
The types of Multiple I/O Terminal, which are kinds of DeviceNet Slaves, are provided. Also, their functions, specifications, and operating procedures are described in details.
The specifications of C200H and CVM1/CV
DeviceNet Master Units, their functions and operating procedures are described.
CS1W-DRM21(-V1)
CJ1W-DRM21
---
Learning about the functions and operating procedure for CS/CJ Series
DeviceNet Units.
Learning about the CX-Integrator that is used to set up the DeviceNet networks and to make settings.
The functions and operating procedures when the CS/CJ Series DeviceNet Unit is used in
CS/CJ series system configuration are described.
The operating procedures for CX-Integrator are described.
38 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Revision History
Revision History
A manual revision code appears as a suffix to the catalog number on the front and back covers of the manual.
Cat. No.
W497-E1-03
Revision code
Revision code
01
02
03
Date
July 2011
March 2012
August 2012
Revised content
Original production
Corrected errors.
Made changes accompanying release of unit version 1.03 of the CPU Unit.
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 39
Revision History
40 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Features and System
Configuration
This section provides an overview of the DeviceNet network, and includes features, specifications, and system configurations.
1
1-4-3 Message Communications Only (Neither Master nor Slave Function
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 1-1
1 Features and System Configuration
1-1 DeviceNet Unit Features
The following are features of the CJ-series DeviceNet Units (CJ1W-DRM21).
z
Multi-vendor Network
You can connect DeviceNet devices made by other companies (masters or slaves) to DeviceNet because it conforms to open field network specifications. You can use a combination of valves, sensors, and other DeviceNet products to adapt the network to various field-level applications. You can use a combination of valves, sensors, and other DeviceNet products to adapt the network to various field-level applications.
z
Simultaneous Remote I/O Communications and Messaging Services
Remote I/O communications that constantly transfer I/O between a DeviceNet Unit and slaves as well as message communications where the DeviceNet Unit sends and receives data as needed can both be executed simultaneously. When a DeviceNet network is constructed, this feature ensures the network will be able to handle applications that require the free flow back and forth of bit data and message data.
Remote I/O Communications
CJ-series DeviceNet
Unit (master)
Remote I/O (master) function
DeviceNet
Slave Slave Slave
Note Refer to
Section 4 Remote I/O Master Communications for details on remote I/O communica-
tions.
Explicit Message Communications
CJ-series
DeviceNet Unit
RS-232C
Slave
Explicit message
DeviceNet
RS-232C
Slave
CJ-series
DeviceNet Unit
Note
Refer to 6-2 Sending Explicit Messages
and 6-3 Receiving Explicit Messages for details on
remote I/O communications.
1-2 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
1 Features and System Configuration z
User-set Allocations without the CX-Integrator
With CJ-series DeviceNet Units, you can allocate remote I/O communications in any area without the CX-Integrator simply by using device variables for CJ-series Unit.
If you use the CX-Integrator, you can change the node address order for more flexible I/O allocations. This feature enables the proper area allocation for any application and simplifies programming, which helps you make effective use of the CPU Unit Area on the memory used for CJ-series
Unit.
Note Refer to
4-4 User-set Allocations for details.
z
Slave Functions
You can use CJ-series DeviceNet Units as both masters and slaves, and you can execute master and slave communications either separately or simultaneously. A Unit that is used as a slave supports fixed and user-set allocations.
CJ-series DeviceNet Unit
(Master)
Master Controller
1
DeviceNet
CJ-series
DeviceNet Unit (Slave)
Slave Controller
64 nodes max.
Note Refer to
Remote I/O Slave Communications for details.
z
Multiple Controllers in a Single Network
You can connect multiple DeviceNet Units in a single network for message communications between
CPU Units as well as for remote I/O communications between Controllers and slaves in multiple groups. This feature allows a DeviceNet to be used as a common bus that can integrate all types of control with less wiring.
CJ-series DeviceNet Unit
(Master)
CJ-series
DeviceNet Unit (Master)
Master Controller
CJ-series
DeviceNet Unit
(Slave)
Master Controller
DeviceNet
Slave
Controller
Remote I/O
Remote I/O
Note Refer to
4-1 Master Remote I/O Communications
for details.
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 1-3
1 Features and System Configuration z
Multiple DeviceNet Units on a Single Controller
You can mount up to 16 CJ-series DeviceNet Units to a single Contoller. This feature enables greater DeviceNet remote I/O control capacity and ensures that DeviceNet can easily handle line expansion as well as other applications.
CJ-series DeviceNet Unit
(master) (See note 1.)
CJ-series DeviceNet Unit
(master)
DeviceNet DeviceNet
CJ-series DeviceNet Unit
(slave) (See note 2.)
CJ-series DeviceNet Unit
(master) (See note 1.)
DeviceNet
DeviceNet
DeviceNet
Note 1 You can mount multiple Units without the CX-Integrator.
2 You can mount DeviceNet Units as slaves with those as masters.
Note Refer to
4-1 Master Remote I/O Communications for details.
1-4 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
1 Features and System Configuration z
DeviceNet Unit Setup Files (SD Memory Card Backup)
You can write setup data (e.g., scan lists) of a DeviceNet Unit as a file to the SD Memory Card mounted in a CPU Unit. This feature greatly simplifies DeviceNet Unit replacement. You can also save a DeviceNet Unit device parameter file (same as setup data file) that is prepared offline with the use of the CX-Integrator on a SD Memory Card, and download the setup data from the SD Memory Card to a DeviceNet Unit.
CJ-series DeviceNet Unit
CPU Unit
SD Memory Card
CX-Integrator
(Laptop PC)
File save
File load
Loads setup data to a DeviceNet Unit using a software switch in CIO Area of the CPU Unit.
Note Refer to
7-1 SD Memory Card Backup Functions
for details.
1
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 1-5
1 Features and System Configuration z
Various Connection Methods
Normal multi-drop, T-branch multi-drop (with up to three branches), and daisy-chain line connections are available. You can combine these methods to construct a flexible system that suits the floor layout.
z
Maximum Network Length of 500 m
A network can connect up to 63 Slaves and can handle remote I/O communications of up to 2,000 byes (16,000 points without the CX-Integrator) per DeviceNet Unit. A maximum network length of
500 m is possible with a baud rate of 125 kbit/s using thick cable.
z
High-speed Communications
High-speed communications are possible at up to 500 kbit/s for a trunk line length of 100 m.
z
Compatibility with Slow Slaves
You can set the communications cycle time without the CX-Integrator. Therefore, you can use slaves with slow response times.
z
A Wide Variety of Slaves
You can use a wide variety of I/O devices, like Remote I/O Terminals, Environment-resistant Terminals, Remote Adapters, Sensor Terminals, Temperature Input Terminals, CQM1 I/O Link Units, Analog I/O Terminals, C200H I/O Link Units, RS-232C Units, Multiple I/O Terminals, Temperature
Adjusters, Inverters, and Intelligent Flags as slaves.
1-6 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
1 Features and System Configuration
1-2 Specifications
1-2-1 DeviceNet Unit
z
General Specifications
General specifications of the CJ-series DeviceNet Unit conform to those of the NJ-series CPU Units.
z
Functional and Performance Specifications
DeviceNet Unit model
Applicable Controller
Unit classification
Applicable unit numbers
Item
Mounting position
No. of
Masters that you can mount
Fixed allocations
User-set allocations
No. of
Slaves that you can mount
Fixed allocations
User-set allocations
Specification
CJ1W-DRM21
NJ Series
CPU Bus Unit
0 to F
CPU Rack or Expansion Rack
3 Units max. (You must allocate unique words with the use of device variables for
CJ-series Unit (for software switch).)
By CX-Integrator 16 Units max. (You must allocate unique words with the use of CX-Integrator.)
By device variables for CJseries Unit
16 Units max. (You must allocate unique words with the use of device variables for CJ-series Unit (user setup tables).)
3 Units max. (You must allocate unique words with the use of device variables for
CJ-series Unit (Software Switches).)
By CX-Integrator 16 Units max. (You must allocate unique words with the use of CX-Integrator.)
By device variables for CJseries Unit
16 Units max. (You must allocate unique words with the use of device variables for CJ-series Unit (user setup tables).)
No. of Units that you can connect per network
Words allocated in the memory used for
CJseries
Unit
DeviceNet remote I/O communications
When used as a Master
When used as a Slave
Fixed allocations Fixed words in the CJ-series DeviceNet Area in the CIO Area (one of three settings).
User-set allocations
Fixed allocations
User-set allocations
64 Units max.
Any I/O memory (Set with the use of the device variables for CJ-series Unit or
CX-Integrator.)
Fixed words in the CJ-series DeviceNet Area in the CIO Area (one of three settings).
Any I/O memory (Set with device variables for CJ-series Unit or CX-Integrator.)
I/O port (without power OFF retention)
(Access via the device variables for CJseries Unit)
25 words/Unit
CPU Unit to DeviceNet Unit: 9 words for the software switches, etc., 6 words for the status area, 8 words for the registered slaves and normal slaves tables
100 words/Unit I/O port (with power OFF retention)
(Access via the device variables for CJseries Unit)
Other I/O memory (Using the userdefined variable for R/W to the allocation area)
Supported connections (communications)
Scan List User Setup Table, Slave User-set Allocations Setup Table, Master I/O
Allocations Reference Table, Slave I/O Allocations Reference Table, Detailed
Slave Status Table, etc.
CPU Unit to DeviceNet Unit: Table for communications cycle time settings
Set the allocation size table for all slaves in any area when remote I/O communications is set to user-set allocations according to the setting in the device variables for CJ-series Unit.
• Remote I/O communications (master and slave): Master/slave connection (poll, bit-strobe, COS, cyclic)
• Explicit message communications: Explicit connection
All conform to DeviceNet communications standards.
1
1-7 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
1 Features and System Configuration
Remote I/O master communications
Item
Slave allocation method
(Using the user-defined variable for R/W to each allocation area)
Fixed allocations
User-set allocations
Specifications
Select one of the following fixed allocations areas with the use of the device variables for CJ-series Unit (Fixed Allocations Area Switches 1, 2, and 3).
Allocated words (CIO
Area)
I/O Size Fixed
Allocation
Area
Setting
1
Fixed
Allocation
Area
Setting
2
Fixed
Allocation
Area
Setting
3
64 words Output
(OUT) area
Input (IN) area
64 words
3200 to
3263
3300 to
3363
3400 to
3463
3500 to
3563
3600 to
3663
3700 to
3763
By CX-
Integrator
By device variables for CJseries Unit
Select one of the above areas with the use of the software switches. All are fixed at 1 word per node address. The default setting is Fixed Allocation Area Setting 1.
Set the areas for the OUT 1/2 and IN 1/2 blocks, the first words, and the allocation sizes for all slaves with the use of the CX-integrator. You can set the blocks for nodes in any order.
Allocated words
The input and output areas can be the following sizes that start from any word in any of the following areas: CIO Area, WR Area,
HR Area, DM Area, or EM Area in the memory used for CJ-series Unit.
Output
(OUT) area
500 words max.
×
2 blocks
Input (IN) area
500 words max.
×
2 blocks
Set the areas and the first words for the OUT 1 and IN 1 blocks in the device variables for CJ-series Unit (Scan List
Setup Table).
Set the allocation size for each slave with the use of the device variables for CJ-series Unit (Allocation Size Setup
Table) in any area. Allocations must be in the order of node addresses.
Allocated words
The input and output areas can be the following sizes that start from any word in any of the following areas: CIO Area, WR Area,
HR Area, DM Area, or EM Area in the memory used for CJ-series Unit.
Output
(OUT) area
500 words max.
×
1 block
Input (IN) area
500 words max.
×
1 block
1-8 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
1 Features and System Configuration
Remote I/O master
Item
Max. No. of Slaves connected per DeviceNet Unit
Max. No. of I/O points per
DeviceNet Unit
Max. No. of I/O per Slave controllable by a DeviceNet Unit
Specifications
Fixed allocations
User-set allocations
By CX-
Integrator
63 nodes
By device variable for
CJ-series
Unit
Fixed allocations
User-set allocations
By CX-
Integrator
By device variable for
CJ-series
Unit
2,048 pts (64 input words, 64 output words)
16,000 pts (500 input words x 1 block, 500 output words x
1 block)
32,000 pts (500 input words x 2 blocks, 500 output words x
2 blocks)
Fixed allocations
User-set allocations
By CX-
Integrator
By device variable for
CJ-series
Unit
2,048 pts (64 input words, 64 output words)
3,200 pts (100 input words, 100 output words)
3,200 pts (100 input words, 100 output words)
1
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 1-9
1 Features and System Configuration
Remote I/O
Slave
Default settings
Item
Allocation method (Using the user-defined variable for R/W to the allocation area)
Max. No. of I/O points per
DeviceNet Unit slave
Fixed allocations
Specifications
Select one of the following fixed allocation areas with the use of the device variable for CJ-series Unit (Slave Fixed Allocated Area Switches
1, 2, and 3).
Allocated words (CIO
Area)
I/O Size Fixed
Allocation
Area
Setting
1
Fixed
Allocation
Area
Setting
2
Fixed
Allocation
Area
Setting
3
3370 3570 3770 Output
(OUT) area to the slave from the master
Input (IN) area to the master from the slave
3270 3470 3670
User-set allocations
Select one of the preceding areas with the use of the software switches.
All are fixed at 1 word per node address. The default setting is Fixed
Allocation Area Setting 1.
By CX-
Integrator
Set the areas for the OUT 1 and IN 1/2 blocks (total of 3 blocks), the first words, and the slave allocation sizes with the use of the CX-Integrator.
By device variable for
CJ-series
Unit
Allocated words
The input and output areas can be the following sizes that start from any word in any of the following areas: CIO Area, WR Area,
HR Area, DM Area, or EM Area.
Output (OUT) area from this slave
Input (IN) area to this slave
100 words x 1
100 words x 2
Set the areas, the first words, and slave allocation size for the OUT 1 and IN 1 blocks (total of 2 blocks) with the use of the device variables for CJ-series Unit (Slave User-set
Allocations Setup Table).
Allocated words
The input and output areas can be the following sizes that start from any word in any of the following areas: CIO Area, WR Area,
HR Area, DM Area, or EM Area memory used for CJ-series Unit.
Output (OUT) area from this slave
Input (IN) area to this slave
Fixed allocations
User-set allocations
By CX-
Integrator
By device variables for CJseries Unit
3,200 pts (100 input words, 100 output words)
• Scan list: Disabled
• Master communications: Supported
• Slave communications: Disabled
• Remote I/O communications: Start
• Master fixed allocations: Fixed Allocation Area Setting 1
• Slave fixed allocations: Fixed Allocation Area Setting 1
100 words x 1
100 words x 1
32 points (1 input word, 1 output word)
4,800 pts (100 input words x 2, 100 output words x 1)
1-10 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
1 Features and System Configuration
Data stored in non-volatile memory (EEPROM) in the
DeviceNet Unit
Applicable connections
Communications cycle time
Item Specifications
Saves the following data settings (same as the Backup file on the SD
Memory Card).
• Master scan list
• Slave scan list
• Message monitoring timer list (monitoring time for explicit message responses)
• Communications cycle time settings
• Master/Slave enabled
The DeviceNet Unit automatically selects the applicable connection. The user can also specify poll, bit-strobe, COS (change of state) or cyclic for the applicable connection of each slave with the use of the CX-Integrator. You can set up to two types of connections for each Slave (although
COS and cyclic cannot be specified simultaneously).
Uses values by default are calculated by the following equations.
Example: 16 Input Slaves (16 points each), 16 Output Slaves (16 points each), and a baud rate of 500 Kbit/s: 9.3 ms
The user can set a value within a range from 2 to 500 ms. However, the calculated value is enabled when the calculated value from the conditions equation is greater than the setting.
Note Uses default values calculated in the way that even missing nodes are cosidered 1 input word 1 output word when the scan list is disabled.
Send explicit messages 63 nodes Message communications
Other functions
Different type of network
SD Memory Card Backup function
CX-Integrator connection method
Setting section
Max. No. of nodes for message communications per DeviceNet Unit
Execution instructions
Inter–network communications
Same type of network
Error history in the DeviceNet Unit
Communications cycle time setting
Message monitoring timer
COS/cyclic heartbeat timer setting
Device data check function
Any commands SendCmd instruction
Allows transmission across the same type of networks between
DeviceNet networks when multiple Units are mounted (can cross up to three levels).
Allows transmission across different types of networks between
DeviceNet and other networks (e.g., Controller Link and Ethernet/IP)
(can cross up to three levels).
Allows DeviceNet Unit setup data (scan list, communications cycle time settings, etc.) to be backed up as a file to a SD Memory Card in the CPU
Unit. You can also read (i.e., restore) the setup data from the SD Memory Card to the DeviceNet Unit.
Data setup file can be restored into a DeviceNet Unit simply by carrying the SD Memory Card to the site if the device parameter file prepared from the CX-Integrator is saved to SD Memory Card from a personal computer.
Supported (You can access the history with the CX-Integrator).
Supported (in the device variable for CJ-series Unit or from the CX-Integrator).
Sets the response monitoring time (explicit connection opening interval) in the DeviceNet Unit for explicit message communications. You can make settings separately for all targeted devices with the use of the
CX-Integrator.
Sets the minimum SEND interval in COS or cyclic connections for all targeted devices. The setting is made using the CX-Integrator.
Performs a comparison check on the following device data when slave data registered in the scan list is compared with actual slave data. You can use the CX-Integrator to set this function for all targeted Slaves.
Vendor, device type and product code
Built-in EtherNet/IP port on CPU Unit or peripheral (USB) port
Rotary switches:
Unit No. (hexadecimal x 1), node address (decimal x 2)
Front panel DIP switch: Baud rate, stop or continue communications when an error occurs
1
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 1-11
1 Features and System Configuration
Display section
Item
Front connector
Communications power supply voltage
Current consumption
External dimensions
Weight
Standard accessories
Specifications
Two indicators (2 colors): Display Unit and network status (Module Status and Network Status).
Two 7-segment indicators: Displays the DeviceNet Unit node address, error code, and node address where an error occurred.
2 dot indicators: Display whether the registration scan list is enabled or not.
One communications connector (communications data: CAN H and CAN
L, communications power supply: V+, V–, shielded)
Use the XW4B-05C1-H1-D connector provided to connect the communications cable.
Note Use the XW4B-05C4-T-D connector sold separately for multi-drop connections.
11 to 25 VDC (supplied from the communications connector)
Communications power supply: 18 mA at 24 VDC, (supplied from the communications connector)
Internal circuit power supply: 290 mA max. at 5 VDC (supplied from the
Power Supply Unit)
31 x 90 x 65 mm (W x H x D)
118 g (connector provided included)
One XW4B-05C1-H1-D connector to connect to a node from a T-branch
Tap.
1-12 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
1 Features and System Configuration
1-3 Overview of CX-Integrator
You can set allocations for remote I/O communications in any order of node addresses with the CX-
Integrator. Users can also set remote I/O communications connections.
For details, refer to the CX-Integrator Ver.2.
@ OPERATION MANUAL (Cat. No. W464).
1
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 1-13
1 Features and System Configuration
1-4 Basic Operating Procedures
1-4-1 Network Installation Procedure
For details on the network installation procedure, refer to the DeviceNet OPERATION MANUAL ( Cat.
No.
W267 ). Only a general description is given here.
(1)
Determine a suitable baud rate for the system.
(2)
Determine the node arrangement, the wiring configuration, and the cable lengths.
A) Restrictions on lengths of trunk lines and branch lines and total drop line length. (Selection of thick cables or thin cables)
B) Separation from noise sources.
Check
Do (1) and (2) above meet the
DeviceNet specifications?
(3)
Yes
Determine the method for how to provide a communications power supply.
(4) Arrange for the required devices.
Delivery of devices.
(5) Installation
No
1-14 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
1 Features and System Configuration
1-4-2 DeviceNet Unit Startup Procedure
The basic operating procedures for DeviceNet Unit are described here.
Use Sysmac Studio to create programs and to set the Unit.
Use the CX-Integrator to set the network configuration.
For details on operations of Sysmac Studio, refer to the Sysmac Studio Version 1 Operation Manual
(Cat. No. W504).
For details on operations of CX-Integrator, refer to CX-Integrator Ver.2.
@ OPERATION MANUAL (Cat.
No. W464).
Step 1: Create POU and global variables
Create unit configuration
Create and register global variables and each POU.
Register variables including variables for accessing the slave area and for message communications data.
Create algorithm of each POU and register local variables of each POU.
Register the Unit in the Unit Configuration on the CPU/Expansion Racks screen in Configuration and Setup.
At this time, set both the device name and the unit number of the unit to be registered.
Allocate device variables for CJ-series Unit to I/O port.
Allocate on the I/O Map View window.
You can use one of the following three methods to allocate.
1. Select and allocate existing variables.
2. Input a new variable name.
3. Automatically create with "Device variable creation".
Step 2: Create Initialization Data of the Unit
Create the Unit settings by using the [Edit Special Unit Settings].
(When the program is transferred, items set here will be reflected in the device variable for CJ-series Unit.)
Step 3: Set up the DeviceNet Unit
Unit number [UNIT No.]
Node address [NODE ADR]
Operation settings for baud rate/ communication errors [DIP switch]
Step 4: Set up Slaves
Node address, baud rate, etc.
Step 5: Mount and wire to the Rack
Wire the slaves
Step 6: Turn ON the power to the
Controller.
Step 7: Transfer the user programs
Set the hardware switch on the front panel.
Set the same unit number as in the Unit Configuration settings.
Initial settings for slaves
Set by referring to the Manual for Slaves.
Reflect the settings for the switches on the front panel of the Unit, in the Unit.
Switch ON the power in the sequence: Communications power → slave power
→ Controller power, or switch all three ON at the same time.
Transfer user programs, Unit Configuration and Setup, and variable information.
1
Step 8: Set up a network configuration Set when you use a unit as a master or a slave.
Step 9: Main operation
A slave may not go online if the communications power supply is turned ON after the slave is turned ON.
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 1-15
1 Features and System Configuration
Additional Information
• The communications power supply and slave power supply, the slave power supply and Controller power supply, or all three of these power supplies may be turned ON simultaneously.
• When Step 6 is performed, an I/O Setting Check Error occurs when there is a Unit Configuration in the CPU Unit which does not match the actual Unit Configuration. In this case, reset the
Controller after Step 7 to cancel the error.
1-16 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
1 Features and System Configuration
Allocation of User-defined Variables to the Memory Used for CJseries Unit
With this Unit, the slave areas of the following functions are allocated to the Memory used for CJ-series
Unit.
• Fixed allocations and user-set allocations (Master)
• Fixed allocations and user-set allocations (Slave)
The user program accesses the slave via the user-defined variable that specifies the AT specification for the area where the slave is allocated. With this Unit, the device variable for CJ-series Unit, or a userdefined variable that specifies the AT specification of the allocation area for the slave as setup using the
CX-Integrator software application, needs to be created. User-defined variables are created using Sysmac Studio.
Have the necessary user-defined variables created before creating a program.
For details on operations, refer to the Sysmac Studio Version 1 Operation Manual (Cat. No. W504).
1
The user is responsible for management of the memory used for CJ-series Unit. Please take great care to avoid overlapping of reference areas between user-defined variables.
Network Configuration Settings
z
Using the Master Function
To use this unit as a master function, the *_Sw1MstrEnblCmd (Master Enable Switch) must be changed to TRUE from Sysmac Studio.
Note Enable master communications through CJW-DRM21 properties if you use CX-Integrator.
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 1-17
1 Features and System Configuration
Turn ON the communications, slave, and Controller power supplies.
(*1)
Switch the CPU Unit to PROGRAM mode.
Fixed Allocations
(Refer to 4-3 Fixed Allocations )
User-set Allocations Using Device Variables for
CJ-series Unit
User-set Allocations Using CX-Integrator
(Refer to the CX-Integrator manual )
TRUE
(Master function enabled)
Check to see if the master function is enabled.
<Check " *_MstrEnblSta " (Master Function Enabled Status) from the Sysmac Studio.>
FALSE (Master function disabled)
Change " *_Sw1MstrEnblCmd " (Master Enable Switch) to
TRUE from the Sysmac Studio. (*2)
Create a network configuration file and device parameters file from the CX-Integrator. (Enable master function in CJ1W-DRM21 property at this time.) Download the above files to the devices on the network.
Change " *_Sw1MstrFixAloc1Cmd to *_Sw1MstrFixAloc3Cmd "
(Master Fixed Allocation
Setting 1 to 3 Switch) to TRUE from the Sysmac Studio. Master remote
I/O communications will begin with the scan list disabled.
Input data in advance into
" *_MstrAlocTblCfg[0]" to "*_
MstrAlocTblCfg[3] " (Master
User-set Allocations Setup Table) and the Allocation Size Setup Table
(specify the position in
"*_MstrAlocTblCfg[4] " and
" *_MstrAlocTblCfg[5] ") from the Sysmac Studio.
Change " *_Sw1SListEnblCmd "
(Scan List Enable Switch) to TRUE from the Sysmac Studio.
Master remote I/O communications will begin with the scan list enabled.
Change "* _Sw1MstrAlocCmd "
(Master User-set Allocations
Switch) to TRUE from the Sysmac
Studio. Master remote I/O communications will begin with the scan list enabled.
Master remote I/O communications will begin with the scan list enabled.
Define user-defined variables in the area to which I/O data is allocated.
Switch the CPU Unit to RUN mode.
*1 Turn ON the communications power supply before turning ON the slave power supplies or the slaves may not go online.
*2 Execute this only when master communications are turned OFF. (If the Master Enable Switch is turned ON when master communications are enabled, a Unit error will occur and a C2 error will be displayed on the 7segment indicator on the front panel.)
1-18 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
1 Features and System Configuration
Precautions for Safe Use
Make sure the scan list is enabled when you use the master function.
This will allow you to check whether slaves are online or not from the CPU Unit so that you will be able to determine whether or not the DeviceNet communicates properly.
Additional Information
You can turn OFF (disconnected) remote I/O communications with a specified slave by changing
*_CnctCmd (Disconnect/Connect Switches) to TRUE when a slave is replaced or is registered in the scan list prior to connection. These switches, however, are changed to FALSE when the power supply is turned OFF, however, so a bit must be turned back to TRUE from the user program when the power turns ON for it to be valid again.
1 z
Using the Slave Function
To use the slave function, the *_Sw2SlavEnblCmd (Slave Enable Switch) must be changed to TRUE from Sysmac Studio.
With fixed allocations or allocations set in the device variables for CJ-series Unit, slave communications must be disabled prior to area allocation and must be enabled following the area allocation.
The order of the procedure is thus Slave Stop Switch (if slave communications are enabled), area allocation, and Slave Enable Switch.
Note Enable slave communications through CJ1W-DRM21 properties if you use a CX-Integrator.
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 1-19
1 Features and System Configuration
Create an I/O table, and switch the CPU Unit to PROGRAM mode.
Fixed Allocations
(Refer to 5-2 Fixed Allocations )
User-set Allocations Using Device Variables for
CJ-series Unit )
User-set Allocations Using CX-Integrator
(Refer to the CX-Integrator manual )
FALSE
(Slave function disabled)
Check to see if the slave function is disabled.
<Check " *_SlavEnblSta " (Slave Function Enabled) from the Sysmac Studio.>
TRUE (Slave function enabled)
Change " *_Sw2SlavDsblCmd " (Slave Stop
Switch) to TRUE from the Sysmac Studio.
Change " *_Sw2SlavFixAloc1Cmd " to " *_SlavFixAloc3Cmd "
(Slave Fixed Allocation
Setting 1 to 3 Switches) to TRUE from the Sysmac Studio.
Input data in advance into
" *_SlavAlocTblCfg[0] " to " *_SlavAlocTblCfg[5] "
(Slave User-set Allocations
Setup Table).
Change "* _Sw2SlavAlocCmd "
(Slave User Allocations Switch) to TRUE from the Sysmac Studio.
Create a device parameter file from the CX-Integrator. (Enable
Slave function in CJ1W-DRM21 properties at this time.) Then download the file to the
DeviceNet Unit.
Change " *_Sw2SlavEnblCmd " (Slave Enable Switch) to TRUE from the Sysmac Studio.
Note: Execute this only when slave communications are turned OFF. (If the Master Enable Switch is turned ON when master communications are enabled, a Unit error will occur and a C2 error will be displayed on the 7-segment indicator on the front panel.)
Define user-defined variables in the area to which I/O data is allocated.
Switch the CPU Unit to RUN mode.
Slave remote I/O communications will begin.
Slave communications must be disabled prior to area allocation when you use fixed allocations or allocations set in the device variable for CJ-series Unit, and the settings must be read to the
Unit when slave communications are enabled.
Allocations will not be valid if slave communications are enabled during area allocation.
1-20 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
1 Features and System Configuration
1-4-3 Message Communications Only (Neither Master nor Slave
Function Used)
The DeviceNet Unit does not have to be registered in the scan list if it is only used for message communications. You can execute message communications (send and receive) with both master and slave communications disabled.
1
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 1-21
1 Features and System Configuration
1-5 List of Usage Methods by Purpose
Design
1-22
Situation
Allocating any words for remote I/O
DeviceNet Unit
Not in order of node addresses
In order of node addresses
Using the Unit as a slave
Set with the use of the CX-Integrator.
Note Allocations with the use of CX-Integrator:
Any node address order and two blocks from
OUT 1, IN 1, OUT 2 and IN 2. Allocation is much easier with the use of a wizard.
Set with the use of the device variables for CJseries Unit.
(Master user-set Allocations Setup Table and Allocation Size Setup Table)
Note
Action
Allocations with the use of device variables for CJ-series Unit: Fixed node address order and one block from OUT 1 and IN 1.
Set with the use of the device variables for CJseries Unit.
Section
Execute communications instructions from the user program.
Section 6 Message Communications
Performing message communications between controllers to which DeviceNet Units are mounted
Mounting multiple DeviceNet
Units using master communications to a single controller
Mounting multiple DeviceNet
Units using slave communications to a single controller
Connecting multiple controllers
(master communications) in a network
Connecting a single Master controller and multiple Slave controllers in a network
Sending DeviceNet explicit messages
3 Units max. with fixed allocations
16 Units max. with user-set allocations
3 Units max. with fixed allocations
16 Units max. with user-set allocations
Supported by user-set allocations with the use of device variables for CJ-series Unit or user-set allocations with the use of the CX-Integrator.
Set multiple Controller to Slave mode from the device variables for CJ-series Unit or the CX-Integrator.
Note Up to 64 Units may be on a network. (Example: 1 Master Controller and 63 Slave Controllers)
Set the command code to 2801.
Setting the node address for a
Setting the baud rate for the
DeviceNet Unit
Stopping remote I/O communications for communications errors
Storing OUT data in slave I/O memory for communications errors
Set the rotary switches on the front of the
DeviceNet Unit.
Set the DIP switch on the front of the DeviceNet
Unit.
Set the DIP switch on the front of the DeviceNet
Unit.
Set the DIP switch on the front of the DeviceNet
Unit.
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
1 Features and System Configuration
Operation
Situation
Stopping remote I/O communications with all Slaves
Using a scan list in remote I/O communications (fixed allocations)
Enabling a scan list in remote I/O communications (user-set allocations by device variables for
CJ-series Unit)
Changing the communications system configuration
Checking to see if all slaves are performing remote I/O communications properly
Checking to see if there is an error history in the DeviceNet
Unit
Monitoring the error history in the DeviceNet Unit
Monitoring status of the
DeviceNet Unit
Checking the current communications cycle time
Adjusting the communications cycle time
Saving all parameters, like scan list data, for masters and slaves on the network
Replacing a DeviceNet Unit
Action
Stop communications with the use of the CX-Integrator or *_Sw1IOCommStopCmd (Remote I/O
Communications Stop Switch).
Change *_Sw1SListEnblCmd (Scan List Enable
Switch) to TRUE.
Set the allocation areas with the use of the device variables for CJ-series Unit, and change
*_Sw1MstrAlocCmd (Master User-set Allocations
Switch) to TRUE.
Change *_Sw1SListClrCmd (Scan List Clear
Switch) to TRUE, and change
*_Sw1SListEnblCmd (Scan List Enable Switch) to
TRUE after you change the communications system.
Monitor the Master Status 2 status codes in
*_Mstr2Sta from Sysmac Studio.
Execute the device monitor function from the CX-
Integrator (Error History Tab).
Execute the device monitor function from the CX-
Integrator (Status and Unit Status Tabs).
Execute the device monitor function from the CX-
Integrator (Current Communications Cycle Time
Tab).
Execute the device parameter edit function from the CX-Integrator (Communications Cycle Time
Tab).
Save the network configuration from the CX-Integrator.
Section
Checking master I/O allocations status (fixed allocations, user-set allocations by device variables for CJ-series Unit, user-set allocations with the CX-Integrator)
Checking to see if all slaves are registered in the scan list
Check *_RegSlavTblSta (Registered Slave Table).
Check *_NormSlavTblSta (Normal Slave Table).
Check the error history (registration yes/no) from
Sysmac Studio.
CS/CJ/CP/NSJ
Series CX-Integrator Ver.2.
@
OPERATION
MANUAL
(W464)
1. Insert a SD Memory Card in the CPU Unit and change the Unit Setup File Backup Switch in the device variables for CJ-series Unit to
TRUE.
2. Replace the DeviceNet Unit.
3. Change Sw2FileRestoreCmd (Unit Setup File
Restore Switch) to TRUE.
4. Change *_Sw1SListEnblCmd (Scan List
Enable Switch) in the device variables for CJseries Unit to TRUE.
5. Make sure the slave is connected, and then change *_Sw1SListEnblCmd (Scan List Clear
Switch) in the device variables for CJ-series
Unit to TRUE.
1
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 1-23
1 Features and System Configuration
1-24 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Nomenclature and Installation
This section describes the nomenclature and installation of the DeviceNet Unit.
2
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 2-1
2 Nomenclature and Installation
2-1 Nomenclature and Functions
2-1-1 Nomenclature and Functions
CJ1W-DRM21
DRM21
MS
NS
01
23
4567
CDE
UNIT
NO.
12
34
9
678 x10 1
12
34
9
678
NODE
ADR x10 0
ON
2
1
4 HOLD
3 ESTP
DR1
DR0
Indicators
Unit No. switch
This switch sets the unit number of the DeviceNet Unit as a onedigit hexadecimal value.
Node address switches
These switches set the node address as a two-digit decimal value.
DIP switch
The pins have the following functions:
Pins 1 and 2: Baud rate
Pin 3: Continue/Stop communications for error (when used as a
Master)
Pin 4: Hold/clear I/O for communications error (when used as a
Slave)
Communications connector
Connect the Network communications cable to this connector. The communications power for this Unit is also supplied through this connector.
A parallel connector with screws (XW4B-O5C1-H1-D) is provided for node connection.
Indicators
The DeviceNet Units are equipped with the following indicators that indicate the operating status of the node itself and the overall network.
a. Two status indicators (two-color: Green or red indicators) b. A two-digit, 7-segment indicator c. Two dot indicators
MS a. Status indicators
NS c. Dot indicators
2-2 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
2 Nomenclature and Installation z
Status Indicators: MS and NS
The MS (Module Status) indicator indicates the status of the node itself and the NS (Network Status) indicator indicates the status of the network.
The MS and NS indicators can be green or red and they can be OFF, ON, or flashing (alternating 0.5-s
ON and 0.5-s OFF). The following table shows the meaning of these indicator conditions.
Indicator
MS
Color Status Meaning (likely errors)
NS
Green
Red
Lit
Lit
Normal operating status
Communications are being performed normally.
A non-recoverable, major fault has occurred.
(Watchdog timer error, memory error, or system error.)
Replace the DeviceNet Unit.
---
Green
Not lit
Lit
Power isn't being supplied or the Unit is being reset.
The Unit is Online with the network and remote I/O communications have been established with a slave registered in the scan list or message communications have been established.
Flashing The Unit is Online with the network, but neither remote
I/O communications nor message communications have been established. Either the scan list is being read, or both remote I/O communications and message communications are disabled.
Red
Flashing A recoverable, partial or minor fault has occurred. (Configuration Error, Switch Setting Error, CPU Unit initialization error, CPU Unit interface error, or Routing Table
Error.)
Correct the error and reset the Unit.
---
Lit A major fault in communications has occurred. Network communications are not possible.
(Node address duplicated or Bus Off error)
Flashing A partial or minor fault in communications has occurred.
(Communications Error, Structure Error, or Verification
Error)
Not lit The Unit is not Online with the network. (There is no network power supply, the Unit is being reset, a partial or minor fault or a sending error has occurred.)
Note The indicators flash at a 0.5-s interval.
2
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 2-3
2 Nomenclature and Installation z
Seven-Segment Indicator
In addition to the MS and NS indicators, DeviceNet Units have a 2-digit, 7-segment indicator that normally indicates the master node address. When an error occurs, the indicator will alternately show between the error code and the node address of the faulty slave.
There are dot indicators at the lower-right corner of each digit. The left dot indicator shows whether or not the master is operating and whether the scan list is enabled or disabled. The right dot indicator shows whether or not the slave is operating.
Normal: Master Unit's node address
Error: Error code and faulty node address
Indicates whether the slave is operating or stopped.
Indicates whether the master is operating or stopped and whether the scan list is enabled or disabled.
Seven-segment Digits
Status
Remote I/O communications active and normal
From power ON to completion of node address check (master function disabled, slave function disabled, or both disabled)
Remote I/O communications started
Display
Displays the master's node address
(00 to 63)
Lit
Flashing
Flashing (until communications actually start)
Flashing From completion of the node address check until the start of remote I/O communications
Error Watchdog timer error
Memory error or
Controller error
Other errors
Not lit
Error code only Lit
Scan list Reading
Registered
Alternately displays the error code and error node address (see diagram below)
"- -" Flashing
2-4 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
2 Nomenclature and Installation
The following diagram shows the alternating error code/ node address display.
OFF (0.1 s)
Error code
(1 s)
Faulty slave's node address
(1 s)
OFF (0.3 s)
Error code
(1 s)
OFF (0.1 s)
Faulty slave's node address
(1 s)
OFF (0.3 s)
OFF (0.3 s)
Master's node address (1 s)
OFF (0.1 s)
Master's error code (1 s)
OFF (0.3 s)
If there is an error at the DeviceNet Unit.
• The master's error code and master's node address will be displayed if an error has occurred at the master.
• There is no priority for showing error codes. All error codes that occur at that time are shown in sequence.
• For the error codes displayed on the seven-segment display, refer to
Dot Indicators
The following table shows the functions of the dot indicators.
Indicator
Left dot
Content
Scan list enabled/disabled, master function disabled
Right dot Slave function disabled
Display
ON: Master function disabled
Flashing: Scan list disabled
OFF: Scan list enabled
ON: Slave function disabled
OFF: Slave operating
2-1-2 Switch Settings
Unit No. Switch
CJ1W-DRM21
01
23
CDE
4567
89
AB
Use the Unit No. Switch to set the unit number for units as a CPU Special Unit. Set a unique unit number for each CPU set Special Unit installed in the CPU Rack and Expansion Rack with the unit numbers in the unit configuration. Turn OFF the Controller before changing the unit number setting.
Setting method: One-digit hexadecimal
Setting range: 0 to F
Note The unit number is set to 0 at the factory.
You can set any unit number from 0 to F as long as it has not been set on another CPU Bus Unit connected to the same CPU Unit.
2
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 2-5
2 Nomenclature and Installation
Precautions for Safe Use
• Use a small flat-blade screwdriver to turn the rotary switches; be careful not to damage the switch.
• Always turn OFF the Controller before changing the unit number setting.
Additional Information
If the unit number is the same as one set on another CPU Bus Unit connected to the same CPU
Unit, a major fault level controller error "Duplicate Unit Number" will occur and it will not be possible to start up the DeviceNet network. After correcting the unit number setting, cycle the power to the Controller.
Node Address Switches
CJ1W-DRM21
9
12
34
678
X 10 1
9
12
34
678
X 10 0
Use these switches to set the node address of the Unit.
Setting method: Two-digit decimal
Setting range: 0 to 63
Note The node address is set to 63 at the factory.
You can set any node address from 0 through 63 as long as it has not been set on another slave node.
Additional Information
If the node address is the same as one set on another node, a node address duplication error will occur and it will not be possible to start up network communications.
2-6
DIP Switch
The DIP switch on the front of the DeviceNet Unit is used to set the baud rate, whether communications will be continued or stopped when a communications error occurs, and whether to hold or clear the remote outputs when a communications error occurs in the slave function.
CJ1W-DRM21
ON
Hold/clear I/O for communications error (when used as a slave)
Continue/stop communications for communications error (when used as a master)
Baud rate
Pin
1
2
3
The settings of the DIP switch pins are shown in the following table. All pins are set to OFF at the factory.
Baud rate
Function Setting
See the next table.
4
Continue/stop remote I/O communications for communication errors
(when used as a master)
Hold/clear remote outputs for communications error (when used as a slave)
OFF: Clear remote outputs
ON: Hold remote outputs
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
2 Nomenclature and Installation z
Baud Rate
Pins 1 and 2 are used to set the baud rate as shown in the following table.
Pin 1 Pin 2
OFF OFF 125 kbit/s
ON OFF 250 kbit/s
OFF ON
ON ON
500 kbit/s
Not allowed.
Baud rate
Precautions for Safe Use
Always turn OFF the Controller before changing the unit number setting.
2
Set the same baud rate on all of the nodes (Master and Slaves) in the Network. Any slaves with baud rates different from the master's rate will not be able to participate in communications and may cause a communications error between nodes that have been set properly.
z
Continue/Stop Remote I/O Communications
If "stop remote I/O communication upon communication error" is set (turned ON) by DIP switch 3, remote I/O communication will stop (*) when any of the following error occurs and will remain stopped after the error is reset (message and slave communications will not stop).
• *_Mstr1IOErr (Remote I/O Communication Error)
• *_SendTimeoutErr (Send Timeout Error)
• *_NetPwrErr (Network Power Error)
To resume communications, change *_ Sw1IOCommStartCmd (Remote I/O Communications Start
Switch) of software switch 1 to TRUE. Refer to
3-2 Device Variables for CJ-series Unit (Software
for details.
Note The 7-segment indicator will show "A0" when remote I/O communications stop.
If pin 3 is OFF, remote I/O communications will stop if a send timeout or network power error occurs, but will restart automatically when the cause of the error is cleared.
z
Hold/Clear Remote Outputs
When the DeviceNet Unit is used as a slave, pin 4 is used to set whether to hold or clear remote outputs when a communications error occurs.
Note If the DeviceNet Unit is used as a slave, the 7-segment indicator will show "L9" when remote
I/O communications stop.
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 2-7
2 Nomenclature and Installation
Communications Connectors
Black
Blue
---
White
Red
Color stickers that match communications cable colors are attached to the communications connectors. Match the colors when connecting communications cables to the connectors. These colors are given in the following table
Color Signal
Power line, negative voltage (V–)
Communications line, low (CAN L)
Shield
Communications line, high (CAN H)
Power line, positive voltage (V+)
For details on communications specifications and wiring, refer to the DeviceNet OPERATION MAN-
UAL (Cat. No. W267).
Precautions for Safe Use
Before connecting communications cables, turn OFF the Controller power supply, all slave power supplies, and the communications power supply.
2-8 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
2 Nomenclature and Installation
2-2 Installing the DeviceNet Unit
2-2-1 System Configuration Precautions
You can mount up to 16 Units on the CPU Rack or an Expansion Rack per CPU (but no more than
10 Units on one Rack).
2-2-2 Mounting
1
Carefully align the connectors to mount the DeviceNet Unit.
Hooks
Connector
Openings for hooks
2
DRM21
MS
NS
12
345
89
23
4
567
DEF
C
UNIT
NO.
10
1
12
345
89
NODE
ADR
10 0
ON
4 HOLD
3
2
1
ESTP
DR1
DR0
2
Move the yellow sliders on the top and bottom of the Unit until they click into position, to lock.
Slide latches back until they lock.
(The latches will click when they lock.)
DRM21
MS
NS
12
345678
UNIT
NO.
12
345
89
10
1
12
345 NODE
ADR
10 0
ON
2
1
4 HOLD
3
ESTP
DR1
DR0
Release
Lock
Slider
Precautions for Safe Use
If the sliders are not securely locked, the DeviceNet Unit functions may not operate sufficiently.
To dismount the Unit, move the sliders to the "Release" direction.
2-9 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
2 Nomenclature and Installation
2-2-3 Handling Precautions
• Always turn OFF the Controller before you mount or dismount a Unit or connect or disconnect cables.
• Provide separate conduits or ducts for the I/O lines to prevent noise from high-tension lines or power lines.
• Prevent wire clippings, cutting chips or other materials from getting inside the Unit. They could cause scorching, failure, and malfunction. Pay particular attention to this during installation and take measures such as covering with a cover.
• If the Unit was shipped from the factory with the dust protection label on top of the unit, be sure to remove that label before switching ON the power. The label prevents heat dissipation and could cause a malfunction.
Remove the label after wiring.
DRM21
MS
NS
23
4567
UNIT
NO.
12
34
89 x10
1
12
34
89
NODE
ADR x10 0
ON
2
1
4 HOLD
3 ESTP
DR1
DR0
2-2-4 External Dimensions
13.7
31
90
DRM21
MS
NS
23
01
4567
CDE
UNIT
NO.
12
34
89 x10
1
12
34
89
NODE
ADR x10
0
ON
2
1
4 HOLD
3
ESTP
DR1
DR0
50
35
5
11 15 5
65
2-10 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Data Exchange with the CPU Unit
This section describes the words allocated to the DeviceNet Unit in the CIO Area and
DM Area. These words both enable controlling the DeviceNet Unit and accessing Unit and network status.
3
3-2 Device Variables for CJ-series Unit (Software Switches, Statuses) . . . . . 3-9
3-2-13 C200H Master Replacement Master Status 1 . . . . . . . . . . . . . . . . . . . . . . . . 3-48
3-3 Device Variables for CJ-series Unit (Allocations Setting Table, Slave
3-3-4 Communications Cycle Time Reference Table . . . . . . . . . . . . . . . . . . . . . . . 3-58
3-1 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
3 Data Exchange with the CPU Unit
3-1 Data Exchange with the CPU Unit
Data exchange between this Unit and the CPU Units uses the I/O port and memory for CJ-series Unit allocated to the DeviceNet Unit.
3-1-1 Data Flow
The CPU Units and CJ-series DeviceNet Units exchange data as shown in the table and chart below.
Data exchange type
Access methods from the user program
Device variable for
CJ-series Unit
AT specification destination
I/O port
Data exchange timing Unit data type
User-defined variable
System-defined variable
Memory used for
CJ-series Unit
None
During I/O refresh
During I/O refresh
At I/O refresh after instruction execution
During I/O refresh
Software switch
Status
Allocations setting table
Slave detailed status
Slave I/O Data
Message send/receive data for communications instructions
Unit Restart Flag, Communications Port Enabled
Flags, etc.
Note The allocations setting table and slave detailed status data are retained in the CPU unit by the battery even during power interruptions.
3-2 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
3 Data Exchange with the CPU Unit
CPU Unit
User program I/O port
Software switch, status data
Device variable for CJ-series
Unit
AT specification
Software switch, status data
:
:
Software switches (I/O refresh)
Status (I/O refresh)
DeviceNet Unit
:
:
Allocations setting table, slave detailed status data
Device variable for CJ-series
Unit
AT specification
Allocations setting table, slave detailed status data
:
:
Allocations setting table
(I/O refresh)
Status (I/O refresh)
Slave I/O message communications data
Device variable for CJ-series
Unit
AT specification
Memory used for
CJ-series Unit
Memory areas such as
CIO and DM
:
:
Slave output, message communications data
(I/O refresh)
Slave input, message communications data
(I/O refresh)
:
:
:
:
3
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 3-3
3 Data Exchange with the CPU Unit
Device Variable for CJ-series Unit
Device variables for CJ-series Units are variables for which AT is specified for the I/O port explained below. The user program uses device variables for CJ-series Unit to access the Configuration Unit such as DeviceNet Unit.
For allocation of the device variables for CJ-series Unit to the I/O port, refer to
Variables for CJ-series Unit (P. 3-5).
z
I/O Port
An "I/O port" is a logical interface for data exchange by a CPU Unit with a DeviceNet Unit or other
Configuration Unit.
An I/O port has a unique pre-defined name for each unit model and function.
An I/O port is automatically created by preparing the Unit Configuration with Sysmac Studio.
For details on the I/O ports defined for DeviceNet Unit, refer to
3-2 Device Variables for CJ-series
Unit (Software Switches, Statuses)
and 3-3 Device Variables for CJ-series Unit (Allocations Setting
Table, Slave Detailed Status) .
DeviceNet Unit has two types of I/O ports; one is for the following software switch/status data, and the other is for allocations setting table/slave detailed status data.
z
Software switches / Status data
Software switches (execution instructions of each function from the CPU Unit to the DeviceNet Unit),
DeviceNet Unit statuses and error data are allocated.
z
Allocations Setting Table, Slave Detailed Status Data
Allocations Setup Tables that the user can freely set and individual slave statuses by node address are allocated.
User-defined Variable
Slaves are allocated to the memory used for CJ-series Unit when you use the functions shown below.
• Master remote I/O communications (fixed/user-set allocation)
• Slave remote I/O communications (fixed/user-set allocation)
To use this area from the user program, you need to create a user-defined variable of AT specification.
3-1-2 Accessing From the User Program
From the user program, various types of information are exchanged using AT specified device variables for CJ-series Unit that are allocated to the I/O ports, and AT specified user-defined variables that are allocated to slave allocation areas.
From the user program, the following is used to exchange various types of information:
3-4 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
3 Data Exchange with the CPU Unit
Setting/status
Data type
Software switches/status data
Allocations setting table, slave detailed status
Slave area
I/O port, memory used for CJ-series Unit
Operation Data
Fixed allocation 1 to 3 Fixed allocation 1 OUT: CIO 3200 to CIO
3263 words
IN: CIO 3300 to CIO 3363 words
Fixed allocation 2 OUT: CIO 3400 to CIO
3463 words
IN: CIO 3500 to CIO 3563 words
Fixed allocation 3 OUT: CIO 3600 to CIO
3663 words
IN: CIO 3700 to CIO 3763 words
Any area of CIO, DM, WR, HR and EM User-set allocation
(By master user-set allocation)
User-set allocation
(By CX-Integrator)
Same as above
Access method
Device variables for CJ-series Unit
User-defined variable
How to Create Device Variables for CJ-series Unit
Use I/O Map in Sysmac Studio to allocate device variables for CJ-series Unit to an I/O port. Specify variable names using one of the methods shown below.
1. Select and allocate existing variables.
2. Input a new variable name.
3. Automatically create with "Create Device Variable".
The following shows the structure of a variable name created automatically with method 3.
*_Sw1SListEnblCmd
This is an I/O port name. The name indicates unit functions, statuses and parameters.
This is the device name when this unit is registered in the Unit Configuration. (By default, a device name is assigned from "J01" in the order of registration in the
Unit Configuration. ) This identifies the individual unit.
For details on device variables for CJ-series Unit, refer to the following:
3-2 Device Variables for CJ-series Unit (Software Switches, Statuses)
3-3 Device Variables for CJ-series Unit (Allocations Setting Table, Slave Detailed Status)
In the explanations from here on, the device name automatically created is used as the device variable name for CJ-series Unit, for example *_Sw1SListEnblCmd .
For details on the memory for CJ-series Unit, refer to NJ-series CPU Unit Software User's Manual
(Cat. No. W501).
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 3-5
3
3 Data Exchange with the CPU Unit
How to Create User-defined Variables
In this unit, slaves are allocated to the memory used for CJ-series Unit when you use the functions shown below.
• Fixed allocations and user-set allocations (Master)
• Fixed allocations and user-set allocations (Slave)
Use the Sysmac Studio to register user-defined variables to the variable table. Use user-defined variables to specify the AT specification of the memory used for CJ-series Unit to which the slave is allocated.
Generally, array variables are created.
Below is an example of allocation to user-defined variables.
• Used with Master Fixed Allocation 1
• Used slaves: 16 I/O points; 64 slaves
In this case, I/O data of each slave is allocated as follows:
Words allocated
CIO 3200
CIO 3201
I/O data
OUT slave I/O data (node address 0)
OUT slave I/O data (node address 1)
CIO 3263 OUT slave I/O data (node address 63)
Allocate the I/O data to the user-defined variables as shown in the example below.
3-6
This example uses the following three data types.
• Slave1_OutData_A (WORD type)
• Slave1_OutData_B (BOOL type)
• Slave1_OutData_C (union)
Use one of these data types or multiple data types to create user-defined variables according to the user program.
When the user program accesses the slave only with WORD type, use the WORD-type user-defined variables Slave1_OutData_A defined in the example.
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
3 Data Exchange with the CPU Unit
The user-defined variables and I/O data of each slave are allocated as follows:
I/O Data User-defined variable name
:
OUT slave I/O data (node address 0) Slave1_OutData_A[0]
OUT slave I/O data (node address 63) Slave1_OutData_A[63]
The user program accesses the slave with WORD-type variables.
3200
Address
3263
When the user program accesses the slave only with BOOL type, use the BOOL-type user-defined variables Slave1_OutData_B defined in the example.
The user-defined variables and I/O data of each slave are allocated as follows:
I/O Data
OUT slave I/O data (node address 0)
Bit 0
OUT slave I/O data (node address 0)
Bit 1
:
OUT slave I/O data (node address
63) Bit 15
User-defined variable name
Slave1_OutData_B[0,0]
Slave1_OutData_B[0,1]
Slave1_OutData_B[63,15]
The user program accesses the slave with BOOL-type variables.
Address
3200.00
3200.01
3263.15
3
When the user program accesses the slave with both WORD type and BOOL type, use the union-type user-defined variables Slave1_OutData_C defined in the example.
The user-defined variables and I/O data of each slave are allocated as follows:
:
I/O Data User-defined variable name
OUT slave I/O data (node address 0) WORD type
Slave1_OutData_C[0].w
BOOL type
Slave1_OutData_C[0].b[0] to
Slave1_OutData_C[0].b[15]
OUT slave I/O data (node address
63)
WORD type
Slave1_OutData_C[63].w
BOOL type
Slave1_OutData_C[63].b[0] to
Slave1_OutData_C[63].b[15]
3200
Address
3200.00
3200.15
3263
3263.00
3263.15
The user program accesses the slave with WORD-type or BOOL-type variables.
When you use the union, prepare the union data type Mem that you can access with WORD and BOOL as shown below.
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 3-7
3 Data Exchange with the CPU Unit
Additional Information
For details on memory used for CJ-series Unit, variable allocation, and user-defined variable registration, refer to the Sysmac Studio Version 1 Operation Manual (Cat. No. W504).
3-8 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
3 Data Exchange with the CPU Unit
3-2 Device Variables for CJ-series Unit
(Software Switches, Statuses)
When you operate and reference software switches and statuses, use the following device variables for
CJ-series Unit allocated to the I/O port of this Unit.
Name of device variable for
CJ-series Unit
*_Sw1Cmd
*_Sw2Cmd
*_MstrCOSSendCmd
*_CnctCmd
*_Unit1Sta
*_Unit2Sta
*_Mstr1Sta
*_Mstr2Sta
*_Slav1Sta
*_Slav2Sta
*_RegSlavTblSta
*_NormSlavTblSta
*_CMstrSta
Type
WORD
WORD
LWORD
LWORD
WORD
WORD
WORD
WORD
WORD
WORD
LWORD
LWORD
WORD
R/W
R
R
R
R
RW
RW
RW
RW
R
R
R
R
R
Area
Software Switches 1
Software Switches 2
Master COS Send Switch
Disconnect/Connect Switches
Unit Status 1
Unit Status 2
Master Status 1
Master Status 2
Slave Status 1
Slave Status 2
Registered Slave Table
Normal Slave Table
C200H Master Replacement Master Status 1
The function of each device variable for CJ-series Unit is explained below.
Described with variables names automatically created on the I/O Map View window.
3
3-2-1 Software Switches 1
Use one of the following device variables for CJ-series Unit is used to operate Software Switches 1 from the user program:
• WORD-type device variable for CJ-series Unit holding all switch functions contained in Software
Switches 1
• BOOL-type device variable for CJ-series Unit separating functions per each switch contained in Software Switches 1
All switches execute some functions when the user changes them to TRUE. They change to FALSE automatically after the functions are executed.
Once a function is set by changing a switch to TRUE (except for the switches listed below), it is saved regardless of whether the power is turned OFF and ON again.
• *_Sw1IOCommStartCmd (Remote I/O Communications Start Switch)
• *_Sw1IOCommStopCmd (Remote I/O Communications Stop Switch)
Note No functions other than the master and slave communications are disabled by stopping master or slave communications.
If multiple switches are changed to TRUE simultaneously, the requests will generate errors and Unit operation will remain unchanged.
The device variables for CJ-series Unit corresponding to the following words will change to TRUE if a request made by a software switch ends in an error.
• *_Unit2Sta (Unit Status 2)
• *_Mstr1Sta (Master Status 1)
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 3-9
3 Data Exchange with the CPU Unit
WORD-type device variables for CJ-series Unit holding all switch functions contained in Software
Switches 1 are shown below.
Name of device variable for
CJ-series Unit
*_Sw1Cmd
Type R/W Area
WORD RW Software
Switches 1
Function
Bits have the following functions:
Bit 00: Scan List Enable Switch
Bit 01: Scan List Clear Switch
Bit 02: Remote I/O Communications Start
Switch
Bit 03: Remote I/O Communications Start
Switch
Bit 04: Remote I/O Communications Stop
Switch
Bit 05: Reserved by system
Bit 06: Master Enable Switch
Bit 07: Master Disable Switch
Bit 08: Master Fixed Allocation Setting 1
Switch
Bit 09: Master Fixed Allocation Setting 2
Switch
Bit 10: Master Fixed Allocation Setting 3
Switch
Bit 11: Master User-set Allocations Switch
Bit 12: Temporary Setting Switch for Communications Cycle Time
Bit 13: Communications Cycle Time Setting Switch
Bit 14: Communications Cycle Time Reference Table Clear Switch
Bit 15: Reserved by system
Default: 16#0000
3-10 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
3 Data Exchange with the CPU Unit
BOOL-type device variables for CJ-series Unit separating functions per each switch contained in
Software Switches 1 are shown below.
Name of device variable for
CJ-series Unit
*_Sw1SListEnblCmd
*_Sw1SListClrCmd
Type
BOOL
R/W Area
RW Scan List
Enable
Switch
BOOL RW Scan List
Clear
Switch
Function
<Operation specifications>
FALSE → TRUE:
Enables the scan list with fixed allocations.
Note The allocated words are the ones set for use when the scan list is disabled.
The following allocated words are the default settings when the scan list is disabled.
• OUT area:
CIO 3200 to CIO 3263
(1 word/1 node address (fixed))
• IN area:
CIO 3300 to CIO 3363
(1 word/1 node address (fixed))
FALSE:
Returns to FALSE when the scan list is registered and the Unit starts operating with the scan list enabled.
Default: FALSE
<Operation conditions>
• CPU Unit is operating in PROGRAM mode.
• Master function is enabled.
• Scan list status is disabled.
<Operation specifications>
FALSE → TRUE:
Clears and disables the scan list.
This switch clears the scan list and operates the Unit using fixed allocations with the scan list disabled regardless of whether operating using fixed allocations, user-set allocations with device variables for CJ-series Unit, or user-set allocations by CX-Integrator. The fixed allocations area used the last time the scan list was disabled will be used.
FALSE:
Returns to FALSE when the scan list data is cleared and the Unit starts operating with the scan list disabled.
Default: FALSE
<Operation conditions>
• CPU Unit is operating in PROGRAM mode.
• Master function is enabled.
• Scan list status is enabled.
3
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 3-11
3 Data Exchange with the CPU Unit
Name of device variable for
CJ-series Unit
*_Sw1IOCommStartCmd
*_Sw1IOCommStopCmd
Type R/W
BOOL
BOOL
Area Function
RW Remote I/O
Communications
Start Switch
<Operation specifications>
FALSE
→
TRUE:
Starts remote I/O communications.
Note 1 The switch is ignored if remote
I/O communications are already running.
2 This switch resumes remote I/O communications if they are stopped by a communications error.
3 Communications with a slave will fail even if remote I/O communications are started when
*_CnctCmd (Disconnect/Connect Switches) is TRUE (Disconnect).
FALSE:
Returns to FALSE at the start of remote
I/O communications.
RW Remote I/O
Communications
Stop Switch
Note This switch will stop remote I/O communications if DIP switch pin 3 on the front panel (remote I/O communications stop/continue with a communications error) is ON (stop) and there is an ongoing communications or send error.
Default: FALSE
<Operation conditions>
• Master function is enabled.
<Operation specifications>
FALSE → TRUE:
Stops remote I/O communications.
Once remote I/O communications have been stopped, they will remain stopped until the Unit restarts or the remote I/O communications restart (i.e., until the
Remote I/O Communications Start Switch is changed to TRUE).
Note 1 The switch is ignored if remote
I/O communications are already stopped.
2 Message communications will remain enabled even if remote
I/O communications are stopped.
FALSE:
Returns to FALSE when remote I/O communications stop.
Default: FALSE
<Operation conditions>
• Master function is enabled.
3-12 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
3 Data Exchange with the CPU Unit
Name of device variable for
CJ-series Unit
*_Sw1MstrEnblCmd
*_Sw1MstrDsblCmd
Type
BOOL
BOOL
R/W Area Function
RW Master
Enable
Switch
RW Master Disable Switch
<Operation specifications>
FALSE → TRUE:
Enables master communications. (The
Unit automatically restarts.)
Once enabled, the Unit will function as a
Master until *_Sw1MstrDsblCmd (Master
Stop Switch) is changed to TRUE, regardless of whether the power is turned OFF and back ON again.
Note 1 Master communications are enabled by default.
2 If this bit is changed to TRUE with master communications enabled, a Unit status error will occur due to a software switch operation error and a C2 error will be displayed on the front 7-segment indicator. The 7-segment indicator will go out automatically after
30 seconds.
FALSE:
Returns to FALSE at the start of master communications.
Default: FALSE
<Operation conditions>
• CPU Unit is operating in PROGRAM mode.
• Master function is stopped.
<Operation specifications>
FALSE → TRUE:
Stops master communications. (The Unit automatically restarts.)
Set this switch to TRUE if the Unit will be used only for slave communications.
FALSE:
Returns to FALSE after master communications stop.
Default: FALSE
<Operation conditions>
• CPU Unit is operating in PROGRAM mode.
• Master function is enabled.
3
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 3-13
3 Data Exchange with the CPU Unit
Name of device variable for
CJ-series Unit
*_Sw1MstrFixAloc1Cmd
*_Sw1MstrFixAloc2Cmd
*_Sw1MstrFixAloc3Cmd
Type R/W
BOOL
Area
RW Master
Fixed Allocation Setting 1
Switch
BOOL
BOOL
RW Master
Fixed Allocation Setting 2
Switch
RW Master
Fixed Allocation Setting 3
Switch
Function
<Operation specifications>
FALSE
→
TRUE:
Sets the I/O allocation area for when the scan list is disabled to the following words.
(Same as default. The Unit automatically restarts after the setting.)
• OUT area:
CIO 3200 to CIO 3263
(1 word/1 node address (fixed))
• IN area:
CIO 3300 to CIO 3363
(1 word/1 node address (fixed))
Note The I/O words used with the scan list disabled are also used with the scan list enabled. Use
*_Sw1SListEnblCmd (Scan List
Enable Switch).
FALSE:
Returns to FALSE after the fixed allocations areas are set.
Default: FALSE
<Operation conditions>
• CPU Unit is operating in PROGRAM mode.
• Master function is enabled.
• Scan list status is disabled.
Functions the same as
*_Sw1MstrFixAloc1Cmd (Master Fixed
Allocation Setting 1 Switch). Sets the I/O allocation area to the following words.
(The Unit automatically restarts.)
• OUT area:
CIO 3400 to CIO 3463
(1 word/1 node address (fixed))
• IN area:
CIO 3500 to CIO 3563
(1 word/1 node address (fixed))
Functions the same as
*_Sw1MstrFixAloc1Cmd (Master Fixed
Allocation Setting 1 Switch). Sets the I/O allocation area to the following words.
(The Unit automatically restarts.)
• OUT area:
CIO 3600 to CIO 3663
(1 word/1 node address (fixed))
• IN area:
CIO 3700 to CIO 3763
(1 word/1 node address (fixed))
3-14 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
3 Data Exchange with the CPU Unit
Name of device variable for
CJ-series Unit
*_Sw1MstrAlocCmd
Type
BOOL
R/W Area Function
RW Master
User-set
Allocations
Switch
<Operation specifications>
FALSE → TRUE:
Reads setting data from
*_MstrAlocTblCfg[0] to
*_MstrAlocTblCfg[5] (Master User-set
Allocations Setup Table) and registers the scan list. (The Unit automatically restarts.)
Once registered, the Unit will operate with master user-set allocations until the scan list is cleared, regardless of whether the power is turned OFF and back ON again.
FALSE:
Returns to FALSE when the scan list is registered and the Unit starts operating with the scan list enabled.
Note If there is a setting information error, an error code will be stored in
*_MstrAlocTblCfgSta (Setting Results of Master User-set Allocations Setup) and *_Mstr1SListRegErr (Scan List
Register/Clear Failed) will change to
TRUE.
Default: FALSE
<Operation conditions>
• CPU Unit is operating in PROGRAM mode.
• Master function is enabled.
3
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 3-15
3 Data Exchange with the CPU Unit
Name of device variable for
CJ-series Unit
*_Sw1CycleTmTmpSet
Type R/W
BOOL
Area Function
RW Temporary
Setting
Switch for
Communications
Cycle Time
<Operation specifications>
FALSE
→
TRUE:
Reads setting data from
*_CommCycleTmCfg (Communications
Cycle Time Setting) and temporarily changes the communications cycle time.
Use this to temporarily extend the communications cycle time to place priority on message communications.
Note You can change the cycle time in any CPU Unit operating mode.
FALSE:
Returns to FALSE after the communications cycle time is changed.
*_CycleTmRefTblSta[0] to
*_CycleTmRefTblSta[3] (Communications Cycle Time Reference Table) will be cleared before the switch returns to
FALSE if the change was successfully completed.
*_CycleTmRefTblSta[0] to
*_CycleTmRefTblSta[3] ( Communications Cycle Time Reference Table ) will be cleared before the switch returns to
FALSE if the change was successfully completed.
Note *_Mstr1CycleTmSetErr (Communications Cycle Time Setting Failed) will change to TRUE if there is a setting error, and the Communications
Cycle Time Reference Table will not be cleared.
Default: FALSE
3-16 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
3 Data Exchange with the CPU Unit
Name of device variable for
CJ-series Unit
*_Sw1CycleTmSetCmd
*_Sw1CycleTmClrCmd
Type
BOOL
BOOL
R/W Area Function
RW Communications
Cycle Time
Setting
Switch
<Operation specifications>
FALSE → TRUE:
Reads setting data from
*_CommCycleTmCfg (Communications
Cycle Time Setting) to change the communications cycle time and to store the communications cycle time in non-volatile memory in the Unit. The setting will therefore be valid again when the power is turned OFF and back ON, or when the
Unit is restarted.
FALSE:
Returns to FALSE after the communications cycle time is changed.
*_CycleTmRefTblSta[0] to
*_CycleTmRefTblSta[3] (Communications Cycle Time Reference Table) will be cleared before the switch returns to
FALSE if the change was successfully completed.
RW Communications
Cycle Time
Reference
Table Clear
Switch
Note *_Mstr1CycleTmSetErr (Communications Cycle Time Setting Failed) will change to TRUE if there is a setting error. In this case,
*_CycleTmRefTblSta[0] to
*_CycleTmRefTblSta[3] (Communications Cycle Time Reference
Table) will not be cleared.
Default: FALSE
<Operation conditions>
• CPU Unit is operating in PROGRAM mode.
<Operation specifications>
FALSE → TRUE:
Clears data from *_CycleTmRefTblSta[0] to *_CycleTmRefTblSta[3] (Communications Cycle Time Reference Table). The data that is cleared will be updated with new data.
FALSE:
Returns to FALSE after the data from
*_CycleTmRefTblSta[0] to
*_CycleTmRefTblSta[3] (Communications Cycle Time Reference Table) is cleared.
Default: FALSE
3
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 3-17
3 Data Exchange with the CPU Unit
3-2-2 Software Switches 2 (n + 1CH)
Use one of the following device variables for CJ-series Unit to operate Software Switches 2 from the user program:
• WORD-type device variable for CJ-series Unit holding all switch functions contained in Software
Switches 2
• BOOL-type device variable for CJ-series Unit separating functions per each switch contained in Software Switches 2
All switches are set to TRUE by the user. The Unit automatically changes them to FALSE after the function is executed.
Once a function is set by changing the status to TRUE (except for the switches listed below), it is saved regardless of whether the power is turned OFF and back ON again.
• *_Sw2SlavCOSSendCmd (Slave COS Send Switch)
• *_Sw2FileRestoreCmd (Unit Setup File Restore Switch)
• *_Sw2FileBkupCmd (Unit Setup File Backup Switch)
If multiple switches are changed to TRUE simultaneously, all requests will generate errors but they will not alter Unit operation.
The error bits corresponding to the following words will change to TRUE if a request made by a software switch ends in an error.
• *_Slav1Sta (Slave Status 1)
WORD-type device variables for CJ-series Unit holding all switch functions contained in Software
Switches 2 are shown below.
Name of device variable for
CJ-series Unit
*_Sw2Cmd
Type R/W Area
WORD RW Software
Switches 2
Function
Bits 0 to 05: Reserved by system
Bit 06: Slave Enable Switch
Bit 07: Slave Stop Switch
Bit 08: Slave Fixed Allocation Setting 1
Switch
Bit 09: Slave Fixed Allocation Setting 2
Switch
Bit 10: Slave Fixed Allocation Setting 3
Switch
Bit 11: Slave User Allocations Switch
Bit 12: Slave COS Send Switch
Bit 13: Reserved by system
Bit 14: Unit Setup File Restore Switch
Bit 15: Unit Setup File Backup Switch
Default: 16#0000
3-18 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
3 Data Exchange with the CPU Unit
BOOL-type device variables for CJ-series Unit separating functions per each switch contained in Software Switches 2 are shown below.
Name of device variable for
CJ-series Unit
*_Sw2SlavEnblCmd
*_Sw2SlavDsblCmd
Type
BOOL
BOOL
R/W Area Function
RW Slave
Enable
Switch
RW Slave Stop
Switch
<Operation specifications>
FALSE → TRUE:
Enables slave communications. (The Unit automatically restarts.)
To use fixed allocations, set this switch to
TRUE after setting
*_Sw2SlavFixAloc1Cmd to
*_Sw2SlavFixAloc3Cmd (Slave Fixed
Allocation Setting Switch) to TRUE.
To use user-set allocations, set this switch to TRUE after setting *_Sw2SlavAlocCmd
(Slave User Allocations Switch) to TRUE.
Once enabled, the Unit will function as a slave until *_ Sw2SlavDsblCmd (Slave
Stop Switch) is changed to TRUE regardless of whether the power is turned OFF and back ON again.
Note 1 Slave communications are disabled by default.
2 If this bit is changed to TRUE with slave communications enabled, a
Unit status error will occur due to a software switch operation error and a C2 error will be displayed on the front 7-segment indicator.
The 7-segment indicator will go out automatically after 30 seconds.
FALSE:
Returns to FALSE at the start of slave communications.
Default: FALSE
<Operation conditions>
• CPU Unit is operating in PROGRAM mode.
• Slave function is stopped.
<Operation specifications>
FALSE → TRUE:
Stops slave communications. (The Unit automatically restarts.)
Set this switch to TRUE if the Unit will be used only for master communications.
FALSE:
Returns to FALSE after slave communications stop.
Default: FALSE
<Operation conditions>
• CPU Unit is operating in PROGRAM mode.
• Slave function is enabled.
3
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 3-19
3 Data Exchange with the CPU Unit
3-20
Name of device variable for
CJ-series Unit
*_Sw2SlavFixAloc1Cmd
*_Sw2SlavFixAloc2Cmd
*_Sw2SlavFixAloc3Cmd
Type R/W
BOOL
BOOL
BOOL
Area Function
RW Slave Fixed
Allocation
Setting 1
Switch
<Operation specifications>
FALSE
→
TRUE:
Sets the Slave Fixed Allocation Area to the following words.
• OUT 1 area (input to the CPU Unit):
CIO 3370 (1 word allocated)
• IN 1 area (output from the CPU Unit):
CIO 3270 (1 word allocated)
• OUT 2 area: Not used
• IN 2 area: Not used
RW Slave Fixed
Allocation
Setting 2
Switch
RW Slave Fixed
Allocation
Setting 3
Switch
Note 1 Disable slave communications before this switch is changed to
TRUE.
After this switch is changed to
TRUE, change *_Sw2SlavEnblCmd
(Slave Enable Switch) to TRUE to enable Fixed Allocation.
2 This is the default setting for the
Unit.
3 The words allocated by this switch are used as the I/O area for the slave. (Use *_Sw2SlavEnblCmd
(Slave Enable Switch).)
FALSE:
Returns to FALSE after fixed allocations are set.
Default: FALSE
<Operation conditions>
• CPU Unit is operating in PROGRAM mode.
• Slave function is stopped.
Functions the same as
*_Sw2SlavFixAloc1Cmd_DRM2 (Slave
Fixed Allocation Setting 1 Switch).
Sets the Slave Fixed Allocation Area to the following words.
• OUT 1 area (input to the CPU Unit):
CIO 3570 (1 word allocated)
• IN 1 area (output from the CPU Unit):
CIO 3470 (1 word allocated)
• OUT 2 area: Not used
• IN 2 area: Not used
Functions the same as
*_Sw2SlavFixAloc1Cmd_DRM2 (Slave
Fixed Allocation Setting 1 Switch).
Sets the Slave Fixed Allocation Area to the following words.
• OUT 1 area (input to the CPU Unit):
CIO 3770 (1 word allocated)
• IN 1 area (output from the CPU Unit):
CIO 3670 (1 word allocated)
• OUT 2 area: Not used
• IN 2 area: Not used
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
3 Data Exchange with the CPU Unit
Name of device variable for
CJ-series Unit
*_Sw2SlavAlocCmd
*_Sw2SlavCOSSendCmd
Type
BOOL
BOOL
R/W Area Function
RW Slave User
Allocations
Switch
<Operation specifications>
FALSE
→
TRUE:
Reads setting data from
*_SlavAlocTblCfg[0] to
*_SlavAlocTblCfg[5] (Slave User-set Allocations Setup Table) and registers slave user-set allocations. Once registered, the
Unit will operate with slave user-set allocations until slave communications are disabled (Slave Stop Switch is changed to
TRUE), regardless of whether the power is turned OFF and back ON again.
Note Disable slave communications before this switch is changed to
TRUE.
After the switch is changed to TRUE, change *_Sw2SlavEnblCmd (Slave
Enable Switch) to TRUE to enable
User-set Allocations.
FALSE:
Returns to FALSE at the start of operation for slave user-set allocations after they are registered.
RW Slave COS
Send
Switch
Note *_Slav1FunSetErr (Slave Function
Enable/Disable Failed) in Unit Status
2 will change to TRUE if there is a setting error.
Default: FALSE
<Operation conditions>
• CPU Unit is operating in PROGRAM mode.
• Slave function is stopped.
<Operation specifications>
FALSE → TRUE:
Sends COS input data to the master.
FALSE:
Returns to FALSE after transmission is completed regardless of whether it was completed normally or in error.
Default: FALSE
3
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 3-21
3 Data Exchange with the CPU Unit
Name of device variable for
CJ-series Unit
*_Sw2FileRestoreCmd
*_Sw2FileBkupCmd
Type R/W
BOOL
BOOL
Area Function
RW Unit Setup
File Restore
Switch
<Operation specifications>
FALSE → TRUE:
Reads Unit settings (for details on the scan list, communications cycle time settings, etc., refer to
Backup Functions on page 7-2.) from the
file within the SD Memory Card of the
CPU Unit and downloads the data as Unit settings. (The Unit automatically restarts.)
Note After the file data is downloaded, the
Unit automatically restarts with the new data.
FALSE:
Returns to FALSE when the Unit restarts if the data is read properly.
RW Unit Setup
File Backup
Switch
Note *_FileRWErr (File Read/Write Error) will change to TRUE if there is a setup data error or a file read error.
Default: FALSE
<Operation conditions>
• CPU Unit is operating in PROGRAM mode.
<Operation specifications>
FALSE → TRUE:
Writes Unit settings (for details on the scan list, communications cycle time settings, etc., refer to
Backup Functions on page 7-2.) as a file
within the SD Memory Card of the CPU
Unit.
Note Files can only be backed up with the scan list enabled. You cannot make a back-up with the scan list disabled.
FALSE:
Returns to FALSE after the data is written to a file.
Note *_FileRWErr (File Read/Write Error) in Unit Status 2 will change to TRUE if data failed to write to a file.
Default: FALSE
<Operation conditions>
• Scan list status is enabled.*
* When the Master function is enabled, the Unit Setup File cannot be backed up unless the scan list is enabled.
3-22 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
3 Data Exchange with the CPU Unit
3-2-3 Master COS Send Switches
Use one of the following device variables for CJ-series Unit is used to operate Master COS Send
Switches.
• *_MstrCOSSendCmd
LWORD-type device variable for CJ-series Unit that is capable of operating switches for all slaves
(node addresses 0 to 63).
• *_MstrCOSSendNdCmd[0 to 63]
BOOL-type device variable for CJ-series Unit that is capable of operating switches for any slave of node addresses 0 to 63.
Bits 00 to 63 of *_MstrCOSSendCmd (Master COS Send Switch) and array elements of
MstrCOSSendNdCmd[0 to 63] correspond to slaves at node addresses 0 to 63.
If a bit or device variable for CJ-series Unit is changed to TRUE, then COS output data will be sent to the corresponding slave.
You can simultaneously change multiple Master COS Switches to TRUE for multiple slaves. Once COS data are sent to slaves, the corresponding switches will be changed back to FALSE.
If a send error occurs, the bit corresponding to *_Nd0Sta to *_Nd63Sta (Slave Detailed Status) will change to TRUE.
The following device variable for CJ-series Unit is used when you execute functions for multiple slaves at the same time.
Name of device variable for
CJ-series Unit
*_MstrCOSSendCmd
Type R/W Area Function
LWORD RW Master
COS Send
Switch
Executes the operation of Master COS
Send Switches for multiple slaves at the same time.
Bits 0 to 63 correspond to the Master COS
Send Switches for slaves at node addresses 0 to 63.
Data range: 16#0000000000000000 to
FFFFFFFFFFFFFFFF
Default: 16#0000000000000000
The following device variable for CJ-series Unit is used when you execute an individual function for each slave.
Name of device variable for
CJ-series Unit
*_MstrCOSSendNdCmd[0 to 63]
Type
BOOL
R/W Area Function
RW Master
COS Send
Switch for
Node
Address
0-63 Slave
<Operation specifications>
FALSE → TRUE:
Sends COS output data to the corresponding slave.
FALSE:
Returns to FALSE when COS is sent.
Default: FALSE
3
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 3-23
3 Data Exchange with the CPU Unit
3-2-4 Disconnect/Connect Switches
Use one of the following device variables for CJ-series Unit is used to operate Disconnect/Connect
Switches from the user program.
• *_CnctCmd
LWORD-type device variable for CJ-series Unit that is capable of operating switches for all slaves
(node addresses 0 to 63).
• *_CnctNdCmd[0 to 63]
BOOL-type device variable for CJ-series Unit that is capable of operating switches for any slave of node addresses 0 to 63.
Bits 00 to 63 of *_CnctCmd (Disconnect/Connect Switches) and array elements of *_CnctNdCmd[0 to
63] correspond to slaves at node addresses 0 to 63.
If a bit or device variable for CJ-series Unit is changed to TRUE, then the remote I/O communications to the slave will be temporarily stopped (i.e., it is disconnected from the network). A communications error will occur for any slave that is disconnected if the corresponding switch is changed to TRUE during communications.
Disconnect/Connect Switches are used primarily to replace slaves or to reserve a place for a slave that will be added (when a Unit is registered in the scan list but not yet connected). A communications error and verification error for the slave that is disconnected will not be generated at the master as long as the corresponding switch is TRUE.
Remote I/O communications will restart (reconnect) with the corresponding slave if a user returns the
Disconnect/Connect Switches to FALSE.
More than one of these switches may be changed to ON for multiple slaves at the same time. If the switch for a slave that is not using remote I/O communications is set to TRUE, it will be ignored.
A Unit that is disconnected can still perform message communications.
Changing this switch to TRUE does not effect the communications cycle time (except that it increases blank time in the communications cycle).
Note All Disconnect/Connect Switches and device variable for CJ-series Unit are cleared and returned to FALSE when the power is turned OFF. If required, write a user program to turn them back to TRUE when the power is turned ON.
The following device variable for CJ-series Unit is used when you execute the functions for multiple slaves at the same time.
Name of device variable for
CJ-series Unit
*_CnctCmd
Type R/W Area
LWORD RW Disconnect/Connect
Switches
Function
Executes the operation of Disconnect/Connect Switches for multiple slaves at the same time.
Bits 0 to 63 correspond to the Disconnect/Connect Switches for slaves at node addresses 0 to 63.
Default: 16#0000000000000000
3-24 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
3 Data Exchange with the CPU Unit
The following device variable for CJ-series Unit is used when you execute an individual function for each slave.
Name of device variable for
CJ-series Unit
*_CnctNdCmd[0 to 63]
Type
BOOL
R/W Area Function
RW Disconnect/Connect
Switches for
Node
Address
0-63 Slave
<Operation specifications>
TRUE:
Stops remote I/O communications with the corresponding slave.
FALSE:
Starts remote I/O communications with the corresponding slave.
Default: FALSE
3-2-5 Unit Status 1
The following device variable for CJ-series Unit is used to reference all information of Unit Status 1.
Name of device variable for
CJ-series Unit
*_Unit1Sta
Type R/W
WORD R
Area Function
Unit Status
1
Bit 00: Unit Error
Bit 01: Master Function Error
Bit 02: Reserved by system
Bit 03: Slave Function Error
Bit 04: Unit Memory Error
Bit 05: Bus Off Error
Bit 06: Node Address Duplicated Error
Bit 07: Network Power Error
Bit 08: Send Timeout Error
Bit 09: Reserved by system
Bit 10: Reserved by system
Bit 11: Reserved by system
Bit 12: Routing Table Error
Bit 13: Invalid Message Timer List Error
Bit 14: Reserved by system
Bit 15: Reserved by system
Default: 16#0000
3
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 3-25
3 Data Exchange with the CPU Unit
The following device variables for CJ-series Unit are used to reference individual information.
Name of device variables for
CJ-series Unit
*_UnitErr
*_MstrFunErr
Type R/W
BOOL R
Area
Unit Error
BOOL R Master
Function
Error
Function
<Operation specifications>
TRUE:
Displays DeviceNet Unit operating errors.
*_UnitErr (Unit Error) changes to TRUE if any bit from 01 to 15 in *_Unit1Sta (Unit
Status 1) is TRUE (OR information of bits
01 to 15).
Usage example: When you write the program for remote I/O communications, use this bit as an N.C. input condition to control slave I/O processing.
FALSE:
Indicates that the error did not occur. Or, changes to FALSE when the error is cleared.
Default: FALSE
<Operation specifications>
TRUE:
Indicates that at least one master error occurred. Refer to *_Mstr1Sta (Master
Status 1).
The master errors are as follows:
• *_Mstr1VefyErr (Verification Error)
• *_Mstr1StruErr (Structure Error)
• *_Mstr1IOErr (Remote I/O Communication Error)
• *_Mstr1SListErr (Invalid Scan List Data
Error)
• *_Mstr1IORefErr (Master I/O Refresh
Error)
FALSE:
Indicates that none of above errors occured. Or, changes to FALSE when all of above errors are cleared.
Default: FALSE
3-26 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
3 Data Exchange with the CPU Unit
Name of device variable for
CJ-series Unit
*_SlavFunErr
*_MemErr
*_BusoffErr
Type
BOOL
BOOL
BOOL
R/W
R
R
R
Area Function
Slave Function Error
Unit Memory Error
Bus Off
Error
<Operation specifications>
TRUE:
Indicates that at least one slave error occurred. Refer to *_Slav1Sta (Slave Status 1).
The slave errors are as follows:
• *_Slav1IO1Err (Remote I/O Communications Error with slave communications enabled, for OUT 1/IN 1)
• *_Slav1IO2Err (Remote I/O Communications Error with slave communications enabled, for OUT 2/IN 2)
• *_Slav1FunDatErr (Invalid Setup Data)
• *_Slav1IORefErr (Slave I/O Refresh
Error)
FALSE:
Indicates that none of the above errors occured. Or, changes to FALSE when all of above errors are cleared.
Default: FALSE
<Operation specifications>
TRUE:
Indicates an error in internal memory where the error history is stored. (The error occurs when the Unit starts up or when the error history is written.)
FALSE:
Indicates that the error did not occur.
Once this error occurs, the bit will remain
TRUE and will not return to FALSE (Normal).
Default: FALSE
<Operation specifications>
TRUE:
Indicates that a Bus OFF error (communications were stopped by multiple data errors) occurred.
When a Bus OFF occurs, the Unit goes offline and all communications stop
(remote I/O communications are stopped, slave operation is stopped, and message communications are disabled).
FALSE:
Indicates that the error did not occur.
Once this error occurred, the bit will remain TRUE and will not return to FALSE
(Normal).
Default: FALSE
3
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 3-27
3 Data Exchange with the CPU Unit
Name of device variable for
CJ-series Unit
*_NdAdrDupErr
*_NetPwrErr
Type R/W
BOOL R
BOOL R
Area Function
Node
Address
Duplicated
Error
Network
Power Error
<Operation specifications>
TRUE:
Indicates a duplicate node address check error when the Unit starts up.
The Unit goes offline and all communications stop. (Remote I/O communications stop, slave operation stop, and message communications are disabled).
FALSE:
Indicates that the error did not occur.
Once this error occurs, the bit will remain
TRUE and will not return to FALSE (Normal).
Default: FALSE
<Operation specifications>
TRUE:
Indicates that there is no power from the network power supply.
Note Remote I/O communications stop if
DIP switch pin 3 (remote I/O communications stop/continue with a communications error) on the front panel is ON (stop).
FALSE:
Indicates that the error did not occur. Or, changes to FALSE when the network power supply restarts.
Default: FALSE
3-28 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
3 Data Exchange with the CPU Unit
Name of device variable for
CJ-series Unit
*_SendTimeoutErr
*_RTblErr
*_MsgListErr
Type
BOOL
BOOL
BOOL
R/W
R
R
R
Area Function
Send Timeout Error
<Operation specifications>
TRUE:
Indicates that a send timeout occurred due to one of the following factors:
• No slaves present.
• Mismatched baud rate settings.
Routing
Table Error
Invalid Message Timer
List Error
Note Remote I/O communications stop if
DIP switch pin 3 (remote I/O communications stop/continue with a communications error) on the front panel is ON (stop).
FALSE:
Returns to FALSE at the start of communications even with just one slave.
Default: FALSE
<Operation specifications>
TRUE:
Incorrect data in the routing tables set in the CPU Unit.
FALSE:
Indicates that the error did not occur. This error will not occur if a routing table is not set.
Default: FALSE
<Operation specifications>
TRUE:
Indicates that the data in the message monitoring timer list is not correct.
FALSE:
Indicates that the data in the message monitoring timer list is correct.
Changes to FALSE if CX-Integrator registers a message monitoring timer list when the error occurs.
Default: FALSE
3
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 3-29
3 Data Exchange with the CPU Unit
3-2-6 Unit Status 2
The following device variables for CJ-series Unit is used to reference all information of Unit Status 2.
Name of device variable for
CJ-series Unit
*_Unit2Sta
Type R/W
WORD R
Area Function
Unit Status
2
Bit 00: Online Status
Bit 01: Remote I/O Communications Status
Bit 02: Reserved by system
Bit 03: Master Function Enabled Status
Bit 04: Scan List Disabled Status
Bit 05: Reserved by system
Bit 06: Automatic Slave Connection Status
Bit 07: Slave Function Enabled Status
Bit 08: File Read/Write Error
Bit 09: Reserved by system
Bit 10: Reserved by system
Bit 11: Reserved by system
Bit 12: Reserved by system
Bit 13: Reserved by system
Bit 14: Reserved by system
Bit 15: Error History Registered Flag
Default: 16#0000
The following device variables for CJ-series Unit are used to reference individual information.
Name of device variable for
CJ-series Unit
*_OnlineSta
Type R/W
BOOL R
Area Function
Online Status
<Operation specifications>
TRUE:
Indicates that the Unit is online.
Note When the Send Command instruction (SendCmd) is executed from the user program, use _Port_isAvailable
(Communications Port Enabled
Flag) in the CPU Unit and this flag as an AND input condition.
FALSE:
Indicates that the Unit is offline.
A Unit will go offline under the following conditions:
• Operation is stopped by the hardware/software check at startup.
• An error occurred in the duplicate node address check (Refer to *_NdAdrDupErr
(Node Address Duplicated Error)).
• A Bus OFF error occurred (Refer to
*_BusoffErr (Bus Off Error)).
Default: FALSE
3-30 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
3 Data Exchange with the CPU Unit
Name of device variable for
CJ-series Unit
*_IOCommSta
*_MstrEnblSta
*_SListDsblSta
Type
BOOL
BOOL
BOOL
R/W
R
R
R
Area Function
Remote I/O
Communications Status
<Operation specifications>
TRUE:
Indicates that remote I/O communications are being performed for the master function.
Master
Function
Enabled
Status
Scan List
Disabled
Status
Note This variable only indicates the start of remote I/O communications, and does not indicate whether data was actually exchanged with slaves.
Actual data exchange between one or more slaves is monitored from
*_Mstr1IOCommSta_DRM (I/O Data
Communications Status). Therefore use the I/O Data Communications
Status rather than this bit as the input condition in I/O processing for slaves from the program.
FALSE:
Indicates remote I/O communications stopped.
Normally, the Unit will perform remote I/O communications automatically.
Note This bit only indicates the start of remote I/O communications, and does not indicate whether data was actually exchanged with slaves.
Actual data exchange between one or more slaves is monitored from
*_Mstr1IOCommSta (I/O Data Communications Status). Therefore use the I/O Data Communications Status rather than this bit as the input condition in I/O processing for slaves from the program.
Default: FALSE
<Operation specifications>
TRUE:
Indicates that master communications are enabled (Unit is operating as a master).
FALSE:
Indicates that master communications are disabled.
Default: FALSE
<Operation specifications>
TRUE:
Indicates that the Unit is operating with the scan list disabled.
FALSE:
Indicates that the Unit is operating with the scan list enabled.
Default: FALSE
3
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 3-31
3 Data Exchange with the CPU Unit
Name of device variable for
CJ-series Unit
*_SlavConnTypSta
*_SlavEnblSta
*_FileRWErr
*_ErrHistorySta
Type R/W
BOOL R
BOOL
BOOL
BOOL
R
R
R
Area Function
Automatic
Slave Connection
<Operation specifications>
TRUE:
Indicates that the connection type was automatically set in the slave scan list.
This device variable for CJ-series Unit is valid only with slave communications enabled.
FALSE:
Indicates that the connection type was set from CX-Integrator in the slave scan list.
Slave Function
Enabled
File
Read/Write
Error
Error History Registered Flag
Note The type of connection in slave communications cannot be specified without CX-Integrator. If it is not set from CX-Integrator, it will be set automatically.
Default: FALSE
<Operation specifications>
TRUE:
Indicates that slave communications are enabled.
FALSE:
Indicates that slave communications are disabled.
Default: FALSE
<Operation specifications>
TRUE:
Indicates that an error occurred when user setup data is read from a SD Memory
Card in the CPU Unit or when data is written as a file to a SD Memory Card.
FALSE:
Indicates that the error did not occur.
Changes to FALSE when the Unit has successfully completed the operation.
Default: FALSE
<Operation specifications>
TRUE:
Indicates that an error history was registered. Changes to TRUE at the first error history registration for the Unit.
FALSE:
Indicates that no errors are registered in the error history. Changes to FALSE when the Unit receives an error history clear request.
Default: FALSE
3-32 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
3 Data Exchange with the CPU Unit
3-2-7 Master Status 1
The following device variable for CJ-series Unit is used to reference all information of Master Status 1.
Name of device variable for
CJ-series Unit
*_Mstr1Sta
Type R/W
WORD R
Area Function
Master Status 1
Bit 00: Verification Error
Bit 01: Structure Error
Bit 02: Remote I/O Communications Error
Bit 03: Reserved by system
Bit 04: Invalid Scan List Data Error
Bit 05: Master I/O Refresh Error
Bit 06: Reserved by system
Bit 07: Reserved by system
Bit 08: Master Function Enable/Disable
Failed
Bit 09: Master User-set Allocations User
Setting Failed
Bit 10: Master Fixed Allocation Area Setting Failed
Bit 11: Scan List Register/Clear Failed
Bit 12: Communications Cycle Time Setting Failed
Bit 13: Reserved by system
Bit 14: Reserved by system
Bit 15: I/O Data Communications Status
Default: 16#0000
The following device variables for CJ-series Unit are used to reference individual information.
Name of device variable for
CJ-series Unit
*_Mstr1VefyErr
*_Mstr1StruErr
Type
BOOL
BOOL
R/W
R
R
Area Function
Verification
Error
Structure
Error
<Operation specifications>
TRUE:
Indicates that the slave information registered in the scan list is different from the actual slave information. It occurs with the scan list enabled.
FALSE:
Indicates that a verification error did not occur. Or, changes to FALSE when a verification error is cleared.
Default: FALSE
<Operation specifications>
TRUE:
Indicates that I/O allocations cannot be made with the scan list disabled.
FALSE:
Indicates that a structure error did not occur. Or, changes to FALSE when a structure error is cleared.
Default: FALSE
3
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 3-33
3 Data Exchange with the CPU Unit
Name of device variable for
CJ-series Unit
*_Mstr1IOErr
*_Mstr1SListErr
Type R/W
BOOL R
BOOL R
Area Function
Remote I/O
Communications
Error
<Operation specifications>
TRUE:
Indicates that a remote I/O communications timeout occurred during remote I/O communications with slaves.
Invalid Scan
List Data
Error
Note Remote I/O communications stop if
DIP switch pin 3 (remote I/O communications stop/continue with a communications error) on the front panel is ON (stop). This error occurs with the scan list enabled or disabled.
FALSE:
Indicates that a remote I/O communications error did not occur. Or, changes to
FALSE when a remote I/O communications error is cleared.
Default: FALSE
<Operation specifications>
TRUE:
Indicates that there is incorrect data in the scan list (mismatched checksum).
Remote I/O communications in the Unit will stop. (Slave operations and message communications will continue.)
FALSE:
Indicates that the scan list data is correct.
Changes to FALSE when an incorrect scan list data error occurs and then the correct scan list is registered.
Default: FALSE
3-34 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
3 Data Exchange with the CPU Unit
Name of device variable for
CJ-series Unit
*_Mstr1IORefErr
*_Mstr1FunSetErr
*_Mstr1AlocErr
Type
BOOL
BOOL
BOOL
R/W
R
R
R
Area Function
Master I/O
Refresh
Error
Master
Function
Enable/Disable Failed
Master
User-set
Allocations
User Setting Failed
<Operation specifications>
TRUE:
Indicates that the I/O memory in the CPU
Unit that is to be refreshed is not present during I/O refreshing for the master.
FALSE:
Indicates that no master I/O refresh errors occurred.
Default: FALSE
<Operation specifications>
TRUE:
Indicates that an error occurred in the following operations:
• *_Sw1MstrEnblCmd (Master Enable
Switch)
• *_Sw1MstrDsblCmd (Master Stop
Switch)
Once this bit changes to TRUE, it will remain TRUE until the operation is successfully completed.
FALSE:
Indicates that the error did not occur. The bit changes to FALSE when the operation is successfully completed.
Default: FALSE
<Operation specifications>
TRUE:
Indicates that an error occurred in the following operations:
• *_Sw1MstrAlocCmd (Master User-set
Allocations Switch)
Once this bit changes to TRUE, it will remain TRUE until the operation is successfully completed.
Details on the master user-set allocation results are output to MstrAlocTblCfgSta
(Setting Results of Master User-set Allocations Setup).
FALSE:
Indicates that the error did not occur. The bit changes to FALSE when the operation is successfully completed.
Default: FALSE
3
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 3-35
3 Data Exchange with the CPU Unit
Name of device variable for
CJ-series Unit
*_Mstr1FixAlocErr
*_Mstr1SListRegErr
Type R/W
BOOL R
BOOL R
Area Function
Master
Fixed Allocation Area
Setting
Failed
Scan List
Register/
Clear Failed
<Operation specifications>
TRUE:
Indicates that an error occurred in one of the following operations:
• *_Sw1MstrFixAloc1Cmd (Master Fixed
Allocation Setting 1 Switch)
• *_Sw1MstrFixAloc2Cmd (Master Fixed
Allocation Setting 2 Switch)
• *_Sw1MstrFixAloc3Cmd (Master Fixed
Allocation Setting 3 Switch)
Once this bit changes to TRUE, it will remain TRUE until the operation is successfully completed.
FALSE:
Indicates that the error did not occur. The bit changes to FALSE when the operation is successfully completed.
Default: FALSE
<Operation specifications>
TRUE:
Indicates that an error occurred in one of the following operations:
• *_Sw1SListEnblCmd (Scan List Enable
Switch)
• *_Sw1SListClrCmd (Scan List Clear
Switch)
Once this bit changes to TRUE, it will remain TRUE until the operation is successfully completed.
FALSE:
Indicates that the error did not occur. The bit changes to FALSE when the operation is successfully completed.
Default: FALSE
3-36 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
3 Data Exchange with the CPU Unit
Name of device variable for
CJ-series Unit
*_Mstr1CycleTmSetErr
*_Mstr1IOCommSta
Type
BOOL
BOOL
R/W
R
R
Area Function
Communications
Cycle Time
Setting
Failed
I/O Data
Communications Status
<Operation specifications>
TRUE:
Indicates that an error occurred when setting *_Sw1CycleTmTmpSet (Temporary
Setting Switch for Communications Cycle
Time) or *_Sw1CycleTmSetCmd (Communications Cycle Time Setting Switch).
Once this bit changes to TRUE, it will remain TRUE until the operation is successfully completed with the device variable for CJ-series Unit.
FALSE:
Indicates that the error did not occur. The bit changes to FALSE when the operation is successfully completed.
Default: FALSE
<Operation specifications>
TRUE:
Indicates that at least one slave is performing remote I/O communications.
Usage example: When writing the user program for master remote I/O communications, use this bit as an N.O. input condition to control slave I/O processing.
FALSE:
Indicates that remote I/O communications are not conducted with any slaves.
Default: FALSE
3
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 3-37
3 Data Exchange with the CPU Unit
3-2-8 Master Status 2
The following device variables for CJ-series Unit indicate the status of master I/O allocations.
Information of MstrIOAlocSta (Master I/O Allocation Status) can be referenced from *_Mstr2Sta (Master
Status 2).
z
Master I/O Allocation Status Codes and Allocation Statuses
Code
16#00
16#01
16#02
16#03
16#11
16#12
16#13
16#20
16#30
16#80
Details
Unit starting up
Fixed allocation status 1 (with the scan list disabled)
Fixed allocation status 2 (with the scan list disabled)
Fixed allocation status 3 (with the scan list disabled)
Fixed allocation status 1
Fixed allocation status 2
Fixed allocation status 3
User-set allocations set with device variable for CJ-series Unit
User-set allocations set by CX-Integrator
Master function disabled
Name of device variable for
CJ-series Unit
*_ Mstr2Sta
Type R/W
WORD R
Area Function
Master Status 2
Bits 00 to 07: Reserved by system
Bits 08 to 15: Master I/O Allocation Status
Default: 16#0000
Name of device variable for
CJ-series Unit
*_ MstrIOAlocSta
Type R/W
BYTE R
Area
Master I/O
Allocation
Status
Function
Master I/O Allocation Status
Data range: 16#00 to 03, 16#11 to 13,
16#20, 16#30, 16#80
Default: 16#00
3-38 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
3 Data Exchange with the CPU Unit
3-2-9 Slave Status 1
The following device variable for CJ-series Unit is used to reference all information of Slave Status 1.
Name of device variable for
CJ-series Unit
*_Slav1Sta
Type R/W
WORD R
Area
Slave Status 1
Function
Bit 00: Reserved by system
Bit 01: Reserved by system
Bit 02: Remote I/O Communications Error with slave communications enabled, for
OUT 1/IN 1
Bit 03: Remote I/O Communications Error with slave communications enabled, for
OUT 2/IN 2
Bit 04: Invalid Setup Data
Bit 05: Slave Function I/O Refresh Error
Bit 06: Reserved by system
Bit 07: Reserved by system
Bit 08: Slave Function Enable/Disable
Failed
Bit 09: Slave User-set Allocations User
Setting Failed
Bit 10: Slave Fixed Allocation Area Setting
Failed
Bit 11: Slave COS Send Failed
Bit 12: Connection 2 Established
Bit 13: Connection 1 Established
Bit 14: Remote I/O Communications for
OUT 2/IN 2
Bit 15: Remote I/O Communications for
OUT 1/IN 1
Default: 16#0000
The following device variables for CJ-series Unit are used to reference individual information.
Name of device variable for
CJ-series Unit
*_Slav1IO1Err
Type
BOOL
R/W
R
Area Function
Remote I/O
Communications
Error for
OUT 1/IN 1
<Operation specifications>
TRUE:
Indicates that a communications error occurred in the OUT 1/IN 1 slave I/O connection.
FALSE:
Indicates that a remote I/O communications error with slave communications enabled, for OUT 1/IN 1 did not occur. Or changes to FALSE when a remote I/O communications error with slave communications enabled, for OUT 1/IN 1 is cleared.
Default: FALSE
3
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 3-39
3 Data Exchange with the CPU Unit
Name of device variable for
CJ-series Unit
*_Slav1IO2Err
*_Slav1FunDatErr
Type R/W
BOOL R
BOOL R
Area Function
Remote I/O
Communications
Error for
OUT 2/IN 2
Invalid
Setup Data
<Operation specifications>
TRUE:
Indicates that a communications error occurred in the OUT 2/IN 2 Slave I/O connection.
FALSE:
Indicates that a remote I/O communications error with slave communications enabled, for OUT 2/IN 2 did not occur. Or changes to FALSE when a remote I/O communications error with slave communications enabled, for OUT 2/IN 2 is cleared.
Default: FALSE
<Operation specifications>
TRUE:
Indicates that there is incorrect data in slave settings (mismatched checksum).
The Unit stops slave communications.
(Remote I/O communications and message communications continue.)
FALSE:
Indicates that a Unit is operating with the correct slave setting data or without slave communications being set.
Changes to FALSE when the slave is properly set after a slave setup data error occurs.
Default: FALSE
3-40 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
3 Data Exchange with the CPU Unit
Name of device variable for
CJ-series Unit
*_Slav1IORefErr
*_Slav1FunSetErr
*_Slav1AlocErr
Type
BOOL
BOOL
BOOL
R/W
R
R
R
Area Function
Slave I/O
Refresh
Error
Slave
Function
Enable/Disable Failed
Slave Userset Allocations User
Setting
Failed
<Operation specifications>
TRUE:
Indicates that the I/O memory in the CPU
Unit that is to be refreshed is not present during I/O refreshing for the slave function. It occurs in several situations, such as when an I/O area is allocated in an EM bank that is not present.
FALSE:
Indicates that a slave I/O refresh error did not occur.
Default: FALSE
<Operation specifications>
TRUE:
Indicates that an error occurred in one of the following operations:
• *_Sw2SlavEnblCmd (Slave Enable
Switch)
• *_Sw2SlavDsblCmd (Slave Stop
Switch)
Once this bit changes to TRUE, it will remain TRUE until the operation is successfully completed.
FALSE:
Indicates that the error did not occur. The bit changes to FALSE when the operation is successfully completed.
Default: FALSE
<Operation specifications>
TRUE:
Indicates that an error occurred in the following operations:
• *_Sw2SlavAlocCmd (Slave User Allocations Switch)
Once this bit changes to TRUE, it will remain TRUE until the operation is successfully completed.
FALSE:
Indicates that the error did not occur. The bit changes to FALSE when the operation is successfully completed.
Default: FALSE
3
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 3-41
3 Data Exchange with the CPU Unit
Name of device variable for
CJ-series Unit
*_Slav1FixAlocErr
Type R/W
BOOL R
Area Function
Slave Fixed
Allocation
Area Setting Failed
<Operation specifications>
TRUE:
Indicates that an error occurred in one of the following operations:
• *_Sw2SlavFixAloc1Cmd (Slave Fixed
Allocation Setting 1 Switch)
• *_Sw2SlavFixAloc2Cmd (Slave Fixed
Allocation Setting 2 Switch)
• *_Sw2SlavFixAloc3Cmd (Slave Fixed
Allocation Setting 3 Switch)
Once this bit changes to TRUE, it will remain TRUE until the operation is successfully completed.
FALSE:
Indicates that the error did not occur. The bit changes to FALSE when the operation is successfully completed.
Default: FALSE
3-42 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
3 Data Exchange with the CPU Unit
Name of device variable for
CJ-series Unit
*_Slav1COSSendErr
*_Slav1Conn2EstbSta
*_Slav1Conn1EstbSta
Type
BOOL
BOOL
BOOL
R/W
R
R
R
Area Function
COS Send
Failed
Connection
2 Established
Connection
1 Established
<Operation specifications>
TRUE:
Indicates that an attempt was made to send COS to a master using
*_Sw2SlavCOSSendCmd (Slave COS
Send Switch), but the transmission failed.
The following may cause the failure of
COS signal transmission:
• A COS connection was not established with a master.
• Bus OFF error occurred.
• A network power error occurred.
• A send timeout occurred.
Once this bit changes to TRUE, it will remain TRUE until the operation is successfully completed.
FALSE:
Indicates that the error did not occur. The bit changes to FALSE when COS is successfully sent.
Default: FALSE
<Operation specifications>
TRUE:
Indicates that an I/O connection is established for OUT 2/IN 2. This bit changes to
TRUE even if valid I/O data is not exchanged.
FALSE:
Indicates that an I/O connection is not established for OUT 2/IN 2.
Default: FALSE
<Operation specifications>
TRUE:
Indicates that an I/O connection is established for OUT 1/IN 1. This bit changes to
TRUE even if valid I/O data is not exchanged.
FALSE:
Indicates that an I/O connection is not established for OUT 1/IN 1.
Default: FALSE
3
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 3-43
3 Data Exchange with the CPU Unit
Name of device variable for
CJ-series Unit
*_Slav1IO2CommSta
*_Slav1IO1CommSta
Type R/W
BOOL R
BOOL R
Area Function
Remote I/O
Communications for
OUT 2/IN 2
Remote I/O
Communications for
OUT 1/IN 1
<Operation specifications>
TRUE:
Indicates that an I/O connection is established for OUT 2/IN 2 and the slave is conducting normal remote I/O communications with the master.
FALSE:
Indicates that an I/O connection is not established for OUT 2/IN 2 and the slave is not conducting normal remote I/O communications with the master.
Usage example: When writing the user program for slave remote I/O communications, use this bit as an N.O. input condition to control I/O processing with the master.
Default: FALSE
<Operation specifications>
TRUE:
Indicates that an I/O connection is established for OUT 1/IN 1 and the slave is conducting normal remote I/O communications with the master.
FALSE:
Indicates that an I/O connection is not established for OUT 1/IN 1 and the slave is not conducting normal remote I/O communications with the master.
Usage example: When writing the user program for slave remote I/O communications, use this bit as an N.O. input condition to control I/O processing with the master.
Default: FALSE
3-44 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
3 Data Exchange with the CPU Unit
3-2-10 Slave Status 2
*_Slav2Sta (Slave Status 2) is used to reference 2 types of information: Master Node Address and
Slave I/O Allocation Status.
Use *_MstrNdAdrSta (Node Address of The Remote Master for Slave Communications) and
*_SlavIOAlocSta (Slave I/O Allocation Status) to reference individual information.
z
*_MstrNdAdrSta (Node Address of The Remote Master for Slave
Communications)
This indicates the node address of the remote master for slave communications.
This information is valid when *_Slav1IO2CommSta (Remote I/O Communications for OUT 2/IN 2) and *_Slav1IO1CommSta (Remote I/O Communications for OUT 1/IN 1) are TRUE in Slave Status
1.
z
*_SlavIOAlocSta (Slave I/O Allocation Status)
This indicates the I/O allocation status of the slave.
Code
16#00
16#01
16#02
16#03
16#20
16#30
16#80
Details
Unit starting up
Fixed allocation status 1
Fixed allocation status 2
Fixed allocation status 3
User-set allocations with set device variable for CJ-series Unit
User-set allocations set by CX-Integrator
Slave function disabled
3
Name of device variable for
CJ-series Unit
*_Slav2Sta
*_MstrNdAdrSta
*_SlavIOAlocSta
Type R/W
WORD R
USINT
BYTE
R
R
Area Function
Slave Status 2
Node
Address of
The
Remote
Master for
Slave Communications
Slave I/O
Allocation
Status
Bits 00 to 07: Master Node Address
Bits 08 to 15: Slave I/O Allocation Status
Default: 16#0000
This indicates the node address of the remote master for slave communications.
Data range: 0 to 63
Default: 0
This indicates the I/O allocation status of the slave.
Data range: 16#00 to 03, 16#20, 16#30,
16#80
Default: 16#00
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 3-45
3 Data Exchange with the CPU Unit
3-2-11 Registered Slave Table
This table indicates the slaves that are registered in the master scan list.
Bits 00 to 63 of LWORD-type device variable for CJ-series Unit *_RegSlavTblSta correspond to slaves at node addresses 0 to 63.
This table is updated when the Unit starts up and when a scan list is registered.
Use the following device variables for CJ-series Unit to reference all information of the Registered Slave
Table.
Name of device variables for
CJ-series Unit
*_RegSlavTblSta
Type R/W
LWORD R
Area Function
Registered
Slave Table
You can reference information concerning all slaves in the Registered Slave Table.
Bits 00 to 63 correspond to information for slaves at node addresses 0 to 63.
Data range: 16#0000000000000000 to
FFFFFFFFFFFFFFFF
Default: 16#0000000000000000
The following device variable for CJ-series Unit is used to reference individual slave information.
Name of device variables for
CJ-series Unit
*_RegSlavTblNdSta[0 to 63]
Type R/W
BOOL R
Area Function
Registered
Slave Table
Corresponding to
Node
Addresses
0 to 63
<Operation specifications>
TRUE:
• With the scan list disabled:
Indicates slaves to which a connection is established at least once. When you register the scan list, slaves in which the bit is TRUE in this table are registered.
• With the scan list enabled:
Indicates that a slave is registered in the scan list.
FALSE:
Indicates that a slave is not registered in the scan list.
Default: FALSE
3-46 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
3 Data Exchange with the CPU Unit
3-2-12 Normal Slave Table
This table indicates the slaves that are communicating normally with the master. Bits 00 to 63 of
LWORD-type device variable for CJ-series Unit *_NormSlavTblSta correspond to slaves at node addresses 0 to 63.
For all set I/O connections, the bits corresponding to slaves that successfully established connection will be TRUE.
If connection is not yet established due to a network error, etc., the applicable slave bit turns FALSE.
These are not flags to show the remote I/O communications status.
This table is updated continuously.
However, in the case of a communications power supply error, Send Timeout Error or remote I/O communications stopped (including remote I/O communications stopped due to a communications error), all bits turn FALSE.
The following device variable for CJ-series Unit is used to reference all information of the Normal Slave
Table.
Name of device variable for
CJ-series Unit
*_NormSlavTblSta
Type R/W
LWORD R
Area Function
Normal
Slave Table
You can reference information concerning all slaves in the Normal Slave Table.
Bits 00 to 63 correspond to information for slaves at node addresses 0 to 63.
Data range: 16#0000000000000000 to
FFFFFFFFFFFFFFFF
Default: 16#0000000000000000
The following device variable for CJ-series Unit is used to reference individual slave information.
Name of device variable for
CJ-series Unit
*_NormSlavTblNdSta[0 to 63]
Type
BOOL
R/W
R
Area Function
Normal
Slave Table
Corresponding to
Node
Addresses
0 to 63
Slave
TRUE:
Indicates normal connection.
FALSE:
Indicates that not all connections are made.
Default: FALSE
3
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 3-47
3 Data Exchange with the CPU Unit
3-2-13 C200H Master Replacement Master Status 1
To simplify changes to user programs for a C200H DeviceNet Master Unit (C200HW-DRM21-V1),
C200H Master Replacement Master Status 1, which has the same bit configuration as Master Status
Area 1, is provided for this Unit.
The following device variable for CJ-series Unit is used to execute all functions of C200H Master
Replacement Master Status 1.
Name of device variable for
CJ-series Unit
*_CMstrSta
Type R/W
WORD R
Area Function
C200H
Master
Replacement Master Status 1
Bit 00: Unit Memory Error
Bit 01: Node Address Duplicated/Bus Off
Error
Bit 02: Reserved by system
Bit 03: Configuration Error
Bit 04: Structure Error
Bit 05: Send Error
Bit 06: Communication Error
Bit 07: Verification Error
Bit 08: I/O Data Communications Not Running Status
Bit 09: Reserved by system
Bit 10: Reserved by system
Bit 11: Reserved by system
Bit 12: Message Communications Permitted
Bit 13: Invalid Scan List Data Flag
Bit 14: Master Error
Bit 15: I/O Data Communications
Default: 16#0000
The following device variables for CJ-series Unit are used to execute individual functions.
Name of device variable for
CJ-series Unit
*_CMstrMemErr
*_CMstrNdDupErr
Type R/W
BOOL R
BOOL R
Area
Unit Memory Error
Node
Address
Duplicated/Bus
Off Error
Function
This is the same as *_MemErr (Unit Memory Error).
Default: FALSE
This bit changes to TRUE if any of the following device variables for CJ-series Unit is TRUE:
• *_NdAdrDupErr (Node Address Duplicated Error)
• *_BusoffErr (Bus Off Error)
Default: FALSE
3-48 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
3 Data Exchange with the CPU Unit
Name of device variable for
CJ-series Unit
*_CMstrCfgErr
*_CMstrStruErr
*_CMstrSendErr
*_CMstrIOErr
*_CMstrVefyErr
*_CMstrIOStopSta
*_CMstrMsgEnblSta
Type
BOOL
BOOL
BOOL
BOOL
BOOL
BOOL
BOOL
R/W
R
R
R
R
R
R
R
Area Function
Configuration Error
Structure
Error
This bit changes to TRUE if any of the following device variables for CJ-series Unit is TRUE:
• *_RTblErr (Routing Table Error)
• *_MsgListErr (Invalid Message Timer
List Error)
• *_Mstr1SListErr (Invalid Scan List Data
Error)
• *_Mstr1IORefErr (Master I/O Refresh
Error)
Default: FALSE
This is the same as *_Mstr1StruErr (Structure Error).
Default: FALSE
Send Error This bit changes to TRUE if any of the following device variables for CJ-series Unit is TRUE:
• *_NetPwrErr (Network Power Error)
• *_SendTimeoutErr (Send Timeout
Error)
Default: FALSE
Communication Error
Verification
Error
This is the same as *_Mstr1IOErr
(Remote I/O Communication Error).
Default: FALSE
This is the same as *_Mstr1VefyErr (Verification Error).
Default: FALSE
I/O Data
Communications Not
Running
Status
This operates in the reverse way of
*_IOCommSta (Remote I/O Communications Status).
Default: FALSE
Message
Communications Permitted
This is the same as *_OnlineSta (Online
Status).
Note When you execute the Send Command instruction (SendCmd) from a program, use _Port.isAvailable
(Network Communications Enabled
Flag) in the CPU Unit and this flag as an AND input condition.
Default: FALSE
3
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 3-49
3 Data Exchange with the CPU Unit
Name of device variable for
CJ-series Unit
*_CMstrSListDsblSta
*_CMstrErr
*_MstrIOCommSta
Type R/W
BOOL R
BOOL
BOOL
R
R
Area Function
Invalid Scan
List Data
Flag
Master
Error
Remote I/O
Data Communications Flag
This is the same as *_SListDsblSta (Scan
List Disable Status).
Default: FALSE
This bit changes to TRUE if bits 0, 1, or 3 to 7 of *_CMstrSta (C200H Master
Replacement Master Status 1) is TRUE.
Default: FALSE
This is the same as *_Mstr1IOCommSta
(I/O Data Communications Status).
Default: FALSE
3-50 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
3 Data Exchange with the CPU Unit
3-3 Device Variables for CJ-series Unit
(Allocations Setting Table, Slave
Detailed Status)
The following device variables for CJ-series Unit are used to set Allocations Setting Tables, reference setup statuses and reference detailed statuses of slaves.
*_CommCycleTmCfg
*_MstrAlocTblCfg[0 to 5]
*_MstrAlocTblCfgSta
*_SlavAlocTblCfg[0 to 5]
*_ SlavAlocTblCfgSta
*_CycleTmRefTblSta[0 to 3]
*_MstrAlocRefTblSta[0 to 11]
*_SlavAlocRefTblSta[0 to 11]
*_Nd0Sta to *_Nd63Sta
UINT
UINT
RW Communications Cycle Time Setting
RW Master User-set Allocations Setup Table
WORD R
UINT RW
Setting Results of Master User-set Allocations Setup
Slave User-set Allocations Setup Table
WORD R
UINT R
UINT
UINT
BYTE R
R
R
Setting Results of Slave User-set Allocations Setup
Communications Cycle Time Reference Table
Master User-set Allocations Reference Table
Slave User-set Allocations Reference Table
Detailed Slave Status Table for Node Addresses 0 to
63
You can use one of the following methods to set the Communications Cycle Time Setting, Master Userset Allocations Setup Table, Slave User-Set Allocations Setup Table.
1. Use Special Unit Setup Editing screen of Sysmac Studio.
2. Use a user program.
If it is necessary to change the System Setting while the user program is being executed, use the user program to change the System Setting.
3
3-3-1 Communications Cycle Time Setting
This sets the communications cycle time for the master using *_CommCycleTmCfg .
You can update the standard communications cycle time with *_Sw1CycleTmTmpSet (Temporary
Setting Switch for Communications Cycle Time) and *_Sw1CycleTmSetCmd (Communications Cycle
Time Setting Switch). For details on these switches, refer to
of
Variables for CJ-series Unit (Software Switches, Statuses) .
Name of device variable for
CJ-series Unit
*_CommCycleTmCfg
Type
UINT
R/W Area Function
RW Communications
Cycle Time
Setting
Sets the communications cycle time in milliseconds. If this bit is set to FALSE, the optimum time calculated by the Unit will be used. If a value higher than 500 ms is set, the Unit will operate at 500 ms.
If the setting cannot be correctly made for some reason, *_Mstr1CycleTmSetErr
(Communications Cycle Time Setting
Failed) in Master Status 1 is changed to
TRUE, and *_Sw1CycleTmTmpSet (Temporary Setting Switch for Communications
Cycle Time) and *_Sw1CycleTmSetCmd return to FALSE.
Data range: 0 to 500
Default: 0
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 3-51
3 Data Exchange with the CPU Unit
Additional Information
The Unit calculates the optimum communications cycle time and stores it internally. If a value smaller than that is set, then the value calculated by the Unit will be used.
3-52 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
3 Data Exchange with the CPU Unit
3-3-2 Master User-set Allocations Setup Table
Use device variables for CJ-series Unit to specify the I/O words for Master User-set Allocations. You can only set OUT block 1 and IN block 1 with this table.
Additional Information
OUT blocks 1 and 2 and IN block 1 and 2 can be set from CX-Integrator.
You can update I/O allocations in the master by setting this table and changing *_Sw1MstrAlocCmd
(Master User-set Allocations Switch) to TRUE. The Unit restarts automatically and starts operating with the scan list enabled.
Name of device variable for
CJ-series Unit
*_MstrAlocTblCfg[0]
*_MstrAlocTblCfg[1]
*_MstrAlocTblCfg[2]
*_MstrAlocTblCfg[3]
*_MstrAlocTblCfg[4]
*_MstrAlocTblCfg[5]
*_MstrAlocTblCfgSta
Type R/W Area Function
UINT
UINT
UINT
UINT
UINT
RW
RW
RW
RW
RW
OUT block
1 area
First word in
OUT block
1
IN block 1 area
First word in
IN block 1
Allocation size setup table area
UINT RW First word in the allocation size setup table
1*.
WORD R Setting
Results of
Master
User-set
Allocations
Setup
Specifies the OUT 1 block area.
Data range: 0 to 20
Default: 0
Specifies the first word for the OUT 1 block.
Data range: 0 to 32767
Default: 0
Specifies the IN 1 block area.
Data range: 0 to 20
Default: 0
Specifies the first word for the IN 1 block.
Data range: 0 to 32767
Default: 0
Specifies the area for the allocation size setup table.
Data range: 0 to 20
Default: 0
Specifies the first word in the allocation size setup table (l).
Data range: 0 to 32767
Default: 0
Stores the Setting Results of Master Userset Allocations Setup.
Data range: 16#0000 to FFFF
Default: 16#0000
* For details on the first word in the allocation size setup table l, refer to
Allocation Size Setup Table (page 3-55).
3
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 3-53
3 Data Exchange with the CPU Unit z
Areas and Word Ranges
Code
0
1
3
4
5
8 to 20
Area name in memory for CJ-series Unit
---
CIO Area (CIO)
Data Memory (DM)
Work Area (WR)
Holding Area (HR)
Expansion Data Memory (EM)
Bank 0 to bank C (13 banks)
Word range
The block is not allocated.
0 to 6143
0 to 32767
0 to 511
0 to 511
0 to 32767
(E0_00000 to E0_32767, ⋅⋅⋅ , EC_00000 to
EC_32767) for all banks
Note You cannot use Holding Area H512 and its subsequent holding areas, or EM Area Bank D and its subsequent banks.
z
Master User Allocations Table Setting Results
Code
16#0000
16#1101
16#1103
16#110C
16#1104
16#2201
16#2211
16#2606
Description
Completed normally
No area
Address range specification error
Parameter error
Address range overflow
Wrong operating mode
Unit busy
Cannot execute service
Details
---
• Incorrect area setting.
• The allocated size in the allocation size setup table is 0.
The first word is outside the setting range.
• The OUT or IN size in the allocation size setup table exceeds 200 bytes.
• Both the OUT and IN blocks are set for no allocations.
• No slaves are allocated.
• The block or the allocation size setup table exceeds the valid word range.
• The block is larger than 1,000 bytes.
The CPU Unit is not in PROGRAM mode.
Service cannot be executed because the Unit is busy.
The Unit master communications are not disabled.
Make sure the CPU Unit is in PROGRAM mode and the master function is enabled before you set these values.
3-54 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
3 Data Exchange with the CPU Unit
Allocation Size Setup Table
Set the following allocation size setup tables in the memory used for CJ-series Units of the CPU Unit to use the Master User-set Allocations Setup Table.
The number of bytes set in the allocation size setup table are allocated in word units in order of node addresses for OUT block 1 and then IN block 1. Set the sizes within a range from 0 to 200 bytes (100 words).
To set the tables shown below from the user program, allocate user-defined variables in the following areas.
For details on allocating user-defined variables, refer to Sysmac Studio Version 1 Operation Manual
(Cat. No. W504).
Word
I
B i t 1 5 B i t 0 8 B i t 0 7
Node address 0 OUT size (bytes) Node address 0 IN size (bytes)
B i t 0 0
I+1 Node address 1 OUT size (bytes) Node address 1 IN size (bytes)
:
:
I+63 Node address 63 OUT size (bytes) Node address 63 IN size (bytes)
3
Additional Information
The areas and first word in the memory used for CJ-series Unit used for setting up the allocation size setup table are set by using the following device variable for CJ-series Unit.
Allocation Size Setup Table Area *_MstrAlocTblCfg[4]
First Word In The Allocation Size Setup Table 1 *_MstrAlocTblCfg[5]
Setting Example
The following example shows the allocation when the size (bytes) for OUT block 1 and IN block 1 is set in the allocation size setup table using the specified values.
Node address 0: OUT size: 1 byte, IN size: 5 bytes
Node address 1: OUT size: 4 byte, IN size: 3 bytes
Node address 2: OUT size: 1 byte, IN size: 2 bytes
Allocation size setup table
1 5
4 3 s s+1
15 OUT block 1
Not usable 00
01 01
00 k k+1
15
00
00
IN block 1
00
00
00
I
I+1
I+2 1 2 s+2 01 01 k+2 Not usable 00
: : s+3 Not usable 02 k+3 01 01
: : k+4 Not usable 01 k+5 02 02 l: First word in allocation size setup table s: First word in OUT block 1 k: First word in IN block 1
: :
Note 1 The numbers in the OUT 1 and IN 1 blocks represent node addresses.
2 Bytes are allocated in the blocks in word units in the order of node addresses. If the allocated size is 1 byte, the rightmost byte is used, but the leftmost byte cannot be used.
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 3-55
3 Data Exchange with the CPU Unit
3-3-3 Slave User-set Allocations Setup Table
The I/O areas in the Memory for CJ-series Units specified here for the slave OUT 1 area and slave IN 1 area are used if the slave function is enabled with *_Sw2SlavAlocCmd (Slave User Allocations Switch).
You can update I/O allocations for the slaves by setting this table and changing *_Sw2SlavAlocCmd
(Slave User Allocations Switch) to TRUE. The Unit restarts automatically and starts operating with the scan list enabled.
Name of device variable for
CJ-series Unit
*_SlavAlocTblCfg[0]
*_SlavAlocTblCfg[1]
*_SlavAlocTblCfg[2]
*_SlavAlocTblCfg[3]
*_SlavAlocTblCfg[4]
*_SlavAlocTblCfg[5]
*_SlavAlocTblCfgSta
Type R/W Area Function
UINT
UINT
UINT
UINT
UINT
UINT
WORD
RW
RW
RW
R
Slave OUT
1 area
RW First word in
Slave OUT
1 area
RW OUT 1 area size
Slave IN 1 area
RW First word in
Slave IN 1 area
IN 1 area size
Setting
Results of
Slave Userset Allocations Setup
Specifies the OUT 1 area.
Data range: 0 to 20
Default: 0
Specifies the first word in the OUT 1 area.
Data range: 0 to 32767
Default: 0
Specifies the size of the OUT 1 area. Unit is in bytes.
The OUT 1 area is not allocated when the value is 0.
Possible range of variables: 0 to 200
Default: 0
Specifies the IN 1 area.
Data range: 0 to 20
Default: 0
Specifies the first word in the IN 1 area.
Data range: 0 to 32767
Default: 0
Specifies the size of the IN 1 Area. Unit is in bytes.
The IN 1 Area is not allocated when the value is 0.
Data range: 0 to 200
Default: 0
Stores the Setting Results of Slave Userset Allocations Setup.
Data range: 16#0000 to FFFF
Default: 16#0000 z
Areas and Word Ranges
Code
0
1
3
4
5
8 to 20
Area name in memory for CJ-series Unit
---
CIO Area (CIO)
Data Memory (DM)
Work Area (WR)
Holding Area (HR)
Expansion Data Memory (EM)
Bank 0 to bank C (13 banks)
Word range
The area is not used.
0 to 6143
0 to 32767
0 to 511
0 to 511
0 to 32767 (E0_00000 to E0_32767, ...,
EC_00000 to EC_32767) for all banks
3-56 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
3 Data Exchange with the CPU Unit
Note You cannot use Holding Area H512 and its subsequent holding areas, or EM Area Bank D and its subsequent banks.
z
Slave User-set Allocations Setup Table Setting Results
Code
16#0000
16#1101
16#1103
16#110C
16#1104
16#2201
16#2211
16#2606
Description
Completed normally
No area
Address range specification error
Parameter error
Address range overflow
Wrong operating mode
Unit busy
Cannot execute service
Details
---
Incorrect area setting.
The first word is outside the setting range.
• The OUT 1 or IN 1 area size exceeds 200 bytes.
• The OUT 1 and IN 1 area sizes are 0.
• Neither the OUT 1 area nor IN 1 area is set for allocation.
The allocated area exceeds the valid word range.
The CPU Unit is not in PROGRAM mode.
Service cannot be executed because the Unit is busy.
The Unit slave communications are not disabled.
3
Precautions for Safe Use
Make sure the CPU Unit is in PROGRAM mode and the Unit has stopped slave communications before you set these values.
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 3-57
3 Data Exchange with the CPU Unit
3-3-4 Communications Cycle Time Reference Table
You can use this table to store the present, maximum and minimum communications cycle times in milliseconds.
All the values in this table are cleared from the Unit and the maximum and minimum values are updated with new values of when *_Sw1CycleTmClrCmd (Communications Cycle Time Reference Table Clear
Switch) is changed to TRUE.
In the case of automatic setting (default), the communications cycle time setting value is set to 0.
Name of device variable for
CJ-series Unit
*_CycleTmRefTblSta[0]
*_CycleTmRefTblSta[1]
*_CycleTmRefTblSta[2]
*_CycleTmRefTblSta[3]
Type R/W
UINT R
UINT
UINT
UINT
R
R
R
Area
Communications cycle time setting value
Communications cycle time present value
Communications cycle time maximum value
Communications cycle time minimum value
Function
Indicates the the set value of communications cycle time.
Data range: 0 to 500
Default: 0
Indicates the present value of communications cycle time.
Data range: 0 to 65535
Default: 0
Indicates the maximum value of communications cycle time.
Data range: 0 to 65535
Default: 0
Indicates the minimum value of communications cycle time.
Data range: 0 to 65535
Default: 0
3-3-5 Master User-set Allocations Reference Table
You can access the settings (area and size) for a maximum of four blocks (OUT block 1, OUT block 2,
IN block 1, and IN block 2) in the Master User-set Allocations Reference Table.
The OUT 1 and IN 1 block settings can be referenced if CX-Integrator is not being used.
Name of device variable for
CJ-series Unit
*_MstrAlocRefTblSta[0]
*_MstrAlocRefTblSta[1]
*_MstrAlocRefTblSta[2]
*_MstrAlocRefTblSta[3]
Type R/W
UINT R
UINT
UINT
UINT
R
R
R
Area Function
OUT block
1 area
First word in
OUT block
1
No. of bytes in OUT block 1
IN block 1 area
Stores the OUT 1 area.
Data range: 0 to 20
Default: 0
Stores the first word for OUT 1 area.
Data range: 0 to 32767
Default: 0
Stores the size of OUT 1 area.
The OUT 1 block is not allocated if the value is 0.
Data range: 0 to 1000
Default: 0
Stores the IN 1 area.
Data range: 0 to 20
Default: 0
3-58 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
3 Data Exchange with the CPU Unit
Name of device variable for
CJ-series Unit
*_MstrAlocRefTblSta[4]
*_MstrAlocRefTblSta[5]
*_MstrAlocRefTblSta[6]
*_MstrAlocRefTblSta[7]
*_MstrAlocRefTblSta[8]
*_MstrAlocRefTblSta[9]
*_MstrAlocRefTblSta[10]
*_MstrAlocRefTblSta[11]
Type
UINT
UINT
UINT
UINT
UINT
UINT
UINT
UINT
R/W
R
R
R
R
R
R
R
R
Area Function
First word in
IN block 1
No. of bytes in IN block 1
OUT block
2 area
First word in
OUT block
2
No. of bytes in OUT block 2
IN block 2 area
First word in
IN block 2
No. of bytes in IN block 2
Stores the first word for IN 1 area.
Data range: 0 to 32767
Default: 0
Stores the size of IN 1 area.
The OUT 1 block is not allocated if the value is 0.
Data range: 0 to 1000
Default: 0
Stores the OUT 2 area.
Data range: 0 to 20
Default: 0
Stores the first word for OUT 2 area.
Data range: 0 to 32767
Default: 0
Stores the size of OUT 2 area.
The OUT 1 block is not allocated if the value is 00 hex.
Data range: 0 to 1000
Default: 0
Stores the IN 2 area.
Data range: 0 to 20
Default: 0
Stores the first word for IN 2 area.
Data range: 0 to 32767
Default: 0
Stores the size of IN 2 area.
The OUT 1 block is not allocated if the value is 0.
Data range: 0 to 1000
Default: 0 z
Areas and Word Ranges
Code
0
1
3
4
5
8 to 20
Area name in memory for CJ-series Units
---
CIO Area (CIO)
Data Memory (DM)
Work Area (WR)
Holding Relay (HR)
Expansion Data Memory (EM)
Bank 0 to bank C (13 banks)
Word range
The block is not used.
0 to 6143
0 to 32767
0 to 511
0 to 511
0 to 32767 (E0_00000 to E0_32767, ...,
EC_00000 to EC_32767) for all banks
Note You cannot use Holding Area H512 and its subsequent holding areas, or EM Area Bank D and its subsequent banks.
3
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 3-59
3 Data Exchange with the CPU Unit
3-3-6 Slave User-set Allocations Reference Table
You can access the slave block settings in the Slave User-set Allocations Reference Table. You can use a maximum of two OUT and two IN areas (OUT 1, IN 1, OUT 2, and IN 2 areas) for slave communications and you can access their area and size in the table.
The OUT 1 and IN 1 areas and their sizes can be referenced if CX-Integrator is not being used.
Name of device variable for
CJ-series Unit
*_SlavAlocRefTblSta[0]
*_SlavAlocRefTblSta[1]
*_SlavAlocRefTblSta[2]
*_SlavAlocRefTblSta[3]
*_SlavAlocRefTblSta[4]
*_SlavAlocRefTblSta[5]
*_SlavAlocRefTblSta[6]
*_SlavAlocRefTblSta[7]
*_SlavAlocRefTblSta[8]
*_SlavAlocRefTblSta[9]
*_SlavAlocRefTblSta[10]
Type R/W
UINT R
UINT
UINT
UINT
UINT
UINT
UINT
UINT
UINT
UINT
UINT
R
R
R
R
R
R
R
R
R
R
Area Function
Slave OUT
1 area
First word in
Slave OUT
1 area
Slave OUT
1 area size
Slave IN 1 area
First word in
Slave IN 1 area
Slave IN 1 area size
Slave OUT
2 area
First word in
Slave OUT
2 area
Slave OUT
2 area size
Slave IN 2 area
First word in
Slave IN 2 area
Stores the OUT 1 area.
Data range: 0 to 20
Default: 0
Stores the first word for OUT 1 area.
Data range: 0 to 32767
Default: 0
Stores the size of OUT 1 area.
The OUT 1 block is not allocated if the value is 0.
Data range: 0 to 200
Default: 0
Stores the IN 1 area.
Data range: 0 to 20
Default: 0
Stores the first word for IN 1 area.
Data range: 0 to 32767
Default: 0
Stores the first word for IN 1 area.
The OUT 1 block is not allocated if the value is 0.
Data range: 0 to 200
Default: 0
Stores the OUT 2 area.
Data range: 0 to 20
Default: 0
Stores the first word for OUT 2 area.
Data range: 0 to 32767
Default: 0
Stores the size of OUT 2 area.
The OUT 1 block is not allocated if the value is 0.
Data range: 0 to 200
Default: 0
Stores the IN 2 area.
Data range: 0 to 20
Default: 0
Stores the first word for IN 2 area.
Data range: 0 to 32767
Default: 0
3-60 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
3 Data Exchange with the CPU Unit
Name of device variable for
CJ-series Unit
*_SlavAlocRefTblSta[11]
Type
UINT
R/W
R
Area
Slave IN 2 area size
Function
Stores the first word for IN 2 area.
The OUT 1 block is not allocated if the value is 0.
Data range: 0 to 200
Default: 0 z
Areas and Word Ranges
Code
3
4
0
1
5
8 to 20
Area name in Memory for CJ-series Units
---
CIO Area (CIO)
Data Memory (DM)
Work Area (WR)
Holding Relay (HR)
Expansion Data Memory (EM)
Bank 0 to bank C (13 banks)
Word range
The block is not used.
0 to 6143
0 to 32767
0 to 511
0 to 511
0 to 32767 (E0_00000 to E0_32767, ...,
EC_00000 to EC_32767) for all banks
Note You cannot use Holding Area H512 and its subsequent holding areas, or EM Area Bank D and its subsequent banks.
3
3-3-7 Slave Detailed Status
Various types of statuses of each slave controlled by the master communication are provided.
The following device variables for CJ-series Unit are used to reference all information of the device variables for CJ-series Unit detailed slave status table.
Name of device variable for
CJ-series Unit
*_Nd0Sta to
*_Nd63Sta
Type
BYTE
R/W
R
Area Function
Detailed
Slave Status Table for
Node
Addresses
0 to 63
Each bit of *_Nd0Sta to *_Nd63Sta indicates the following statuses for slaves at node addresses 0 to 63.
Bit 00: Slave Error for node addresses 0 to
63
Bit 01: Slave Verification Error Flag at node addresses 0 to 63
Bit 02: Slave Configuration Error for node addresses 0 to 63
Bit 03: Slave Remote I/O Communications
Error for node addresses 0 to 63
Bit 04: Reserved by system
Bit 05: Master COS Send Error for node addresses 0 to 63
Bit 06: Scan List Registration Flag for node addresses 0 to 63
Bit 07: Remote I/O Communications Flag for node addresses 0 to 63
Data range: 16#00 to FF
Default: 16#00
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 3-61
3 Data Exchange with the CPU Unit
The following device variables for CJ-series Unit are used to reference individual information.
Name of device variable for
CJ-series Unit
*_Nd0Err to
*_Nd63Err
*_Nd0VefyErr to
*_Nd63VefyErr
*_Nd0CfgErr to
*_Nd63CfgErr
Type R/W
BOOL R
BOOL
BOOL
R
R
Area Function
Slave Error for node addresses
0 to 63
Slave Verification Error for node addresses
0 to 63
Slave Configuration
Error for node addresses
0 to 63
<Operation specifications>
TRUE:
Indicates that a remote I/O communications error occurred with the corresponding slave.
More specifically, this bit changes to
TRUE when at least one of the following errors occurs:
• *_Mstr1VefyErr (Verification Error)
• *_Mstr1StruErr (Structure Error)
• *_Mstr1IOErr (Remote I/O Communication Error)
FALSE:
Indicates that none of the above errors occured. Changes to FALSE when the error is clear.
Default: FALSE
<Operation specifications>
TRUE:
Indicates that the data for the slave registered in the scan list is different from the actual Slave.
FALSE:
Indicates that a verification error did not occur. Changes to FALSE when a verification error is cleared.
Default: FALSE
<Operation conditions>
It occurs with the scan list enabled.
<Operation specifications>
TRUE:
Indicates that I/O allocations cannot be made with the scan list disabled.
FALSE:
Indicates that a structure error did not occur. Changes to FALSE when a structure error is cleared.
Default: FALSE
3-62 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
3 Data Exchange with the CPU Unit
Name of device variable for
CJ-series Unit
*_Nd0IOErr to
*_Nd63IOErr
*_Nd0COSSendErr to
*_Nd63COSSendErr
*_Nd0SListRegSta to
*_Nd63SListRegSta
Type
BOOL
BOOL
BOOL
R/W
R
R
R
Area Function
Slave
Remote I/O
Communications
Error for node addresses
0 to 63
Master
COS Send
Error for node addresses
0 to 63
Scan List
Registration Flag for node addresses
0 to 63
<Operation specifications>
TRUE:
Indicates that an error occurred in remote
I/O communications with the corresponding slave.
This bit changes to TRUE if a timeout occurs in at least one connection with multiple connections set.
FALSE:
Indicates that a remote I/O communications error did not occur. Or, changes to
FALSE when a remote I/O communications error is cleared.
Default: FALSE
<Operation specifications>
TRUE:
Indicates that COS sent to a slave destination failed.
Use *_MstrCOSSendCmd (Master COS
Send Switch) to send COS.
The following may cause the failure of
COS signal transmission:
• Remote I/O communications stopped.
• A COS connection was not established.
• Bus OFF is occurring or has occurred.
• A network power error is occurring or has occurred.
• A send timeout is occurring or has occurred.
Once this bit changes to TRUE, it will remain TRUE until the operation is successfully completed.
FALSE:
Indicates that the error did not occur. The bit changes to FALSE when the operation is successfully completed.
Default: FALSE
<Operation specifications>
TRUE:
Indicates that the corresponding slave is registered in the scan list.
FALSE:
Indicates that the Unit is operating with the scan list disabled or the slave is not registered in the scan list.
Default: FALSE
3
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 3-63
3 Data Exchange with the CPU Unit
Name of device variable for
CJ-series Unit
*_Nd0IOCommSta to
*_Nd63IOCommSta
Type R/W
BOOL R
Area Function
Remote I/O
Communications Flag at node addresses
0 to 63
<Operation specifications>
TRUE:
Indicates that normal remote I/O communications were conducted with the corresponding slaves at all set connections.
This bit changes to FALSE if a timeout occurs in at least one connection with multiple connections set.
FALSE:
Indicates that remote I/O communications failed (no slave present, no scan list registered, verification error, structure error) or that a communications error is occurring.
Default: FALSE
3-64 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Remote I/O Master
Communications
This section describes the remote I/O communications performed as a DeviceNet master by the DeviceNet Unit.
4
4-1 Master Remote I/O Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
4-4-2 Settings through Device Variables for CJ-series Unit (Master User-set
4-5 Starting and Stopping Remote I/O Communications . . . . . . . . . . . . . . . . 4-31
4-6 Example of User Program for Remote I/O Communications . . . . . . . . . . 4-32
4-7 Errors that May Occur in Remote I/O Communications . . . . . . . . . . . . . . 4-33
4-1 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
4 Remote I/O Master Communications
4-1 Master Remote I/O Communications
Remote I/O communications are used to automatically transfer data between slaves and the CPU Unit without any special programming in the CPU Unit under which the Master Unit is mounted.
z
Master Communications
NJ-series CPU Unit
CJ-series DeviceNet Unit (master)
Remote I/O communications
DeviceNet
Slaves
Note A CJ-series DeviceNet Unit can function as either a master or slave in remote I/O communications and it can even function as both a master and a slave at the same time. Change
*_Sw1MstrEnblCmd (Master Enable Switch) to TRUE to set the CJ-series DeviceNet Unit to function as a master. Once master communications are enabled, the Unit will continue to perform master communications regardless of whether the power is turned OFF and back ON again.
Change *_Sw1MstrDsblCmd (Master Disable Switch) to TRUE to stop master communications. Master communications are the focus of this section.
In the following descriptions, a CJ-series DeviceNet Unit set to function as a master is referred to as a "Master Unit" and a CJ-series DeviceNet Unit set to function as a slave is referred to as a "Slave Unit".
4-1-1 Allocations
All slaves are allocated in the I/O memory area in the NJ-series CPU Unit to which the Master Unit is mounted. They are allocated using one of the following methods:
1) Fixed allocations
2) User-set allocations
Note With either fixed or user-set allocations, to access the area where each slave is allocated from the user program, a user-defined variable that specifies the AT specification of that area needs to be defined.
4-2 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
4 Remote I/O Master Communications
Fixed Allocations
You can use *_Sw1MstrFixAloc1Cmd to *_Sw1MstrFixAloc3Cmd (Master Fixed Allocation Setting 1 to
3 Switch) to specify where a slave is allocated in the following fixed allocation areas 1 to 3. The output
(OUT) block and the input (IN) block are allocated to a certain area as shown below in the order of node address.
To access the allocated area from the user program, a user-defined variable that specifies the AT specification of that area needs to be defined.
User program NJ Series
Memory used for CJ-series Unit
Master Fixed Allocation
Setting 1 Switch
User-defined variable
CIO 3200
CIO 3263
Output
(OUT) block 1
CIO 3300
CIO 3363
Input
(IN) block 1
CIO 3200
CIO 3201
:
CIO 3262
CIO 3263
Address 0
Address 1
:
Address 62
Address 63
CIO 3300
CIO 3301
:
CIO 3362
CIO 3363
Address 0
Address 1
:
Address 62
Address 63
Master Fixed Allocation
Setting 2 Switch
User-defined variable
Master Fixed Allocation
Setting 3 Switch
User-defined variable
CIO 3400
CIO 3463
Output
(OUT) block 2
CIO 3500
CIO 3563
Input
(IN) block 2
CIO 3600
CIO 3663
Output
(OUT) block 3
CIO 3700
CIO 3763
Input
(IN) block 3
CIO 3400
CIO 3401
:
CIO 3462
CIO 3463
Address 0
Address 1
:
Address 62
Address 63
CIO 3500
CIO 3501
:
CIO 3562
CIO 3563
Address 0
Address 1
:
Address 62
Address 63
CIO 3600
CIO 3601
:
CIO 3662
CIO 3663
Address 0
Address 1
:
Address 62
Address 63
CIO 3700
CIO 3701
:
CIO 3762
CIO 3763
Address 0
Address 1
:
Address 62
Address 63
4
Specify using master fixed allocation setting switches 1-3.
Words are allocated to slaves that start from address 0 in the output (OUT) and input (IN) blocks. Each address is allocated at least one byte (rightmost).
• More than one word is allocated for each slave (according to its node address) with more than16
I/O points.
• The rightmost byte of the word is allocated to each slave that has 8 I/O points or less.
User-set Allocations
The following methods are used for user-set allocations:
• Using the CX-Integrator
• Using the device variable for CJ-series Unit (Master User-set Allocations Setup Table)
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 4-3
4 Remote I/O Master Communications
4-4 z
With CX-Integrator
When using the CX-Integrator, you can allocate four blocks to each slave: Output (OUT) blocks 1 and 2 and input blocks 1 and 2. Each block is a maximum of 500 words. To access the allocated area from the user program, a user-defined variable that specifies the AT specification of that area needs to be defined.
User program
User-defined variable
CPU Unit
CJ-Series Unit memory
Output area
OUT block 1
OUT block 2
You can set the position of each block.
An order (such as IN block 1, OUT block 2,
IN block 2 and OUT block 1) can also be used.
Any address order Address
Address
Any address order Address
Address
User-defined variable
Input area
IN block 1
IN block 2
Address
Address
Address
Address
Any address order
Any address order
You can use any order for block allocations and for slave allocations within each block. Each address is allocated at least one byte (rightmost).
• More than one word is allocated for each slave with more than16 I/O points (using it's node address).
• The leftmost or rightmost byte of the word is allocated to each slave that has 8 I/O points or less.
z
Using "*_MstrAlocTblCfg[0 to 5]" (Master User-set Allocations Setup Table)
In *_MstrAlocTblCfg[0 to 5] (Master User-set Allocations Setup Table), set the areas and first words for the output block (OUT 1) and the input block (IN 1) and set the area and first word for the Allocation Size Setup Table. You can allocate each slave two blocks, OUT 1 and IN 1, according to the settings in this device variable for CJ-series Unit. The OUT and IN blocks will be allocated in order of slave node addresses. Each block is a maximum of 500 words.
To access the allocated area from the user program, a user-defined variable that specifies the AT specification of that area needs to be defined.
User program CPU Unit
CJ Unit memory
Device variables for CJ-series Unit
User-defined variable
OUT block 1
Ascending order that start from address 0
Address
Address
Ascending order that start from address 0
Address
User-defined variable
IN block 1
Address
Specify the area, first word, and allocation size to allocate output/input block 1.
Each address is allocated at least one byte (rightmost).
• More than one word is allocated for each slave with more than16 I/O points (according to its node address).
• The rightmost byte of the word is allocated to each slave that has 8 I/O points or less.
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
4 Remote I/O Master Communications
4-1-2 Remote I/O Master Specifications
Item
Slave allocation methods
No. of Masters that you can mount
Max. No. of
Slaves connected per
DeviceNet
Unit
Fixed allocations
User-set allocations
Specifications
Select one of the following fixed allocations areas with the use of *_Sw1MstrFixAloc1Cmd to *_Sw1MstrFixAloc3Cmd (Master Fixed Allocation Setting 1 to 3 Switch).
Allocated words (CIO
Area)
By CX-Integrator
I/O Size Fixed Allocation Area Setting 1
Fixed Allocation Area Setting 2
Fixed Allocation Area Setting 3
3200 to 3263 3400 to 3463 3600 to 3663 Output
(OUT) area
Input (IN) area
64 words
64 words 3300 to 3363 3500 to 3563 3700 to 3763
Note Select one of the above areas with the use of the device variable for
CJ-series Unit. All are fixed at 1 word per node address. The default setting is Fixed Allocation Area Setting 1.
Set the areas for the OUT 1/2 and IN 1/2 blocks, the first words, and the allocation sizes for all slaves with the use of the CX-Integrator. You can set blocks for nodes in any order.
Allocated words
The input and output areas can be the following sizes that start from any word in any of the following areas: CIO Area,
WR Area, HR Area, DM, Area, or EM Area.
Output (OUT) area
Input (IN) area
500 words max. × 2 blocks
500 words max. × 2 blocks
By device variable for
CJ-series
Unit
Fixed allocations
Set the areas and the first words for the OUT 1 and IN 1 blocks in the device variable for CJ-series Unit.
Set the allocation size for each slave with the use of the allocation size Setup
Table (in the memory used for CJ-series Unit). Allocations must be in the order of node addresses.
Allocated words
The input and output areas can be the following sizes that start from any word in any of the following areas: CIO Area,
WR Area, HR Area, DM Area, or EM Area in the memory used for CJ-series Unit.
Output (OUT) area
Input (IN) area
500 words max. × 1 block
500 words max. × 1 block
Allocation by the node address order
3 Units max. (Unique words must be allocated with the use of
*_Sw1MstrFixAloc1Cmd to *_Sw1MstrFixAloc3Cmd (Master Fixed Allocation Setting 1 to 3 Switch).)
16 Units max. (Unique words must be allocated with the use of the user
Setup Table (Device variable for CJ-series Unit).)
User-set allocations
By device variable for
CJ-series
Unit
By CX-Integrator
Fixed allocations
User-set allocations
By device variable for
CJ-series
Unit
By CX-Integrator
16 Units max. (Unique words must be allocated with the use of the CX-Integrator.)
63 nodes
4
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 4-5
4 Remote I/O Master Communications
Max. No. of
I/O points per
DeviceNet
Unit
Item
Max. No. of
I/O per Slave controllable by a DeviceNet
Unit
Fixed allocations
User-set allocations
By device variable for
CJ-series
Unit
By CX-Integrator
Fixed allocations
User-set allocations
By device variable for
CJ-series
Unit
By CX-Integrator
Specifications
2,048 pts (64 input words, 64 output words)
16,000 pts (500 input words x 1 block, 500 output words x 1 block)
32,000 pts (500 input words x 2 blocks, 500 output words x 2 blocks)
1,024 pts (32 input words, 32 output words)
3,200 pts (100 input words, 100 output words)
3,200 pts (100 input words, 100 output words)
4-1-3 Precautions on the Number of Master Units
You can construct the following system configurations based on various numbers of Master Units when
DeviceNet Units are used.
Pattern One Master Unit connected on a single network
Multiple Master Units connected on a single network
Multiple Master Units connected to a single CPU Unit
Configuration
Yes
A B
Remote I/O communications
Fixed allocations
Userset allocations
By
CX-
Integrator
By device variable for CJseries
Unit
❍
❍
❍
×
❍ (See note.)
❍ (See note.)
❍ (You can use up to 3 Master
Units.)
❍
❍
4-6 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
4 Remote I/O Master Communications
Pattern
Precautions
One Master Unit connected on a single network
Same as previous networks.
Multiple Master Units connected on a single network
Multiple Master Units connected to a single CPU Unit
• The communications cycle time is longer.
Note The communications cycle time for the network in the figure above is TA+TB if sections A and B above are separate networks with a communications cycle time of TA and TB.
• Multiple Master Units cannot share a single Slave Unit.
• Bus Off errors (communications stopped by multiple transmissions) may occur if multiple
Master Units with disabled scan lists are present on a single network.
• Make sure that each word allocated in the system is allocated to only one Master Unit.
Note You can connect only one Master Unit to a network if you specify a COS or cyclic connection with the use of CX-Integrator. Remote I/O communication errors may occur. In such a case, therefore, change the system setup so that only one Master Unit is connected to a network.
4
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 4-7
4 Remote I/O Master Communications
4-1-4 Procedure for Using Remote I/O Master
z
Fixed Allocations for Remote I/O
Turn ON the communications, slave, and Controller power supplies.
*1 Turn ON the communications power supply prior to turning ON the slave power supply or the slaves may not go online.
Switch the CPU Unit to PROGRAM mode.
Change *_Sw1MstrEnblCmd (Master Enable Switch) to TRUE. (The master will remain enabled even if the power is turned OFF and back ON again.)
*2 Execute this only when master communications are disabled.
(If the Master Enable Switch is turned ON when master communications are enabled, a
Unit error will occur and a C2 error will be displayed on the 7-segment indicator on the front panel.)
Perform the following steps to start with the scan list disabled.
*3
Perform the following steps to re-register the scan list when starting with the scan list enabled.
*3
Perform the following steps to make no changes to the fixed allocations area and scan list when starting with the scan list enabled.
*3
1) Change *_Sw1MstrFixAloc1Cmd to
*_Sw1MstrFixAloc3Cmd (Master
Fixed Allocation Setting 1 to 3
Switch) to TRUE.
2) Monitor and check the Registered
Slave Table ( *_RegSlavTblSta,
*_RegSalvTblNbSta[0] to [63] ) to see if communications are possible with registered slaves.
3) Change *_Sw1SListEnblCmd (Scan
List Enable Switch) to TRUE.
1) Change *_Sw1SListClrCmd
(Scan List Clear Switch) to TRUE.
2) Change *_Sw1MstrFixAloc1Cmd to
*_Sw1MstrFixAloc3Cmd
(Master Fixed Allocation Setting
1 to 3 Switch) to TRUE.
3) Monitor and check the Registered
Slave Table ( *_RegSlavTblSta,
*_RegSalvTblNbSta[0] to [63] ) to see if communications are possible with registered slaves.
4) Change *_Sw1SListEnblCmd (Scan
List Enable Switch) to TRUE.
Master remote I/O communications will begin with the scan list enabled.
(Use the software switches to start or stop communications.)
Check to see if both the MS and NS indicators are lit green on the Master Unit and all slaves.
*3 The mode can be confirmed from the dots on the
7-segment indicator on the Master Unit.
Left dot not lit: Scan list enabled
Left dot flashing: Scan list disabled
Define user-defined variables in the area to which I/O data is allocated.
Switch the CPU Unit to RUN mode.
4-8 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
4 Remote I/O Master Communications z
User-set Remote I/O Allocations Using the CX-Integrator
Start the CX-Integrator.
Turn ON the communications, slave, and Controller power supplies.
Note: Turn ON the communications power supply prior to turning ON the slave power supply. Or the slaves may not go online.
Switch the CPU Unit to PROGRAM mode.
1) Create a network configuration online on the CX-Integrator.
2) Enable master communications in the CJ1W-DRM21 properties.
3) Create master device parameters.
4) Save the data as a project file.
5) Read the project file, go online, and download the file to the network devices.
3) Read the project file, go online, and download the file to the network devices.
4
Master remote I/O communications will begin with the scan list enabled.
(Use the software switches or CX-Integrator to start or stop communications.)
Check to see if both the MS and NS indicators are lit green on the Master Unit and all slaves.
Note: The mode can be confirmed from the dots on the
7-segment indicator on the Master Unit.
Left dot not lit: Scan list enabled
Left dot flashing: Scan list disabled
Read the network components using the CX-Integrator.
Save the components as a project file using the CX-Integrator.
Define user-defined variables in the area to which I/O data is allocated.
Switch the CPU Unit to RUN mode.
Additional Information
You can stop remote I/O communications with a specified slave to effectively disconnect the slave from the network by changing *_CnctCmd (Disconnect/Connect Switches) to TRUE. You can do this when a slave is replaced or to register a slave in the scan list in preparations to connect it to the network at a later time. The Disconnect/Connect Switches, however, are cleared when the power supply is turned OFF, so the bit must be changed back to TRUE from the user program after the power turns ON in order for it to remain effective.
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 4-9
4 Remote I/O Master Communications z
User-set Remote I/O Allocations Using Device Variable for CJ-series Unit
Turn ON the communications, slave, and Controller power supplies.
Note Turn ON the communications power supply prior to turning ON the slave power supply or the slaves may not go online.
Switch the CPU Unit to PROGRAM mode.
Change *_Sw1MstrEnblCmd (Master Enable Switch) to TRUE (The master will remain enabled even if the power is turned OFF and back ON again.)
Note: Execute this only when master communications are disabled. (If the Master Enable
Switch is turned ON when master communications are enabled, a Unit error will occur and a C2 error will be displayed on the 7-segment indicator on the front panel.)
1) From Sysmac Studio, change data in *_MstrAlocTblCfg[0] to *_MstrAlocTblCfg[5] (Master User-set
Allocations Setup Table), to TRUE, and set the data to the Allocation Size Setup Table.
2) Change *_Sw1MstrAlocCmd (Master User-set Allocations Switch) to TRUE.
Master remote I/O communications will begin with the scan list enabled.
(Use the software switches to start or stop communications.)
Check to see if both the MS and NS indicators are lit green on the Master Unit and all slaves.
Note: The mode can be confirmed from the dots on the
7-segment indicator on the Master Unit.
Left dot not lit: Scan list enabled
Left dot flashing: Scan list disabled
Define user-defined variables in the area to which I/O data is allocated.
Switch the CPU Unit to RUN mode.
4-10 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
4 Remote I/O Master Communications
4-2 Scan List
4-2-1 Scan List
A scan list is used to register the slaves with which the Master Unit communicates in DeviceNet remote
I/O communications. It is the basis on which the Master Unit communicates with slaves.
The Master Unit does not contain a scan list by default. DeviceNet Unit, however, has a default setting that allows it to communicate with all slaves even with the scan list disabled, but this operating mode should not be used for normal operation. Always create a scan list prior to operating the Unit.
z
Scan List Contents
Vendor
Item
The contents of the scan list is listed in the following table. When a Master Unit goes online, it compares each of these items with the slaves that are actually connected to the network. The items that are compared, however, will depend on the allocation method that is used.
Description Fixed allocations User-set allocations using device variables for CJ-series
Unit
User-set allocations from the CX-Integrator
Node address
Allocated IN/OUT sizes and allocation
Device type
Product code
Connection type
Connection path
Node address for every Slave
Settings of the number of bytes allocated to every slave in a data area of the Master Unit
Unique manufacturer
ID
Unique product type value
Unique product model value
Applicable DeviceNet protocol
(See A-2 DeviceNet
Connections for details.)
Type of slave I/O data
(See A-2 DeviceNet
Connections for details.)
Compared
Compared
Not compared
Not compared
Not compared
Automatically set
Cannot be set
Compared
Compared
Set from CX-Integrator
Set from CX-Integrator
Set from CX-Integrator
Automatically set or set from CX-Integrator
Set from CX-Integrator
4
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 4-11
4 Remote I/O Master Communications z
Creating the Scan List
The way that a scan list is prepared varies with the allocation method as shown below.
Allocations
How to create scan list
Fixed allocations
With the CPU Unit in PRO-
GRAM mode:
1. Change the one of the
Fixed Allocated
Switches (1 to 3) to
TRUE.
2. Change the Scan List
Enable Switch to
TRUE.
User-set allocations using device variable for
CJ-series Unit
With the CPU Unit in PRO-
GRAM mode.
1. Change the Master
User-set Allocations
Setup Switch to TRUE.
User-set allocations from the CX-Integrator
Create a list from the CX-
Integrator. (Acquire a list of online devices, use it to create a scan list, and then register the scan list in the Master Unit.)
Precautions for Safe Use
• Be sure to create a scan list before you start actual system operation.
• It is still possible to communicate with Units (with the scan list disabled) if a scan list is not created when fixed allocations areas 1 to 3 are used. This may result in faulty operation because the Master Unit will communicate with slaves even if they do not start up due to errors, such as equipment failure if there is no scan list.
4-2-2 Scan List Enabled and Scan List Disabled
The scan list must be made. The scan list modes are described here.
z
Scan List Enabled (Used for Actual Operation)
Remote I/O communications are performed according to the registered scan list and only with slaves that are on the list. A Verification Error occurs ( *_Mstr1VefyErr changes to TRUE) if a slave registered on the scan list is not present on the network, if a slave did not start up when remote I/O communications started, or if the number of I/O points did not match the number registered.
z
Scan List Disabled (Used when Changing System Configuration)
You can perform remote I/O communications with fixed allocations instead of a scan list in order to change a system configuration. Do not operate without a scan list during actual system operation.
Use this mode only to replace a Master Unit or to change system configuration (change a connected slave or a node address).
Note 1 To disable the scan list, change *_Sw1SListClrCmd (Scan List Clear Switch) to TRUE during remote I/O communications with the scan list enabled (with fixed allocations, user-set allocations using device variable for CJ-series Unit, or user-set allocations using the CX-
Integrator). In all these cases, remote I/O communications are executed using the fixed allocations area that was last used when the list was disabled.
2 Slaves that are connected to the network while communications are in progress are also targeted for communications. Errors cannot be confirmed, however, even if there are slaves present that did start up due to errors because there is no scan list available to check communications against. The communications cycle time will also be significantly longer than the calculated value.
4-12 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
4 Remote I/O Master Communications
The scan list is automatically enabled when user-set allocations are set using the device variables for CJ-series Unit or the CX-Integrator. If the list is subsequently cleared using
*_Sw1SListClrCmd (Scan List Clear Switch), fixed allocations (1 to 3) will be used for remote I/O communications when the scan list is disabled. Make sure the system has stopped before you disable the scan list with a Master Unit that is set for user-set allocations. Particularly when multiple Master Units are connected to a single network, communications will not be performed successfully if even one Master Unit on the network is operating with the scan list disabled. Once the list is disabled, the user-set allocations data registered in the Master Unit is lost.
4-2-3 Backing Up the Scan List
A scan list must be created to switch the DeviceNet Unit to operation with the scan list disabled or to replace a DeviceNet Unit. It is important to back up the list with the use of one of the following methods: z
Fixed Allocations or User-set Allocations in Device Variable for CJ-series Unit
Save the scan list as a backup file on SD Memory Card in the CPU Unit by changing
*_Sw2FileBkupCmd (Unit Setup File Backup Switch) to TRUE.
z
User-set Allocations from the CX-Integrator
Save the scan list as a backup file on SD Memory Card or save it either as a device parameter file or project file by using the CX-Integrator.
In the preceding cases, change *_Sw2FileRestoreCmd (Unit Setup File Restore Switch) to TRUE to input setup data including the scan list backed up on the SD Memory Card into a DeviceNet Unit.
4
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 4-13
4 Remote I/O Master Communications
4-3 Fixed Allocations
4-3-1 Allocated Words
If fixed allocation is used, allocated words are in the following I/O (CIO) area in the memory used for CJseries Unit. You can select an area of words from one of three fixed allocation areas. Use
*_Sw1MstrFixAloc1Cmd to *_Sw1MstrFixAloc3Cmd (Master Fixed Allocation Setting 1 to 3 Switch) to select the allocation area.
Each area is comprised of an OUT area that is used to write output data to slaves and an IN area that is used for input from slaves in remote I/O communications.
To access a slave allocated to the fixed allocations areas 1 to 3 from the user program, user-defined variables that specify the AT specification of the memory used for CJ-series Unit to which the slave is allocated need to be defined.
Area
Fixed allocation area 1
Fixed allocation area 2
Fixed allocation area 3
OUT area (word) IN area (word) Selection method
CIO 3200 to CIO 3263 CIO 3300 to CIO 3363 Change *_Sw1MstrFixAloc1Cmd (Master
Fixed Allocation Setting 1 Switch) to TRUE.
CIO 3400 to CIO 3463 CIO 3500 to CIO 3563 Change *_Sw1MstrFixAloc2Cmd (Master
Fixed Allocation Setting 2 Switch) to TRUE.
CIO 3600 to CIO 3663 CIO 3700 to CIO 3763 Change *_Sw1MstrFixAloc2Cmd (Master
Fixed Allocation Setting 3 Switch) to TRUE.
You can include a maximum of 3 DeviceNet Units as masters in a single CPU Unit because the three allocation areas above on the memory used for CJ-series Unit are set individually for fixed allocations.
The default setting is fixed allocations area 1.
Each OUT/IN area is allocated to a slave according to its node address as shown below. Allocated words are determined by the node address in fixed allocations as shown.
OUT area
Node address
IN area
Area 3
C I O 3 6 0 0
C I O 3 6 0 1
C I O 3 6 0 2
Area 2
C I O 3 4 0 0
C I O 3 4 0 1
C I O 3 4 0 2
Area 1
C I O 3 2 0 0
C I O 3 2 0 1
C I O 3 2 0 2
Area 1
C I O 3 3 0 0
C I O 3 3 0 1
C I O 3 3 0 2
Area 2
C I O 3 5 0 0
C I O 3 5 0 1
C I O 3 5 0 2
Area 3
C I O 3 7 0 0
C I O 3 7 0 1
C I O 3 7 0 2
C I O 3 6 6 1
C I O 3 6 6 2
C I O 3 6 6 3
C I O 3 4 6 1
C I O 3 4 6 2
C I O 3 4 6 3
C I O 3 2 6 1
C I O 3 2 6 2
C I O 3 2 6 3
C I O 3 3 6 1
C I O 3 3 6 2
C I O 3 3 6 3
C I O 3 5 6 1
C I O 3 5 6 2
C I O 3 5 6 3
C I O 3 7 6 1
C I O 3 7 6 2
C I O 3 7 6 3
Note You can include more than one Master Unit in a single CPU Unit with fixed allocations, as shown below (3 Units max.).
Master Unit
Master Unit
Slave
Slave
4-14 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
4 Remote I/O Master Communications
4-3-2 Allocation Procedures
z
Step 1: Place the CPU Unit in PROGRAM mode.
z
Step 2: Change the Master Enable Switch to TRUE
If the master communications have been disabled (if *_MstrEnblSta (Master Function Enabled Status) is set to FALSE), change *_Sw1MstrEnblCmd (Master Enable Switch) to TRUE to enable master communications. Once Master communications have been enabled by changing this switch to
TRUE, it will not change even if the power is turned OFF and back ON again.
Note If the master communications are enabled (if *_MstrEnblSta (Master Function Enabled Status) is TRUE), skip this step and go onto the next step. (If the Master Enable Switch is changed to TRUE (when master communications are enabled), a Unit error will occur and a
C2 error will be displayed on the 7-segment indicator on the front panel.) z
Step 3: Change the Scan List Clear Switch to TRUE
If the Unit is in the Scan List Enable mode (if *_SListDsblSta (Scan List Disable Status) is set to
FALSE), change *_Sw1SListClrCmd (Scan List Clear Switch) to TRUE to change to the Scan List
Disabled mode.
Note If the Unit is already in the Scan List Disabled mode (if *_SListDsblSta (Scan List Disable
Status) is TRUE), skip this step and go onto the next step. (If the Scan List Clear Switch is changed to TRUE (when the Unit is in the Scan List Disabled mode), a Unit error will occur and a C2 error will be displayed on the 7-segment indicator on the front panel.) z
Step 4: Select Fixed Allocations Area 1 to 3
Change *_Sw1MstrFixAloc1Cmd to *_Sw1MstrFixAloc3Cmd (Master Fixed Allocation Setting 1 to 3
Switch) to TRUE to select the fixed allocations area from 1 to 3.
One word will be allocated per node address in order of node addresses for the output (OUT) block and one word for the input (IN) block in the CIO Area in the memory used for CJ-series Unit.
Name of device variables for
CJ-series Unit
*_Sw1MstrFixAloc1C md
*_Sw1MstrFixAloc2C md
*_Sw1MstrFixAloc3C md
Name
Master Fixed Allocation
Setting 1 Switch
Master Fixed Allocation
Setting 2 Switch
Master Fixed Allocation
Setting 3 Switch
Fixed allocations area number
Allocated
OUT area
Allocated
IN area
Fixed allocations area
1
Fixed allocations area
2
Fixed allocations area
3
CIO 3200 to
CIO 3263
CIO 3400 to
CIO 3463
CIO 3600 to
CIO 3663
CIO 3300 to
CIO 3363
CIO 3500 to
CIO 3563
CIO 3700 to
CIO 3763 z
Step 5: Change the Scan List Enable Switch to TRUE
Remote I/O communications will start with the scan list disabled after you select a fixed allocations area. Check to see if communication is proceeding normally with each slave, and then change
*_Sw1SListEnblCmd (Scan List Enable Switch) to TRUE to communicate with the scan list enabled.
4
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 4-15
4 Remote I/O Master Communications z
Step 6: Define the User-defined Variable
Define a user-defined variable for the area to which each slave is allocated. By using the userdefined variable, the user program can access the allocation area of the slave.
Below is an example of a user-defined variable in which fixed allocations area 1 is selected.
Fixed Allocations Area 1
OUT blocks are allocated to slaves from CIO 3200 to CIO 3263 and IN blocks are allocated to slaves from CIO 3300 to CIO 3363 in the memory used for CJ-series Unit. To access the output (OUT) block and the input (IN) block from the user program, allocate a user-defined variable to the applicable area.
CIO Area in memory for CJ-series Units
Bit
CIO 3200
OUT block
Bit
CIO 3200
CIO 3201
CIO 3202
Address 0
Address 1
Address 2 to to
Output to Slaves to OUT block
CIO 3263
CIO 3260
CIO 3261
CIO 3262
CIO 3263
Address 60
Address 61
Address 62
Address 63
Bit
CIO 3300 to
CIO 3363
IN block
IN block
Bit
CIO 3300
CIO 3301
CIO 3302
Address 0
Address 1
Address 2 to to
CIO 3360
CIO 3361
CIO 3362
CIO 3363
Address 60
Address 61
Address 62
Address 63
Input from Slaves
4-16 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
4 Remote I/O Master Communications
Fixed Allocations Area 2
OUT blocks are allocated to slaves from CIO 3400 to CIO 3463 and IN blocks are allocated to slaves from CIO 3500 to CIO 3563 in the memory used for CJ-series Unit. To access the output (OUT) block and the input (IN) block from the user program, allocate a user-defined variable to the applicable area.
OUT block
CIO Area in the memory for CJ-series Units
Bit
CIO 3400
Bit
CIO 3400
CIO 3401
CIO 3402
Address 0
Address 1
Address 2 to to
Output to Slaves to
OUT block
CIO 3463
CIO 3460
CIO 3461
CIO 3462
CIO 3463
Address 60
Address 61
Address 62
Address 63
IN block
Bit
CIO 3500 to
CIO 3563
IN block
CIO 3500
CIO 3501
CIO 3502 to
CIO 3560
CIO 3561
CIO 3562
CIO 3563
Address 0
Address 1
Address 2 to
Address 60
Address 61
Address 62
Address 63
Input from Slaves
4
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 4-17
4 Remote I/O Master Communications
Fixed Allocations Area 3
OUT blocks are allocated to slaves from CIO 3600 to CIO 3663 and IN blocks are allocated to slaves from CIO 3700 to CIO 3763 in the memory used for CJ-series Unit. To access the output (OUT) block and the input (IN) block from the user program, allocate a user-defined variable to the applicable area.
OUT block
CIO Area in the memory for CJ-series Units
Bit
CIO 3600
Bit
CIO 3600
CIO 3601
CIO 3602
Address 0
Address 1
Address 2 to to
Output to Slaves to
OUT block
CIO 3663
CIO 3660
CIO 3661
CIO 3662
CIO 3663
Address 60
Address 61
Address 62
Address 63
IN block
Bit
CIO 3700
CIO 3700
CIO 3701
CIO 3702
Address 0
Address 1
Address 2 to IN block to to
Input from Slaves
CIO 3763
CIO 3760
CIO 3761
CIO 3762
CIO 3763
Address 60
Address 61
Address 62
Address 63
The Slave allocation order is fixed in the output (OUT) and IN blocks that start from address 0. Each address is allocated at least one byte (rightmost).
• More than one word is allocated for each slave (according to it's node address) with more than16 I/O points.
• The rightmost byte of the word is allocated to each slave that has 8 I/O points or less.
4-3-3 Changing System Components
The scan list must be cleared in the following situations:
• Adding a slave
• Disconnecting a slave
• Changing a node address
Set the CPU Unit to PROGRAM Mode. Change *_Sw1SListClrCmd (Scan List Clear Switch) to TRUE to clear the scan list. (Remote I/O communications will be performed with the scan list disabled using fixed allocations in the fixed allocations area that was used the last time the list was disabled.)
Make sure that communications with all slaves are operating properly after the scan list is cleared and the system component is changed, and then change *_Sw1SListEnblCmd (Scan List Enable Switch) to
TRUE again to register all slaves currently online in the scan list. Remote I/O communications will continue during this time with the scan list enabled.
4-18 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
4 Remote I/O Master Communications
4-3-4 Fixed Allocations Example
This example shows the allocations that are used when Fixed Allocations 1 are used for the following slaves.
6
7
8
9
Node address
0
1
2
3
4
5
Outputs
0 pts
8 pts
0 pts
16 pts
8 pts
16 pts
0 pts
32 pts
8 pts
Inputs
0 pts
16 pts
0 pts
8 pts
16 pts
48 pts
0 pts
Product
8-pt Transistor Input Terminal
(DRT1-ID08)
8-pt Transistor Output Terminal (DRT1-OD08)
16-pt Transistor Input Terminal
(DRT1-ID16)
16-pt Transistor Output Terminal (DRT1-OD16)
8-pt Input and 8-pt Output
Environment-resistant Terminal
(DRT1-MD16C)
CQM I/O Link Terminal
(CQM1-DRT21)
C200 I/O Link Unit (C200HW-
DRM21) with 48 input pts (3 words)
Analog Output Terminal with 2 output pts (DRT2-DA02) z
Resulting Slave Allocation
Slave type
8 inputs
8 outputs
16 inputs
16 outputs
8 inputs, 8 outputs
16 inputs, 16 outputs
48 inputs
(Master)
32 outputs
Allocation
Node address setting
00
01
02
03
04
05
06
07
08
Node address Output Input
00
01
02
03
04
0
8
0
16
8
8
0
16
0
8
16 16 05
06
07
08
0 48
Master Unit
09
10
11
32
None
See note 1.
0
None
See note 2.
OUT block
CIO
3200
15
Allocation disabled
0
3201
Allocation disabled
Allocated
3202 Allocation disabled
3203
3204
3205
Allocated
Allocation disabled
Allocated
Allocated
3206
3207
3208
3209
3210
3211
Allocation disabled
Allocation enabled
Allocated
Allocated
Not used
Not used
IN block
CIO
3300
15
Allocation disabled
3301
Allocated
Allocation disabled
0
3302
3303
3304
3305
Allocated
Allocation disabled
Allocation disabled
Allocated
Allocated
3306
3307
3308
Allocated
Allocated
Allocation enabled
Allocation enabled 3309
3310
3311
Not used
Not used
63 None None 3263 Not used 3363 Not used
Note 1 The Master Unit does not require any word allocation and so it can use any available address.
2 You can allocate blocks for which allocation is enabled to Slaves as long as the blocks do not overlap.
3 To use the I/O data allocated to the address above using Sysmac Studio, you need to register user-defined variables.
z
Change the Scan List Enable Switch to TRUE
Change *_Sw1SListEnblCmd (Scan List Enable Switch) to TRUE. This will create a scan list based on data for slaves that are actually online and will start remote I/O communications with the scan list enabled.
4
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 4-19
4 Remote I/O Master Communications
4-4 User-set Allocations
With a CJ-series DeviceNet Unit, you can allocate remote I/O communication slaves in any area of a memory used for CJ-series Unit (CIO, WR, HR, DM, or EM) with the use of one of the following methods:
• Setting through CX-Integrator
• Setting through device variables for CJ-series Unit (Master User-set Allocations Setup Table)
To access a given allocation area from the user program, a user-defined variable that specifies the AT specification of that allocation area needs to be defined.
z
User-set Allocations Methods
Method
Allocation areas in memory used for CJ-series Unit *
No. of allocated blocks
Block allocation order
Node address order
Start bit for allocations
Set through CX-Integrator
Set through Device Variables for CJseries Unit (Master User-set Allocations Setup Table)
CIO: 0000 to 6143
WR: W000 to W511
HR: HR000 to HR511
DM: D00000 to D32767
EM: E _00000 to E _32767 ( = 0 to C)
4 blocks: OUT 1, IN 1, OUT 2 and IN 2
You can create OUT 1, IN 1, OUT 2, and
IN 2 anywhere in the above areas.
Any order
2 blocks: OUT 1 and IN 1
You can create OUT 1 and IN 1 anywhere in the above areas.
Any order Allocations must be in order of node addresses (0 to 63 in ascending order)
Note 1 Node addresses do not have to
2 correspond between blocks.
One node address cannot be allocated to different blocks.
Allocations can start from bit 00 or bit 08.
Allocations that start from bit 08 are in
1-byte units only.
Note 1 Not all nodes need to be allocated, reducing the number of words required.
2 Node addresses do not have to correspond between blocks.
All allocations start from bit 00 (Cannot start from bit 08. All allocations are in 1 word units.)
500 words max.
2,000 words max. for a total of 4 blocks 1,000 words max. for a total of 2 blocks
The leftmost byte (bits 07 to 15) cannot be used.
Allocation size Per block
Total size
Slave allocation limits
Slaves with more than 8 points
Slaves with 8 points
Slaves with 16 points
Slaves with more than 16 points
Allocated to the leftmost or rightmost bytes (not allocated a word)
Allocated one word
Allocated multiple words (with an odd number of bytes, only the rightmost byte is allocated in the last word)
* You cannot use Holding Area H512 and its subsequent holding areas, or EM Area Bank D and its subsequent banks.
4-20 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
4 Remote I/O Master Communications
Functions will vary as shown below depending on whether allocations are set with the use of CX-
Integrator or through device variable for CJ-series Unit (Master User-set Allocations Setup
Table.)
• You can determine the order of node addresses when the CX-Integrator is used. Words are always allocated to slaves in order of ascending node addresses when allocations are set with device variable for CJ-series Unit. However, even when you use device variable for CJ-series
Unit, nodes do not have to be allocated words, reducing the number of words required.
• There are four blocks (OUT1 and 2 and IN1 and 2) available when setting is made with the CX-
Integrator, but you can only allocate two blocks (OUT1 and IN1) with device variables for CJseries Unit.
• The first bit for node allocations can be either bit 00 or bit 08 when setting allocations with CX-
Integrator (allocations for slaves with two bytes or more cannot start at bit 08), while it is always bit 00 with device variable for CJ-series Unit.
4
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 4-21
4 Remote I/O Master Communications
4-4-1 Settings through CX-Integrator
You can allocate slaves in any order for the following blocks: OUT block 1, OUT block 2, IN block 1, and IN block 2.
To access the area where the slave is allocated from the user program, a user-defined variable that specifies the AT specification of that area needs to be defined.
OUT block 1
User-set block order
Specified areas in memory used for CJ-series Unit
User-set block order
Bit
First word specified
Bit
First word specified
Address
Address
Address to
Output to slaves
OUT block 1 to to
Address
Address
Address
Address
IN block 1
User-set block order
Bit
First word specified
Bit
First word specified
Address
Address
Address to
IN block 1 to to
Input from slaves
Address
Address
Address
Address
OUT block 2
User-set block order
Specified areas in I/O memory
Bit
First word specified
Bit
First word specified
Address
Address
Address to
Output to slaves to
OUT block 2
Address
Address
Address
Address
Bit
First word specified
IN block 2
Bit
First word specified
Address
Address
Address
User-set block order to
IN block 2 to to
Address
Address
Address
Address
Input from slaves
You can set the block allocation order, block allocation areas, and order of node addresses in each block. Each address is allocated at least one byte (rightmost or leftmost byte).
• More than one word is allocated for each slave (according to it's node address) with more than 16 I/O points.
• The leftmost or rightmost byte of the word is allocated to each slave that has 8 I/O points or less.
4-22 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
4 Remote I/O Master Communications
Allocation Procedures
Step 1
Set the area, start word, and words allocated for each block with the use of the CX-Integrator.
Step 2
Allocate words to all node addresses in each block as shown below with the use of the CX-Integrator.
OUT block 1
Node address 00
Node address 00: DRT1-OD16 (16 output pts)
Node address 03 Node address 03: DRT2-DA02 (2 analog output points = 32 bits)
IN block 1
Node address 01: DRT1-ID08 (8 input pts)
Node address 01
Node address 02
Node address 02: DRT1-ID08 (8 input pts)
• Each address is allocated at least one byte (rightmost or leftmost byte).
Note a) You can set the order of all blocks as you desire.
OUT block 1
4
IN block 2
OUT block 2
IN block 1 b) Node addresses do not have to correspond between an output block and input block.
Example: This is not necessary.
OUT block 1 IN block 1
Node address 01 Node address 01
Node address 02
Node address 03
Node address 02 c) The same node address cannot be allocated more than once.
Example:
OUT block 1
Node address 02
OUT block 2
Node address 02
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 4-23
4 Remote I/O Master Communications d) The start bit for node addresses can be bit 00 or bit 08. If it is bit 08 however, 2 or more bytes cannot be allocated as shown below.
Start byte e) Multiple masters cannot share the same slave.
Master Master
Slave
You can determine whether there are duplicate node addresses in the I/O allocations (scan lists) that were created simply by conducting a master parameter file duplicate check from the CX-Integrator.
f) Be sure to use user-set allocations and operate with the scan list enabled if multiple masters are connected to a single network. A Bus OFF errors will occur if multiple fixed allocations masters operating with the scan list disabled are present on a single network.
g) You can include multiple Master Units in a single CPU Unit as shown below using user-set allocations (16 Units max.).
Master Unit
Master Unit
Slave
Slave
Step 3: Define User-defined Variable
To access the area where the slave is allocated from the user program, a user-defined variable that specifies the AT specification of that area needs to be defined.
Example of User-set Allocations Using the CX-Integrator
Slave types
16 output pts
Combination of 8 input and output pts
Combination of 16 input and output pts
8 input pts
32 output pts
Slave types
48 input pts
8 input pts
Combination of 8 output and 16 input pts
Node address setting
00
01
02
03
10
Node address setting
04
09
12
Node address
00
01
02
03
10
Node address
04
09
12
Allocation status
Output
16 pts
8 pts
16 pts
0 pts
32 pts
Output
0 pts
0 pts
8 pts
Input
0 pts
8 pts
16 pts
8 pts
0 pts
CIO 1950
1 5
OUT block 1
Allocation (00)
0
CIO 1951 Allocation (01)
CIO 1952
Not used
Allocation (02)
CIO 1953
CIO 1954
Allocation
Allocation
(10)
0
Input
48 pts
8 pts
16 pts
01000
15
OUT area
OUT block 2
Not used
00
Allocation (12)
IN area
IN block 1
CIO 1900
1 5 0 0
Allocation (02)
CIO 1901 Allocation (01) Allocation (03)
10 wd
11 wd
15
12 wd
13 wd
14 wd
15 wd
IN block 2
Allocation
00
Allocation
Allocation
Not used
Allocation (12)
(04)
Not used Allocation (09)
4-24 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
4 Remote I/O Master Communications
CX-Integrator Setting Methods
Refer to CX-Integrator Ver.2.
@ OPERATION MANUAL (Cat. No. W464).
4-4-2 Settings through Device Variables for CJ-series Unit (Master
User-set Allocations Setup Table)
All slaves are allocated words in order of node addresses in two blocks: OUT block 1 and IN block 1.
In the block area, the first word is set with *_MstrAlocTblCfg[0 to 3] . In addition, an Allocation Size
Setup Table is created in the area and word location is specified through *_MstrAlocTblCfg[4 and 5] , and you can define the size for each block. To access the area where the slave is allocated from the user program, a user-defined variable that specifies the AT specification of that area needs to be defined.
Addresses are in ascending order.
Not all nodes need to be allocated and addresses for nodes with no allocations are skipped.
Area specified in I/O memory
Bit
First word specified
OUT areas
Bit
First word specified
Address 0
Node addresses in ascending order
OUT block 1 to
Output to Slaves to to
4
Bit
First word specified to
IN block 1
IN areas
Bit
First word specified Address 0
Node addresses in ascending order
Addresses are in ascending order.
Not all nodes need to be allocated and addresses for nodes with no allocations are skipped.
to to Input from Slaves
You can set the block allocation order and block allocation areas. Node addresses in each block are allocated words in ascending order from 0 to 63. Node addresses that are not allocated are skipped
(not allocated words). Each address is allocated at least one word (rightmost byte, 1 word, or multiple words).
• More than one word is allocated for each slave (according to it's node address) with more than16 I/O points.
• The rightmost byte of the word is allocated to each slave that has 8 I/O points or less.
Note You can include multiple Master Units in a single CPU Unit as shown below with the use of user-set allocations (16 Units max.).
Master Unit
Master Unit
Slave
Slave
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 4-25
4 Remote I/O Master Communications
Allocation Procedures
Step 1: Set the CPU Unit to PROGRAM Mode.
Step 2: Set the Master Enable Switch to TRUE.
Make sure that master communications was disabled by checking to see if *_MstrEnblSta (Master
Function Enabled Status) is FALSE, and then set to TRUE the *_Sw1MstrEnblCmd (Master Enable
Switch) to enable master communications. Once you have turned this switch from OFF to ON, which will enable the master, the system operates over the master whether the power supply is turned OFF or ON.
Note Do not change the Master Enable Switch to TRUE unless master communications are stopped. (If the Master Enable Switch is change to TRUE when master communications are enabled, a Unit error will occur and a "C5" error will be displayed on the 7-segment indicator on the front panel.)
Step 3: Set the Master User-set Allocations Setup Table
This table specifies the area and first word for each block and the area and first word for the Allocation Size Setup Table.
• Master User-set Allocations Setup Table
Name of device variables for
CJ-series Unit
*_MstrAlocTblCfg[0]
*_MstrAlocTblCfg[1]
*_MstrAlocTblCfg[2]
*_MstrAlocTblCfg[3]
*_MstrAlocTblCfg[4]
*_MstrAlocTblCfg[5]
*_MstrAlocTblCfgSta
Type Name
UINT
UINT
UINT
UINT
OUT block 1 area
First word in OUT block 1
IN block 1 area
First word in IN block 1
UINT
UINT
Allocation size setup table area
First word in allocation size setup table 1
WORD Setting Results of Master User-set Allocations Setup
Range
0 to 20
0 to 32767
0 to 20
0 to 32767
0 to 20
0 to 32767
16#0000 to FFFF
3
4
0
1
5
8 to 20
• Areas and Word Ranges for OUT Block 1, IN Block 1, and the Allocation Size Setup Table
Code Area name in memory used for CJ-series Unit
---
CIO Area (CIO)
Data Memory (DM)
Work (WR)
HR (HR)
Expansion Data Memory (EM)
Bank 0 to bank C (13 banks)
Word range
The block is not used.
0 to 6143
0 to 32767
0 to 511
0 to 511
0 to 32767 (E0_00000 to E0_32767,
... , EC_00000 to EC_32767) for all banks
Note You cannot use Holding Area H512 and its subsequent holding areas, or EM Area Bank D and its subsequent banks.
4-26 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
4 Remote I/O Master Communications
Step 4: Set the Allocation Size Setup Table
Specify the area and first word l in this table at words *_MstrAlocTblCfg[4] (Allocation size setup table area) and *_MstrAlocTblCfg[5] (First word in the allocation size setup table 1).
Allocate user-defined variables to the areas on the allocation size setup table.
After allocating user-defined variables to the areas, IN and OUT sizes for all nodes are set here as shown in the table below. The setting range for each node is 0 to 200 bytes (0 to 100 words), although actual size depends on the allocated slaves. The maximum size per block is 500 words. If the size set here is larger than 1 byte, the start bit for all slaves is bit 00 and size is allocated in ascending node address order that start from the beginning of the OUT 1 and IN 1 areas in word units. If the size is set at 0 bytes for a node address, it is skipped the words are allocated to the next address.
• Allocation Size Setup Table l is the start address for the Allocation Size Setup Table specified with *_MstrAlocTblCfg[4]
(Allocation Size Setup Table Area) and *_MstrAlocTblCfg[5] (First Word in Allocation Size Setup
Table 1).
Bit 15
I+0
08 07
Node address 0 OUT size (bytes) Node address 0 IN size (bytes)
00
I+1 to
Node address 1 OUT size (bytes) to
Node address 1 IN size (bytes)
I+62
I+63
Node address 62 OUT size (bytes)
Node address 63 OUT size (bytes)
Node address 62 IN size (bytes)
Node address 63 IN size (bytes)
Step 5: Set the Master User-set Allocations Setup Switch to TRUE.
Change *_Sw1MstrAlocCmd (Master User-set Allocations Switch) to TRUE. The DeviceNet Unit performs the following two steps simultaneously to start remote I/O communications with the scan list enabled: reading allocation result for the above slaves from the NJ-series CPU Unit, and creating a scan list based on actual connection information of slaves.
Note The Master User-set Allocations Switch not only reads slave allocation data, but it also enables the scan list.
Master User-set Allocations Setup Table
Name of device variables for CJ-series Unit
*_MstrAlocTblCfg[0]
*_MstrAlocTblCfg[1]
*_MstrAlocTblCfg[2]
*_MstrAlocTblCfg[3]
*_MstrAlocTblCfg[4]
*_MstrAlocTblCfg[5]
Name
OUT block 1 area
First word in OUT block 1
IN block 1 area
First word in IN block 1
Allocation size setup table area
First word in Allocation Size Setup Table 1
Set first word.
Specify the first word.
Specify the first word.
First word specified
Output (OUT) area
Bit 15 0
Node address 0
Node address 1 to to
Node address 63
Allocation Size Setup
Table
Bit 15 l wd Address 0
OUT size l+1wd Address 1
OUT size to l+63wd Address 63
OUT size
Specify the size.
Address 0
IN size
Address 1
IN size
0
Specify the size.
First word specified
Input (IN) area
Bit 15
Node address 0
Node address 1
0 to to
Address 63
IN size
Node address 63
: Specify the first word.
: Specify the size.
Note 1 You can use any order for the OUT 1 and IN 1 blocks.
2 Node addresses do not have to correspond between output block 1 and input block 1.
4
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 4-27
4 Remote I/O Master Communications
Example: This is not necessary.
OUT block 1
Node address 01
IN block 1
Node address 01
Node address 02
Node address 03
Node address 02
3 The start bit for node addresses must always be bit 00, and never bit 08.
4 Multiple masters cannot share the same slave.
Master Master
Slave
5 Be sure to use user-set allocations and operate the Master Unit with the scan list enabled if multiple masters are connected to a single network. Communications will not be possible if there is more than one master with the scan list disabled connected to a network.
Step 6: Define the User-defined Variable
Define a user-defined variable that specifies the AT specification for the area to which each slave is allocated. By using the user-defined variable, the user program can access the allocation area of the slave.
Changing System Components
In the following situations, the table must be reset, the *_Sw1MstrAlocCmd (Master User-set Allocations Switch) changed to TRUE, and the scan list recreated:
• Adding a slave
• Removing a slave
• Changing a node address
• Changing a node allocation
There is no need to clear the scan list.
4-28 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
4 Remote I/O Master Communications
Example Settings for User-set Allocations through Device Variables for CJ-series Unit
This example uses the following settings for unit number 0.
• OUT block 1 area and first word: WR (4), 50CH (50)
• IN block 1 area and first word: WR (4), 100CH (100)
• Allocation Size Setup Table area and first word: DM (3), 00100 (100)
0
1
2
3
4
5
This example shows user-set allocations for the following slaves.
Node address Outputs
16 pts
8 pts
16 pts
0 pts
None
160 pts
0 pts
8 pts
16 pts
8 pts
Inputs
160 pts
Product
16-pt Transistor Output Terminal
(DRT1-OD16)
8-pt input and 8-pt Output Environmentresistant Terminal (DRT1-MD16C)
CQM I/O Link Terminal (CQM1-DRT21)
8-pt Transistor Input Terminal (DRT1-
ID08)
---
CJ-series DeviceNet Unit (CJ1W-
DRM21) (Slave Unit)
4
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 4-29
4 Remote I/O Master Communications
4-30 z
Master User-set Allocations Setup Table
Name of device variables for
CJ-series Unit
*_MstrAlocTblCfg[0]
*_MstrAlocTblCfg[1]
*_MstrAlocTblCfg[2]
*_MstrAlocTblCfg[3]
*_MstrAlocTblCfg[4]
*_MstrAlocTblCfg[5]
Name Setting (function)
OUT block 1 area
First word in OUT block 1
IN block 1 area
First word in IN block 1
4 (WR)
50 (50 words)
4 (WR)
100 (100 words)
Allocation size setup table area 3 (DM)
First word in Allocation Size Setup Table 1 100 (100 words) z
Allocation Size Setup Table
Address
Bits 00 to 07 for D00100
Bits 08 to 15 for D00100
Bits 00 to 07 for D00101
Bits 08 to 15 for D00102
Bits 00 to 07 for D00103
Bits 08 to 15 for D00103
Bits 00 to 07 for D00104
Bits 08 to 15 for D00104
Bits 00 to 07 for D00105
Bits 08 to 15 for D00105
Bits 00 to 07 for D00106
Bits 08 to 15 for D00106
User-defined variable name (USINT type)
Slave0_InSizeTab
Setting
0
Slave0_OutSizeTab 2
Slave1_InSizeTab 1
Slave1_OutSizeTab 1
Slave2_InSizeTab 2
Slave2_OutSizeTab 2
Slave3_InSizeTab 1
Slave3_OutSizeTab 0
Slave4_InSizeTab 0
Slave4_OutSizeTab 0
Slave5_InSizeTab 20
Slave5_OutSizeTab 20
Number of slave
2
1
1
2
0
2
1
0
0
0
20
20 bytes z
Resulting Slave Allocations
Slaves are allocated as follows. Before a user program can access the following areas, a userdefined variable that specifies the AT specification of that allocation area must to be defined.
OUT area 1
Address 0
Not used Address 1
Address 2
Address 0 allocated two bytes (1 word).
Address 1 allocated 1 byte, leftmost byte is not used.
Address 2 allocated two bytes (1 word).
Address 5
Address 5 allocated 20 bytes (10 words).
IN area 1
Not used Address 1
Address 2
Not used Address 3
Address 1 allocated 1 byte, leftmost byte is not used.
Address 2 allocated two bytes (1 word).
Address 3 allocated 1 byte, leftmost byte is not used.
Address 5
Address 5 allocated 20 bytes (10 words).
z
Changing the Master User-set Allocations Switch to TRUE
Change *_Sw1MstrAlocCmd (Master User-set Allocations Switch) to TRUE. The Master User-set
Allocations Switch will read the allocation results data for the above slaves and create a scan list based on data for slaves that are actually online prior to starting remote I/O communications with the scan list enabled.
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
4 Remote I/O Master Communications
4-5 Starting and Stopping Remote I/O
Communications
4-5-1 Starting Remote I/O Communications
Remote I/O communications start automatically after the Unit is restarted or the Controller is reset, including when the power is turned ON.
The *_Mstr1IOCommSta (I/O Data Communications Status) is changed to TRUE when remote I/O communications is started with at least one slave.
4-5-2 Stopping Remote I/O Communications
Remote I/O communications stop under the following user-controlled conditions. Message communications can still be performed when the remote I/O communications stop.
Stop Communications with All Slaves
When *_Sw1IOCommStopCmd (Remote I/O Communications Stop Switch) is changed to TRUE.
Stop Communications with a Specified Slave
When associated device variables for CJ-series Unit *_CnctNdCmd[0] to *_CnctNdCmd[63] (Disconnect/Connect Switches for Node Address 0-63 Slave) are changed to TRUE (Disconnected when changed to TRUE).
Note The communications cycle time is not shorter even though a slave was disconnected from remote I/O communications by setting the Disconnect/Connect Switch to TRUE. (Blank time in the communications cycle will only be increased.)
4
4-5-3 Restarting Remote I/O Communications
Remote I/O communications restart under the following conditions.
Restart Communications with All Slaves
Remote I/O communications restart when *_Sw1IOCommStartCmd (Remote I/O Communications
Start Switch) is changed to TRUE. (Only communications with slaves with the Disconnect/Connect
Switch changed to FALSE will be restarted.)
Restart Communications with Specified Slave
When associated device variables for CJ-series Unit *_CnctNdCmd[0] to *_CnctNdCmd[63] (Disconnect/Connect Switches for Node Address 0-63 Slave) are changed to FALSE. (Connected when changed to FALSE.)
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 4-31
4 Remote I/O Master Communications
4-6 Example of User Program for Remote
I/O Communications
When user program are written for remote I/O communications, make sure it performs I/O processing with a slave under the following conditions:
• *_Mstr1IOCommSta (I/O Data Communications Status) is changed to TRUE.
• *_UnitErr (Unit Error) is changed to FALSE.
Example: There is no jump and slave I/O is processed when the JMP(004) instruction input condition is
FALSE in the following instructions. There is a jump and slave I/O is not processed when the JMP(004) instruction input condition is TRUE.
(I/O Data Communications) aaaa_Mstr1IOCommSta STEP1
(Unit Error) aaaa_UnitErr
Slave I/O processing
STEP1:
Processing other than slave I/O
Even if there is a communications error with the slave, the slave input data is saved in the allocated area.
To prevent operating errors, make a user program so that no slave I/O processing will occur when *_UnitErr (Unit Error) is TRUE.
4-32 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
4 Remote I/O Master Communications
4-7 Errors that May Occur in Remote I/O
Communications
The following errors may occur during remote I/O communications.
Condition Error Details Results
Error occurs in fixed allocations with the scan list disabled
*_Mstr1StruE rr (Structure
Error) is
TRUE
Duplicate
I/O area
I/O area range exceeded
Unsupported
Slave
The same I/O word is allocated to two or more slaves. (This occurs whenever a slave that is allocated multiple words has one of the words allocated to the node address of another Slave.)
A slave is allocated an area outside the fixed allocations area.
(This occurs whenever slaves are allocated multiple words and a slave is allocated a word beyond node address 63 in the fixed allocations area.)
The I/O size of a slave exceeds
200 bytes (100 words). (This occurs if either the IN or the OUT size exceeds 200 bytes.)
A Slave registered in the scan list is not present.
The I/O size registered in the scan list does not match the I/O size of the slave.
Reconnect with the error slave and continue remote I/O communications.
Error occurs in either fixed or user-set allocations with the scan list enabled
*_Mstr1VefyE rr (Verification Error) is
TRUE
No slaves present
I/O size mismatched
Incorrect vendor
Incorrect device type
Incorrect product code
Incorrect connection bus
Unsupported connection
Note I/O size is compared in 8point (1-byte) units. If I/O size is registered at 8 points for example, then an error
I/O size mismatch will not occur with a Slave with just one input point connected.
The vendor registered in the scan list does not match the slave vendor.
The device type registered in the scan list does not match the slave device type.
The product code registered in the scan list does not match the slave product code.
The connection bus registered in the scan list is set incorrectly.
The slave does not support the connection registered in the scan list.
Indicators 7-segment indicator d0 MS: Not related
NS:
Flashes red d1 d2 d5 d6 d6 d6 d6 d6 d6
4
4-33 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
4 Remote I/O Master Communications
Condition
Fixed or user-set allocations
Error
I/O communications error
Details
A timeout occurred during remote
I/O communications. (The Slave response timed out 6 times in a row or an error occurred 3 times in a row.)
Results
Reconnect with the error Slave and continue remote I/O communications.*
Network power error
Send timeout
Duplicated node address
Bus OFF detected
Master scan list logic error
The network is not supplying communications power.
A communications request was not successfully completed due to the following reasons:
• There are no devices on the network.
• Baud settings do not match for every node.
• CAN controller error
The master node address is the same address as another node.
Bus OFF error was detected.
The master scan list data is incorrect.
All communications stop
(remote I/O communications stop, slave operation stops, and message communications are disabled).
Remote I/O communications stop
(Slave operation stops, but message communications are enabled).
Indicators 7-segment indicator d9 MS: Not related
NS:
Flashes red
MS: Not related
NS: Goes out
E0
E2
MS: Not related
NS:
Flashes red
MS:
Flashes red
NS: Not related
F0
F1
E8
* Remote I/O communications will stop (7-segment indicator: A0) if DIP switch pin 3 on the front panel is turned
ON to specify stopping remote I/O communications for I/O communications errors.
4-34 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Remote I/O Slave
Communications
This section describes the remote I/O communications performed as a DeviceNet slave by the DeviceNet Unit.
5-1-2 Remote I/O and Slave Communications Specifications . . . . . . . . . . . . . . . . . . 5-3
5-1-3 Procedures for Using Remote I/O Slave Communications . . . . . . . . . . . . . . . 5-4
5-3-2 Settings through Device Variables for CJ-series Unit (Slave User-set
5
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 5-1
5 Remote I/O Slave Communications
5-1 Slave Remote I/O Communications
A CJ-series DeviceNet Unit can function as a Slave Unit in remote I/O communications and a single CJseries DeviceNet Unit can function as both a Master Unit and a Slave Unit. This section describes Slave communications.
z
Slave Communications
CJ-series DeviceNet Unit (Master)
CJ-series CPU Unit
IN area OUT area
Remote I/O communications
DeviceNet
IN area OUT area
NJ-series CPU Unit
CJ-series DeviceNet Unit (Slave)
Slaves
• In the following descriptions, the areas used to transfer data from the master to the slaves are called OUT areas and the areas used to transfer data from the slaves to the master are called the
IN areas.
• In the following descriptions, a CJ-series DeviceNet Unit set to function as a master is referred to as a "Master Unit" and a CJ-series DeviceNet Unit set to function as a slave is referred to as a
"Slave Unit".
5-1-1 Allocation Methods
The specified areas in the memory used for CJ-series Unit of the NJ-series CPU Unit in which a Slave
Unit is installed, are allocated to the Master Unit as DeviceNet slave. They are allocated using one of the following methods:
1) Fixed allocations
2) User-set allocations
To access the OUT/IN Areas that was specified with the above method from the user program, a user-defined variable that specifies the AT specification of that area needs to be defined.
5-2 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
5 Remote I/O Slave Communications
5-1-2 Remote I/O and Slave Communications Specifications
Item
Allocation method
Max. No. of
I/O points per
DeviceNet
Unit slave
Fixed allocations
User-set allocations
User-set allocations
Specifications
Select one of the following fixed allocations areas 1, 2, and 3 using *_Sw2SlavFixAloc1Cmd to
*_Sw2SlavFixAloc3Cmd (Slave Fixed Allocation Setting 1 Switch to Slave Fixed Allocation Setting 3
Switch).
Allocated words (CIO
Area)
I/O Size Fixed Allocation Area
Setting 1
Fixed Allocation Area
Setting 2
Fixed Allocation Area
Setting 3
Output (OUT) area to the slave from the master
Input (IN) area to the master from the slave
3370 3570 3770
3270 3470 3670
Note Select one of the preceding areas with the use of the device variables for CJ-series Unit. All are fixed at 1 word per node address. The default setting is Fixed Allocations Area Setting 1.
By CX-Integrator Set the areas for the OUT 1 and IN 1/2 blocks, the first words, and the slave allocation sizes with the use of the CX-Integrator.
Allocated words The input and output areas can be the following sizes that start from any word in any of the following areas:
CIO Area, WR Area, HR Area, DM Area, or EM Area in the memory used for CJ-series Unit.
Output (OUT) area from this master 100 words
By device variables for CJ-series Unit
Input (IN) area to this master 100 words
Set the areas, the first words, and slave allocation size for the OUT 1 and IN 1 blocks (total of 2 blocks) with the use of the Slave User Allocation Setup Table in the device variables for CJ-series Unit.
Fixed allocations
By device variables for CJ-series Unit
By CX-Integrator
Allocated words The input and output areas can be the following sizes that start from any word in any of the following areas:
CIO Area, WR Area, HR Area, DM Area, or EM Area in the memory used for CJ-series Unit.
Output (OUT) area from this master
Input (IN) area to this master
100 words
100 words
32 points (1 input word, 1 output word)
3,200 pts (100 input words, 100 output words)
4,800 pts (100 input words x 2, 100 output words x 1)
5
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 5-3
5 Remote I/O Slave Communications
5-1-3 Procedures for Using Remote I/O Slave Communications
z
Fixed Allocations for Remote I/O
Switch the CPU Unit to PROGRAM mode.
Change "*_Sw2SlavDsblCmd" (Slave Stop Switch) to TRUE from the Sysmac Studio.
Change "*_Sw2SlavFixAloc1Cmd" to "*_Sw2SlavFixAloc3Cmd"
(Slave Fixed Allocation Setting 1 to 3 Switch) to TRUE from the Sysmac Studio.
Change "*_Sw2SlavEnblCmd" (Slave Enable Switch) to TRUE from the Sysmac Studio.
Define user-defined variables in the area to which I/O data is allocated.
Switch the CPU Unit to RUN mode.
Slave remote I/O communications will begin.
Note Slave communications must be disabled prior to area allocation and must be enabled after area allocation. The order of the procedure is 1) stop slave communications, allocate areas, and then enable slave communications. The allocated areas will not be valid if the procedure is done in any other order.
5-4 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
5 Remote I/O Slave Communications z
User-set Remote I/O Allocations Using the CX-Integrator
Connect the CX-Integrator to the NJ-series CPU Unit.
Switch the CPU Unit to PROGRAM mode.
1) Enable slave communications in CJ1W-DRM21 Properties using the CX-Integrator.
2) Create the device parameters to set slave communications.
3) Save the data as a device parameter file.
4) Read the device parameter file, go online,
and download the file to the DeviceNet Unit
slave.
3) Go online and directly download the device
parameter file to the DeviceNet Unit slave
without saving the file.
Define user-defined variables in the area to which I/O data is allocated.
Switch the CPU Unit to RUN mode.
Slave remote I/O communications will begin.
Note Enable slave communications in CJ1W-DRM21 Properties if the CX-Integrator is used.
5
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 5-5
5 Remote I/O Slave Communications z
User-set Remote I/O Allocations Using Device Variables for CJ-series Unit
Switch the CPU Unit to PROGRAM mode.
Change "*_Sw2SlavDsblCmd" (Slave Stop Switch) to TRUE from the Sysmac Studio.
1) Input data in advance into "*_SlavAlocTblCfg[0]" to "*_SlavAlocTblCfg[5]" (Slave User-set Allocations
Setup Table) and the Allocation Size Setup Table from the Sysmac Studio.
2) Set "*_Sw2SlavAlocCmd" (Slave User Allocations Switch) to TRUE from the Sysmac Studio.
Change "*_Sw2SlavEnblCmd" (Slave Enable Switch) to TRUE from the Sysmac Studio.
Define user-defined variables in the area to which I/O data is allocated.
Switch the CPU Unit to RUN mode.
Slave remote I/O communications will begin.
Note Slave communications must be disabled prior to area allocation and must be enabled after area allocation. The order of the procedure is 1) stop slave communications, allocate areas, and then enable slave communications. The allocated areas will not be valid if the procedure is done in any other order.
In fixed allocation or user-set allocations through the device variables for CJ-series Unit, area allocations must be set with slave communications disabled and will be transferred to Units when slave communications are enabled.
Allocations will not be valid if slave communications are enabled during area allocation.
5-6 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
5 Remote I/O Slave Communications
5-2 Fixed Allocations
5-2-1 Allocated Words
If fixed allocation is used, allocated words are in the following I/O (CIO) area in the memory used for CJseries Unit. You can select words from one of three fixed allocations areas. Use
*_Sw2SlavFixAloc1Cmd to *_Sw2SlavFixAloc3Cmd (Slave Fixed Allocation Setting 1 to 3 Switch) to select the allocation area.
Each area is comprised of an OUT area that is used to write data to the master IN area and an IN area that is used for inputs from the master OUT area in remote I/O communications.
To access the following areas from the user program, user-defined variables that specify the AT specification of these areas need to be defined.
Area Selection method
Fixed allocation area 1
OUT area
(master to slave)
CIO 3370
IN area
(slave to master)
CIO 3270
Fixed allocation area 2
Fixed allocation area 3
CIO 3570
CIO 3770
CIO 3470
CIO 3670
Change *_Sw2SlavFixAloc1Cmd
(Slave Fixed Allocation Setting 1
Switch) to TRUE.
Change *_Sw2SlavFixAloc2Cmd
(Slave Fixed Allocation Setting 2
Switch) to TRUE.
Change *_Sw2SlavFixAloc3Cmd
(Slave Fixed Allocation Setting 3
Switch) to TRUE.
You can include a maximum of 3 CJ-series DeviceNet Units as slaves in a single NJ-series CPU Unit because the three allocation areas above are set individually for fixed allocations. The default setting is fixed allocation area 1.
5
Allocation Procedures
z
Step 1: Set the CPU Unit to PROGRAM Mode.
z
Step 2: Stop Slave Communications
If the Unit already functions as a Slave Unit, change *_Sw2SlavDsblCmd (Slave Stop Switch) to
TRUE to stop slave communications. This step is not necessary if slave communications are stopped.
z
Step 3: Select a Fixed Allocation Area
Change *_Sw2SlavFixAloc1Cmd to *_ Sw2SlavFixAloc3Cmd (Slave Fixed Allocation Setting 1 to 3
Switch) to TRUE to select a fixed allocations area between 1 and 3.
One word is allocated for the output (OUT) area from the Slave Unit to the CPU Unit and another word is allocated for the input (IN) area from the CPU Unit to the Slave Unit in the memory used for
CJ-series Unit, as shown below.
5-7 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
5 Remote I/O Slave Communications
Name of device variables for CJseries Unit
*_Sw2SlavFixAloc1C md
*_Sw2SlavFixAloc2C md
*_Sw2SlavFixAloc3C md
Name
Slave Fixed Allocation
Setting 1 Switch
Slave Fixed Allocation
Setting 2 Switch
Slave Fixed Allocation
Setting 3 Switch
Fixed allocation area
Fixed allocation area 1
Fixed allocation area 2
Fixed allocation area 3
Allocated output
(OUT) area
(master to slave)
CIO 3370
CIO 3570
CIO 3770
Allocated input (IN) area
(slave to master)
CIO 3270
CIO 3470
CIO 3670 z
Step 4: Change the Slave Enable Switch to TRUE
Change *_Sw2SlavEnblCmd (Slave Enable Switch) to TRUE. This will allocated the fixed allocation areas as slave areas and the DeviceNet Unit will start slave remote I/O communications. Slave communications will run automatically after that whenever the power is turned ON.
Fixed Allocations Area Setting 1
CIO Area on memory for CJ-series Units
Bit
CIO 3370
Slave
15
Output (OUT) area
0
Master
OUT area
Bit
CIO 3270
15
Input (IN) area
0
IN area
Fixed Allocations Area Setting 2
CIO Area on memory for CJ-series Units
Bit
CIO 3570
Slave
15
Output (OUT) area
0
Master
OUT area
Bit
CIO 3470
15
Input (IN) area
0
IN area
Fixed Allocations Area Setting 3
CIO Area on memory for CJ-series Units
Master
Bit
CIO 3770
Slave
15
Output (OUT) area
0
OUT area
Bit
CIO 3670
15
Input (IN) area
0
IN area z
Step 5: Define User-defined Variables
Define a user-defined variable for the area to which each slave is allocated. By using the userdefined variable, the user program can access the allocation area of the slave.
5-8 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
5 Remote I/O Slave Communications
5-3 User-set Allocations
With a CJ-series DeviceNet Unit, you can allocate remote I/O communication slaves in any area of a memory used for CJ-series Unit (CIO, WR, HR, DM, or EM) using one of the following methods:
• Setting through CX-Integrator
• Setting through the device variables for CJ-series Unit (Slave User-set Allocations Setup Table) z
User-set Allocations Methods
Method
Areas in memory used for CJseries Unit available for allocations*
No. of allocation blocks
Allocation size Per block
Total size
Connection type
Set through CX-Integrator
Set through the device variables for
CJ-series Unit (Slave User Allocations
Setup Table)
CIO: CIO 0000 to CIO 6143
WR: W000 to W511
HR: H000 to H511
DM: D00000 to D32767
EM: (E € _00000 to E € _32767: € = 0 to C)
3 blocks: OUT 1, IN 1 and IN 2
100 words max.
2 blocks: OUT 1 and IN 1
300 words max. for a total of 3 blocks
Automatic or user specified
200 words max. for a total of 2 blocks
Automatic (connection specified by the master)
* You cannot use Holding Area H512 and its subsequent holding areas, or EM Area Bank D and its subsequent banks.
5
Functions will vary as shown below depending on whether allocations are set through the device variables for CJ-series Unit (Slave User Allocations Setup Table) or through the CX-Integrator.
You can only allocate two blocks (OUT 1 and IN 1) when settings are made with the device variables for CJ-series Unit, but there are three blocks (OUT 1 and IN 1/2) available with the CX-Integrator.
5-3-1 Setting through CX-Integrator
You can allocate a maximum of three blocks at any location in I/O memory for the output (OUT) area block 1, input (IN) area block 1, and input (IN) area block 2.
To access a slave allocated to the memory used for CJ-series Unit from the user program, userdefined variables that specify the AT specification of the memory used for CJ-series Unit to which the slave is allocated must be defined.
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 5-9
5 Remote I/O Slave Communications
Specified areas in memory used for CJ-series Unit
User-set block order
Bit
First word specified
15 0 to
Slave output
(OUT) area 1
Master
OUT area
Bit
First word specified
15 to
Slave input
(IN) area 1
0
IN area
Bit
First word specified
15 to
Slave input
(IN) area 2
0
IN area
You can set the block allocation order and block allocation areas as required. Refer to CX-Integrator
Ver.2.
@ OPERATION MANUAL (Cat. No. W464).
Connection Types
You can specify the type of connection if the CX-Integrator is used for settings. The number of applicable allocation areas varies with the type of connection used.
• You can use a maximum of three areas (OUT 1, IN 1, and IN 2) if you specify multiple connections.
• You can use two allocation areas (OUT 1 and IN 1) if you specify the automatic connection setting or a single connection.
5-10 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
5 Remote I/O Slave Communications z
Connection Types and Allocated I/O Areas
The following table shows the relationship between various connection combinations and the allocated areas that are applicable with those connections.
IN 1 area IN 2 area Specified connection type
Poll
OUT 1 area
Bit-strobe
COS
Cyclic
Poll+bit-strobe
Poll OUT data
Not used
COS OUT data
Cyclic OUT data
Poll OUT data
Poll+COS (See note.) Poll/COS OUT data
Poll+cyclic (See note.) Poll/cyclic OUT data
COS+bit-strobe
Cyclic+bit-strobe
COS OUT data
Cyclic OUT data
Poll IN data
Bit-strobe IN data
COS IN data
Cyclic IN data
Poll IN data
Poll IN data
Poll IN data
COS IN data
Cyclic IN data
Not used
Not used
Not used
Not used
Bit-strobe IN data
COS IN data
Cyclic IN data
Bit-strobe IN data
Bit-strobe IN data
Note With poll + COS connections, the OUT data is the same for poll and COS. Set the same OUT areas for poll and COS connections when you specify the areas with the CX-Integrator.
With poll + cyclic connections as well, the OUT data is the same for poll and cyclic. Set the same OUT areas for poll and cyclic when you specify the areas with the CX-Integrator.
5
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 5-11
5 Remote I/O Slave Communications
5-3-2 Settings through Device Variables for CJ-series Unit (Slave Userset Allocations Setup Table)
You can allocate words for the OUT 1 area (master to Slave Unit) and IN 1 area (Slave Unit to master) from any specified location for the memory used for CJ-series Unit specified in the settings in the device variables for CJ-series Unit. To access a slave allocated to the memory used for CJ-series
Unit from the user program, user-defined variables that specify the AT specification of the memory used for CJ-series Unit to which the slave is allocated must be defined.
Specified areas in memory used for CJ-series Unit
Slave
Master
Bit
First word specified
15 0
OUT 1 area OUT area to
Bit
First word specified
15 to
IN 1 area
0
IN area
5-12
Connection Types
The type of connection cannot be specified when the device variables for CJ-series Unit is used for settings. The master specifies a poll, bit-strobe, COS, or cyclic connection.
Allocation Procedures
Step 1: Set the CPU Unit to PROGRAM Mode.
Step 2: Stop Slave Communications
If the Unit already functions as a slave, change *_Sw2SlavDsblCmd (Slave Stop Switch) to TRUE to stop slave communications. This step is not necessary if slave communications are stopped.
Step 3: Set the Slave User-set Allocations Table
This table is used to specify the areas, first words, and sizes for OUT block 1 and IN block 1 to the device variables for CJ-series Unit below.
• Slave User-set Allocations Setup Table
Name of device variables for
CJ-series Unit
*_SlavAlocTblCfg[0]
*_SlavAlocTblCfg[1]
*_SlavAlocTblCfg[2]
*_SlavAlocTblCfg[3]
Type
UINT
UINT
UINT
UINT
Name
Slave OUT 1 area
First word in slave OUT 1 area
OUT 1 area size
Slave IN 1 area
Range
0 to 20
0 to 32767
0 to 200
0 to 20
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
5 Remote I/O Slave Communications
Name of device variables for
CJ-series Unit
*_SlavAlocTblCfg[4]
*_SlavAlocTblCfg[5]
*_SlavAlocTblCfgSta
Type
UINT
UINT
WORD
Name
First word in slave IN 1 area
IN 1 area size
Setting Results of Slave User-set
Allocations Setup
0
1
3
4
5
8 to 20
• Areas and Word Ranges for the OUT 1/IN 1 Areas
Code
---
Area name in memory for
CJ-series Unit
Word range
CIO Area (CIO)
DM Area (DM)
Word Area (WR)
Holding Area (HR)
The block is not used.
0 to 6143
0 to 32767
0 to 511
0 to 511
Expansion Data Memory (EM)
Bank 0 to C (13 banks)
0 to 32767 (E0_00000 to E0_32767,
... , EC_00000 to EC_32767) for all banks
Range
0 to 32767
0 to 200
16#0000 to
FFFF
Note You cannot use Holding Area H512 and its subsequent holding areas, or EM Area Bank D and its subsequent banks.
Step 4: Change the Slave User-set Allocations Switch to TRUE
Change *_Sw2SlavAlocCmd (Slave User Allocations Switch) to TRUE.
Step 5: Change the Slave Enable Switch to TRUE
Change *_Sw2SlavEnblCmd (Slave Enable Switch) to TRUE. This will allocate the above areas as slave areas and the DeviceNet Unit will start slave remote I/O communications.
Note Once slave communications are enabled by changing the Slave Enable Switch to TRUE, the
Unit will continue to perform slave communications even after the power is turned OFF and back ON again.
Slave User Allocations Setup Table
Name of device variables for CJ-series Unit
*_SlavAlocTblCfg[0]
*_SlavAlocTblCfg[1]
*_SlavAlocTblCfg[2]
*_SlavAlocTblCfg[3]
*_SlavAlocTblCfg[4]
*_SlavAlocTblCfg[5]
Name
Slave OUT 1 area
First word in slave OUT 1 area
OUT 1 area size
Slave IN 1 area
First word in slave IN 1 area
IN 1 area size
Specify the first word.
Specify the size.
Specify the first word.
Slave output (OUT) area
Bit 15 0
First word specified to to
Master
OUT area
5
Specify the size.
Bit
First word
Slave input (IN) area
15 0 specified to to
Master
IN area
: Specify the first word.
: Specify the size.
Example Settings for User-set Allocations through Device Variable for CJ-series Unit
This example uses the following settings for unit number 0.
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 5-13
5 Remote I/O Slave Communications
• OUT block 1 area and first word: WR (4), 50 (50CH (50)), 20-byte size = 10 words (20)
• IN block 1 area and first word: WR (4), 100 (100CH (100)), 10-byte size = 5 words (10)
• Slave User-set Allocations Setup Table
Name of device variables for CJ-series Unit
*_SlavAlocTblCfg[0]
*_SlavAlocTblCfg[1]
*_SlavAlocTblCfg[2]
*_SlavAlocTblCfg[3]
*_SlavAlocTblCfg[4]
*_SlavAlocTblCfg[5]
• Slave areas
OUT area 1
Name
Slave OUT 1 area
First word in slave OUT 1 area
OUT 1 area size
Slave IN 1 area
First word in slave IN 1 area
IN 1 area size
Value (meaning)
4 (Work Area)
50 (W050)
20 (10 words)
4 (Work Area)
100 (W100)
105 (5 words)
IN area 1 to
Step 1: Change the Slave User-set Allocations Switch to TRUE
Make sure that slave communications have stopped prior when you perform this operation. Change
*_Sw2SlavAlocCmd (Slave User Allocations Switch) to TRUE.
Step 2: Change the Slave Enable Switch to TRUE
Change *_Sw2SlavEnblCmd (Slave Enable Switch) to TRUE. This will allocate the above areas as slave areas and the DeviceNet Unit will start slave remote I/O communications.
5-14 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Message Communications
This section describes explicit message communications sent from the user program in the CPU Unit.
6-2-2 Sending Explicit Messages Using SendCmd Instruction . . . . . . . . . . . . . . . . 6-11
6
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 6-1
6 Message Communications
6-1 Overview
Message communications enable messages to be set between nodes on a DeviceNet network when required by system conditions. It is possible for messages to be sent between a PLC and a DeviceNet master or slave made by another company. You can use them to send/receive data; read time data, error logs, and other data; or control operation, e.g., refreshing with user-specified values.
There is one type of messages: Explicit messages.
6-1-1 Outline of Message Communications
Overview
Remote devices
Features
Explicit message communications
General-purpose message communications that uses DeviceNet protocol
• DeviceNet masters and slaves from other companies
• C200H-series DeviceNet Units, CVM1/CV-series DeviceNet Units, and CS/CJ-series DeviceNet
Units
• Message communications with DeviceNet devices from other companies can be performed.
• Explicit messages from OMRON PLCs (with C200H-series DeviceNet Units and CVM1/
CV-series DeviceNet Units) can be received. Explicit messages can be sent to OMRON PLCs
(with C200H I/O Link Units).
Message communications functions
Explicit message communications function
Send
Receive z
Overall Structure
NJ-Series CPU Unit DeviceNet Unit
SendCmd instruction
(2801 Hex)
2801 Explicit message
Explicit message function
DeviceNet network
DeviceNet message communications
Explicit message
Additional Information
If only the message communications function is being used and the remote I/O communications function is not being used, message communications are possible even if the master function is disabled. In this case, it is not necessary to register a scan list.
6-2 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
6 Message Communications
6-1-2 Explicit Message Communications
You can send service requests to DeviceNet masters and slaves made by other manufacturers and
OMRON slaves (C200H I/O Link Units, CS-series DeviceNet Units, etc.) with the use of explicit messages defined for DeviceNet.
Service requests to read/write CPU Unit status and I/O memory can also be received from PLCs with
C200H-series DeviceNet Units (C200HW-DRM21-V1), PLCs with CVM1/CV-series DeviceNet Units
(CVM1-DRM21-V1), PLCs with CS/CJ-series DeviceNet Units, and DeviceNet masters made by other manufacturers using explicit messages.
Additional Information
A specific command (2801) is used to send explicit messages.
Item
Network communications instruction
Remote devices and supported functions
Sending
You can use the SendCmd instruction using command code 2801 hex to send explicit messages to
DeviceNet Units.*
• DeviceNet masters and slaves made by other manufacturers. Supported services determine supported functions.
Receiving
Automatically responds to explicit messages from other devices.
• DeviceNet masters made by other manufacturers
• PLCs with CS/CJ-series DeviceNet Units.
• PLCs with C200H-series DeviceNet Master
Units.
• PLCs with CVM1/CV-series DeviceNet Master
Units.
• All listed devices support status read/write and
I/O memory read/write for the local CPU Unit.
* A specific command (2801) is used to send explicit messages.
Additional Information
This CJ-series DeviceNet Unit (CJ1W-DRM21) contains a PLC Object so that the I/O memory of the CPU Unit of this DeviceNet Unit can be read/written from other devices. The C200H I/O Link
Unit (C200HW-DRT21) and CS-series DeviceNet Unit (CS1W-DRM21(-V1)) also contain a PLC
Object so that you can read/write the I/O memory of the CPU Unit of the C200H I/O Link Unit from other devices. The C200HW-DRM21-V1 and CVM1-DRM21-V1 DeviceNet Master Units, however, do not have PLC Objects, the I/O memory of the CPU Unit for these Units cannot be read or written from other devices.
6
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 6-3
6 Message Communications
6-1-3 Message Communications Specifications
Supported CPU Unit functions
Unit model number
Max. No. of communications nodes per Unit
Explicit messages
Communications instructions Explicit
DeviceNet messages
Sources: destinations
Data length (excluding command code)
Response monitoring time
Retries
Message monitor timer function (explicit message communications)
CJ1W-DRM21
63
SendCmd instruction
Specification
Sends explicit messages to DeviceNet masters/slaves made by other manufacturers, PLCs with C200H I/O Link Units, or PLCs with CS/CJseries DeviceNet Units mounted to them.
1:1 (Broadcasting is not supported)
SendCmd instruction: 542 bytes max.
Default setting: 2 s
User setting: 0.1 to 6553.5 s
0 to 15
You can set the response monitoring time for DeviceNet Units during explicit message communications (the interval the explicit connection is open) from the CX-Integrator for each device. (The settings for all devices can be stored in the DeviceNet Unit. This is called the Message Monitoring Timer List.)
6-4 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
6 Message Communications
6-1-4 Message Communications Error Indications
There are two ways to obtain information on communications errors that occur in message communications: 1) Using the error history in the DeviceNet Unit and 2) Using DeviceNet Unit displays, indicators, and Master Status Areas.
1
Each time a communications error occurs, an error code is placed in an error record in the error history kept in the RAM of the DeviceNet Unit. Up to 96 records can be stored in the error history. The time and date the record occurred is also recorded.
Code
Code
Can be monitored from the CX-Integrator.
96 records
Code
Master
Unit
Monitor CX-Integrator
2
You can use the MS and NS indicators and the 7-segment indicator on the front panel of the
DeviceNet Unit together with the *_Unit1Sta (Unit Status 1) in the CPU Unit to obtain information on a communications error that has occurred. This information can be used as the basis for troubleshooting.
MS
NS
Example: Routing table error
Flashing red
MS
NS
Not relevant
*_Unit1Sta
(Unit Status 1)
NJ-Series
CPU Unit
Master
Unit
6
6-1-5 Message Monitoring Timer
A message monitoring timer monitors responses for the DeviceNet Unit. A timer can be set for each device that will be communicated with (each message destination).
You can set the timers with the CX-Integrator. The default setting is 2 seconds (2,000 ms). The setting range is 500 to 30,000 ms.
If the response from the remote communications device (message destination) is slow, the timer setting must be increased. The next message cannot be sent to the same communications device during the response waiting time, so the setting should not be set too high.
The DeviceNet Unit uses this timer to monitor message timeouts. The CPU Unit performs the monitoring based on the response monitoring time for SendCmd instruction. There will be no effect, therefore, if either the message monitoring timer or the response monitoring time for SendCmd instruction setting only is increased or decreased. Both must be increased or decreased for there to be an effect.
Set the response monitoring time for the SendCmd instruction the same as or longer than the message monitoring timer, i.e., Response monitoring time for the SendCmd instruction
≥
Message monitoring timer.
If a lot of timeouts occur, maintain this relationship but lengthen the time for both.
6-1-6 Message Communications Errors
The following table shows the main errors that occur when messages are sent or received. Refer to
Section 9 Troubleshooting and Maintenance
for countermeasures and errors recorded in error history that are not shown by the indicators.
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 6-5
6 Message Communications
Network power error
Send timeout
Routing table error
Bus Off detected
Error
Node address duplicated
CPU Unit service monitoring error
Other CPU error
Local node not part of network; cannot send
No. of retries limit exceeded; cannot send
Remote device busy; cannot send
Header error; cannot send
Reception buffer full; message destroyed
Illegal message received; received message destroyed
Local node busy; cannot send
MS
No change
Flashing red
Indicators
NS
Not lit
No change
No change Lit red
7-segment indicator*
E0
E2
HC
F0
Unit status 1 Error history code
*_NetPwrErr is 1.
*_SendTimeo utErr is 1.
*_RTblErr is
1.
*_NdAdrDupE rr is 1.
F1 *_BusoffErr is
1.
Flashing red
Not lit HE ––
H7
No change No change No change ––
(Hex)
0341
0342
021A
0211
0340
0002
0006
0101
0103
0109
0112
0117
0118
0119
* The 7-segment indicator alternately displays the error and the master node address where the error occurred.
6-6 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
6 Message Communications
6-2 Sending Explicit Messages
CJ-series DeviceNet Units can send explicit messages. Explicit messages can be sent to the following destinations.
• DeviceNet masters or slaves made by other manufacturers
• CS/CJ-series DeviceNet Unit
Example
NJ-series CPU Unit
CJ-series DeviceNet Unit
Other manufacturer DeviceNet master or slave or CJ-series DeviceNet Unit
Explicit messages can be sent
Explicit message
DeviceNet
6
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 6-7
6 Message Communications
6-2-1 Sending Explicit Messages
The command code 28 01 can be used to send explicit DeviceNet messages to OMRON special slaves and DeviceNet masters/slaves made by other manufacturers.
NJ-series CPU Unit
Explicit message
Header
DeviceNet Unit
Header Explicit message
OMRON special slaves or
Slave or Master by other manufacturer
SendCmd DeviceNet network Use 28 01 for the command code.
Header Response
Header
Response
The local DeviceNet Unit is specified as the destination in the communications instruction in the PLC's user program (not the OMRON Special Slave or DeviceNet device made by another manufacturer), and the node address of the actual destination (i.e., the DeviceNet Slave or Master made by another manufacturer) is specified in the command data for the explicit message send command.
Command
CPU Unit
Send
Cmd
SendCmd instruction:
Input variable DnetAdr :
InDNetAdr.NetNo
: Destination network address. Set 0 (local network).
InDNetAdr.NetNo
: Destination node address. Set 0 (communications within local PLC).
InDNetAdr.UnitNo
: Destination unit address. Set unit number +16#10.
Explicit message
OMRON special slave or master not by OMRON or slave not by OMRON
Depending on the network status, the destination slave may not always accept an explicit message. Always perform retry processing when sending explicit messages.
6-8
EXPLICIT MESSAGE SEND (28 01)
EXPLICIT MESSAGE SEND will send an explicit DeviceNet message to the specified class and receive a response.
z
Command Block
28 01 534 bytes max.
Command
Code
Class ID
Service Code
Destination Node Address
Instance ID Service Data
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
6 Message Communications z
Response Block
Normal Response
28 01 00 00 534 bytes max.
Command
Code
Response
Code
No. of Byte
Received
Service Data
Service Code
Destination Node Address (remote node)
Error Responses
The following response is returned if an error occurs for the explicit message.
28 01 00 00 94
Command
Code
Response No. of Bytes
Code Received
Error Code
Service Code 94 (Hex)
Destination Node Address (remote node)
The following response is returned if the explicit message cannot be sent or times out.
28 01
Command received
Response received z
Parameters
Destination Node Address (command): The node address of the destination of the explicit message. The node address of the local Master Unit is specified as the input variables DstNetAdr (Destination network address) in the SendCmd instruction when the Explicit Message Send command is sent, but the node address of the actual destination is specified here.
Service Code (command, response): A service code defined for DeviceNet. In a normal response, bit 15 of the service code specified in the command will be TRUE and returned. In an error response, 94 Hex will always be returned.
Class ID (command): The class ID of the destination of the explicit message.
Instance ID (command): The instance ID of the destination of the explicit message.
Service Data (command, response): In command, the data defined by the service codes are specified. In response, the receive data defined by the service codes are returned.
No. of Bytes Received (response): The number of bytes received from the destination node address (remote node).
Destination Node Address (remote node) (response): The node address of the remote device to which the explicit message was sent is returned.
Error Code (response): An error code defined by DeviceNet.
z
Explanation
• This command sends a DeviceNet-defined explicit message to a DeviceNet Slave manufactured by another company and receives a response.
• When the Explicit Message Send command is sent, specify the DeviceNet Master Unit of the local node address as the destination of the input variable DstNetAdr (Destination network address) in the SendCmd instruction, and specify the node address of the actual destination by the "Destination Node Address" in the Explicit Message Send command.
Be sure to specify the Master Unit of the local node address as the input variables DstNetAdr
(Destination network address) in the SendCmd instruction. If the Master Unit of any other node address is specified, an error will occur.
• If the DeviceNet Master receives an explicit message, it will automatically return a response.
6
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 6-9
6 Message Communications z
Service Data
Word (2-byte) data and double-word (4-byte) data in the Service Data (such as channel data and error clear codes) shall conform to the command format of specifying the lower byte (L) first, followed by the higher byte (H). Example) To specify word data 16#1234, specify 16#34 first, and then 16#12. To specify double-word data 16#12345678, specify 16#78, 16#56, 16#34, and 16#12, in this order.
Command Format Example
Eg. For 16#1234 Eg. For 16#12345678
34 12 78 56 34 12
Service Data Service Data
Accordingly, set data in the SendCmd instruction as follows.
Example: 16#1234
From higher byte
Bit 15
S+n 34
08 07
12
00
Example: 16#12345678
From higher byte
Bit 15 08 07 00
S+n 78 56
34 12
Bit
S+n
From lower byte
15 08 07 00
34
Bit
S+n
From lower byte
15 08 07 00
78
12 56 34
12
Similarly when word (2-byte) data or double-word (4-byte) data in the Service Data is returned, the response format is to return the lower byte (L) first, followed by the higher byte (H).
Additional Information
• Since data in the Service Data is stored in the little endien order when used in the response format, these word (2-byte) data and double-word (4-byte) data must be converted using the
AryBTo instruction. Refer to the NJ-series Instructions Reference Manual (Cat. No. W502.)
• Contact the ODVA to obtain copies of the DeviceNet specification.
ODVA's URL: http://www.odva.org/
6-10 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
6 Message Communications
6-2-2 Sending Explicit Messages Using SendCmd Instruction
The SendCmd (send command) instruction can be used in the CPU Unit user program of the CJ-series
DeviceNet Unit to send explicit messages.
The explicit message command data that contains the command code 2801 hex at its beginning is sent.
The explicit message response is received after the command code 2801 hex and the end code.
In a program that issues explicit messages, the following execution conditions are generally used based on the AND gate:
1) Network Enabled Flag on the CPU Unit side
2) *_OnlineSta (Online Flag) or *_CMstrMsgEnblSta (Message Communications Permitted Flag) on the
DeviceNet Unit side
Execution Condition _Port_isAvailable *_OnlineSta sample
SendCmd
Execute
DstNetAdr
CommPort
CmdDat
CmdSize
RespDat
Option
Done
Busy
Error
ErrorID
ErrorIDEx
RespDat z
Example: Sending Explicit Messages Using SendCmd Instruction
NJ series CPU Unit
DeviceNet Unit No. 0
6
SendCmd
Node address 05
Unit address 10 Hex
Explicit message Slave node 11
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 6-11
6 Message Communications z
Operation
Here, an example of reading the vendor code (OMRON vendor code: 002F hex) from the DeviceNet slave (unit address: 16#10).
Destination Command source
Sdata[0]
Sdata[1]
SendCmd
Execute Done
DstNetAdr Busy
CommPort
CmdDat
CmdSize
RespDat
Option
Error
ErrorID
ErrorIDEx
RespDat
Sdata[7]
Sdata[8]
Rdata[0]
Rdata[1]
SendCmd
Response
Command code interpretation
Execution
Rdata[8]
Rdata[9]
Input Variable
Execute
DstNetAdr
CommPort
CmdDat
CmdSize
RespDat
Option
Function
The operation SendCmd is executed when TRUE is set.
The destination network address is specified with the use of the network address/node address/unit address.
The destination port is specified.
Sdata[0] Command code
Sdata[1]
Sdata[2] Slave node address (11)
Sdata[3]
Sdata[4]
Sdata[5]
Sdata[6]
ServiceCode
ClassID
InstanceID
Example Details
---
Network address: 0
Node address: 0
Unit address: 16#10
NONE (Default)
16#28
16#01
16#0B
16#0E
16#00
16#01
16#00
Sdata[7]
Sdata[8] AttributeID
The number of bytes corresponding to the command data to be sent is specified.
Command code
16#01
16#01
9
Rdata[0]
Rdata[1]
Rdata[2]
Rdata[3]
End code
16#28
16#01
16#00
16#00
Rdata[4]
Rdata[5]
Rdata[6]
Rdata[7]
Number of bytes received
Slave node address (11)
ServiceCode (when completed normally)
Vendor code
16#00
16#04
16#0B
16#8E
Rdata[8]
Rdata[9]
16#2F
16#00
Response monitoring, and number of resends, are specified.
ResponseTime = 20
Retry = 2
6-12 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
6 Message Communications
Additional Information
You can send explicit messages to OMRON slaves and DeviceNet devices made by other manufacturers by setting the command code to 28 01.
In this case, set the response monitoring time to at least the value set for the message monitoring timer (default: 2s). If it is set to less than the value, communications may be busy even if the next command is executed after the first one times out.
z
Unit Settings
Name
Unit Configuration
Device name of this unit
Unit number
Special Unit Setup
Setting target
CPU/Expansion Racks under
Controller Configurations and
Setup of Sysmac Studio
Settings
Mount CJ1W-DRM21 in slot 0 of the
CPU Rack.
"DeviceNet"
Unit number 0 Unit No. Switch and Unit Configuration and Setup
(CPU/Expansion Racks under
Controller Configurations and
Setup of Sysmac Studio)
System setup data Not required z
Program Example
System-defined variable
Name
_Port_isAvailable
Data type
BOOL ---
Default Comments
Communications Port
Enabled Flags
Details
TRUE when there are internal logical ports available, FALSE when there is no internal logical port available.
6
User-defined variables (Define before or when creating a program)
Name
Trigger
OperatingEnd
Operating
InDNetAdr
InOption
Sdata
Rdata
RS_instance
SendCmd_instance
BOOL
BOOL
BOOL
Data type
_sDNET_ADR
Default
False
False
False
(NetNo := 0, NodeNo := 0,
UnitNo := 16#0)
_sRESPONSE (isNonResp := False, TimeOut :=
0, Retry := 0)
ARRAY[0..8] OF BYTE [9(16#0)]
ARRAY[0..9] OF BYTE [10(16#0)]
RS
SendCmd
---
---
Details
Execution conditions
Process completed
Processing
Destination network address
Response monitoring and retry setting
Send data
Receive data
---
---
Device variables for CJ-series Unit (Create on the I/O Map View window after the unit configuration is created)
Name
DeviceNet_Online
Sta
Data type
BOOL ---
Default
Allocated address (AT)
IOBus://rack#0/slot
#0/Unit2Sta/Online
Sta
Comments
Online Status
Details
TRUE when the
Unit is online.
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 6-13
6 Message Communications
Determining the SendCmd instruction execution completion
SendCmd_instance.Done
SendCmd_instance.Error
Trigger reception
Trigger _Port_isAvailable DeviceNet_OnlineSta
OperatingEnd
RS_instance
RS
Set Q1
Reset1
Communications parameters settings
Operating
1 InDNetAdr.NetNo:=0;
2 InDNetAdr.NodeNo:=0;
3 InDNetAdr.UnitNo:=BYTE#16#10;
4 InOption.isNonResp:=FALSE;
5 InOption.TimeOut:=20;
6 InOption.Retry:=2;
7 Sdata[0]:=BYTE#16#28;
8 Sdata[1]:=BYTE#16#01;
9 Sdata[2]:=BYTE#16#0B;
10 Sdata[3]:=BYTE#16#0E;
11 Sdata[4]:=BYTE#16#00;
12 Sdata[5]:=BYTE#16#01;
13 Sdata[6]:=BYTE#16#00;
14 Sdata[7]:=BYTE#16#01;
15 Sdata[8]:=BYTE#16#01;
//
//
//
//
//
//
//
//
// Network address settings
//
//
// Response monitoring and retry settings
//
//
// Command data settings
SendCmd instruction execution
Operating
InDNetAdr
_ePORT#_NONE
Sdata[0]
UINT#9
Rdata[0]
InOption
SendCmd_instance
SendCmd
Execute Done
DstNetAdr
CommPort
Busty
Error
CmdDat
CmdSize
RespDat
Option
ErrorID
ErrorIDEx
RespDat
Processing at normal end
Operating SendCmd_instance.Done
1
2 ;
// Processing after normal end
OperatingEnd
Operating
Processing at an error completion
Operating SendCmd_instance.Error
1
2 ;
// Processing after an error completion
6-14 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
6 Message Communications
The message service function does not guarantee that a given message will reach the remote node. Messages may be lost during communication due to noise, etc. When the message service function is used, normally the node that issues an instruction performs resend to avoid the above condition. With the SendCmd instruction, the resend process is performed automatically when the number of resends is specified. For the number of resends, be sure to specify a value other than 0.
6
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 6-15
6 Message Communications
6-3 Receiving Explicit Messages
CJ-series DeviceNet Unit contains a PLC Object. The Unit will receive messages addressed to the PLC
Object, process service requests addressed to the CPU Unit, and return responses.
The following services are provided by the PLC Object.
• CPU Unit status read/write
• CPU Unit I/O memory read/write
The explicit messages can be received from the following sources:
• DeviceNet masters made by other manufacturers
• PLCs with C200H-series DeviceNet Master Units (C200HW-DRM21-V1)
• PLCs with CVM1/CV-series DeviceNet Master Units (CVM1-DRM21-V1)
• NJ-series PLCs with CJ-series DeviceNet Units
• CS/CJ-series PLCs with CS/CJ-series DeviceNet Units z
Example
NJ-series CPU Unit
CJ-series DeviceNet Unit
Explicit messages can be received
C200H-series DeviceNet Master Unit
C200HX/HG/HE
CPU Unit
DeviceNet master made by other manufacturers
Explicit message
DeviceNet
Note Status and the I/O memory read/write operations cannot be performed for PLCs with a
C200H-series or CVM1/CV-series DeviceNet Master Units. The CPU Unit of a CS/CJ-series
DeviceNet Unit can also send an explicit message to read/write I/O memory of PLCs with
C200H I/O Link Units.
6-16 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
6 Message Communications
6-3-1 List of PLC Object Services
PLC Objects provide the following services.
z
Status Read/Write for CPU Units
Services
CPU Unit Information Read
CPU Unit Write
CPU Unit Status
Read
Service code
0E Hex
10 Hex
40 Hex
Class ID Instance ID Request service data
2F Hex 00 Hex Attribute ID =
64 Hex
Attribute ID =
65 Hex
Attribute ID =
66 Hex
Attribute ID =
64 Hex,
Attribute Value
Attribute ID =
65 Hex
Attribute Value
None
Contents
Reads the operating mode of the
CPU Unit.
Reads if there is a Controller error the CPU Unit.
Reads CPU Unit model.
Changes the operating mode of the
CPU Unit.
Clears errors.
Reads the detailed status of the CPU
Unit.
Operation status: Stop, run
Operating modes: PROGRAM, RUN z
I/O Memory Read/Write for CPU Units
Service
Word Data
Read
Word Data
Write
Service code
Byte Data Read 1C Hex
1D Hex
Byte Data Write 1E Hex
1F Hex
Class ID
2F Hex
Instance ID
Specifies area (01 Hex to 14 Hex)
Request service data
Address,
No. of read bytes
Address,
No. of read words
Address, word data
Address word data
Contents
Reads the specified node data in byte units. The word data is read in order, from high to low bytes.
Read data: 200 bytes max.
Reads the specified node data in word units. The word data is read in order, from low to high bytes.
Read data: 100 words max.
Writes the specified node data in byte units.
The word data is specified in order, from high to low bytes.
Write data: 200 bytes max.
Writes the specified node data in word units. The word data is specified in order, from low to high bytes.
Write data: 100 words max.
The commands and responses for the explicit messages that can be sent and received are described on the following pages.
In the following command and response formats, all boxes represents 1 byte.
6
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 6-17
6 Message Communications
Information Read for CPU Units (Service Code: 0E Hex)
Reads CPU Unit information, including Operating Mode, Controller Errors, and the CPU Unit model.
z
Command Block
0E 2F
(*)
00
(*)
Class ID
Service Code
Attribute ID
Instance ID
Note A body format of either 8 bits or 16 bits is possible.
z
Response Block
8E
Service Code
Attribute Value z
Parameters
Service Code (command, response): 0E Hex is specified for commands. For responses, the highest bit be ON and 8E Hex will be returned.
Class ID (command): Always 2F Hex.
Instance ID (command): Always 00 Hex.
Attribute ID (command): The read information is specified by the attribute ID. The attribute IDs are listed in the following table.
64
65
66
Attribute ID (Hex) Contents Attribute value size
CPU Unit operating mode 1 word (2 bytes)
CPU Unit controller errors 1 word (2 bytes)
CPU Unit model 22 bytes
• CPU Operating Mode (when Attribute ID = 64 Hex)
Reads the CPU Unit operating mode.
• CPU Unit Errors (when Attribute ID = 65 Hex)
Reads if there are any major fault controller errors in the CPU Unit.
• CPU Unit Model (when Attribute ID = 66 Hex)
Reads the CPU Unit model.
Read Data (response): The specified information is returned in order.
• CPU Unit operating mode (attribute ID = 64 Hex).
The CPU Unit operating mode is returned in 1-word (2-byte) hexadecimal format, as follows:
0001 hex: "Program" Mode, 0002 hex: "RUN" Mode
0
PROGRAM mode
RUN mode
6-18 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
6 Message Communications
Note The codes for the above modes are 1-word (2-byte) data and are returned in low byte first.
For example, for PROGRAM mode, the code is returned as 01 Hex followed by 00 Hex.
• CPU Unit Errors (when Attribute ID = 65 Hex)
The CPU Unit controller error data is returned in 1-byte (2-digit) hexadecimal format.
01 hex: Controller Error, 00 hex: No Controller Error.
1: Controller error
• CPU Unit Model (when Attribute ID = 66 Hex)
The CPU Unit model is returned in ASCII.
Size: 2 bytes (Always 1400 Hex) + Model: 20 bytes (fixed). Unused area is filled with 20 Hex
(spaces) and returned.
20 bytes
B y t e B y t e B y t e B y t e B y t e
Unit name
CPU Unit Write (Service Code: 10 Hex)
This PLC Object service writes CPU Unit information, including the operating mode and clearing errors.
z
Command Block
10 2F
(*)
00
(*) 6
Class ID
Service Code
Attribute ID
Instance ID Attribute Value
Note A body format of either 8 bits or 16 bits is possible.
z
Response Block
90
Service Code z
Parameters
Service Code (command, response): 10 Hex is specified for commands. For responses, the highest bit will turn ON and 90E Hex will be returned.
Class ID (command): Always 2F Hex.
Instance ID (command): Always 00 Hex.
Attribute ID (command): Information to write is specified by the attribute ID. The attribute IDs are listed in the following table.
Attribute ID (Hex)
64
65
Contents Attribute value size
CPU Unit operating mode 1 word (2 bytes)
CPU Unit errors 1 word (2 bytes)
• CPU Operating Mode (Attribute ID = 64 Hex)
Changes the CPU Unit operating mode.
The Attribute Values are as follows:
0001 hex: "Program" Mode, 0002 hex or 0004 hex : "Run" Mode
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 6-19
6 Message Communications
Note The specified code for the above operating modes are 1-word (2-byte) data, and are specified with the low byte first. For example, for PROGRAM mode, the code is specified as 01
Hex followed by 00 Hex. Accordingly, the low to high bytes for the above codes are set as high to low bytes in I/O memory, when setting the input variable CmdDat of the SendCmd instruction as data.
Additional Information
NJ-series CPU Units do not support the "CPU Unit Error Reset" command. For details on the error reset, refer to the NJ-series Troubleshooting Manual (Cat. No. W503).
6-20 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
6 Message Communications
CPU Unit Status Read (Service Code: 40 Hex)
This PLC Object service reads detailed status (operation status, operating mode) from the CPU
Unit.
z
Command Block
40 2F
(*)
00
(*)
Service Code Instance ID
Class ID
Note A body format of either 8 bits or 16 bits is possible.
z
Response Block
C0
Service Code
Detailed status z
Parameters
Service Code (command, response): 40 Hex is specified for commands. For responses, the highest bit will turn ON and C0 Hex will be returned.
Class ID (command): Always 2F Hex.
Instance ID (command): Always 00 Hex.
Read Data (response): The read data is given in the following table. The data is returned after the service code in the order shown in the table (high to low).
Operation Status
RUN mode
00 Hex
00 Hex
00 Hex
00 Hex
00 Hex
00 Hex
00 Hex
00 Hex
ASCII with 20 hex (space) in 16 bytes
• Operation status: Returns the operation status of the CPU Unit in 1-byte (2-digit) hexadecimal.
00 Hex: "Stop" Mode, 01 Hex: "Run" Mode
• Operating mode: Returns the operating mode of the CPU Unit in 1-byte (2-digit) hexadecimal.
00 Hex: "Program" Mode, 04 Hex: "Run" Mode
6
Byte Data Read (Service Code: 1C Hex)
Byte Data Read reads any I/O memory area data in the memory used for CJ-series Unit in a CPU Unit with a CJ-series DeviceNet Unit mounted. The read word data is in byte units. The response block is returned from high to low bytes.
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 6-21
6 Message Communications
6-22 z
Command Block
1C 2F
(*) (*)
Class ID
Service Code
Address L
Instance ID
No. of bytes read
Address H
* A body format of either 8 bits or 16 bits is possible.
z
Response Block
9C
Service Code Word data L
Word data H
Word data L
Word data H
Read data (200 bytes max.) z
Parameters
Service Code (command, response): 1C Hex is specified for commands. For responses, the highest bit will turn ON and 9C Hex will be returned.
Class ID (command): Always 2F Hex.
Instance ID (command): The type of area in the memory used for CJ-series Unit that will read the data is specified as shown in the following table.
Instance ID (Hex)
01
03
04
05
08 to 14
CPU Unit memory area for read
CIO
DM
WR
HR
EM, banks 0 to C
Word range
CIO 0000 to CIO 6143
D00000 to D32767
W000 to W511
H000 to H511
En_00000 to En_32767
(n: 0 to C)
Address L, Address H (command): The address of the first word from which to read the data is specified in hexadecimal as shown below.
Address L: The lower 2 digits when the first word address is given in 4-digit hexadecimal.
Address H: The higher 2 digits when the first word address is given in 4-digit hexadecimal.
No. of Read Bytes (command): The number of bytes of read data is specified in 1-byte (2-digit) hexadecimal. The range is 01 to C8 Hex (1 to 200 decimal).
No. of Bytes Received (response): The number of bytes received from the destination node address (remote node) is returned in hexadecimal.
Destination Node Address (response): The node address of the CJ-series DeviceNet Unit that returned the response is returned in hexadecimal.
Read Data (response): The specified area, word, and byte data is returned in order from word H
(high byte: bits 8 to 15) to word L (low byte: bits 0 to 7). If an odd number is specified for the number of read bytes, the last 1 byte of data will be read to the high word.
z
Important Points
The actual address L, address H, and number of read bytes that can be specified depends on the model of the CPU Unit of the CJ-series DeviceNet Unit and the type of memory area. Do not exceed the boundary of the data areas for the CPU Unit you are using.
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
6 Message Communications
Word Data Read (Service Code: 1D Hex)
Word Data Read reads any I/O memory area data in the memory used for CJ-series Unit in a CPU Unit with a CJ-series DeviceNet Unit mounted. The read word data is in word units. The response block is returned from low to high bytes.
z
Command Block
1C 2F
(*) (*)
Class ID
Service Code
Address L
Instance ID
No. of words read
Address H
* A body format of either 8 bits or 16 bits is possible.
z
Response Block
9D
Service Code Word data H
Word data L
Word data H
Word data L
Read data (200 bytes max.) z
Parameters
Service Code (command, response): 1D Hex is specified for commands. For responses, the highest bit will turn ON and 9D Hex will be returned.
Class ID (command): Always 2F Hex.
Instance ID (command): The type of area in the memory used for CJ-series Unit that will read the data is specified as shown in the following table.
Instance ID (Hex)
01
03
04
05
08 to 14
CPU Unit memory area for read
CIO
DM
WR
HR
EM, banks 0 to C
Word range
CIO 0000 to CIO 6143
D00000 to D32767
W000 to W511
H000 to H511
En_00000 to En_32767
(n: 0 to C)
Address L, Address H (command): The address of the first word to read the data from is specified in hexadecimal as shown below.
Address L: The lower 2 digits when the first word address is given in 4-digit hexadecimal.
Address H: The higher 2 digits when the first word address is given in 4-digit hexadecimal.
No. of Read Words (command): The number of words of read data is specified in 1-byte (2-digit) hexadecimal. The range is 01 to 64 Hex (1 to 100 decimal).
Read Data (response): The specified area, word, and byte data is returned in order from word L
(low byte: bits 0 to 7) to word H (high byte: bits 8 to 15).
z
Important Points
The actual address L, address H, and number of write data bytes that can be specified depends on the CPU Unit of the CJ-series DeviceNet Unit and the Memory Area. Do not exceed the boundary of the data areas for the CPU Unit you are using.
6
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 6-23
6 Message Communications
6-24
Byte Data Write (Service Code: 1E Hex)
Byte Data Write writes data to any I/O memory area in the memory used for CJ-series Unit in a CPU
Unit with a CJ-series DeviceNet Unit mounted. The write word data is in byte units. The command block is specified from high to low bytes, as shown in the following diagram.
z
Command Block
1E 2F
(*) (*)
Class ID
Service Code
Address L
Instance ID
Word data H
Address H Word data L
Word data H
Word data L
Write data (200 bytes max.)
* A body format of either 8 bits or 16 bits is possible.
z
Response Block
9E
Service Code z
Parameters
Service Code (command, response): 1E Hex is specified for commands. For responses, the highest bit will turn ON and 9E Hex will be returned.
Class ID (command): Always 2F Hex.
Instance ID (command): The type of area in the memory used for CJ-series Unit to which the data will be written is specified as shown in the following table.
Instance ID (Hex)
01
03
04
05
08 to 14
CPU Unit memory area for write
CIO
DM
WR
HR
EM, banks 0 to C
Word range
CIO 0000 to CIO 6143
D00000 to D32767
W000 to W511
H000 to H511
En_00000 to En_32767
(n: 0 to C)
Note You cannot use Holding Area H512 and its subsequent holding areas, or EM Area Bank D and its subsequent banks.
Address L, Address H (command): The address of the first word to which the data will be written is specified in hexadecimal as shown below.
Address L: The lower 2 digits when the first word address is displayed in 4-digit hexadecimal.
Address H: The higher 2 digits when the first word address is displayed in 4-digit hexadecimal.
Write Data (command): The specified area and write data is returned in order from word H (higher byte: bits 8 to 15) to word L (lower byte: bits 0 to 7). If an odd number is specified, the last 1 byte of data will be written to word H.
z
Important Points
The actual address L, address H, and number of write data words that can be specified depends on the type of CPU Unit with CJ-series DeviceNet Unit mounted and the type of memory area. Do not exceed the boundary of the data areas for the CPU Unit you are using.
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
6 Message Communications
Word Data Write (Service Code: 1F Hex)
Word Data Write writes data to any I/O memory area in the memory used for CJ-series Unit in a CPU
Unit with a CJ-series DeviceNet Unit mounted. The write word data is in word units. The response block is returned from low to high bytes.
z
Command Block
1F 2F
(*) (*)
Class ID
Service Code
Address L
Instance ID
Word data L
Address H Word data H
Word data L
Word data H
Write data (200 bytes max.)
Note A body format of either 8 bits or 16 bits is possible.
z
Response Block
9F
Service Code z
Parameters
Service Code (command, response): 1F Hex is specified for commands. For responses, the highest bit will turn ON and 9F Hex will be returned.
Class ID (command): Always 2F Hex.
Instance ID (command): The type of area in the memory used for CJ-series Unit to which the data will be written is specified as shown in the following table.
Instance ID (Hex) Word range
01
03
04
05
08 to 14
CPU Unit memory area for write
CIO
DM
WR
HR
EM, banks 0 to C
CIO 0000 to CIO 6143
D00000 to D32767
W000 to W511
H000 to H511
En_00000 to En_32767
(n: 0 to C)
Address L, Address H (command): The address of the first word to which the data is written is specified in hexadecimal as shown below.
Address L: The lower 2 digits when the first word address is displayed in 4-digit hexadecimal.
Address H: The higher 2 digits when the first word address is displayed in 4-digit hexadecimal.
Write Data (command): The specified area and write data is returned in order from word L (lower byte: bits 0 to 7) to word H (higher byte: bits 8 to 15).
z
Important Points
The actual address L, address H, and number of write words that can be specified depends on the mode of CPU Unit for the CJ-series DeviceNet Unit and the type of memory areas. Do not exceed the boundary of the data areas for the CPU Unit you are using.
6
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 6-25
6 Message Communications
6-26 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Other Functions
This section describes connecting to Sysmac Studio via the DeviceNet and the SD
Memory Card backup function.
7-1 SD Memory Card Backup Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
7
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 7-1
7 Other Functions
7-1 SD Memory Card Backup Functions
The DeviceNet Unit stores the following setup data in the internal non-volatile memory.
• Master scan lists
• Slave scan lists
• Message monitoring timer lists
• Communications cycle time settings
• Master/Slave functions enabled/disabled settings
Note Backup is possible only when scan lists are enabled.
With the CJ-series DeviceNet Unit, all this setup data can be backed up to and restored from an SD
Memory Card mounted to the CPU Unit.
If all setup data for a DeviceNet Unit that starts normally is saved on an SD Memory Card that data can be read and used when replacing DeviceNet Units, making the replacement process smooth.
Device parameter files (.dvf files) created using the CX-Integrator can be saved from the computer to the SD Memory Card and can be restored to the DeviceNet Unit mounted to the CPU Unit. This means that setup data created using the CX-Integrator (scan lists and other parameters) can be downloaded to
DeviceNet Units simply by taking the SD Memory Card to site.
CJ-series
DeviceNet Unit NJ-series CPU Unit Unit Setup File Backup Switch
FALSE → TRUE
FALSE
→
TRUE
Unit Setup File Restore Switch
CX-Integrator
All setup data
Backup
Restore
SD Memory Card
Save file
Load file
7-2 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
7 Other Functions
7-1-1 Outline of Functions
Backing Up Unit Setup Files
Saves all internal Unit setup data to the SD Memory Card mounted to the CPU Unit.
Method: By changing the software switch *_Sw2FileBkupCmd (Unit Setup File Backup Switch) to
TRUE, save the internal Unit setup data on an SD Memory Card as unit setup files.
CJ-series
DeviceNet Unit NJ-series CPU Unit
Unit Setup File Backup switch
FALSE → TRUE
All setup data SD Memory Card
Backup
Restoring Unit Setup Files (Restore and Set in the Unit)
Restore the data saved on a CPU Unit's SD Memory Card into the Unit.
Method: By changing the software switch *_Sw2FileRestoreCmd (Unit Setup File Restore Switch) to
TRUE, restore the Unit setup data on an SD Memory Card and make it effective as Unit settings.
After the file data is restored, the Unit automatically restarts with the new settings.
CJ-series
DeviceNet Unit NJ-series CPU Unit
Unit Setup File Restore Switch
FALSE → TRUE
All setup data SD Memory Card
Restore
7
Note *_FileRWErr (File Read/Write Error) in Unit Status 2 will change to TRUE if there is a setup data error or a file read error.
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 7-3
7 Other Functions
Saving Files from CX-Integrator to SD Memory Card
You can restore the data setup file into a DeviceNet Unit by saving a device parameter file (extension .dvf) for this DeviceNet Unit created with CX-Integrator to an SD Memory Card with the file name DNnn-
BKUP.dvf (nn: unit number (2-digit hexadecimal), mounting it in the CPU Unit, and changing the software switch *_Sw2FileRestoreCmd (Unit Setup File Restore Switch) to TRUE.
Note The file name when saving setup data to the SD Memory Card must be DNnnBKUP.dvf (where nn is the Unit number in 2-digit hexadecimal). For example, for unit number 00, the file name must be DN00BKUP.dvf. If the file is saved under another name, the data cannot be restored from the SD Memory Card to the DeviceNet Unit.
DeviceNet Unit CPU Unit
Unit Setup File Restore Switch
FALSE → TRUE
SD Memory Card
CX-Integrator
(computer)
All setup data SD Memory Card
Restore Saving device parameter file
Saved as file name
DNnnBKUP.dvf
(where nn is the Unit number in 2-digit hexadecimal.)
7-1-2 File Names
The following files are created on the SD Memory Card.
Directory (fixed): Route and directory.
File name (fixed): DNnnBKUP.dvf (nn: Unit number in 2-digit hexadecimal).
(Ex.: File name is N00BKUP.dvf when Unit No. is 00.)
Additional Information
The above file is data compatible with device parameter files for the Master (this Unit) created with CX-Integrator.
7-4 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Communications Timing
This section describes the time required for remote I/O communications and message communications.
8-1 Remote I/O Communications Characteristics . . . . . . . . . . . . . . . . . . . . . . . 8-2
8-2-2 Calculating the Maximum Message Response Time . . . . . . . . . . . . . . . . . . . 8-11
8
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 8-1
8 Communications Timing
8-1 Remote I/O Communications
Characteristics
This section describes the characteristics of remote I/O communications when the DeviceNet Unit is used as a master in combination with OMRON DeviceNet slaves. Use this section for reference when planning operations that require precise I/O timing.
The equations provided here are valid under the following conditions:
• The DeviceNet Unit is operating with the scan list enabled.
• All of the required Slaves are participating in communications.
• No errors are being indicated at the DeviceNet Unit
• Messages aren't being produced in the Network (from another company's configurator, for example).
Additional Information
The values provided by these equations may not be accurate if another company's DeviceNet
Master or Slave is being used in the Network.
8-1-1 Communications Cycle Time
This section explains the communications cycle time and communications time per slave required for calculating processing time by the DeviceNet Unit.
Communications Cycle Time
The communications cycle time is the time from the completion of a Slave's remote I/O communications processing until remote I/O communications with the same Slave are processed again. The communications cycle time is used to calculate the maximum I/O response time.
The communications cycle time depends on the number of Masters in the Network and on whether or not message communications are being performed. The following explanation is for a network with one Master.
For networks with two or more Masters, refer to 8-1-3 More than One Master in Network .
z
Communications Cycle Time Graph
The following graph shows communications cycle time for the number of slaves when there are both
16-point output and 16-point input slaves.
Inputs: Bit strobe, Outputs: Poll connection
Number of Slaves
: Communications cycle time: 500 kbit/s (ms)
: Communications cycle time: 250 kbit/s (ms)
: Communications cycle time: 125 kbit/s (ms)
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 8-2
8 Communications Timing z
Communications Cycle Time Calculation
Use the equations shown below to calculate the communications cycle time (T
RM
) for a network with one Master. Note that if the result of this calculation is less than 2 ms, the actual communications cycle time will be 2 ms.
T
RM
= Σ (Communications time per Slave)
+ High-density Unit processing time
+ Explicit message communications time
+ COS/Cyclic connection time (ms)
+ 0.01 × N + 1.0 [ms]
Communications Time per Slave:
This is the communications time required for a single Slave.
" Σ (Communications time per Slave)" represents the total of the "Communications time per Slave" for all the Slaves in the network.
High-density Unit Processing Time:
3.5 ms
This is added if there are any Slaves in the network that use at least 8 bytes for input, output, or both.
Explicit Message Communications Time:
(0.11 × T
B
) × n [ms]
The explicit message communications time is added as a delay time when explicit communications
(sending or receiving) are performed.
n= Number of explicit messages (both sending and receiving) that occur simultaneously within one
CPU Unit task period of CPU Unit
T
B
= The baud rate factor
(500 kbit/s: T
B
= 2; 250 kbit/s: T
B
= 4; 125 kbit/s: T
B
= 8)
COS/Cyclic Connection Time:
{(0.05+0.008 × S) × T
B
} × n (ms)
The COS/cyclic connection time is added as a delay time when COS/cyclic communications are performed.
S: Total number of inputs and outputs in the COS/cyclic connection (bytes)
T
B
: The baud rate factor
(500 kbit/s: T
B
= 2; 250 kbit/s: T
B
= 4; 125 kbit/s: T
B
= 8) n: Number of nodes occurring simultaneously within 1 communications cycle time in the COS/Cyclic connection
N: Number of Slaves
8
Communications Time/Slave
The communications time per Slave is the communications time required for a single Slave.
The following equations show the communications time/Slave (T
RT
) for each kind of Slave Unit.
The communications time for each slave is not related to the type of connection (protocol) used by the slave.
z
Output Slaves with Less Than 8 Bytes of Output
T
RT
= 0.016
×
T
B
×
S
OUT1
+ 0.11
×
T
B
+ 0.07 [ms]
S
OUT1
: The number of Output Slave output words
T
B
: The baud rate factor
(500 kbit/s: T
B
= 2; 250 kbit/s: T
B
= 4; 125 kbit/s: T
B
= 8)
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 8-3
8 Communications Timing z
Input Slaves with Less Than 8 Bytes of Input
T
RT
= 0.016
×
T
B
×
S
IN1
+ 0.06
×
T
B
+ 0.05 [ms]
S
IN1
: The number of Input Slave input words
T
B
: The baud rate factor
(500 kbit/s: T
B
= 2; 250 kbit/s: T
B
= 4; 125 kbit/s: T
B
= 8) z
Mixed I/O Slaves with Less Than 8 Bytes of Input or Output
T
RT
= 0.016
×
T
B
×
(S
OUT2
+ S
IN2
) + 0.11
×
T
B
+ 0.07 [ms]
S
OUT2
: The number of Mixed I/O Slave output words
S
IN2
: The number of Mixed I/O Slave input words
T
B
: The baud rate factor
(500 kbit/s: T
B
= 2; 250 kbit/s: T
B
= 4; 125 kbit/s: T
B
= 8) z
Slaves with More Than 8 Bytes of Input or Out put
T
RT
= T
OH
+ T
BYTE-IN
×
B
IN
+ T
BYTE-OUT
×
B
OUT
[ms]
T
OH
: Protocol overhead
T
BYTE-IN
: The input byte transmission time
B
IN
: The number of input words
T
BYTE-OUT :
B
OUT :
The output byte transmission time
The number of output words
Baud rate
500 kbit/s
250 kbit/s
125 kbit/s
T
OH
0.306 ms
0.542 ms
1.014 ms
T
BYTE-IN
0.040 ms
0.073 ms
0.139 ms
T
BYTE-OUT
0.036 ms
0.069 ms
0.135 ms
For Input Slaves take B
OUT
to be 0, and for Output Slaves take B
IN
to be 0.
8-4 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
8 Communications Timing
8-1-2 Calculating Guidelines for I/O Response Times
This section describes the formulas to use to calculate the minimum and maximum I/O response times
time and the communications time per slave, which are used in the formulas.
User program
IN1 OUT1
NJ-series CPU Unit
DeviceNet
DeviceNet
Input slave
IN1 OUT1
Output slave
IN1
OUT1
I/O response time
Precautions for Safe Use
Actual I/O response times depend on the number of CJ-series Units that you use, the size of I/O data that is refreshed for other CPU Bus Units, and other factors. The values that are calculated with these formulas are guidelines only. You must always check performance under actual conditions with the actual hardware and make sure that suitable I/O response times are achieved.
8
Formula for the Maximum I/O Response Time
You can calculate the maximum I/O response time T
MAX
(ms) with the following formula.
T
MAX
= T
IN
+ T
RM
× 2 + N
RMMAX
× T
RM
+ T
RT-OUT
+ T
OUT
T
IN
: Input slave ON or OFF delay (ms)
T
RM
: Communications cycle time (ms)
N
RMMAX
: Number of communications cycles of the DeviceNet Unit that waits for data to return from the
CPU Unit
T
RT-OUT
: Communications time per slave for output slaves (ms)
T
OUT
: Output slave ON or OFF delay (ms)
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 8-5
8 Communications Timing
8-6
N
RMMAX
is the smallest value that meets the following condition.
N
RMMAX
×
T
RM
> T
RFNJ
T
RFNJ
= T
INNJMAX
+ Task period × (3 + y) + T
OUTNJMAX y = ((Number of CPU Bus Units + 1)
×
1 ms)
÷
Task period
Note Truncate the decimal portion of y and use the resulting integer in the formula.
T
INNJMAX
: Input processing time in CPU Unit (ms)
T
OUTNJMAX
: Output processing time in CPU Unit (ms)
Task period: The period of the task in which I/O refreshing is assigned for the DeviceNet Unit (ms)
Number of CPU Bus Units: The number of CPU Bus Units that are connected in the Controller
T
INNJMAX
= 0.5 + 0.0005 × Total size of all master input data in bytes
T
OUTNJMAX
= 0.2 + 0.0006
×
Total size of all master output data in bytes
However, if the DeviceNet Unit is on an Expansion Rack, use the following formulas to calculate T
INNJ-
MAX
and T
OUTNJMAX
.
T
INNJMAX
= 0.5 + 0.00075 × Total size of all master input data in bytes
T
OUTNJMAX
= 0.2 + 0.0009
×
Total size of all master output data in bytes
Formula for the Minimum I/O Response Time
You can calculate the minimum I/O response time T
MIN
(ms) with the following formula.
T
MIN
= T
IN
+ T
RT-IN
+ T
RT-OUT
+ T
RFNJ
+ T
OUT
T
IN
: Input slave ON or OFF delay (ms)
T
RT-IN
: Communications time per slave for input slaves (ms)
T
RT-OUT
: Communications time per slave for output slaves (ms)
T
OUT
: Output slave ON or OFF delay (ms)
T
RFNJ
= T
INNJMIN
+ Task period + T
OUTNJMIN
T
INNJMIN
: Input processing time in CPU Unit (ms)
T
OUTNJMIN
: Output processing time in CPU Unit (ms)
Task period: The period of the task in which I/O refreshing is assigned for the DeviceNet Unit (ms)
T
INNJMIN
= 0.4 + 0.0004 × Data size per slave for input slaves in bytes
T
OUTNJMIN
= 0.1 + 0.0005
×
Data size per slave for output slaves in bytes
However, if the DeviceNet Unit is on an Expansion Rack, use the following formulas to calculate T
IN-
NJMIN
and T
OUTNJMIN
.
T
INNJMIN
= 0.4 + 0.0006 × Data size per slave for input slaves in bytes
T
OUTNJMIN
= 0.1 + 0.00075
×
Data size per slave for output slaves in bytes
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
8 Communications Timing
8-1-3 More than One Master in Network
The following equation shows the remote I/O communications cycle time (T
RM
) when there is more than one master in the network. An example for two masters is used.
First, the network is divided into two groups: Master A and the slaves in remote I/O communications with it and master B and the slaves in remote I/O communications with it.
Group A
Master A
Group B
Master B
Slave A Slave B Slave C Slave D Slave E Slave F
Slaves in remote I/O communications with Master A
Slaves in remote I/O communications with Master B
Although in the above diagram the Slaves are separated into two groups for convenience, the actual physical positions in the Network are irrelevant.
Next, we can refer to
Communications Cycle Time on page 8-2
and calculate the communications cycle time for each group as if they were separate Networks.
Group A Group B
Master A Master B
Slave A Slave B Slave C Slave D Slave E Slave F
Group A communications cycle time: T
RM-A
Group A communications cycle time: T
RM-B
In Networks with two Masters, the communications cycle time for the entire Network will be the sum of the communications cycle times for the groups.
T
RM
= T
RM-A
+ T
RM-B
Although this example shows only two Masters in the Network, the total communications cycle time for any Network can be calculated by dividing it into groups and adding the communications cycle times of all groups.
8
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 8-7
8 Communications Timing
8-1-4 System Startup Time
Master Function
This section describes the system startup time (estimated) for a network operating with the scan list enabled. The system startup time is the delay from when the controller is reset or restarted including turning ON the DeviceNet Unit (master) until remote I/O communications begin. Here, we assume that the scan list is enabled and that remote I/O communications are set to start automatically at startup.
The following table shows the system startup times for 2 cases. In the first case, the DeviceNet Unit starts up just after all of the Slaves' power supplies are turned ON. In the second case, the DeviceNet
Unit is restarted while communications are in progress.
Case Slave's indicator status System startup time
(estimated)
13 seconds The Master is started just after
Slave startup.
Just the Master is restarted.
Just the Slaves are restarted.
The NS indicator is OFF or flashing green.
The NS indicator is flashing red while the
Master is OFF.
---
15 seconds
9 seconds
Program Example
As shown in the preceding table, it takes time for DeviceNet communications to start up. This programming uses flags in the Master status area to prevents the Slaves' I/O processing from being performed until remote I/O communications start up.
This programming is for a DeviceNet Unit with a unit number of 00.
I/O Data Communications Status aaaa_Mstr1IOCommSta STEP1
Unit Error aaaa_UnitErr
Slave I/O processing
STEP1:
Processing other than slave I/O
8-8 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
8 Communications Timing
Additional Information
Refer to 3-2 Device Variables for CJ-series Unit (Software Switches, Statuses)
for details on the
Master Status Area.
Slave Function
It takes approximately 12 seconds from the time that the Controller is reset or restarted, including when the power is turned ON to the DeviceNet Unit (slave), until remote I/O communications with the master begin.
8
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 8-9
8 Communications Timing
8-2 Message Communications
8-2-1 Message Communications Time
The message communications time is the time required from the time a Master Unit starts to send a message over the Network to another node until the Master Unit completes sending the message.
The following equation can be used to compute the approximate message communications time.
Message communications time =
Communications cycle time x ((No. of message bytes + 15)
÷
6 + 1)
No. of message bytes: No. of data bytes following the command code (16#2801)
The communications cycle time depends on whether or not remote I/O communications are being used.
Message Communications Only (No Remote I/O Communications)
The following equation can be used to compute the message communications time when remote I/O communications are not being used.
Communications cycle time =
2 (see note) + 0.11 × T
B
+ 0.6 [ms]
T
B
: The baud rate factor
(500 kbit/s: T
B
= 2; 250 kbit/s: T
B
= 4; 125 kbit/s: T
B
= 8)
Note The communications cycle time will be 2 ms even if remote I/O communications are not being used.
Remote I/O and Message Communications
Performing message communications in addition to remote I/O communications will increase the message communications time.
Communications cycle time=
Communications cycle time for remote I/O communications only
+ 0.11 × T
B
+ 0.6 [ms]
T
B
: The baud rate factor
(500 kbit/s: T
B
= 2; 250 kbit/s: T
B
= 4; 125 kbit/s: T
B
= 8)
(Varies depending on the baud rate.)
The above equations can be used to find the approximate message communications time, but this is a typical time, not the maximum time. The message communications time will vary depending on the frequency of message communications, the load on the remote node, the communications cycle time, and other factors. For any one Master Unit, the message communications time can be greatly increased due to heavy loads and the user program must be written to allow for this.
8-10 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
8 Communications Timing
8-2-2 Calculating the Maximum Message Response Time
The message response time is the time required from the time a DeviceNet Unit starts to receive an I/O memory read request message (BYTE DATA READ explicit message) until the DeviceNet Unit completes sending the response message to the client.
The message response times described below are based on the following conditions:
• Only one DeviceNet Unit is mounted.
• The I/O memory read request is returned from CPU Unit in 2 CPU Unit task periods.
• Baud rate: 500 Kbit/s
• Communications cycle time: 3 ms (no remote I/O communications)
• CPU Unit task period: 10 ms
• DeviceNet Unit's refresh time on the CPU Unit: 2 ms z
Request from One Client (BYTE DATA READ)
CPU Unit
Task execution
Task execution
BYTE DATA READ processing time:
CPU Unit task period x 2
Shared memory
DeviceNet internal buffer
Communications cycle
Client Read request Read result
T CPU T CPU
Shown below is the response time required to return data for 100 words.
• BYTE DATA READ request sending time: T
BRS
DeviceNet header (4 bytes) + Parameters (3 bytes) = 7 bytes (no fragment)
Therefore, T
BRS
= 1 communications cycle time (T
RM
) = 3 ms
• CPU Unit's processing time: T
CPU
x 2
T
CPU
x 2 = CPU Unit task period x 2 = 10 x 2 = 20 ms
• BYTE DATA READ response receiving time: T
BRR
DeviceNet header (3 bytes) + Number of words to be read x 2 = 203 bytes
Therefore, T
BRR
= 1 + 203 bytes/6 communications cycle time = 35 communications cycle time
• DeviceNet Unit refresh time: T
RF
= 2 ms
The message response time will be as follows:
= T
RM
+ T
CPU
x 2 + T
RM
x 35 + T
RF
x 2 =3+20+105+4
= 132 ms
8
Shown below is the response time required to return data for 100 words to 8 clients.
• BYTE DATA READ request sending time: T
BRS
DeviceNet header (4 bytes) + Parameters (3 bytes) = 7 bytes (no fragment)
Therefore, T
BRS
= 1 communications cycle time (T
RM
) = 3 ms
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 8-11
8 Communications Timing
• CPU Unit's processing time: T
CPU
x 6 + T
CPU
x 2 = T
CPU
x 8
The following time is required to process data with other clients before the CPU Unit starts processing.
7 other clients/2 = Approximately cycle time x 3
If one processing requires two CPU Unit task periods, the time will be as follows:
CPU Unit task period x 3 x 2 = CPU Unit task period x 6
CPU Unit's processing time: T
CPU
x 2 = CPU Unit task period x 2
Total time will be as follows: CPU Unit task period x 8
• BYTE DATA READ response receiving time: T
BRR
DeviceNet header (3 bytes) + Number of words to be read x 2 = 203 bytes
Therefore, T
BRR
= 1 + 203 bytes/6 communications cycle time = 35 communications cycle time
• DeviceNet Unit refresh time: T
RF
= 2 ms
The message response time will be as follows:
= T
RM
+ T
CPU
x 8 + T
RM
x 35 + T
RF
x 2 x 8 =3+80+105+32
= 220 ms
The above equations can be used to find the approximate message response time, but this is the typical time, not the maximum time. The message response time will vary depending on the frequency of message communications, the load on the remote node, the communications cycle time, and other factors. For any one DeviceNet Unit, the message communications time can be greatly increased due to heavy loads and the user program must be written to allow for this.
8-12 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Troubleshooting and Maintenance
This section describes error processing, periodic maintenance operations, and troubleshooting procedures needed to keep the DeviceNet network operating properly. We recommend reading through the error processing procedures before operation so that operating errors can be identified and corrected more quickly.
9-1 Troubleshooting with the DeviceNet Unit Indicators . . . . . . . . . . . . . . . . . 9-2
9-1-2 Troubleshooting Errors Occurring in the DeviceNet Unit . . . . . . . . . . . . . . . . . 9-4
9
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 9-1
9 Troubleshooting and Maintenance
9-1 Troubleshooting with the DeviceNet
Unit Indicators
9-1-1 Determining Operating Status from the Indicators
MS
OFF
ON
(green)
ON
(green)
ON
(green)
ON
(green)
Indicator status
NS 7-segment
OFF OFF
OFF
Flashing
(green)
ON
(green)
ON
(green)
Network/Unit status Comments
Master's node address
- - (flashing)
Initializing with CPU Unit Initialization processing with the CPU Unit is in progress.
Restart the DeviceNet Unit if this status continues for an extended period of time. Replace the CPU
Unit and/or DeviceNet Unit if the problem is not corrected by restarting.
The node address duplication check is performed after initialization.
Master's node address
(flashing)
Master's node address
(flashing)
Master's node address
Checking for node address duplication
Waiting for remote I/O communications
Waiting for message communications connection
Remote I/O or message communications in progress.
Scan list operation in progress.
The Unit will have this status until remote I/O communications are performed with the master or slave function. (When both functions are operating, the Unit will have this status until remote I/O communications are performed with either function.)
The Unit will have this status when both the master and slave functions are disabled and the Unit is waiting for a connection by message communications.
This is the normal display when the master and/or slave is active.
The scan list is being saved in flash memory or the scan list is being cleared.
9-2 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
9 Troubleshooting and Maintenance
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 9-3
9
9 Troubleshooting and Maintenance
9-1-2 Troubleshooting Errors Occurring in the DeviceNet Unit
MS
-
Indicators
NS
-
7-segment
*1
A0
Error category
Master function
Error Likely cause DeviceNet Unit response
Remote
I/O communications stopped by a communications error
Pin 3 on the master's DIP switch is set to stop communications in the event of a communications error and communications have been stopped due to a remote I/O communications error, network power supply error, or transmission timeout.
• Remote I/O communications as a master will stop. Remote I/O communications as a slave and message communications will continue.
• Records the error in the error log.
Error log
(Hex)
0346
-
-
-
-
-
-
C0
C2
C4
Software settings errors
CPU Unit status error
Unit status error
Structure error
The software switch operation couldn't be performed because the CPU Unit wasn't in PROGRAM mode.
The software switch operation failed because the
Unit could not perform the requested process in its current status.
*2
The software switch operation failed because a structure error occurred.
• The only response is the error code displayed on the 7-segment indicator.
• The error display will be cleared the next time that a software switch operation is completed normally.
-
-
-
*1 The 7-segment indicator will alternate between the Unit's node address and the code given in the tables in this section.
*2 The most common causes of Unit status errors during settings switch operations are listed below:
• The master was stopped and a software switch operation relating to the master function was performed. (This does not include the master enable switch operation.)
• The scan list was enabled and a software switch operation was performed that can only be performed while the scan list is disabled. (Scan list enable and fixed allocation setting operations)
• The scan list was disabled and a software switch operation was performed that can only be performed while the scan list is enabled. (Clear scan list and Backup Unit settings file operations)
• The slave was stopped and a software switch operation relating to the slave function was performed. (This does not include the slave enable switch operation.)
9-4 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
9 Troubleshooting and Maintenance
Status of C200H Master Replacement
Master Status 1
*_CMstrSta*_CMstrSta
Status of device variables for CJ-series Units
Correction
*_CMstrErr (Master Error) and
*_CMstrIOErr (Communication Error) are
TRUE or *_CMstrErr (Master Error) and
*_CMstrSendErr (1Send Error) are
TRUE.
*_Mstr1IOErr (Remote I/O Communication Error), *_UnitErr (Unit Error) and
*_MstrFunErr (Master Function Error) are TRUE, or *_NetPwrErr (Network
Power Error) and *_UnitErr (Unit Error), or *_SendTimeoutErr (Send Timeout
Error) and *_UnitErr (Unit Error) are
TRUE.
-
Perform error processing according to the cause:
• Remote I/O communications error
(See error d9.)
• Network power supply error (See error E0.)
• Transmission timeout error (See error E2.)
Correct the cause of the error and then restart remote I/O communications using the software switch
*_Sw1IOCommStartCmd (the
Remote I/O Communications Start
Switch.)
Switch the CPU Unit to PROGRAM mode and try the operation again.
-
-
The C2 display will automatically go out after 30 seconds or will go out if the new software switch operation is successful.
Correct the structure error's cause
(see errors d0 to d2), then register to the scan list again after checking there is no error.
9
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 9-5
9 Troubleshooting and Maintenance
MS
-
-
-
-
Indicators
NS
-
7-segment *1
C5
-
Red
(flashing)
Red
(flashing)
C6 d0 d1
Error category
Software settings errors
Master function
Error
Incorrect setting
Multiple switches
ON
Structure error *2
(I/O area duplication)
Structure error *2
(I/O area range exceeded)
Likely cause DeviceNet Unit response
Error log
(Hex)
There was an error in the parameters specified in the user settings and the requested settings could not be made.
Two or more software switches were changed to
TRUE simultaneously or a second software switch was changed to TRUE before a prior operation was completed.
• The only response is the error code displayed on the 7-segment indicator.
• The error display will be cleared the next time that a software switch operation is completed normally.
The slave's I/O areas overlap. (Occurred with the scan list disabled.)
Note Errors will occur in the slaves that join afterwards.
The master will periodically attempt to reconnect with the slave with the structure error.
The slave's I/O area isn't within the allowed range.
(Occurs with the scan list disabled.)
-
-
0343
0343
*1 The 7-segment indicator will alternate between the Unit's node address and the code given in the tables in this section.
*2 When a (master function) structure error or verification error occurs, only the most recent error is displayed for each slave.
If the Unit is set to stop the remote I/O communications for a communications error, two errors can be displayed: The slave's communications error and its most recent error.
9-6 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
9 Troubleshooting and Maintenance
Status of C200H Master Replacement
Master Status 1
*_CMstrSta*_CMstrSta
-
Status of device variables for CJ-series Units
-
Correction
Check the parameters in the user settings and try the operation again.
Execute software switch operations one at a time.
*_CMstrErr (Master Error) and
*_CMstrStruErr (Structure Error) are
TRUE.
*_Mstr1StruErr (Structure Error),
*_UnitErr (Unit Error) and *_MstrFunErr
(Master Function Error) are TRUE.
Set the slaves' node addresses again.
*_CMstrErr (Master Error) and
*_CMstrStruErr (Structure Error) are
TRUE.
*_Mstr1StruErr (Structure Error),
*_UnitErr (Unit Error) and *_MstrFunErr
(Master Function Error) are TRUE.
Set the slaves' node addresses again or use user-set allocations.
9
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 9-7
9 Troubleshooting and Maintenance
MS
-
-
Indicators
NS
Red
(flashing)
7-segment *1 d2
Error category
Error
Structure error
*2
(Unsupported slave)
Red
(flashing) d5
Likely cause
The size of the slave's input and/or output area exceeded 200 bytes.
(Occurs with the scan list disabled.)
DeviceNet Unit response
The master will periodically attempt to reconnect with the slave with the structure error.
Error log
(Hex)
0343
Verification error
*2
(Non-existent slave)
A slave registered in the scan list doesn't exist or the local node's (master's) node address is registered in the scan list.
(Occurs with the scan list enabled.)
• If a slave is involved, the master will periodically attempt to reconnect.
• If the master is involved, it will not send an OPEN frame to itself.
0344
*1 The 7-segment indicator will alternate between the Unit's node address and the code given in the tables in this section.
*2 When a (master function) structure error or verification error occurs, only the most recent error is displayed for each slave.
If the Unit is set to stop the remote I/O communications for a communications error, two errors can be displayed: The slave's communications error and its most recent error.
9-8 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
9 Troubleshooting and Maintenance
Status of C200H Master Replacement
Master Status 1
*_CMstrSta*_CMstrSta
*_CMstrErr (Master Error) and
*_CMstrStruErr (Structure Error) are
TRUE.
Status of device variables for CJ-series Units
Correction
*_Mstr1StruErr (Structure Error),
*_UnitErr (Unit Error) and *_MstrFunErr
(Master Function Error) are TRUE.
Use slaves with input and output areas of 200 bytes max.
*_CMstrErr (Master Error) and
*_CMstrVefyErr (Verification Error) are
TRUE.
*_Mstr1VefyErr (Verification Error),
*_UnitErr (Unit Error) and *_MstrFunErr
(Master Function Error) are TRUE.
Check the following:
• Matching master and slave baud rates
• Proper cable lengths (trunk and branch lines)
• Broken or loose cables
• Installation of terminators only at both ends of the trunk line
• Excessive noise
9
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 9-9
9 Troubleshooting and Maintenance
MS
-
-
-
-
-
-
Indicators
NS
Red
(flashing)
7-segment *1 d6
Error category
Master function
Red
(flashing)
Red
(flashing)
Red
(flashing) d6 d6 d6 Master function
Error Likely cause DeviceNet Unit response
Verification error
*2
(Illegal vendor)
The CX-Integrator is set to check the vendor and the slave's vendor does not match the registered scan list. (Occurs with the scan list enabled.)
The master will periodically attempt to reconnect with the slave with the verification error.
Verification error *2
(Illegal connection path)
The connection path was set with the CX-Integrator and there is a mistake in the connection path setting in the scan list. (Occurs with the scan list enabled.)
The master will periodically attempt to reconnect with the slave with the verification error.
Verification error *2
(I/O size mismatch)
The slave's I/O data size does not match the registered scan list. (Occurs with the scan list enabled.)
The master will periodically attempt to reconnect with the slave with the verification error.
Verification error *2
(Illegal device)
The CX-Integrator is set to check the device type and the slave's device type does not match the registered scan list. (Occurs with the scan list enabled.)
Records the error in the error log. The master will periodically attempt to reconnect with the slave with the verification error.
Error log
(Hex)
0344
0344
0344
0344
Red
(flashing)
Red
(flashing) d6 d6 Master function
Verification error
*2
(Illegal product code)
The CX-Integrator is set to check the product code and the slave's product code does not match the registered scan list.
(Occurs with the scan list enabled.)
Records the error in the error log. The master will periodically attempt to reconnect with the slave with the verification error.
Verification error
*2
(Unsupported connection)
The device does not support the I/O service specified in the scan list.
(Occurs with the scan list enabled.)
Records the error in the error log. The master will periodically attempt to reconnect with the slave with the verification error.
0344
0344
Red
(flashing) d9 Remote
I/O communications error
A timeout occurred during remote I/O communications using the master function. (The response from the slave timed out 6 consecutive times.)
Records the error in the error log. The master will periodically attempt to reconnect with the slave with the error, but remote
I/O communications will stop if the master is set to stop communications.
0345
*1 The 7-segment indicator will alternate between the Unit's node address and the code given in the tables in this section.
*2 When a (master function) structure error or verification error occurs, only the most recent error is displayed for each slave.
If the Unit is set to stop the remote I/O communications for a communications error, two errors can be displayed: The slave's communications error and its most recent error.
9-10 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
9 Troubleshooting and Maintenance
Status of C200H Master Replacement
Master Status 1
*_CMstrSta*_CMstrSta
*_CMstrErr (Master Error) and
*_CMstrVefyErr (Verification Error) are
TRUE.
Status of device variables for CJ-series Units
Correction
*_Mstr1VefyErr (Verification Error),
*_UnitErr (Unit Error) and *_MstrFunErr
(Master Function Error) are TRUE.
Inspect the slave and then create the scan list again.
*_CMstrErr (Master Error) and
*_CMstrVefyErr (Verification Error) are
TRUE.
*_Mstr1VefyErr (Verification Error),
*_UnitErr (Unit Error) and *_MstrFunErr
(Master Function Error) are TRUE.
Inspect the slave and then create the scan list again.
*_CMstrErr (Master Error) and
*_CMstrVefyErr (Verification Error) are
TRUE.
*_Mstr1VefyErr (Verification Error),
*_UnitErr (Unit Error) and *_MstrFunErr
(Master Function Error) are TRUE.
Inspect the slave and then create the scan list again.
*_CMstrErr (Master Error) and
*_CMstrVefyErr (Verification Error) are
TRUE.
*_Mstr1VefyErr (Verification Error),
*_UnitErr (Unit Error) and *_MstrFunErr
(Master Function Error) are TRUE.
Inspect the slave and then create the scan list again.
*_CMstrErr (Master Error) and
*_CMstrVefyErr (Verification Error) are
TRUE.
*_Mstr1VefyErr (Verification Error),
*_UnitErr (Unit Error) and *_MstrFunErr
(Master Function Error) are TRUE.
Inspect the slave and then create the scan list again.
*_CMstrErr (Master Error) and
*_CMstrVefyErr (Verification Error) are
TRUE.
*_Mstr1VefyErr (Verification Error),
*_UnitErr (Unit Error) and *_MstrFunErr
(Master Function Error) are TRUE.
Inspect the slave and then create the scan list again.
*_CMstrErr (Master Error) and
*_CMstrIOErr (Communications Error) are TRUE.
*_Mstr1IOErr (Remote I/O Communications Error), *_UnitErr (Unit Error) and
*_MstrFunErr (Master Function Error) are TRUE.
Check the following:
• Matching master and slave baud rates
• Proper cable lengths (trunk and branch lines)
• Broken or loose cables
• Installation of terminators only at both ends of the trunk line
• Excessive noise
9
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 9-11
9 Troubleshooting and Maintenance
MS
-
Indicators
NS 7-segment *1
E0 OFF or
Red
(flashing) *2
Error category
Error Likely cause DeviceNet Unit response
Network Network power supply error
The communications power supply is not being supplied properly from the network.
Records the error in the error log.
As long as power is not being supplied remote I/O communications will remain stopped and errors will be returned in response to requests for message transmissions.
The indicator status, scanning, and message processing will return to normal when the network power supply is restored, although scanning will not resume if the DeviceNet
Unit is set to stop remote
I/O communications when a communications error occurs.
Error log
(Hex)
0341
*1 The 7-segment indicator will alternate between the Unit's node address and the code given in the tables in this section.
*2 The NS indicator will flash red if the error occurs during remote I/O communications, otherwise the indicator will be OFF.
9-12 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
9 Troubleshooting and Maintenance
Status of C200H Master Replacement
Master Status 1
*_CMstrSta*_CMstrSta
Status of device variables for CJ-series Units
Correction
*_CMstrErr (Master Error) and
*_CMstrSendErr (Send Error) are TRUE.
*_NetPwrErr (Network Power Error) and
*_UnitErr (Unit Error) are TRUE.
Check the network power supply and the wiring of the network cables.
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 9-13
9
9 Troubleshooting and Maintenance
MS
-
Red
(flashing)
Red
(flashing)
Indicators
NS
OFF or
Red
(flashing)
*2
7-segment *1
E2
-
E6
E7
Error category
Network
Memory access
Error
Transmission timeout error
Likely cause DeviceNet Unit response
Error log
(Hex)
A transmission request was not completed normally for one of the following reasons:
• There is not even one device such as a slave in the network.
• The communications speed settings are not the same in all of the nodes.
• CAN controller error
As long as transmission timeout is in effect, remote
I/O communications will remain stopped and errors will be returned in response to requests for message transmissions.
The indicator status, scanning, and message processing will return to normal when the transmission timeout returns to normal, although scanning will not resume if the
DeviceNet Unit is set to stop remote I/O communications when a communications error occurs.
0342
Message monitoring timer list logic error
There is an error in the contents of the message monitoring timer list stored in non-volatile memory.
Records the error in the error log.
Operation will continue using the default message monitoring timer values.
021A
Slave scan list logic error
There is an error in the contents of the slave scan list stored in non-volatile memory.
• Records the error in the error log.
• The slave remote I/O communications will be stopped.
• Message processing and the exchange of data with the CPU Unit will continue. Normal operation will resume when the slave scan list is written normally. (Start the slave remote I/O communications.)
021A
*1 The 7-segment indicator will alternate between the Unit's node address and the code given in the tables in this section.
*2 The NS indicator will flash red if the error occurs during remote I/O communications, otherwise the indicator will be OFF.
9-14 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
9 Troubleshooting and Maintenance
Status of C200H Master Replacement
Master Status 1
*_CMstrSta*_CMstrSta
Status of device variables for CJ-series Units
*_CMstrErr (Master Error) and
*_CMstrSendErr (Send Error) are TRUE.
*_SendTimeoutErr (Send Timeout
Error) and *_UnitErr (Unit Error) are
TRUE.
Correction
Check the following:
• Matching master and slave baud rates
• Proper cable lengths (trunk and branch lines)
• Broken or loose cables
• Installation of terminators only at both ends of the trunk line
• Excessive noise
*_CMstrErr (Master Error) and
*_CMstrCfgErr (Configuration Error) are
TRUE.
*_UnitErr (Unit Error) and *_MsgListErr
(Invalid Message Timer List Error) are
TRUE.
Use the CX-Integrator to register the message monitoring timer list again.
*_UnitErr (Unit Error), *_SlavFunErr
(Slave Function Error) and *_MemErr
(Unit Memory Error) are TRUE.
Disable the slave, reset the allocations, and then enable the slave again or use the CX-Integrator to reset the slave scan list.
9
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 9-15
9 Troubleshooting and Maintenance
MS
Red
(flashing)
Indicators
NS
-
7-segment *1
E8
Error category
Memory access
Error
Master scan list logic error
Likely cause DeviceNet Unit response
Error log
(Hex)
There is an error in the contents of the master scan list stored in non-volatile memory.
• Records the error in the error log.
• The master remote I/O communications will be stopped.
• Data exchange, slave operation, and message communications with the
CPU Unit will continue.
Normal operation will resume when the master scan list is written normally. (Start the master remote I/O communications.)
021A
*1 The 7-segment indicator will alternate between the Unit's node address and the code given in the tables in this section.
9-16 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
9 Troubleshooting and Maintenance
Status of C200H Master Replacement
Master Status 1
*_CMstrSta*_CMstrSta
Status of device variables for CJ-series Units
Correction
*_CMstrErr (Master Error) and
*_CMstrCfgErr (Configuration Error) are
TRUE.
*_UnitErr (Unit Error), *_MstrFunErr
(Master Function Error) and
*_Mstr1SListErr (Invalid Scan List Data
Error) are TRUE.
Clear the scan list and register the scan list again or use the CX-Integrator to reset the master scan list.
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 9-17
9
9 Troubleshooting and Maintenance
MS
Red
(flashing)
Indicators
NS
-
7-segment *1
E9
Error category
Memory access
Error
Memory access error
Likely cause DeviceNet Unit response
Error log
(Hex)
An error occurred in the
Unit's non-volatile memory itself. This error will occur in the following cases.
Error1:
An error occurs reading the identity information during initialization.
Error2:
All error log records cannot be used during initialization or registering an error log record.
Error3:
An error occurs while reading or writing the error log.
Error4:
An error occurs while reading or writing the master function enabling data or the master scan list.
Error5:
An error occurs while reading or writing the slave function enabling data or the slave scan list.
Error6:
An error occurs while reading or writing the message monitoring timer.
Error7:
An error occurs while reading or writing the communications cycle time set value.
Error8:
An error occurs while reading the identity information during Identity object server processing.
Registers an error record with error code 0602 in the
RAM error log area.
For Error 1:
Normal operation continues.
For Error 2 or 3:
Remaining writes to
EEPROM are all ignored.
Other than that, normal operation continues. (Error records continue to be written to RAM.)
For Error 4:
The master remote I/O communications are stopped. Other operations continue.
For Error 5:
The slave scanning is stopped and other operations continue.
For Error 6:
The default values are used for the message monitoring timer and operation continues.
For Error 7:
The communications cycle time is set automatically and operation continues.
For Error 8:
Operation continues.
Note This error does occur for checksum errors while reading data.
0602
*1 The 7-segment indicator will alternate between the Unit's node address and the code given in the tables in this section.
9-18 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
9 Troubleshooting and Maintenance
Status of C200H Master Replacement
Master Status 1
*_CMstrSta*_CMstrSta
Status of device variables for CJ-series Units
*_CMstrErr (Master Error) and
*_CMstrMemErr (Unit Memory Error) are
TRUE.
*_UnitErr (Unit Error) and *_MemErr
(Unit Memory Error) are TRUE.
Correction
Replace the Unit if the error recurs.
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 9-19
9
9 Troubleshooting and Maintenance
MS
-
-
Indicators
NS
Red (lit)
7-segment *1
F0
Error category
Error
Network Node address duplication
Likely cause
The master's node address is duplicated on another node.
Red (lit) F1 Bus Off detected
A Bus Off condition was detected.
DeviceNet Unit response
Error log
(Hex)
• The Unit will go offline and communications will be disabled. Error responses will be returned to all communications requests.
• The exchange of data with the CPU Unit will continue.
• The Unit will go offline and communications will be disabled. Error responses will be returned to all communications requests.
• The exchange of data with the CPU Unit will continue.
0211
0340
Red
(flashing)
Red
(flashing)
Red (lit)
OFF
OFF
H1
H2
CPU Unit exchange
Unit number duplication
CPU Unit faulty (H2)
The unit number is duplicated on another Unit.
-
Stops operation.
Stops operation.
-
-
OFF H3 DeviceNet
Unit faulty
Stops operation.
-
Red
(flashing)
Red
(flashing)
Red
(flashing)
Red
(flashing)
OFF
OFF
OFF
OFF
H4
H5
H6
H7
Node address setting error
Communications speed setting error
CPU Unit faulty (H6)
The node address set on the rotary switches is outof-range (64 or higher.)
The communications speed is set incorrectly.
I/O table not registered
Stops operation.
Stops operation.
-
-
-
The CPU Unit's I/O table is not registered.
• Records the error in the error log. (The time information is set to all zeroes.)
• Stops operation.
• Records the error in the error log.
• Stops operation.
000F
0006
*1 The 7-segment indicator will alternate between the Unit's node address and the code given in the tables in this section.
9-20 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
9 Troubleshooting and Maintenance
Status of C200H Master Replacement
Master Status 1
*_CMstrSta*_CMstrSta
Status of device variables for CJ-series Units
*_CMstrErr (Master Error) and
*_CMstrNdDupErr (Node Address Duplicated/Bus Off Error) are TRUE.
*_UnitErr (Unit Error) and
*_NdAdrDupErr (Node Address Duplicated) are TRUE.
Correction
Check the node addresses set on other nodes in the network. Correct the settings to eliminate the duplication and restart the DeviceNet Units.
*_CMstrErr (Master Error) and
*_CMstrNdDupErr (Node Address Duplicated/Bus Off Error) are TRUE.
*_UnitErr (Unit Error) and *_BusoffErr
(Bus Off Error) are TRUE.
-
Check the following:
• Matching master and slave baud rates
• Proper cable lengths (trunk and branch lines)
• Broken or loose cables
• Installation of terminators only at both ends of the trunk line
• Excessive noise
Set the unit numbers correctly and restart the DeviceNet Units.
-
-
-
-
-
Replace the CPU Unit if the error recurs when the Controller is restarted.
Replace the DeviceNet Unit if the same error recurs when the Unit is mounted to another CPU Unit.
Set the node address correctly and restart the DeviceNet Units.
Set the communications speed correctly and restart the DeviceNet Units.
-
-
-
Replace the CPU Unit if the error recurs when the Controller is restarted.
Create the Unit Configuration in which the Unit is registered to.
9
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 9-21
9 Troubleshooting and Maintenance
MS
Red
(flashing)
Indicators
NS
-
7-segment *1
HA
Red
(flashing)
Red
(flashing)
Red
(flashing)
-
-
-
Hb
HC
Hd
Error category
Error Likely cause DeviceNet Unit response
Error log
(Hex)
CPU Unit exchange
CPU Unit memory faulty
CPU Unit faulty (Hb)
Routing table logic error
I/O refresh error
A parity error occurred while reading the routing table.
A timeout occurred while reading the routing table.
• Records the error in the error log and continues processing
• The routing table is treated as missing.
• Continues processing but data exchange with the CPU Unit is stopped.
• The routing table is treated as missing.
• Records the error in the error log.
There is an error in the contents of the routing table.
• The I/O areas set in the master scan list or slave scan list do not exist in the CPU Unit.
• This error can occur when the Unit is mounted to a different
CPU Unit with a different number of EM banks or
EM that has been converted to file memory.
Note There is a possibility that this error will occur again. If it does occur again, restart remote I/O communications to return the system to normal operation.
Note This error may occur during remote I/O communications, too.
• Records the error in the error log.
• The routing table is treated as missing and processing continues.
Stops remote I/O communications for the function
(master or slave) using the non-existent area.
0012
0011
021A
0347
*1 The 7-segment indicator will alternate between the Unit's node address and the code given in the tables in this section.
9-22 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
9 Troubleshooting and Maintenance
Status of C200H Master Replacement
Master Status 1
*_CMstrSta*_CMstrSta
Status of device variables for CJ-series Units
*_CMstrErr (Master Error) and
*_CMstrCfgErr (Configuration Error) are
TRUE.
*_RTblErr (Routing Table Error) and
*_UnitErr (Unit Error) are TRUE.
*_CMstrErr (Master Error) and
*_CMstrCfgErr (Configuration Error) are
TRUE.
*_RTblErr
*_UnitErr
(Routing Table Error) and
(Unit Error) are TRUE.
Correction
Register the routing table in the CPU
Unit again and restart the Controller.
Replace the CPU Unit if the error recurs.
Register the routing table in the CPU
Unit again and restart the Controller.
Replace the CPU Unit if the error recurs.
*_CMstrErr (Master Error) and
*_CMstrCfgErr (Configuration Error) are
TRUE.
*_RTblErr (Routing Table Error) and
*_UnitErr (Unit Error) are TRUE.
Set the routing table in the CPU Unit correctly and restart the DeviceNet
Units.
*_CMstrErr (Master Error) and
*_CMstrCfgErr (Configuration Error) are
TRUE.
*_UnitErr (Unit Error), *_MstrFunErr
(Master Function Error) and
*_Mstr1IORefErr (Master I/O Refresh
Error) are TRUE, or *_UnitErr (Unit
Error), *_SlavFunErr (Slave Function
Flag) and *_Slav1IORefErr (Slave I/O
Refresh Error) are TRUE.
Check the master scan list and slave scan list and reset with a correct allocation.
9
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 9-23
9 Troubleshooting and Maintenance
MS
Red
(flashing)
Indicators
NS
-
7-segment *1
HE
Error category
Error Likely cause DeviceNet Unit response
CPU Unit exchange
CPU Unit service monitoring error
Servicing from the CPU
Unit is not performed at fixed intervals. Servicing is normally monitored performed at 11 s.
• Records the error in the error log.
• Stops master and slave remote I/O communications.
Performs the following processing if it receives commands that must be passed along to the CPU
Unit:
• Returns an error response (0302 Hex) to commands requiring a response.
• Discards other frames and stores an error record (010B Hex) in the error log.
Error log
(Hex)
0002
Red
(flashing)
HF CPU Unit watchdog timer error
An error occurred in the
CPU Unit.
*2
Note Remote I/O communications will not restart automatically for this error. First confirm that the error has been eliminated and then perform the procedure to start remote I/O communications.
• Records the error in the error log.
• Stops master and slave remote I/O communications.
Performs the following processing if it receives commands that must be passed along to the CPU
Unit:
• Returns an error response (0302 Hex) to commands requiring a response.
• Discards other frames and stores an error record (010B Hex) in the error log.
0001
*1 The 7-segment indicator will alternate between the Unit's node address and the code given in the tables in this section.
*2 The CPU Unit's watchdog timer error can occur during initialization.
9-24 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
9 Troubleshooting and Maintenance
Status of C200H Master Replacement
Master Status 1
*_CMstrSta*_CMstrSta
There is no status notification because communications with the CPU Unit are disabled.
Status of device variables for CJ-series Units
Correction
There is no status notification because communications with the CPU Unit are disabled.
Inspect the CPU Unit's operating environment.
There is no status notification because communications with the CPU Unit are disabled.
There is no status notification because communications with the CPU Unit are disabled.
Replace the CPU Unit.
9
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 9-25
9 Troubleshooting and Maintenance
MS
-
Indicators
NS
Red
(flashing)
7-segment *1
L9
Error category
Slave function
Error
Remote
I/O communications error
Likely cause DeviceNet Unit response
Error log
(Hex)
A timeout occurred during remote I/O communications using the slave function.
If slave has outputs, the status of those outputs is determined by the hold/clear outputs setting for communications errors.
0345
Red (lit)
-
OFF
-
OFF
-
Unit
CPU Unit
Special
Unit error
CPU Unit major fault
-
• Records the error in the error log.
• Stops the Unit.
Output data is set to 0.
(With the master, these are output bits. With the slave, these are input bits to the other master.)
0601
-
*1 The 7-segment indicator will alternate between the Unit's node address and the code given in the tables in this section.
9-26 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
9 Troubleshooting and Maintenance
Status of C200H Master Replacement
Master Status 1
*_CMstrSta*_CMstrSta
-
-
Status of device variables for CJ-series Units
Correction
*_Slav1IO1Err (Remote I/O Communications Error for OUT1/IN1) or
*_Slav1IO2Err (Remote I/O Communications Error for OUT2/IN2) is TRUE and *_UnitErr (Unit Error) and
*_SlavFunErr (Slave Function Flag) are
TRUE.
-
Check the following:
• Master Operation is normal
• Matching master and slave baud rates
• Proper cable lengths (trunk and branch lines)
• Broken or loose cables
• Installation of terminators only at both ends of the trunk line
• Excessive noise
Restart Controller. Replace the
DeviceNet Unit if the error recurs.
-
9
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 9-27
9 Troubleshooting and Maintenance
9-2 Error Log Functions
Errors detected by the DeviceNet Unit are stored in the error log along with the date and time of their occurrence. You can monitor the error log by using the CX-Integrator.
Refer to the CX-Integrator Operation Manual (Cat. No. W464) for error log monitoring operations.
9-2-1 Error Log Table
z
Error Log Table
Each time an error occurs, one error record is recorded in the DeviceNet Unit's RAM error log table.
You can record a maximum of 96 records with Unit Ver. 1.1 or later, and a maximum of 64 records with versions before Ver.1.1. If another error occurs when the table is full, the oldest record will be erased to make room for the new error record.
The error log table records the following information.
• Error code (Refer to
9-2-2 Error Codes and Detail Codes
)
•
Detail code (Refer to 9-2-2 Error Codes and Detail Codes
)
• Time of occurrence (The CPU Unit's time is used for the time stamp.) z
Error Log Storage Area
When an error is detected, information on the error and the time stamp are stored in the Unit's internal RAM as an error log record. Serious errors are recorded in EEPROM as well as RAM*. The error log records in EEPROM are retained even when Controller is turned OFF or the Unit is restarted.
The error log records in EEPROM are copied to RAM when the DeviceNet Unit is turned ON.
When the error log is read from the CX-Integrator, only the error log records in RAM are read. When the error log is cleared from the CX-Integrator, the error log records in RAM and EEPROM are erased.
* Refer to
9-2-2 Error Codes and Detail Codes
for a table listing the error codes.
z
Reading and Clearing the Error Log
When you use the CX-Integrator, you can monitor the error log with the master error history read operation. With the CX-Integrator, the error log can only be monitored and cannot be saved.
Additional Information
The CPU Unit's time information is used for the time stamps in the DeviceNet Unit's error log records. If the time information cannot be read from the CPU Unit, the time stamp will contain all zeroes.
Moreover, if the battery is replaced in an NJ-series controller, the time of the CPU Unit's built-in clock must be set again the next time that power is turned ON. If the built-in clock time is not set, the correct time information will not be recorded. If this error log is read from the CPU Unit, the time information will not be consistent.
9-28 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
9 Troubleshooting and Maintenance
9-2-2 Error Codes and Detail Codes
Error code
(Hex)
Error
0001 CPU Unit watchdog timer error
0002 CPU Unit service monitoring error (Servicing from the CPU Unit is not performed at fixed intervals.)
0006 Other CPU error
000F
0011
0012
CPU Unit initialization error
Event timeout
CPU Unit memory error
00 Hex
First byte
Detail code
Monitoring time (ms)
00 Hex
Second byte
Bit 14 ON: Duplicate unit number setting
Bit 11 ON: Unit not in registered Unit
Configuration in the CPU Unit
Other bits: Reserved by system
00 Hex
MRC
01 Hex: Read error
02 Hex: Write error
00 Hex
SRC
03 Hex: Routing table
04 Hex: CPU Bus Unit system settings error
05 Hex: Special Unit CIO or DM allocation
Yes
Yes
Yes
Yes
Record stored in
EEPROM
Yes
Yes
9
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 9-29
9 Troubleshooting and Maintenance
Error code
(Hex)
Error
0101 Transmission failed because the local node is not participating in the network.
0105 Transmission failed because of a node address setting error.
0106 Transmission failed because of a node address duplication error.
0107 Transmission failed because the other node is not participating in the network.
0108 Transmission failed because there is no Unit with the specified unit number.
0109 Transmission failed because the other node is busy.
010B Transmission failed because of a CPU Unit error. Frame discarded due to one of the following:
• A cyclic service monitoring timeout occurred.
• A CPU Unit watchdog timer error occurred.
• Another CPU Unit error occurred.
010D Transmission failed because the destination address is not registered in the routing table.
010E Transmission failed because the routing table has not been registered.
010F Transmission failed because of a routing table error.
0110 Transmission failed because of too many repetitions.
0111 Transmission failed because the command exceeded the max. command length.
0112 Transmission failed because of a header error.
First byte
Detail code
Second byte
Explicit message communications command:
Bit 15: OFF
Bits 14 to 8: 0
Bit 7: ON
Bits 6 to 0: Node address of command source
Explicit message communications response:
Bit 15: ON
Bits 14 to 8: 0
Bit 7: ON
Bits 6 to 0: Node address of command source
0117 Packet discarded because the internal reception buffer is full.
0118 Illegal packet discarded.
0120 Unexpected routing error
0123 Packet discarded because the internal transmission buffer is full.
0124 Routing failed because maximum frame length was exceeded.
0125 Packet discarded because of response timeout.
021A Setting table logic error 00 Hex 03 Hex: Routing table
0A Hex: Master scan list
0B Hex: Slave scan list
0C Hex: Message monitoring timer list
0D Hex: Scan time
0211 Node address duplication (cause) 00 Hex Local node address
0300 Packet discarded because of parameter error.
Same as the code (such as 0101 Hex) in the discarded explicit message packet.
0340 Bus Off detected 00 Hex 00 Hex
0341 Network power supply error
0342 Transmission timeout
00 Hex
00 Hex
00 Hex
00 Hex
Record stored in
EEPROM
No
Yes
No
No
No
No
No
9-30 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
9 Troubleshooting and Maintenance
Error code
(Hex)
0343 Structure error
0344
0345
0346 Remote I/O communications stopped because of a remote I/O communications error.
0347
0348 Message discarded because a new request
0601
0602
Verification error
Remote I/O communications error
I/O refreshing error was received.
Special Unit error
Error
Special Unit memory error
First byte
Detail code
Second byte
01 Hex: I/O area duplication
02 Hex: I/O area range exceeded
03 Hex: Unsupported slave
01 Hex: Non-existent slave
02 Hex: Illegal vendor
03 Hex: Illegal device type
04 Hex: Illegal product code
05 Hex: Unsupported connection
06 Hex: I/O size mismatch
07 Hex: Illegal connection path
01 Hex: Master
02 Hex: Slave
Slave's node address
Slave's node address
01 Hex: Remote I/O communications error
02 Hex: Network power supply error
03 Hex: Transmission timeout
Master:
Slave's node address
Slave:
Master's node address
Remote I/O comm. error:
Slave's node address
Power supply error:
Local (master's) node address
Transmission timeout:
Local (master's) node address
01 Hex: Master
02 Hex: Slave
00 Hex
Same as the code (such as 0101 Hex) in the discarded explicit message packet.
Uncertain contents
01 Hex: Read error
02 Hex: Write error
06 Hex: Error log
09 Hex: Identity data
0A Hex: Master scan list
0B Hex: Slave scan list
0C Hex: Message monitoring timer list
0D Hex: Communications cycle time setting
Record stored in
EEPROM
No
No
No
No
No
No
Yes
Yes*
* The error information is not written to EEPROM when a memory error occurs in the error log area (EEPROM).
9
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 9-31
9 Troubleshooting and Maintenance
9-3 Troubleshooting
9-3-1 CPU Unit's ERR/ALM Indicator Lit or Flashing
Error
An I/O setting check error occurred.
Special Unit access is denied.
An I/O Bus check error occurred.
Probable cause
• Make sure that the Unit is mounted properly.
• The CPU Bus Unit model registered in the Unit Configuration in the CPU
Unit does not match the actual Unit Configuration. Compare using "Synchronize" operation and use one of the following procedures.
• Correct the Unit number setting
• Correct the project Unit Configuration and transfer to the CPU Unit
• Make sure that the Unit is mounted properly.
• Restart the Unit. If operation is not restored even after the Unit is restarted, replace the Unit.
• Make sure that the Unit is mounted properly.
• Restart the Unit. If operation is not restored even after the Unit is restarted, replace the Unit.
Note Refer to the NJ-Series CPU Unit Hardware User's Manual (Cat. No. W500) and NJ-Series CPU
Unit Software User's Manual (Cat. No. W501) for more details on these errors.
9-3-2 Remote I/O Communications Disabled
Error
All of the DeviceNet Unit's indicators are OFF.
The DeviceNet Unit's MS indicator is ON and green, but the NS indicator remains OFF.
(The green NS indicator normally goes ON about 2 seconds after the green MS indicator goes ON.)
Probable cause
• Check whether power is being supplied to the NJ-series Controller.
• Check whether the DeviceNet Unit is mounted in the Backplane correctly.
• When a watchdog timer (WDT) error has occurred in the CPU Unit, follow the procedures described in the CPU Unit's manual to correct the problem.
• All of a CJ1W-DRM21 Unit's indicators will be OFF when a CPU Bus
Unit error has occurred.
• Restart the Unit. If operation is not restored even after the Unit is restarted, replace the Unit.
• If the DeviceNet Unit's 7-segment indicator is displaying an error code, refer to the tables in
9-1 Troubleshooting with the DeviceNet
• Make sure that the master's unit number setting is correct.
• Make sure that the unit number is not duplicated on another Special
Unit.
• Use the Synchronize function to compare the Unit Configurations.
• Use one of the following procedures according to the comparison results.
• Correct the Unit number setting
• Correct the project Unit Configuration and transfer to the CPU Unit
• Restart the Unit. If operation is not restored even after the Unit is restarted, replace the Unit.
9-32 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
9 Troubleshooting and Maintenance
Error
The DeviceNet Unit's MS indicator is ON and green, but the NS indicator continues to flash green.
(The green NS indicator normally goes ON about 2 seconds after the green MS indicator goes ON.)
The DeviceNet Unit's MS and NS indicators are
ON and green, but the 7-segment indicator continues to flash the master's node address.
(If the slave is connected correctly, the local node address normally goes ON within 8 seconds after the green NS indicator goes ON.)
Probable cause
• If the DeviceNet Unit's 7-segment indicator is displaying an error
code, refer to the tables in 9-1 Troubleshooting with the DeviceNet
• Restart the Unit. If operation is not restored even after the Unit is restarted, replace the Unit.
• Check that the Master Unit's baud rate matches the baud rates set on all of the slaves. If they don't match, set all of the baud rates to the same value.
• Make sure that there are121Ω terminators connected at both ends of the trunk line. Connect 121Ω terminators if the wrong resistance is being used.
• Check whether all of the slaves' settings are correct.
• Check whether the communications cables are wired correctly.
• Check whether the power supply cables and power supply are wired and set correctly.
• Check for broken wires in the communications and power supply cables attached to the connectors.
• Check whether the slaves are operating properly.
When an OMRON DeviceNet slave is being used, refer to the
DeviceNet Slaves Operation Manual (Cat. No. W347).
When another company's DeviceNet slave is being used, refer to that slave's user's manual.
9-3-3 I/O Link Problems
Error
The I/O isn't simultaneous.
Probable cause
Observe the following precautions when writing application programs:
• Node unit data simultaneity is ensured between the NJ-series CPU
Unit and Master Unit.
• In OMRON DeviceNet slaves, the data simultaneity of words are ensured.
• If another manufacturer's DeviceNet slave is being used, refer to that slave's user's manual for details.
9
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 9-33
9 Troubleshooting and Maintenance
9-3-4 Communications Error Operation Settings
Error
Communications are stopped even though there is no communications error.
After stopping is performed because of the communications stop setting for when a communications error occurs, stopping is not released even after a "stop release" operation.
Probable cause
When pin 3 on the DIP switch is ON, communications will be stopped if a communications error, transmission timeout, or network power supply error occurs.
While communications are stopped, the 7-segment indicators will alternately display error code A0 and the error code of the communications error that caused the stoppage.
In the case of a network power supply error or a transmission timeout, the error code will disappear and the indicator will show just the communications stoppage code (A0) after the correction.
• When communications can't be restarted with slaves that were communicating normally before the stoppage, stop the communications again.
Check that the slave has started up and perform the "clear communications error stoppage" operation.
• It may be necessary to perform the operation twice if the network contains another company's slave that take a long time to join the network.
9-3-5 Scan List Problems
Error
A scan list couldn't be created by the "create scan list" operation.
A scan list couldn't be cleared by the "clear scan list" operation.
The "create scan list" or "clear scan list" operation was executed, but the master's 7segment indicators still display "- -".
(The "- -" display usually lasts for 1 second after the "create scan list" operation or 0.1 seconds after the "clear scan list" operation.)
Probable cause
Neither the scan list clear nor create scan list operations can be performed until *_Mstr1IOCommSta (I/O Data Communications) changes to TRUE in the Master Status Area after the power is turned ON and the I/O Data Communications Status will change to TRUE again after the scan list clear operation is executed.
Make sure that the I/O Data Communications Status changes to TRUE before attempting to execute the create scan list or scan list clear operations.
Restart the DeviceNet Unit, execute the clear scan list operation, and then the create scan list operation if necessary.
Replace the DeviceNet Unit if this doesn't correct the problem.
9-34 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
9 Troubleshooting and Maintenance
9-4 Event Logs
9-4-1 Overview of the Event Logs
You use the same methods to manage all of the events that occur on the NJ-series Controller. (The events include errors and information.) You can use the Sysmac Studio or an NS-series PT to confirm current Controller events and the logs of events that have occurred. These logs are called event logs.
Controller errors that occur for this Unit are also reported as events in the NJ-series CPU Unit.
Refer to the NJ-series CPU Unit Software User's Manual (Cat. No. W501) for details on the event logs in an NJ-series CPU Unit. Refer to the NJ-series Troubleshooting Manual (Cat. No. W503) for details on
Controller errors, confirmation methods, and corrections.
Check current Controller events and the event log of past events.
Sysmac Studio
Event source
NJ-series CPU Unit
PLC Function
Module
Motion Control
Function Module
EtherCAT Master
Function Module
EtherNet/IP
Function Module
CJ-series
Units
Errors in
Special Units
Or
NS-series PT
Event logs
User program
Create User-defined
Error instruction:
SetAlarm
Create User-defined
Information instruction: SetInfo
Backup battery
Check current Controller events and the event log of past events.
EtherCAT slave
To use an NS-series PT to check events, connect the PT to the built-in EtherNet/IP port on the CPU
Unit.
9
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 9-35
9 Troubleshooting and Maintenance
9-4-2 Error Table
The errors that may occur for this Unit are listed below.
The following abbreviations and symbols are used in the event level column.
Maj
Abbreviation
Prt
Min
Obs
Info
Meaning
Major fault level
Partial fault level
Minor fault level
Observation
Information
Symbol
S
U
Meaning
Event levels that are defined by the system.
Event levels that can be changed by the user. *
* This symbol appears only for events for which the user can change the event level.
A version in parentheses in the Event code column is the unit version of the CPU Unit when the event was added.
Refer to the NJ-series Troubleshooting Manual (Cat. No. W503) for all of the event codes that may occur in an NJ-series Controller.
Event code Event name Meaning Assumed cause
0488 0000 hex
0489 0000 hex
148D 0000 hex
148E 0000 hex
Unit Memory
Error
Network
Power Error
Invalid Scan
List Data
Invalid Setup
Data
An error occurred when writing to internal memory where the error history is saved.
Network power is not being supplied.
There is an error in the contents of the slave scan list or master scan list stored in non-volatile memory.
There is illegal data in the settings for the slave function.
•
•
There is a source of noise nearby.
Non-volatile memory failure
• Communications power is not being supplied normally from the network.
• The power was interrupted during writing the scan list to the non-volatile memory.
• The power was interrupted while the system was writing the parameters.
• Non-volatile memory life
• The node address of the
DeviceNet Unit is also set for another node.
2448 0000 hex Node
Address
Duplicated
Error
An error was discovered during the node address duplication check when starting the
DeviceNet Unit.
34BC 0000 hex Routing Table
Error
There is illegal data in the routing tables set in the CPU Unit.
•
•
The local DeviceNet Unit is not in the routing tables.
The routing table format is incorrect.
• Reading the routing tables timed out.
Level
Maj Prt Min Obs Info
S U
Reference
S
S
S
S
S U
9-36 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
9 Troubleshooting and Maintenance
Event code Event name Meaning Assumed cause
34BD 0000 hex
34BE 0000 hex
Verification
Error
Structure
Error
The slave information registered in the scan list does not agree with the actual slave information.
The scan list is disabled and an error occurred that prevented making I/O allocations.
• A slave that is in the scan list does not exist.
• The node address of the local
Unit, which is the master, is registered in the scan list.
• If the system is set to check the vendor in the detailed verification settings, the vendor of the slave does not match the registration in the scan list.
• If the connection path is set in the detailed verification settings, then setting the connection path that is set in the scan list failed.
• The size of the slave I/O data does not match the registration in the scan list.
• If the device type is set in the detailed verification settings, then setting the device type that is set in the scan list failed.
• If the product code is set in the detailed verification settings, then setting the product code that is set in the scan list failed.
• The device does not support the I/O service specified in the scan list.
• The I/O words allocated to slave overlap.
• The I/O words allocated to the slave exceed the valid range.
• The I/O size of the slave exceeds 200 bytes for outputs or 200 bytes for inputs.
• I/O words are allocated in an
EM bank that does not exist.
34BF 0000 hex
34C0 0000 hex Master Userset Allocations User
Setting Failed
34C1 0000 hex
Master I/O
Refresh Error
Communications Cycle
Time Setting
Failed
The I/O memory in the destination
CPU Unit for I/O refreshing could not be found when refreshing the master function data in the CPU Unit.
An error occurred in the following operation for user allocation of the master.
An error occurred in one of the following operations when setting the communications cycle time.
• The master function is not enabled.
• There is a mistake in the user allocations in the master.
• CPU Unit is not in PROGRAM mode.
• More than one software switch changed to TRUE at the same time. Or, another software switch changed to TRUE before processing was completed for a previous software switch.
• There is an error in the set information.
• CPU Unit is not in PROGRAM mode.
Level
Maj Prt Min Obs Info
S
Reference
S
S
S
S
9
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 9-37
9 Troubleshooting and Maintenance
Event code Event name Meaning Assumed cause
34C2 0000 hex Slave I/O
Refresh Error
34C3 0000 hex
64AC 0000 hex
7460 0000 hex
Slave User
Allocation
Area Setting
Failed
Send Timeout Error
Master Function
Enable/Disable Failed
7461 0000 hex Master Fixed
Allocation
Area Setting
Failed
The I/O memory in the destination
CPU Unit for I/O refreshing could not be found when refreshing the slave function data in the
CPU Unit.
An error occurred in the following operation for user allocation of the slave.
A send timeout occurred.
An operating error occurred when enabling or disabling the master function.
An error occurred in one of the following operations for fixed allocation of the master.
• I/O words are allocated in an
EM bank that does not exist.
• The slave function is not disabled.
• There is a mistake in the user allocations to a slave.
• CPU Unit is not in PROGRAM mode.
• More than one software switch changed to TRUE at the same time. Or, another software switch changed to TRUE before processing was completed for a previous software switch.
• There is no slave or other device on the network.
• The same baud rate is not set for all nodes.
• Communications cable lengths
(trunk line and branch lines) are unsuitable.
• A communications cable is disconnected or loose.
• The terminating resistance is somewhere other than the ends of the trunk line.
• Noise
• There is an error in the CAN controller.
• An attempt was made to enable the master function when it was already enabled.
• An attempt was made to disable the master function when it was already disabled.
• CPU Unit is not in PROGRAM mode.
• More than one software switch changed to TRUE at the same time. Or, another software switch changed to TRUE before processing was completed for a previous software switch.
• The master function is not enabled.
• The scan list is not disabled.
• CPU Unit is not in PROGRAM mode.
• More than one software switch changed to TRUE at the same time. Or, another software switch changed to TRUE before processing was completed for a previous software switch.
Level
Maj Prt Min Obs Info
S
Reference
S
S
S
S
9-38 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
9 Troubleshooting and Maintenance
Event code Event name
7462 0000 hex Scan List
Register/Clear
Failed
7463 0000 hex Slave Function
Enable/Disable Failed
7464 0000 hex Slave Fixed
Allocation
Area Setting
Failed
Meaning Assumed cause
An operating error occurred when registering or clearing the scan list by performing one of the following operations.
An error occurred in one of the following operations in the slave function.
An error occurred in one of the following operations for fixed allocation of the slave.
• CPU Unit is not in PROGRAM mode.
• Request processing is not possible in this status or the request was made when the operation was already in progress. The following are the main causes of Unit status errors.
• A software switch operation for the master function was executed when the master function was disabled.
• A switch that can be used only when the scan list is disabled was used when the scan list was enabled.
• A switch that can be used only when the scan list is enables was used when the scan list was disabled.
• A software switch operation for the slave function was executed when the slave function was disabled.
• A configuration error has occurred.
• There is an error in the parameters specified in the user settings, and the requested setting could not be made.
• More than one software switch changed to TRUE at the same time. Or, another software switch changed to TRUE before processing was completed for a previous software switch.
• An attempt was made to enable the slave function when it was already enabled.
• An attempt was made to disable the slave function when it was already disabled.
• CPU Unit is not in PROGRAM mode.
• More than one software switch changed to TRUE at the same time. Or, another software switch changed to TRUE before processing was completed for a previous software switch.
• The slave function is not disabled.
• CPU Unit is not in PROGRAM mode.
• More than one software switch changed to TRUE at the same time. Or, another software switch changed to TRUE before processing was completed for a previous software switch.
Level
Maj Prt Min Obs Info
S
Reference
S
S
9
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 9-39
9 Troubleshooting and Maintenance
Event code Event name Meaning Assumed cause
8474 0000 hex
8475 0000 hex Remote I/O
Communications Error
8476 0000 hex Remote I/O
Communications Error
(during Slave
Operation)
8477 0000 hex
048A 0000 hex
148C 0000 hex
Bus Off
Detected
Slave COS
Send Failed
File
Read/Write
Error
Invalid Message Timer
List Error
A Bus Off error occurred (i.e., communications stopped because there were too many communications errors).
A timeout occurred in remote I/O communications.
An error occurred in remote I/O communications.
• The master and slave have different baud rates.
• Communications cable lengths
(trunk line and branch lines) are unsuitable.
• A communications cable is disconnected or loose.
• The terminating resistance is somewhere other than the ends of the trunk line.
• Noise
• The master and slaves have different baud rates.
• Communications cable lengths
(trunk line and branch lines) are unsuitable.
• A communications cable is disconnected or loose.
• The terminating resistance is somewhere other than the ends of the trunk line.
• Noise
• The master is not in operation.
• The master and slaves have different baud rates.
• Communications cable lengths
(trunk line and branch lines) are unsuitable.
• A communications cable is disconnected or loose.
• The terminating resistance is somewhere other than the ends of the trunk line.
• Noise
• A COS connection to the master is not open.
• A Bus Off state occurred.
• A network power error occurred.
• A send timeout occurred.
An attempt was made to send COS data to the master using the Slave
COS Send Switch
(software switch 2, device variable
*_ Sw2SlavCOSSen dCmd ), but the send failed.
An error occurred when user setup data was read from an SD Memory
Card in the CPU
Unit or when data was written as a file to an SD Memory
Card.
The data in the message monitoring timer list is not correct.
• The available capacity on the
SD Memory Card was insufficient to write a file.
• Write-protection is set on the
SD Memory Card when you write to a file.
• Noise
• The SD Memory Card is damaged.
• The CPU Unit has failed.
• The power supply was interrupted while writing the message-monitoring timer list to the non-volatile memory.
Level
Maj Prt Min Obs Info
S
Reference
S
S
S
U
U
U
S
S
9-40 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
9 Troubleshooting and Maintenance
9-4-3 Error Descriptions
This section describes the information that is given for individual errors.
Controller Error Descriptions
The items that are used to describe individual errors (events) are described in the following copy of an error table.
Event name
Meaning
Source
Error attributes
Effects
System-defined variables
Cause and correction
Attached information
Precautions/
Remarks
Gives the name of the error.
Gives a short description of the error.
Gives the source of the error.
Event code Gives the code of the error.
Source details Gives details on the source of the error.
Detection timing
Tells when the error is detected.
Level
User program
Tells the level of influence on control.
*1
Tells what will happen to execution of the user program.*4
Recovery
Operation
Gives the recovery method.
*2
Log category Tells which log the error is saved in.
*3
Provides special information on the operation that results from the error (event).
Variable
Assumed cause
Data type
Correction
Lists the possible causes, corrections, and preventive measures for the error.
Name
Lists the variable names, data types, and meanings for system-defined variables that provide direct error notification, that are directly affected by the error, or that contain settings that cause the error.
Prevention
This is the attached information that is displayed by the Sysmac Studio or an NS-series PT.
If the user can set the event level, the event levels that can be set, the recovery method, operational information, and other information are also provided.
*1 One of the following:
Major fault: Major fault level
Partial fault: Partial fault level
Minor fault: Minor fault level
Observation
Information
*2 One of the following:
Automatic recovery: Normal status is restored automatically when the cause of the error is removed.
Error reset: Normal status is restored when the error is reset after the cause of the error is removed.
Cycle the power supply: Normal status is restored when the power supply to the Controller is turned OFF and then back
ON after the cause of the error is removed.
Controller reset: Normal status is restored when the Controller is reset after the cause of the error is removed.
Depends on cause: The recovery method depends on the cause of the error.
*3 One of the following:
System: System event log
Access: Access event log
*4 One of the following:
Continues: Execution of the user program will continue.
Stops: Execution of the user program stops.
Starts: Execution of the user program starts.
9
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 9-41
9 Troubleshooting and Maintenance
Error Descriptions
Event name
Meaning
Source
Error attributes
Effects
System-defined variables
Cause and correction
Attached information
Precautions/
Remarks
Unit Memory Error Event code 0488 0000 hex
An error occurred when writing to internal memory where the error history is saved.
PLC Function Module
Level
User program
Variable
Minor fault
Continues.
Source details
Recovery
Operation
Data type
CJ-series Unit Detection timing
Cycle the power supply.
Log category
Non-volatile memory cannot be written.
Name
At power ON,
Controller reset, or error history save
System
None
Assumed cause
There is a source of noise nearby.
Non-volatile memory failure
---
Correction
Implement noise countermeasures.
If the above cause does not apply, replace the Unit.
---
Prevention
Use the Controller away from sources of noise.
None
None
You can change the event level to the observation level. If you change the level to the observation level, the column above will be changed to “Error reset.”
Recovery
Event name
Meaning
Source
Error attributes
Effects
System-defined variables
Cause and correction
Attached information
Precautions/
Remarks
Network Power Error
Network power is not being supplied.
PLC Function Module
Level
User program
Variable
None
Assumed cause
Minor fault
Continues.
Communications power is not being supplied normally from the network.
Event code 0489 0000 hex
Source details
Recovery
Operation
CJ-series Unit Detection timing
Log category
Continuously
Cycle the power supply.
System
The DeviceNet Unit will stop remote I/O communications and return errors for message send requests whenever there is a network power supply error. When the network power supply returns to normal status, the error display will stop, the scan will be started, and message processing will return to normal. The scan will not start again after recovery to normal operation, however, if remote I/O communications are set to stop when a communications error occurs.
Data type
---
Correction
Check the network power supply and network cable connections and correct any errors.
Name
---
Prevention
Check to see if the network power supply and network cables are correctly wired.
None
None
9-42 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
9 Troubleshooting and Maintenance
Event name
Meaning
Source
Error attributes
Effects
System-defined variables
Cause and correction
Attached information
Precautions/
Remarks
Invalid Scan List Data Event code 148D 0000 hex
There is an error in the contents of the slave scan list or master scan list stored in non-volatile memory.
PLC Function Module Source details
Level
User program
Minor fault
Continues.
Recovery
Operation
CJ-series Unit Detection timing
Log category
At power ON or
Controller reset
System Error reset
The DeviceNet Unit will stop remote I/O communications for the master or slaves. Data exchange processing with the CPU Unit and message processing will continue. Normal operation will be recovered if writing is performed normally.
Variable
None
Assumed cause
The power was interrupted during writing the scan list to the non-volatile memory.
Data type
---
Correction
If there is an error in the slave scan list, disable the slave function, reset the allocations, and then enable the slave function. Or, reset the slave scan list with the CX-Integrator. If there is an error in the master scan list, clear the scan list, and then register the scan list again. Or, reset the master scan list with the CX-Integrator.
Name
---
Prevention
Do not turn OFF the power supply while the system is writing the settings.
None
None
Event name
Meaning
Source
Error attributes
Effects
System-defined variables
Cause and correction
Attached information
Precautions/
Remarks
Invalid Setup Data
There is illegal data in the settings for the slave function.
PLC Function Module Source details
Level
User program
Variable
None
Assumed cause
The power was interrupted while the system was writing the parameters.
Non-volatile memory life
None
Minor fault
Continues.
Event code 148E 0000 hex
Recovery
Operation
Data type
---
Replace the Unit.
CJ-series Unit Detection timing
Log category
At power ON or
Controller reset
System Automatic recovery, cycle power supply, or reset controller
The DeviceNet Unit will stop the slave function. Remote
I/O communications and message communications will continue.
Name
---
Correction
Write the parameters again.
Prevention
Do not turn OFF the power supply while the system is writing the parameters.
None
None
9
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 9-43
9 Troubleshooting and Maintenance
Event name
Meaning
Source
Error attributes
Effects
System-defined variables
Cause and correction
Attached information
Precautions/
Remarks
Node Address Duplicated Error Event code 2448 0000 hex
An error was discovered during the node address duplication check when starting the DeviceNet Unit.
PLC Function Module Source details
Level
User program
Minor fault
Continues.
Recovery
Operation
CJ-series Unit Detection timing
Log category
When trying to establish a link
System Cycle the power supply.
The DeviceNet Unit is offline. Communications will not operate. Error responses are returned to all communications requests. Data refreshing with the CPU Unit will continue. Communications are not performed if two
DeviceNet Units have the same node address.
Variable
None
Assumed cause
The node address of the DeviceNet
Unit is also set for another node.
Data type
---
Correction
Correct the node address of the
DeviceNet Unit so that it is not set for any other node.
Name
---
Prevention
Set node addresses so that each one is used only once.
None
None
Event name
Meaning
Source
Error attributes
Effects
System-defined variables
Cause and correction
Attached information
Precautions/
Remarks
Routing Table Error
There is illegal data in the routing tables set in the CPU Unit.
Event code
PLC Function Module Source details CJ-series Unit
Level
User program
Variable
Minor fault
Continues.
Recovery
Operation
Data type
34BC 0000 hex
Detection timing
Log category
At power ON or
Controller reset
System Cycle the power supply or reset the Controller.
Processing will continue without using routing tables.
Name
None
Assumed cause
The local DeviceNet Unit is not in the routing tables.
The routing table format is incorrect.
---
Correction
Correct the routing tables so that the local DeviceNet Unit is included in them.
Correct the routing tables so that the proper format is used.
---
Prevention
Make sure that the local DeviceNet
Unit is in the routing tables.
Make sure that the routing tables are set correctly.
None Reading the routing tables timed out.
Check the status of the CPU Unit, and then perform the required corrective actions.
None
You can change the event level to the observation level. If you change the level to the observation level, the column above will be changed to “Cycle power supply or reset Controller.”
Recovery
9-44 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
9 Troubleshooting and Maintenance
Event name
Meaning
Source
Error attributes
Effects
System-defined variables
Cause and correction
Attached information
Precautions/
Remarks
Verification Error Event code 34BD 0000 hex
The slave information registered in the scan list does not agree with the actual slave information.
PLC Function Module
Level
User program
Variable
None
Minor fault
Continues.
Source details
Recovery
Operation
Data type
---
CJ-series Unit Detection timing
When trying to establish an ID connection
Error reset Log category System
The DeviceNet Unit periodically performs reconnection processing for slaves.
Name
---
Assumed cause
A slave that is in the scan list does not exist.
• The master and slaves have different communications settings.
• Communications cable lengths
(trunk line and branch lines) are unsuitable.
• A communications cable is disconnected or loose.
• The terminating resistance is somewhere other than the ends of the trunk line.
• Noise
Correction
• Correct the settings so that the master and slaves use the same baud rate.
• Adjust the communications cables of the trunk and branch lines to suitable lengths.
• Connect the communications cable securely. If the communications cable is broken, replace it.
• Connect terminating resistance only to the ends of the trunk line.
• Implement noise countermeasures.
Prevention
• Set the master and slaves to the same baud rate.
• Install suitable lengths of communications cables for the trunk and branch lines.
• Connect the communications cable securely. Check to see if the communications cable is broken.
• Connect terminating resistance only to the ends of the trunk line.
• Implement noise countermeasures.
Do not register the node address of the local Unit in the scan list.
Do not register the node address of the local Unit in the scan list.
The node address of the local Unit, which is the master, is registered in the scan list.
If the system is set to check the vendor in the detailed verification settings, the vendor of the slave does not match the registration in the scan list.
If the connection path is set in the detailed verification settings, then setting the connection path that is set in the scan list failed.
The size of the slave I/O data does not match the registration in the scan list.
If the device type is set in the detailed verification settings, then setting the device type that is set in the scan list failed.
If the product code is set in the detailed verification settings, then setting the product code that is set in the scan list failed.
The device does not support the I/O service specified in the scan list.
None
Correct the scan list if the slave is correct. If the slave is incorrect, replace it with the correct slave.
Make sure that the information in the scan list matches the information of the slaves that are actually connected.
None
9
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 9-45
9 Troubleshooting and Maintenance
Event name
Meaning
Source
Error attributes
Effects
System-defined variables
Cause and correction
Attached information
Precautions/
Remarks
Structure Error Event code 34BE 0000 hex
The scan list is disabled and an error occurred that prevented making I/O allocations.
PLC Function Module Source details
Level
User program
Minor fault
Continues.
Recovery
Operation
CJ-series Unit Detection timing
When trying to establish an ID connection
System Error reset Log category
The Unit will continue processing the connection again with the slave that has the error, and remote I/O will also continue.
Variable
None
Assumed cause
The I/O words allocated to slave overlap.
The I/O words allocated to the slave exceed the valid range.
The I/O size of the slave exceeds 200 bytes for outputs or 200 bytes for inputs.
None
Data type
---
Correction
Correct the node addresses of the slaves so that I/O area words do not overlap.
Correct the node addresses of the slaves so that the I/O area words do not exceed the valid range.
Use a slave with 200 output bytes or less and 200 input bytes or less.
Name
---
Prevention
Set the node addresses of the slaves so that I/O area words do not overlap.
Set the node addresses of the slaves so that the I/O area words do not exceed the valid range. Or, use the slaves with user allocations.
Use a slave with 200 output bytes or less and 200 input bytes or less.
None
Event name
Meaning
Source
Error attributes
Effects
System-defined variables
Cause and correction
Master I/O Refresh Error
The I/O memory in the destination CPU Unit for I/O refreshing could not be found when refreshing the master function data in the CPU Unit.
PLC Function Module Source details
Event code
CJ-series Unit
34BF 0000 hex
Detection timing
At power ON or
Controller reset
Level
User program
Variable
None
Minor fault
Continues.
Recovery
Operation
Data type
---
Error reset Log category
Remote I/O communications stop.
Name
---
System
Assumed cause
I/O words are allocated in an EM bank that does not exist.
Correction
Correct the I/O allocations so that only I/O words that exist in the I/O memory of a CPU Unit are allocated.
Prevention
Allocate only I/O words that exist in the I/O memory of a CPU Unit.
None Attached information
Precautions/
Remarks
None
9-46 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
9 Troubleshooting and Maintenance
Event name
Meaning
Source
Error attributes
Effects
System-defined variables
Cause and correction
Master User-set Allocations User Setting Failed Event code
An error occurred in the following operation for user allocation of the master.
• Master User Allocation Setting Switch (device variable *_Sw1MstrAlocCmd )
PLC Function Module Source details CJ-series Unit
34C 00000 hex
Detection timing
Log category Level
User program
Variable
None
Minor fault
Continues.
Recovery
Operation
Data type
---
Error reset
Not affected.
Assumed cause
The master function is not enabled.
Correction
Enable the master function.
There is a mistake in the user allocations in the master.
Correct the master user allocation settings.
CPU Unit is not in PROGRAM mode.
Change the CPU Unit to PROGRAM mode.
Execute the software switch operations one at a time.
Name
---
Prevention
At user operation
System
Enable the master function.
Correct the master user allocation settings.
Change the CPU Unit to PROGRAM mode when setting user allocations in the master.
Execute the software switch operations one at a time.
More than one software switch changed to TRUE at the same time.
Or, another software switch changed to TRUE before processing was completed for a previous software switch.
None Attached information
Precautions/
Remarks
None
Event name
Meaning
Source
Error attributes
Effects
System-defined variables
Cause and correction
Attached information
Precautions/
Remarks
Communications Cycle Time Setting Failed Event code 34C1 0000 hex
An error occurred in one of the following operations when setting the communications cycle time.
• Communications Cycle Time Temporary Setting Switch (device variable *_Sw1CycleTmTmpSet )
• Communications Cycle Time Setting Switch (device variable *_Sw1CycleTmSetCmd )
PLC Function Module Source details CJ-series Unit
Level
User program
Minor fault
Continues.
Recovery
Operation
Error reset
Not affected.
Detection timing
Log category
At user operation
System
Variable
None
Assumed cause
There is an error in the set information.
Data type
---
Correction
Correct the set information.
CPU Unit is not in PROGRAM mode.
Change the CPU Unit to PROGRAM mode.
Name
---
Prevention
Correct the set information.
Change the CPU Unit to PROGRAM mode before setting the communications cycle time.
None
None
9
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 9-47
9 Troubleshooting and Maintenance
Event name
Meaning
Source
Error attributes
Effects
System-defined variables
Cause and correction
Slave I/O Refresh Error
The I/O memory in the destination CPU Unit for I/O refreshing could not be found when refreshing the slave function data in the CPU Unit.
PLC Function Module Source details
Event code
CJ-series Unit
34C2 0000 hex
Detection timing
At power ON or
Controller reset
Level
User program
Variable
None
Minor fault
Continues.
Recovery
Operation
Data type
---
Error reset Log category
Remote I/O for the slave function
Name
---
System
Assumed cause
I/O words are allocated in an EM bank that does not exist.
Correction
Correct the I/O allocations so that only I/O words that exist in the I/O memory of a CPU Unit are allocated.
Prevention
Allocate only I/O words that exist in the I/O memory of a CPU Unit.
None Attached information
Precautions/
Remarks
None
Event name
Meaning
Source
Error attributes
Effects
System-defined variables
Cause and correction
Slave User Allocation Area Setting Failed Event code
An error occurred in the following operation for user allocation of the slave.
• Slave user allocation setting switch (device variable *_Sw2SlavAlocCmd )
PLC Function Module Source details CJ-series Unit
34C3 0000 hex
Recovery
Operation
Data type
---
Error reset
Not affected.
Correction
Disable the slave function.
Detection timing
Log category
At user operation
Level
User program
Variable
None
Assumed cause
Minor fault
Continues.
The slave function is not disabled.
System
There is a mistake in the user allocations to a slave.
Use the correct settings.
CPU Unit is not in PROGRAM mode.
Change the CPU Unit to PROGRAM mode.
Execute the software switch operations one at a time.
Change the CPU Unit to PROGRAM mode before setting user allocations for the slaves.
Execute the software switch operations one at a time.
More than one software switch changed to TRUE at the same time.
Or, another software switch changed to TRUE before processing was completed for a previous software switch.
None
Name
---
Prevention
Disable the slave function to set slave user allocations.
Check the settings.
Attached information
Precautions/
Remarks
None
9-48 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
9 Troubleshooting and Maintenance
Event name
Meaning
Source
Error attributes
Effects
System-defined variables
Cause and correction
Attached information
Precautions/
Remarks
Send Timeout Error
A send timeout occurred.
PLC Function Module
Level
User program
Variable
None
Assumed cause the network.
nodes.
nected or loose.
Minor fault
Continues.
There is no slave or other device on
The same baud rate is not set for all
Communications cable lengths (trunk line and branch lines) are unsuitable.
A communications cable is discon-
Event code 64AC 0000 hex
Source details
Recovery
Operation
CJ-series Unit Detection timing
When trying to establish a link or during DeviceNet communications
System Automatic recovery
Log category
The DeviceNet Unit will stop remote I/O communications and return errors for message send requests wherever there is a transmission timeout. When the system returns to normal status from the transmission timeout, the error display will stop, remote I/O communications will start, and message processing will return to normal. Remote I/O communications will not start again after recovery to normal operation, however, if remote I/O communications are set to stop when a communications error occurs.
Data type
---
Correction
Add at least one device to the network.
Name
---
Prevention
Connect at least one device to the network.
Set all nodes to the same baud rate.
Correct the settings so that all nodes use the same baud rate.
Adjust the communications cables to suitable lengths.
Connect the communications cable securely. If the communications cable is broken, replace it.
Connect terminating resistance only to the ends of the trunk line.
Make sure that the communications cable lengths are suitable.
Connect the communications cable securely. Check the communications cable to see if it is operating properly.
Connect terminating resistance only to the ends of the trunk line.
The terminating resistance is somewhere other than the ends of the trunk line.
Noise
There is an error in the CAN controller.
None
Implement noise countermeasures.
Replace the DeviceNet Unit.
Implement noise countermeasures.
None
None
9
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 9-49
9 Troubleshooting and Maintenance
Event name
Meaning
Source
Error attributes
Effects
System-defined variables
Cause and correction
Master Function Enable/Disable Failed Event code
An operating error occurred when enabling or disabling the master function.
• Master Function Enable Switch (device variable *_ Sw1MstrEnblCmd )
• Master Function Disable Switch (device variable *_ Sw1MstrDsblCmd )
PLC Function Module Source details CJ-series Unit
7460 0000 hex
Level
User program
Variable
None
Minor fault
Continues.
Recovery
Operation
Data type
---
Error reset
Not affected.
Assumed cause
An attempt was made to enable the master function when it was already enabled.
Correction
Disable the master function before you enable it.
An attempt was made to disable the master function when it was already disabled.
Enable the master function before you disable it.
CPU Unit is not in PROGRAM mode.
Change the CPU Unit to PROGRAM mode.
Execute the software switch operations one at a time.
Detection timing
Log category
At user operation
System
Name
---
Prevention
Disable the master function before you enable it.
Enable the master function before you disable it.
Change the CPU Unit to PROGRAM before you enable or disable the master function.
Execute the software switch operations one at a time.
More than one software switch changed to TRUE at the same time.
Or, another software switch changed to TRUE before processing was completed for a previous software switch.
None Attached information
Precautions/
Remarks
None
9-50 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
9 Troubleshooting and Maintenance
Event name
Meaning
Source
Error attributes
Effects
System-defined variables
Cause and correction
Master Fixed Allocation Area Setting Failed Event code 7461 0000 hex
An error occurred in one of the following operations for fixed allocation of the master.
• Fixed Allocation Area Setting 1 Switch (device variable *_Sw1MstrFixAloc1Cmd )
• Fixed Allocation Area Setting 2 Switch (device variable *_Sw1MstrFixAloc2Cmd )
• Fixed Allocation Area Setting 3 Switch (device variable *_ Sw1MstrFixAloc3Cmd )
PLC Function Module Source details CJ-series Unit
Level
User program
Minor fault
Continues.
Recovery
Operation
Error reset
Not affected.
Detection timing
Log category
Variable
None
Assumed cause
The master function is not enabled.
Data type
---
Correction
Enable the master function.
Name
---
Prevention
At user operation
System
Enable the master function.
The scan list is not disabled.
Disable the scan list.
CPU Unit is not in PROGRAM mode.
Change the CPU Unit to PROGRAM mode.
More than one software switch changed to TRUE at the same time.
Or, another software switch changed to TRUE before processing was completed for a previous software switch.
None
Execute the software switch operations one at a time.
Disable the scan list.
Change the CPU Unit to PROGRAM mode.
Execute the software switch operations one at a time.
Attached information
Precautions/
Remarks
None
9
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 9-51
9 Troubleshooting and Maintenance
Event name
Meaning
Source
Error attributes
Effects
System-defined variables
Cause and correction
Scan List Register/Clear Failed Event code 7462 0000 hex
An operating error occurred when registering or clearing the scan list by performing one of the following operations.
• Scan List Enable Switch (device variable *_ Sw1SListEnblCmd )
• Scan List Clear Switch (device variable *_Sw1SListClrCmd )
PLC Function Module Source details CJ-series Unit At user operation
Level
User program
Minor fault
Continues.
Recovery
Operation
Error reset
Not affected.
Detection timing
Log category System
Variable
None
Assumed cause Correction
CPU Unit is not in PROGRAM mode.
Change the CPU Unit to PROGRAM mode before executing a software switch operation.
Change to a status that supports software switch operations.
Request processing is not possible in this status or the request was made when the operation was already in progress. The following are the main causes of Unit status errors.
• A software switch operation for the master function was executed when the master function was disabled.
• A switch that can be used only when the scan list is disabled was used when the scan list was enabled.
• A switch that can be used only when the scan list is enables was used when the scan list was disabled.
• A software switch operation for the slave function was executed when the slave function was disabled.
A configuration error has occurred.
Data type
---
There is an error in the parameters specified in the user settings, and the requested setting could not be made.
More than one software switch changed to TRUE at the same time.
Or, another software switch changed to TRUE before processing was completed for a previous software switch.
None
Remove the cause of the configuration error, check that the error does not occur, and then register the scan list again.
Correct the parameter settings in the user settings and execute the software switch operation again.
Execute the software switch operations one at a time.
Name
---
Prevention
Change the CPU Unit to PROGRAM mode before executing a software switch operation.
Use the software switches only when the current status permits them.
Make sure that the configuration is correct.
Set the correct parameter settings in the user settings and execute the software switch operation again.
Execute the software switch operations one at a time.
Attached information
Precautions/
Remarks
None
9-52 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
9 Troubleshooting and Maintenance
Event name
Meaning
Source
Error attributes
Effects
System-defined variables
Cause and correction
Slave Function Enable/Disable Failed Event code
An error occurred in one of the following operations in the slave function.
• Slave Function Enable Switch (device variable *_ Sw2SlavEnblCmd )
• Slave Function Disable Switch (device variable *_ Sw2SlavDsblCmd )
PLC Function Module Source details CJ-series Unit
7463 0000 hex
Level
User program
Variable
None
Minor fault
Continues.
Assumed cause
An attempt was made to enable the slave function when it was already enabled.
Recovery
Operation
Data type
---
Error reset
Not affected.
Correction
Disable the slave function before you enable it.
An attempt was made to disable the slave function when it was already disabled.
Enable the slave function before you disable it.
CPU Unit is not in PROGRAM mode.
Change the CPU Unit to PROGRAM mode.
More than one software switch changed to TRUE at the same time.
Or, another software switch changed to TRUE before processing was completed for a previous software switch.
Execute the software switch operations one at a time.
None
Detection timing
Log category
At user operation
System
Name
---
Prevention
Disable the slave function before you enable it.
Enable the slave function before you disable it.
Change the CPU Unit to PROGRAM mode.
Execute the software switch operations one at a time.
Attached information
Precautions/
Remarks
None
9
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 9-53
9 Troubleshooting and Maintenance
Event name
Meaning
Source
Error attributes
Effects
System-defined variables
Cause and correction
Slave Fixed Allocation Area Setting Failed Event code 7464 0000 hex
An error occurred in one of the following operations for fixed allocation of the slave.
• Slave Fixed Allocation Area Setting 1 Switch (device variable *_Sw2SlavFixAloc1Cmd )
• Slave Fixed Allocation Area Setting 2 Switch (device variable *_Sw2SlavFixAloc2Cmd )
• Slave Fixed Allocation Area Setting 3 Switch (device variable *_ Sw2SlavFixAloc3Cmd )
PLC Function Module Source details CJ-series Unit
Level
User program
Minor fault
Continues.
Recovery
Operation
Error reset
Not affected.
Detection timing
Log category
Variable
None
Assumed cause
The slave function is not disabled.
Data type
---
Correction
Disable the slave function.
Name
---
Prevention
At user operation
System
Disable the slave function.
CPU Unit is not in PROGRAM mode.
Change the CPU Unit to PROGRAM mode.
More than one software switch changed to TRUE at the same time.
Or, another software switch changed to TRUE before processing was completed for a previous software switch.
Execute the software switch operations one at a time.
None
Change the CPU Unit to PROGRAM mode.
Execute the software switch operations one at a time.
Attached information
Precautions/
Remarks
None
9-54 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
9 Troubleshooting and Maintenance
Event name
Meaning
Source
Error attributes
Effects
System-defined variables
Cause and correction
Attached information
Precautions/
Remarks
Bus Off Detected Event code 8474 0000 hex
A Bus Off error occurred (i.e., communications stopped because there were too many communications errors).
PLC Function Module Source details CJ-series Unit Detection timing
When the I/O connection is established or
DeviceNet communications are performed
Level
User program
Minor fault
Continues.
Recovery
Operation
Cycle the power supply or reset the Controller.
Log category System
The DeviceNet Unit is offline. Communications will not operate. Error responses are returned to all communications requests. Data refreshing with the CPU Unit continues.
Variable
None
Assumed cause
The master and slave have different baud rates.
Communications cable lengths (trunk line and branch lines) are unsuitable.
A communications cable is disconnected or loose.
The terminating resistance is somewhere other than the ends of the trunk line.
Noise
None
Data type
---
Correction
Correct the settings so that the master and slaves use the same baud rate.
Refer to the communications specifications and adjust all of the communications cables to suitable lengths.
Connect the communications cable securely. If the communications cable is broken, replace it.
Connect terminating resistance only to the ends of the trunk line.
Implement noise countermeasures.
Name
---
Prevention
Set the master and slaves to the same baud rate.
Refer to the communications specifications and adjust all of the communications cables to suitable lengths.
Connect the communications cable securely. Check the communications cable to see if it is operating properly.
Connect terminating resistance only to the ends of the trunk line.
Implement noise countermeasures.
None
9
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 9-55
9 Troubleshooting and Maintenance
Event name
Meaning
Source
Error attributes
Effects
System-defined variables
Cause and correction
Attached information
Precautions/
Remarks
Remote I/O Communications Error
A timeout occurred in remote I/O communications.
PLC Function Module Source details
Level
User program
Variable
None
Assumed cause
The master and slaves have different baud rates.
Minor fault
Continues.
Event code 8475 0000 hex
Recovery
Operation
Data type
---
Correction
Correct the settings so that the master and slaves use the same baud rate.
CJ-series Unit Detection timing
Log category
During DeviceNet communications
System Error reset
The DeviceNet Unit periodically performs reconnection processing for slaves that have a remote I/O communications error. Remote I/O communications will stop, however, when a communications error occurs and remote I/O communications are set to stop.
Name
---
Prevention
Set the master and slaves to the same baud rate.
Communications cable lengths (trunk line and branch lines) are unsuitable.
A communications cable is disconnected or loose.
The terminating resistance is somewhere other than the ends of the trunk line.
Noise
None
Refer to the communications specifications and adjust all of the cables to suitable lengths.
Connect the communications cable securely. If the communications cable is broken, replace it.
Connect terminating resistance only to the ends of the trunk line.
Implement noise countermeasures.
Refer to the communications specifications and adjust all of the cables to suitable lengths.
Connect the communications cable securely. Check to see if the communications cable is operating properly.
Connect terminating resistance only to the ends of the trunk line.
Implement noise countermeasures.
You can change the event level to the observation level. If you change the level to the observation level, recovery procedures are not required.
9-56 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
9 Troubleshooting and Maintenance
Event name
Meaning
Source
Error attributes
Effects
System-defined variables
Cause and correction
Remote I/O Communications Error (during Slave Operation)
An error occurred in remote I/O communications.
PLC Function Module Source details
Level
User program
Variable
None
Assumed cause
Minor fault
Continues.
The master is not in operation.
Event code 8476 0000 hex
Recovery
Operation
CJ-series Unit Detection timing
Log category
During DeviceNet communications
System Error reset
Outputs will be retained or cleared according to the settings if there are output words.
Name
---
Data type
---
Correction
Check to see if the master is operating normally. If it is not, investigate the cause, and then perform corrective actions.
Prevention
Check to make sure the master is operating normally.
The master and slaves have different baud rates.
Set the master and slaves to the same baud rate.
Communications cable lengths (trunk line and branch lines) are unsuitable.
A communications cable is disconnected or loose.
The terminating resistance is somewhere other than the ends of the trunk line.
Noise
None
Correct the settings so that the master and slaves use the same baud rate.
Refer to the communications specifications and adjust all of the communications cables to suitable lengths.
Connect the communications cable securely. If the communications cable is broken, replace it.
Connect terminating resistance only to the ends of the trunk line.
Implement noise countermeasures.
Refer to the communications specifications and adjust all of the cables to suitable lengths.
Connect the communications cable securely. Check to see if the communications cable is operating properly.
Connect terminating resistance only to the ends of the trunk line.
Implement noise countermeasures.
Attached information
Precautions/
Remarks
None
9
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 9-57
9 Troubleshooting and Maintenance
Event name
Meaning
Source
Error attributes
Effects
System-defined variables
Cause and correction
Slave COS Send Failed
An attempt was made to send COS data to the master using the Slave COS Send Switch (software switch 2, device variable *_ Sw2SlavCOSSendCmd ), but the send failed.
PLC Function Module Source details
Event code
CJ-series Unit
8477 0000 hex
Detection timing
During DeviceNet communications
Level
User program
Variable
None
Minor fault
Continues.
Recovery
Operation
Data type
---
Error reset Log category
COS transmissions are not possible.
Name
---
System
Assumed cause
A COS connection to the master is not open.
A Bus Off state occurred.
Correction
Open a COS connection to the master.
Prevention
When you perform COS communications, open a COS connection between the master and slave.
Take measures to prevent the errors from occurring again.
A network power error occurred.
A send timeout occurred.
Remove the cause of the Bus Off error.
Remove the cause of the power supply error.
Remove the cause of the send timeout.
None Attached information
Precautions/
Remarks
None
Event name
Meaning
Source
Error attributes
Effects
System-defined variables
Cause and correction
File Read/Write Error
An error occurred when user setup data was read from an SD Memory Card in the CPU Unit or when data was written as a file to an SD Memory Card.
PLC Function Module Source details
Event code
CJ-series Unit
048A 0000 hex
Detection timing
When SD Memory Card backup is executed
Level
User program
Variable
None
Observation
Continues.
Recovery
Operation
Data type
---
---
Not affected.
Log category
Name
---
System
Assumed cause
The available capacity on the SD
Memory Card was insufficient to write a file.
Write-protection is set on the SD
Memory Card when you write to a file.
Correction
Replace the SD Memory Card for one with sufficient available capacity. Or, delete unnecessary files from the SD
Memory Card.
Remove write-protection from the SD
Memory Card.
Prevention
Use an SD Memory Card with sufficient available capacity when you save files to it.
Noise
The SD Memory Card is damaged.
The CPU Unit has failed.
None
Implement noise countermeasures.
Replace the SD Memory Card.
Replace the CPU Unit.
Disable write-protection on the SD
Memory Card before you save the file to the SD Memory Card.
Implement noise countermeasures.
None
None
Attached information
Precautions/
Remarks
You can change the event level to the minor fault level. If you change the level to the minor fault level, the umn above will be changed to “Error reset.”
Recovery col-
9-58 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
9 Troubleshooting and Maintenance
Event name
Meaning
Source
Error attributes
Effects
System-defined variables
Cause and correction
Attached information
Precautions/
Remarks
Invalid Message Timer List Error
The data in the message monitoring timer list is not correct.
Event code
PLC Function Module Source details
Level
User program
Observation
Continues.
Recovery
Operation
148C 0000 hex
CJ-series Unit Detection timing
Log category
At power ON or
Controller reset
System ---
The message monitoring timer will operate with the default value.
Variable
None
Assumed cause
The power supply was interrupted while writing the message-monitoring timer list to the non-volatile memory.
None
Data type
---
Correction
Register the message-monitoring timer list again.
Name
---
Prevention
Do not turn OFF the power supply while the system is writing the settings.
You can change the event level to the minor fault level. If you change the level to the minor fault level, the umn above will be changed to “Error reset.”
Recovery col-
9
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 9-59
9 Troubleshooting and Maintenance
9-5 Maintenance and Replacement
This section describes the routine cleaning and inspection recommended as regular maintenance as well as the Unit replacement procedure.
9-5-1 Cleaning
Clean the DeviceNet Units regularly as described below in order to keep the network in its optimal operating condition.
• Wipe the Unit daily with a dry, soft cloth.
• When a spot can't be removed with a dry cloth, dampen the cloth with a neutral cleanser (2% solution), wring out the cloth, and wipe the Unit.
• A smudge may remain on the Unit from gum, vinyl, or tape that was left on for a long time. Remove the smudge when cleaning.
Never use volatile solvents such as paint thinner, benzene, or chemical wipes. These substances could damage the surface of the Unit.
9-5-2 Inspection
Be sure to inspect the system periodically to keep it in its optimal operating condition. In general, inspect the system once every 6 to 12 months, but inspect more frequently if the system is used with high temperature or humidity or under dirty/dusty conditions.
Inspection Equipment
Prepare the following equipment before inspecting the system.
z
Required Equipment
Have a standard and Phillips-head screwdriver, multimeter, alcohol, and a clean cloth.
z
Equipment Required Occasionally
Depending on the system conditions, a synchroscope, oscilloscope, thermometer, or hygrometer (to measure humidity) might be needed.
Inspection Procedure
Check the items in the following table and correct any items that are below standard.
Environmental conditions
Item
Ambient and cabinet temperature
Ambient and cabinet humidity
Standard
0
°
C to 55
°
C
Equipment
Thermometer
Hygrometer
Dust/dirt accumulation
10% to 90%
(with no condensation or icing)
None Check visually
9-60 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
9 Troubleshooting and Maintenance
Installation
Item Standard Equipment
Are the Units installed securely?
No looseness Phillips head screwdriver
Are the communications connectors fully inserted?
Are the external wiring screws tight?
Are the connecting cables undamaged?
No looseness
No looseness
No damage
Phillips head screwdriver
Phillips head screwdriver
Check visually
9-5-3 Replacing Faulty Units
Replace a DeviceNet Unit with an error as soon as possible. Refer to the DRT2 Series DeviceNet
Slaves Operation Manual (Cat. No. W404) or the DeviceNet MULTIPLE I/O TERMINAL Operation Manual (Cat. No. W348) for details on replacing slaves. We recommend having spare Units available to restore network operation as quickly as possible.
Precautions
Observe the following precautions when replacing a faulty Unit.
• After replacement make sure that there are no errors with the new Unit.
• When a Unit is being returned for repair, attach a sheet of paper detailing the problem and return the Unit to your OMRON dealer.
• If there is a faulty contact, try wiping the contact with a clean, lint-free cloth dampened with alcohol.
Precautions for Safe Use
To prevent electric shock when replacing a Unit, be sure to stop communications in the network and turn OFF the power supplies to all of the nodes (master and slaves) before removing the faulty Unit.
Settings after Replacing DeviceNet Units
When the master communication is used, the scan list (project file) must be registered again.
All of the settings data stored in the DeviceNet Unit can be saved to the CPU Unit's SD Memory
Card*
1
and later read from the SD Memory Card*
2
. It will be much easier to replace the Unit if you save all of the settings data when the Unit is operating normally.
*1 Change *_Sw2FileBkupCmd (Unit Setup File Backup Switch) to TRUE.
*2 Change *_Sw2FileRestoreCmd (Unit Setup File Restore Switch) to TRUE.
The backup file is saved to the CPU Unit's SD Memory Card with the filename DNnnBKUP.dvf. (The number "nn" is the unit number in 2-digit hexadecimal.) z
Fixed Remote I/O Allocations
Turn ON power to all slaves and then select one of the fixed allocations areas (1, 2, or 3) and change
*_Sw1SListEnblCmd (Scan List Enable Switch) of software switch 1 to TRUE. The scan list will be registered.
For details on allocation procedures, refer to 4-3-2 Allocation Procedures .
z
User-set Remote I/O Allocations
Use one of the following procedures.
9
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) 9-61
9 Troubleshooting and Maintenance
Using the Settings Data Stored in the NJ-series CPU Unit's SD Memory Card
Use the following procedure to write all of the settings data from the SD Memory Card to the
DeviceNet Unit.
1
Turn ON the Controller power supply.
2
Switch the CPU Unit to PROGRAM mode.
3
Change *_Sw2FileRestoreCmd (Unit Setup File Restore Switch) of software switch 2 to TRUE.
Using a Stored Project File
Write the settings to the Master Unit from a project file saved on a disk.
1
Turn ON the power to the DeviceNet Unit.
2
Place the CX-Integrator online and read the project file that was previously saved.
3
Use the Device Parameters Edit operation to specify the Master Unit that has been replaced, and to write the settings from the project file to the device.
Writing a Network Configuration
Read out the network configuration from the actual configuration and write this to the Master Unit again.
1
Turn ON the power to the Master Unit and slaves.
2
Place the CX-Integrator online and read the Network Configuration.
3
Specify the Master, and use the Device Parameters Edit operation to register slaves and to allocate I/O.
4
Write the settings to the devices.
• When user-set remote I/O allocations are used, always save the project file to restore operation quickly if the Master Unit needs to be replaced.
• When the CPU Unit is replaced, be sure that all data in the DM Area, HR Area, and other memory areas is transferred to the new CPU Unit before starting operation.
9-62 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
pp
Appendices
A-3 DeviceNet Explicit Message Send Command for Other Manufacturer
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) A-1
Appendices
A-1 Differences in Available Functions
Depending on the CPU Unit (NJ or
CJ Series)
Some of the specifications when a DeviceNet Unit is connected to a CJ-series CPU Unit are different from the specifications when the DeviceNet Unit is connected to an NJ-series CPU Unit. A list of these differences is provided below.
A-1-1 Functional Differences
There are differences in function support, function names, and specifications between when a
DeviceNet Unit is connected to a CJ-series CPU Unit and when the DeviceNet Unit is connected to an
NJ-series CPU Unit.
Unsupported Functions
The following function cannot be used when the DeviceNet Unit is connected to an NJ-series CPU Unit.
• DeviceNet Configurator connection (Use the CX-Integrator instead.)
Functions with Different Names
The names of the following functions are different between when a DeviceNet Unit is connected to a
CJ-series CPU Unit and when the DeviceNet Unit is connected to an NJ-series CPU Unit. The corresponding names are listed in the following table.
Item
DeviceNet Unit connected to a CJ-series
CPU Unit
Backup functions Simple backup function
Backup with PLC backup tool
DeviceNet Unit connected to an NJ-series
CPU Unit
SD Memory Card backup function *
Sysmac Studio Controller backup function *
* An NJ-series CPU Unit with unit version 1.03 or later and Sysmac Studio version 1.04 or higher are required.
A-1-2 Differences in Accessing from User Program
When this Unit is operated with an NJ-series device, a user program accesses various functions provided by the DeviceNet Unit through device variables for CJ-series Unit that specifies AT specification for the memory used for CJ-series Unit.
The device variables for CJ-series Unit in the NJ-series CPU Unit's memory for CJ series Unit that correspond to the addresses and bit positions in the CJ-series CPU Unit's I/O memory are listed below.
First word in Special I/O Unit CIO Area: n = CIO 1,500 + Unit number
×
25 (Unit number: 0 to 15)
First word in Special I/O Unit DM Area: m = D30,000 + Unit number × 100 (Unit number: 0 to 15)
CPU Bus Unit Words Allocated in CIO Area
z
CIO n (Software Switch 1)
The device variable for CJ-series Unit that corresponds to all bits of a word starting with CIO n is as follows:
A-2 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Appendices
CJ-series I/O memory address
Word address
CIO n
Bit
0 to 15 *_Sw1Cmd
NJ-series device variables for CJ-series Unit
Variable name Description
Software Switches 1 (The functions of bits 0 to 15 of CIO n correspond to those of bits 0 to 15 of this CJ-series
Unit device variable.)
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) A-3
Appendices
The device variables for CJ-series Units that correspond to bits 0 to 15 of a word starting with CIO n are as follows:
CJ-series I/O memory address
Word address
CIO n
Bit
0
3
4
1
2
9
10
11
12
7
8
5
6
13
14
15
NJ-series device variables for CJ-series Unit
Variable name
*_Sw1SListEnblCmd
Description
Scan List Enable Switch
*_Sw1SListClrCmd
*_Sw1IOCommStartCmd
Undefined
*_Sw1IOCommStopCmd
Scan List Clear Switch
Remote I/O Communications Start Switch
Undefined
Remote I/O Communications Stop Switch
---
*_Sw1MstrEnblCmd
*_Sw1MstrDsblCmd
*_Sw1MstrFixAloc1Cmd
*_Sw1MstrFixAloc2Cmd
*_Sw1MstrFixAloc3Cmd
*_Sw1MstrAlocCmd
*_Sw1CycleTmTmpSet
*_Sw1CycleTmSetCmd
*_Sw1CycleTmClrCmd
---
Reserved by system
Master Enable Switch
Master Disable Switch
Master Fixed Allocation Setting 1 Switch
Master Fixed Allocation Setting 2 Switch
Master Fixed Allocation Setting 3 Switch
Master User-set Allocations Switch
Temporary Setting Switch for Communications Cycle Time
Communications Cycle Time Setting
Switch
Communications Cycle Time Reference
Table Clear Switch
Reserved by system z
CIO n+1 (Software Switch 2)
The device variable for CJ-series Unit that corresponds to all bits of a word starting with CIO n+1 is as follows:
CJ-series I/O memory address
Word address Bit
CIO n+1 0 to 15 *_Sw2Cmd
NJ-series device variables for CJ-series Unit
Variable name CJ-series function name
Software Switches 2 (The functions of bits
1 to 0 of CIO n+1 correspond to those of bits 0 to 15 of this CJ-series Unit device variable.)
A-4 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Appendices
The device variables for CJ-series Units that correspond to bits 0 to 15 of a word starting with CIO n+1 are as follows:
CJ-series I/O memory address
Word address
CIO n+1
Bit
0 to 5
8
9
6
7
10
11
12
13
14
15
NJ-series device variables for CJ-series Unit
Variable name
---
CJ-series function name
Reserved by system
*_Sw2SlavEnblCmd
*_Sw2SlavDsblCmd
*_Sw2SlavFixAloc1Cmd
*_Sw2SlavFixAloc2Cmd
Slave Enable Switch
Slave Stop Switch
Slave Fixed Allocation Setting 1 Switch
Slave Fixed Allocation Setting 2 Switch
*_Sw2SlavFixAloc3Cmd
*_Sw2SlavAlocCmd
*_Sw2SlavCOSSendCmd
---
*_Sw2FileRestoreCmd
*_Sw2FileBkupCmd
Slave Fixed Allocation Setting 3 Switch
Slave User Allocations Switch
Slave COS Send Switch
Reserved by system
Unit Setup File Restore Switch
Unit Setup File Backup Switch z
CIO n+2 to n+5 (Master COS Send Switch)
The device variable for CJ-series Unit that corresponds to all bits of 4 words from CIO n+2 to n+5 is as follows:
CJ-series I/O memory address
Word address Bit
NJ-series device variables for CJ-series Unit
Variable name
CIO n+2 to n+5 0 to 15 for each word *_MstrCOSSendCmd
CJ-series function name
Master COS Send Switch
Bits 0 to 15 in each word correspond to the bits of this CJ-series Unit device variable as follows:
• Bits 0 to 15 of CIO n+2 correspond to bits 0 to 15 of this CJ-series Unit device variable.
• Bits 0 to 15 of CIO n+3 correspond to bits 16 to 31 of this CJ-series Unit device variable.
• Bits 0 to 15 of CIO n+4 correspond to bits 32 to 47 of this CJ-series Unit device variable.
• Bits 0 to 15 of CIO n+5 correspond to bits 48 to 63 of this CJ-series Unit device variable.
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) A-5
Appendices
The device variables for CJ-series Units that correspond to bits 0 to 15 of 4 words from CIO n+2 to n+5 are as follows:
CJ-series I/O memory address
Word address
CIO n+2
Bit
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
NJ-series device variables for CJ-series Unit
Variable name
*_MstrCOSSendNdCmd[0]
*_MstrCOSSendNdCmd[1]
*_MstrCOSSendNdCmd[2]
*_MstrCOSSendNdCmd[3]
*_MstrCOSSendNdCmd[4]
*_MstrCOSSendNdCmd[5]
*_MstrCOSSendNdCmd[6]
*_MstrCOSSendNdCmd[7]
*_MstrCOSSendNdCmd[8]
*_MstrCOSSendNdCmd[9]
*_MstrCOSSendNdCmd[10]
*_MstrCOSSendNdCmd[11]
*_MstrCOSSendNdCmd[12]
*_MstrCOSSendNdCmd[13]
*_MstrCOSSendNdCmd[14]
*_MstrCOSSendNdCmd[15]
CJ-series function name
Master COS Send Switch for Node
Address 0 Slave
Master COS Send Switch for Node
Address 1 Slave
Master COS Send Switch for Node
Address 2 Slave
Master COS Send Switch for Node
Address 3 Slave
Master COS Send Switch for Node
Address 4 Slave
Master COS Send Switch for Node
Address 5 Slave
Master COS Send Switch for Node
Address 6 Slave
Master COS Send Switch for Node
Address 7 Slave
Master COS Send Switch for Node
Address 8 Slave
Master COS Send Switch for Node
Address 9 Slave
Master COS Send Switch for Node
Address 10 Slave
Master COS Send Switch for Node
Address 11 Slave
Master COS Send Switch for Node
Address 12 Slave
Master COS Send Switch for Node
Address 13 Slave
Master COS Send Switch for Node
Address 14 Slave
Master COS Send Switch for Node
Address 15 Slave
A-6 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Appendices
The device variables for CJ-series Units that correspond to bits 0 to 15 of 4 words from CIO n+2 to n+5 are as follows:
CJ-series I/O memory address
Word address
CIO n+3
Bit
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
NJ-series device variables for CJ-series Unit
Variable name
*_MstrCOSSendNdCmd[16]
*_MstrCOSSendNdCmd[17]
*_MstrCOSSendNdCmd[18]
*_MstrCOSSendNdCmd[19]
*_MstrCOSSendNdCmd[20]
*_MstrCOSSendNdCmd[21]
*_MstrCOSSendNdCmd[22]
*_MstrCOSSendNdCmd[23]
*_MstrCOSSendNdCmd[24]
*_MstrCOSSendNdCmd[25]
*_MstrCOSSendNdCmd[26]
*_MstrCOSSendNdCmd[27]
*_MstrCOSSendNdCmd[28]
*_MstrCOSSendNdCmd[29]
*_MstrCOSSendNdCmd[30]
*_MstrCOSSendNdCmd[31]
CJ-series function name
Master COS Send Switch for Node
Address 16 Slave
Master COS Send Switch for Node
Address 17 Slave
Master COS Send Switch for Node
Address 18 Slave
Master COS Send Switch for Node
Address 19 Slave
Master COS Send Switch for Node
Address 20 Slave
Master COS Send Switch for Node
Address 21 Slave
Master COS Send Switch for Node
Address 22 Slave
Master COS Send Switch for Node
Address 23 Slave
Master COS Send Switch for Node
Address 24 Slave
Master COS Send Switch for Node
Address 25 Slave
Master COS Send Switch for Node
Address 26 Slave
Master COS Send Switch for Node
Address 27 Slave
Master COS Send Switch for Node
Address 28 Slave
Master COS Send Switch for Node
Address 29 Slave
Master COS Send Switch for Node
Address 30 Slave
Master COS Send Switch for Node
Address 31 Slave
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) A-7
Appendices
CJ-series I/O memory address
Word address
CIO n+4
Bit
0
1
2
5
6
3
4
13
14
11
12
15
9
10
7
8
NJ-series device variables for CJ-series Unit
Variable name
*_MstrCOSSendNdCmd[32]
*_MstrCOSSendNdCmd[33]
*_MstrCOSSendNdCmd[34]
*_MstrCOSSendNdCmd[35]
*_MstrCOSSendNdCmd[36]
*_MstrCOSSendNdCmd[37]
*_MstrCOSSendNdCmd[38]
*_MstrCOSSendNdCmd[39]
*_MstrCOSSendNdCmd[40]
*_MstrCOSSendNdCmd[41]
*_MstrCOSSendNdCmd[42]
*_MstrCOSSendNdCmd[43]
*_MstrCOSSendNdCmd[44]
*_MstrCOSSendNdCmd[45]
*_MstrCOSSendNdCmd[46]
*_MstrCOSSendNdCmd[47]
CJ-series function name
Master COS Send Switch for Node
Address 32 Slave
Master COS Send Switch for Node
Address 33 Slave
Master COS Send Switch for Node
Address 34 Slave
Master COS Send Switch for Node
Address 35 Slave
Master COS Send Switch for Node
Address 36 Slave
Master COS Send Switch for Node
Address 37 Slave
Master COS Send Switch for Node
Address 38 Slave
Master COS Send Switch for Node
Address 39 Slave
Master COS Send Switch for Node
Address 40 Slave
Master COS Send Switch for Node
Address 41 Slave
Master COS Send Switch for Node
Address 42 Slave
Master COS Send Switch for Node
Address 43 Slave
Master COS Send Switch for Node
Address 44 Slave
Master COS Send Switch for Node
Address 45 Slave
Master COS Send Switch for Node
Address 46 Slave
Master COS Send Switch for Node
Address 47 Slave
A-8 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Appendices
CJ-series I/O memory address
Word address
CIO n+5
Bit
0
1
2
5
6
3
4
13
14
11
12
15
9
10
7
8
NJ-series device variables for CJ-series Unit
Variable name
*_MstrCOSSendNdCmd[48]
*_MstrCOSSendNdCmd[49]
*_MstrCOSSendNdCmd[50]
*_MstrCOSSendNdCmd[51]
*_MstrCOSSendNdCmd[52]
*_MstrCOSSendNdCmd[53]
*_MstrCOSSendNdCmd[54]
*_MstrCOSSendNdCmd[55]
*_MstrCOSSendNdCmd[56]
*_MstrCOSSendNdCmd[57]
*_MstrCOSSendNdCmd[58]
*_MstrCOSSendNdCmd[59]
*_MstrCOSSendNdCmd[60]
*_MstrCOSSendNdCmd[61]
*_MstrCOSSendNdCmd[62]
*_MstrCOSSendNdCmd[63]
CJ-series function name
Master COS Send Switch for Node
Address 48 Slave
Master COS Send Switch for Node
Address 49 Slave
Master COS Send Switch for Node
Address 50 Slave
Master COS Send Switch for Node
Address 51 Slave
Master COS Send Switch for Node
Address 52 Slave
Master COS Send Switch for Node
Address 53 Slave
Master COS Send Switch for Node
Address 54 Slave
Master COS Send Switch for Node
Address 55 Slave
Master COS Send Switch for Node
Address 56 Slave
Master COS Send Switch for Node
Address 57 Slave
Master COS Send Switch for Node
Address 58 Slave
Master COS Send Switch for Node
Address 59 Slave
Master COS Send Switch for Node
Address 60 Slave
Master COS Send Switch for Node
Address 61 Slave
Master COS Send Switch for Node
Address 62 Slave
Master COS Send Switch for Node
Address 63 Slave
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) A-9
Appendices z
CIO n+6 to n+9 (Disconnect/Connect Switch)
The device variable for CJ-series Unit that corresponds to all bits of 4 words from CIO n+6 to n+9 is as follows:
CJ-series I/O memory address
Word address Bit
CIO n+6 to n+9 0 to 15 for each word *_CnctCmd
NJ-series device variables for CJ-series Unit
Variable name CJ-series function name
Disconnect/Connect Switches
Bits 0 to 15 in each word correspond to the bits of this CJ-series Unit device variable as follows:
• Bits 0 to 15 of CIO n+6 correspond to bits 0 to 15 of this CJ-series Unit device variable.
• Bits 0 to 15 of CIO n+7 correspond to bits 16 to 31 of this CJ-series Unit device variable.
• Bits 0 to 15 of CIO n+8 correspond to bits 32 to 47 of this CJ-series Unit device variable.
• Bits 0 to 15 of CIO n+9 correspond to bits 48 to 63 of this CJ-series Unit device variable.
A-10 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Appendices
The device variables for CJ-series Units that correspond to bits 0 to 15 of 4 words from CIO n+6 to n+9 are as follows:
CJ-series I/O memory address
Word address
CIO n+6
Bit
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
*_CnctNdCmd[1]
*_CnctNdCmd[2]
*_CnctNdCmd[3]
*_CnctNdCmd[4]
*_CnctNdCmd[5]
*_CnctNdCmd[6]
*_CnctNdCmd[7]
*_CnctNdCmd[8]
*_CnctNdCmd[9]
NJ-series device variables for CJ-series Unit
Variable name
*_CnctNdCmd[0]
*_CnctNdCmd[10]
*_CnctNdCmd[11]
*_CnctNdCmd[12]
*_CnctNdCmd[13]
*_CnctNdCmd[14]
*_CnctNdCmd[15]
CJ-series function name
Disconnect/Connect Switch for Node
Address 0 Slave
Disconnect/Connect Switch for Node
Address 1 Slave
Disconnect/Connect Switch for Node
Address 2 Slave
Disconnect/Connect Switch for Node
Address 3 Slave
Disconnect/Connect Switch for Node
Address 4 Slave
Disconnect/Connect Switch for Node
Address 5 Slave
Disconnect/Connect Switch for Node
Address 6 Slave
Disconnect/Connect Switch for Node
Address 7 Slave
Disconnect/Connect Switch for Node
Address 8 Slave
Disconnect/Connect Switch for Node
Address 9 Slave
Disconnect/Connect Switch for Node
Address 10 Slave
Disconnect/Connect Switch for Node
Address 11 Slave
Disconnect/Connect Switch for Node
Address 12 Slave
Disconnect/Connect Switch for Node
Address 13 Slave
Disconnect/Connect Switch for Node
Address 14 Slave
Disconnect/Connect Switch for Node
Address 15 Slave
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) A-11
Appendices
CJ-series I/O memory address
Word address
CIO n+7
Bit
0
1
2
5
6
3
4
13
14
11
12
15
9
10
7
8
NJ-series device variables for CJ-series Unit
Variable name
*_CnctNdCmd[16]
*_CnctNdCmd[17]
*_CnctNdCmd[18]
*_CnctNdCmd[19]
*_CnctNdCmd[20]
*_CnctNdCmd[21]
*_CnctNdCmd[22]
*_CnctNdCmd[23]
*_CnctNdCmd[24]
*_CnctNdCmd[25]
*_CnctNdCmd[26]
*_CnctNdCmd[27]
*_CnctNdCmd[28]
*_CnctNdCmd[29]
*_CnctNdCmd[30]
*_CnctNdCmd[31]
CJ-series function name
Disconnect/Connect Switch for Node
Address 16 Slave
Disconnect/Connect Switch for Node
Address 17 Slave
Disconnect/Connect Switch for Node
Address 18 Slave
Disconnect/Connect Switch for Node
Address 19 Slave
Disconnect/Connect Switch for Node
Address 20 Slave
Disconnect/Connect Switch for Node
Address 21 Slave
Disconnect/Connect Switch for Node
Address 22 Slave
Disconnect/Connect Switch for Node
Address 23 Slave
Disconnect/Connect Switch for Node
Address 24 Slave
Disconnect/Connect Switch for Node
Address 25 Slave
Disconnect/Connect Switch for Node
Address 26 Slave
Disconnect/Connect Switch for Node
Address 27 Slave
Disconnect/Connect Switch for Node
Address 28 Slave
Disconnect/Connect Switch for Node
Address 29 Slave
Disconnect/Connect Switch for Node
Address 30 Slave
Disconnect/Connect Switch for Node
Address 31 Slave
A-12 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Appendices
The device variables for CJ-series Units that correspond to bits 0 to 15 of 4 words from CIO n+6 to n+9 are as follows:
CJ-series I/O memory address
Word address
CIO n+8
Bit
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
NJ-series device variables for CJ-series Unit
Variable name
*_CnctNdCmd[32]
*_CnctNdCmd[33]
*_CnctNdCmd[34]
*_CnctNdCmd[35]
*_CnctNdCmd[36]
*_CnctNdCmd[37]
*_CnctNdCmd[38]
*_CnctNdCmd[39]
*_CnctNdCmd[40]
*_CnctNdCmd[41]
*_CnctNdCmd[42]
*_CnctNdCmd[43]
*_CnctNdCmd[44]
*_CnctNdCmd[45]
*_CnctNdCmd[46]
*_CnctNdCmd[47]
CJ-series function name
Disconnect/Connect Switch for Node
Address 32 Slave
Disconnect/Connect Switch for Node
Address 33 Slave
Disconnect/Connect Switch for Node
Address 34 Slave
Disconnect/Connect Switch for Node
Address 35 Slave
Disconnect/Connect Switch for Node
Address 36 Slave
Disconnect/Connect Switch for Node
Address 37 Slave
Disconnect/Connect Switch for Node
Address 38 Slave
Disconnect/Connect Switch for Node
Address 39 Slave
Disconnect/Connect Switch for Node
Address 40 Slave
Disconnect/Connect Switch for Node
Address 41 Slave
Disconnect/Connect Switch for Node
Address 42 Slave
Disconnect/Connect Switch for Node
Address 43 Slave
Disconnect/Connect Switch for Node
Address 44 Slave
Disconnect/Connect Switch for Node
Address 45 Slave
Disconnect/Connect Switch for Node
Address 46 Slave
Disconnect/Connect Switch for Node
Address 47 Slave
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) A-13
Appendices
CJ-series I/O memory address
Word address
CIO n+9
Bit
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
NJ-series device variables for CJ-series Unit
Variable name
*_CnctNdCmd[48]
*_CnctNdCmd[49]
*_CnctNdCmd[50]
*_CnctNdCmd[51]
*_CnctNdCmd[52]
*_CnctNdCmd[53]
*_CnctNdCmd[54]
*_CnctNdCmd[55]
*_CnctNdCmd[56]
*_CnctNdCmd[57]
*_CnctNdCmd[58]
*_CnctNdCmd[59]
*_CnctNdCmd[60]
*_CnctNdCmd[61]
*_CnctNdCmd[62]
*_CnctNdCmd[63]
CJ-series function name
Disconnect/Connect Switch for Node
Address 48 Slave
Disconnect/Connect Switch for Node
Address 49 Slave
Disconnect/Connect Switch for Node
Address 50 Slave
Disconnect/Connect Switch for Node
Address 51 Slave
Disconnect/Connect Switch for Node
Address 52 Slave
Disconnect/Connect Switch for Node
Address 53 Slave
Disconnect/Connect Switch for Node
Address 54 Slave
Disconnect/Connect Switch for Node
Address 55 Slave
Disconnect/Connect Switch for Node
Address 56 Slave
Disconnect/Connect Switch for Node
Address 57 Slave
Disconnect/Connect Switch for Node
Address 58 Slave
Disconnect/Connect Switch for Node
Address 59 Slave
Disconnect/Connect Switch for Node
Address 60 Slave
Disconnect/Connect Switch for Node
Address 61 Slave
Disconnect/Connect Switch for Node
Address 62 Slave
Disconnect/Connect Switch for Node
Address 63 Slave z
CIO n+10 (Unit Status 1)
The device variables for CJ-series Unit that corresponds to all bits of a word starting with CIO n+10 is as follows:
CJ-series I/O memory address
Word address
CIO n+10
Bit
0 to 15 *_Unit1Sta
NJ-series device variables for CJ-series Unit
Variable name CJ-series function name
Unit Status 1 (The functions of bits 0 to 15 of CIO n+10 correspond to those of bits 0 to 15 of this CJ-series Unit device variable.)
A-14 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Appendices
The device variables for CJ-series Units that correspond to bits 0 to 15 of a word starting with CIO n+10 are as follows:
CJ-series I/O memory address
Word address
CIO n+10
Bit
0
3
4
1
2
7
8
5
6
9 to 11
12
13
14, 15
NJ-series device variables for CJ-series Unit
Variable name
*_UnitErr
*_MstrFunErr
---
CJ-series function name
Unit Error
Master Function Error
Reserved for by system
*_SlavFunErr
*_MemErr
*_BusoffErr
*_NdAdrDupErr
Slave Function Error
Unit Memory Error
Bus Off Error
Node Address Duplicated Error
*_NetPwrErr
*_SendTimeoutErr
---
*_RTblErr
*_MsgListErr
---
Network Power Error
Send Timeout Error
Reserved by system
Routing Table Error
Invalid Message Timer List Error
Reserved by system z
CIO n+11 (Unit Status 2)
The device variables for CJ-series Unit that corresponds to all bits of a word starting with CIO n+11 is as follows:
CJ-series I/O memory address
Word address Bit
CIO n+11 0 to 15 *_Unit2Sta
NJ-series device variables for CJ-series Unit
Variable name CJ-series function name
Unit Status 2 (The functions of bits 0 to 15 of CIO n+11 correspond to those of bits 0 to 15 of this CJ-series Unit device variable.)
The device variables for CJ-series Units that correspond to bits 0 to 15 of a word starting with CIO n+11 are as follows:
CJ-series I/O memory address
Word address Bit
CIO n+11 0
1
4
5
2
3
6
7
8
9 to 14
15
NJ-series device variables for CJ-series Unit
Variable name CJ-series function name
*_OnlineSta
*_IOCommSta
Online Status
Remote I/O Communications Status
*_MstrEnblSta
*_SListDsblSta
*_ErrHistorySta
---
---
*_SlavConnTypSta
*_SlavEnblSta
*_FileRWErr
---
Reserved by system
Master Function Enabled Status
Master Function Enabled Status
Reserved by system
Automatic Slave Connection
Slave Function Enabled
File Read/Write Error
Reserved by system
Error History Registered Flag
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) A-15
Appendices z
CIO n+12 (Master Status 1)
The device variable for CJ-series Unit that corresponds to all bits of a word starting with CIO n+12 is as follows:
CJ-series I/O memory address
Word address Bit
CIO n+12 0 to 15 *_Mstr1Sta
NJ-series device variables for CJ-series Unit
Variable name CJ-series function name
Master Status 1 (The functions of bits 0 to
15 of CIO n+12 correspond to those of bits 0 to 15 of this CJ-series Unit device variable.)
The device variables for CJ-series Units that correspond to bits 0 to 15 of a word starting with CIO n+12 are as follows:
CJ-series I/O memory address
Word address
CIO n+12
Bit
0
3
4
1
2
5
6, 7
8
9
10
11
12
13, 14
15
NJ-series device variables for CJ-series Unit
Variable name
*_Mstr1VefyErr
CJ-series function name
Verification Error
*_Mstr1StruErr
*_Mstr1IOErr
Structure Error
Remote I/O Communications Error
Reserved by system
Invalid Scan List Data Error
---
*_Mstr1SListErr
*_Mstr1IORefErr
*_Mstr1FunSetErr
*_Mstr1AlocErr
---
*_Mstr1FixAlocErr
*_Mstr1SListRegErr
*_Mstr1CycleTmSetErr
Master I/O Refresh Error
Reserved by system
Master Function Enable/Disable Failed
Master User-set Allocations User Setting
Failed
Master Fixed Allocation Area Setting
Failed
Scan List Register/Clear Failed
---
*_Mstr1IOCommSta
Communications Cycle Time Setting
Failed
Reserved by system
I/O Data Communications Status z
CIO n+13 (Master Status 2)
The device variable for CJ-series Unit that corresponds to all bits of a word starting with CIO n+13 is as follows:
CJ-series I/O memory address
Word address
CIO n+13
Bit
0 to 15
NJ-series device variables for CJ-series Unit
*_Mstr2Sta
Variable name CJ-series function name
Master Status 2 (The functions of bits 0 to
15 of CIO n+13 correspond to those of bits 0 to 15 of this CJ-series Unit device variable.)
The device variables for CJ-series Units that correspond to bits 0 to 15 of a word starting with CIO n+13 are as follows:
CJ-series I/O memory address
Word address Bit
CIO n+13 0 to 7
8 to 15
NJ-series device variables for CJ-series Unit
Variable name CJ-series function name
---
*_MstrIOAlocSta
Reserved by system
Master I/O Allocation Status
A-16 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Appendices z
CIO n+14 (Slave Status 1)
The device variable for CJ-series Unit that corresponds to all bits of a word starting with CIO n+14 is as follows:
CJ-series I/O memory address
Word address Bit
CIO n+14 0 to 15 *_Slav1Sta
NJ-series device variables for CJ-series Unit
Variable name CJ-series function name
Slave Status 1 (The functions of bits 0 to
15 of CIO n+14 correspond to those of bits 0 to 15 of this CJ-series Unit device variable.)
The device variable for CJ-series Units that correspond to bits 0 to 15 of a word starting with CIO n+14 are as follows:
CJ-series I/O memory address
Word address
CIO n+14
Bit
0, 1
2
3
10
11
12
13
14
4
5
6, 7
8
9
15
NJ-series device variables for CJ-series Unit
Variable name CJ-series function name
Reserved by system
*_Slav1IO1Err
*_Slav1IO2Err
Remote I/O Communications Error with slave communications enabled, for OUT
1/IN 1
Remote I/O Communications Error with slave communications enabled, for OUT
2/IN 2
*_Slav1FunDatErr
*_Slav1IORefErr
*_Slav1FunSetErr
*_Slav1AlocErr
*_Slav1FixAlocErr
*_Slav1COSSendErr
*_Slav1Conn2EstbSta
*_Slav1Conn1EstbSta
*_Slav1IO2CommSta
*_Slav1IO1CommSta
Invalid Setup Data
Slave I/O Refresh Error
Reserved by system
Slave Function Enable/Disable Failed
Slave User-set Allocations Area Setting
Failed
Slave Fixed Allocation Area Setting Failed
COS Send Failed
Connection 2 Established
Connection 1 Established
Remote I/O Communications for OUT
2/IN 2
Remote I/O Communications for OUT
1/IN 1 z
CIO n+15 (Slave Status 2)
The device variable for CJ-series Unit that corresponds to all bits of a word starting with CIO n+15 is as follows:
CJ-series I/O memory address
Word address
CIO n+15
Bit
0 to 15
NJ-series device variables for CJ-series Unit
*_Slav2Sta
Variable name CJ-series function name
Slave Status 2 (The functions of bits 0 to
15 of CIO n+15 correspond to those of bits 0 to 15 of this CJ-series Unit device variable.)
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) A-17
Appendices
The device variable for CJ-series Units that correspond to bits 0 to 15 of a word starting with CIO n+15 are as follows:
CJ-series I/O memory address
Word address
CIO n+15
Bit
0 to 7
8 to 15 *_SlavIOAlocSta
NJ-series device variables for CJ-series Unit
Variable name
*_MstrNdAdrSta
CJ-series function name
Node Address of The Remote Master for
Slave Communications
Slave I/O Allocation Status z
CIO n+16 to n+19 (Registered Slave Table)
The device variable for CJ-series Unit that corresponds to all bits of 4 words from CIO n+16 to n+19 is as follows:
CJ-series I/O memory address
Word address Bit
CIO n+16 to n+19
0 to 15 for each word *_RegSlavTblSta
NJ-series device variables for CJ-series Unit
Variable name CJ-series function name
Registered Slave Table
Bits 0 to 15 in each word correspond to the bits of this CJ-series Unit device variable as follows:
• Bits 0 to 15 of CIO n+16 correspond to bits 0 to 15 of this CJ-series Unit device variable.
• Bits 0 to 15 of CIO n+17 correspond to bits 16 to 31 of this CJ-series Unit device variable.
• Bits 0 to 15 of CIO n+18 correspond to bits 32 to 47 of this CJ-series Unit device variable.
• Bits 0 to 15 of CIO n+19 correspond to bits 48 to 63 of this CJ-series Unit device variable.
A-18 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Appendices
The device variable for CJ-series Units that correspond to bits 0 to 15 of 4 words from CIO n+16 to n+19 are as follows:
CJ-series I/O memory address
Word address
CIO n+16
Bit
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
NJ-series device variables for CJ-series Unit
Variable name
*_RegSlavTblNdSta[0]
*_RegSlavTblNdSta[1]
*_RegSlavTblNdSta[2]
*_RegSlavTblNdSta[3]
*_RegSlavTblNdSta[4]
*_RegSlavTblNdSta[5]
*_RegSlavTblNdSta[6]
*_RegSlavTblNdSta[7]
*_RegSlavTblNdSta[8]
*_RegSlavTblNdSta[9]
*_RegSlavTblNdSta[10]
*_RegSlavTblNdSta[11]
*_RegSlavTblNdSta[12]
*_RegSlavTblNdSta[13]
*_RegSlavTblNdSta[14]
*_RegSlavTblNdSta[15]
CJ-series function name
Registered Slave Table Corresponding to
Node Address 0 Slave
Registered Slave Table Corresponding to
Node Address 1 Slave
Registered Slave Table Corresponding to
Node Address 2 Slave
Registered Slave Table Corresponding to
Node Address 3 Slave
Registered Slave Table Corresponding to
Node Address 4 Slave
Registered Slave Table Corresponding to
Node Address 5 Slave
Registered Slave Table Corresponding to
Node Address 6 Slave
Registered Slave Table Corresponding to
Node Address 7 Slave
Registered Slave Table Corresponding to
Node Address 8 Slave
Registered Slave Table Corresponding to
Node Address 9 Slave
Registered Slave Table Corresponding to
Node Address 10 Slave
Registered Slave Table Corresponding to
Node Address 11 Slave
Registered Slave Table Corresponding to
Node Address 12 Slave
Registered Slave Table Corresponding to
Node Address 13 Slave
Registered Slave Table Corresponding to
Node Address 14 Slave
Registered Slave Table Corresponding to
Node Address 15 Slave
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) A-19
Appendices
CJ-series I/O memory address
Word address
CIO n+17
Bit
0
1
2
5
6
3
4
13
14
11
12
15
9
10
7
8
NJ-series device variables for CJ-series Unit
Variable name
*_RegSlavTblNdSta[16]
*_RegSlavTblNdSta[17]
*_RegSlavTblNdSta[18]
*_RegSlavTblNdSta[19]
*_RegSlavTblNdSta[20]
*_RegSlavTblNdSta[21]
*_RegSlavTblNdSta[22]
*_RegSlavTblNdSta[23]
*_RegSlavTblNdSta[24]
*_RegSlavTblNdSta[25]
*_RegSlavTblNdSta[26]
*_RegSlavTblNdSta[27]
*_RegSlavTblNdSta[28]
*_RegSlavTblNdSta[29]
*_RegSlavTblNdSta[30]
*_RegSlavTblNdSta[31]
CJ-series function name
Registered Slave Table Corresponding to
Node Address 16 Slave
Registered Slave Table Corresponding to
Node Address 17 Slave
Registered Slave Table Corresponding to
Node Address 18 Slave
Registered Slave Table Corresponding to
Node Address 19 Slave
Registered Slave Table Corresponding to
Node Address 20 Slave
Registered Slave Table Corresponding to
Node Address 21 Slave
Registered Slave Table Corresponding to
Node Address 22 Slave
Registered Slave Table Corresponding to
Node Address 23 Slave
Registered Slave Table Corresponding to
Node Address 24 Slave
Registered Slave Table Corresponding to
Node Address 25 Slave
Registered Slave Table Corresponding to
Node Address 26 Slave
Registered Slave Table Corresponding to
Node Address 27 Slave
Registered Slave Table Corresponding to
Node Address 28 Slave
Registered Slave Table Corresponding to
Node Address 29 Slave
Registered Slave Table Corresponding to
Node Address 30 Slave
Registered Slave Table Corresponding to
Node Address 31 Slave
A-20 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Appendices
The device variable for CJ-series Units that correspond to bits 0 to 15 of 4 words from CIO n+16 to n+19 are as follows:
CJ-series I/O memory address
Word address
CIO n+18
Bit
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
NJ-series device variables for CJ-series Unit
Variable name
*_RegSlavTblNdSta[32]
*_RegSlavTblNdSta[33]
*_RegSlavTblNdSta[34]
*_RegSlavTblNdSta[35]
*_RegSlavTblNdSta[36]
*_RegSlavTblNdSta[37]
*_RegSlavTblNdSta[38]
*_RegSlavTblNdSta[39]
*_RegSlavTblNdSta[40]
*_RegSlavTblNdSta[41]
*_RegSlavTblNdSta[42]
*_RegSlavTblNdSta[43]
*_RegSlavTblNdSta[44]
*_RegSlavTblNdSta[45]
*_RegSlavTblNdSta[46]
*_RegSlavTblNdSta[47]
CJ-series function name
Registered Slave Table Corresponding to
Node Address 32 Slave
Registered Slave Table Corresponding to
Node Address 33 Slave
Registered Slave Table Corresponding to
Node Address 34 Slave
Registered Slave Table Corresponding to
Node Address 35 Slave
Registered Slave Table Corresponding to
Node Address 36 Slave
Registered Slave Table Corresponding to
Node Address 37 Slave
Registered Slave Table Corresponding to
Node Address 38 Slave
Registered Slave Table Corresponding to
Node Address 39 Slave
Registered Slave Table Corresponding to
Node Address 40 Slave
Registered Slave Table Corresponding to
Node Address 41 Slave
Registered Slave Table Corresponding to
Node Address 42 Slave
Registered Slave Table Corresponding to
Node Address 43 Slave
Registered Slave Table Corresponding to
Node Address 44 Slave
Registered Slave Table Corresponding to
Node Address 45 Slave
Registered Slave Table Corresponding to
Node Address 46 Slave
Registered Slave Table Corresponding to
Node Address 47 Slave
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) A-21
Appendices
CJ-series I/O memory address
Word address
CIO n+19
Bit
0
1
2
5
6
3
4
13
14
11
12
15
9
10
7
8
NJ-series device variables for CJ-series Unit
Variable name
*_RegSlavTblNdSta[48]
*_RegSlavTblNdSta[49]
*_RegSlavTblNdSta[50]
*_RegSlavTblNdSta[51]
*_RegSlavTblNdSta[52]
*_RegSlavTblNdSta[53]
*_RegSlavTblNdSta[54]
*_RegSlavTblNdSta[55]
*_RegSlavTblNdSta[56]
*_RegSlavTblNdSta[57]
*_RegSlavTblNdSta[58]
*_RegSlavTblNdSta[59]
*_RegSlavTblNdSta[60]
*_RegSlavTblNdSta[61]
*_RegSlavTblNdSta[62]
*_RegSlavTblNdSta[63]
CJ-series function name
Registered Slave Table Corresponding to
Node Address 48 Slave
Registered Slave Table Corresponding to
Node Address 49 Slave
Registered Slave Table Corresponding to
Node Address 50 Slave
Registered Slave Table Corresponding to
Node Address 51 Slave
Registered Slave Table Corresponding to
Node Address 52 Slave
Registered Slave Table Corresponding to
Node Address 53 Slave
Registered Slave Table Corresponding to
Node Address 54 Slave
Registered Slave Table Corresponding to
Node Address 55 Slave
Registered Slave Table Corresponding to
Node Address 56 Slave
Registered Slave Table Corresponding to
Node Address 57 Slave
Registered Slave Table Corresponding to
Node Address 58 Slave
Registered Slave Table Corresponding to
Node Address 59 Slave
Registered Slave Table Corresponding to
Node Address 60 Slave
Registered Slave Table Corresponding to
Node Address 61 Slave
Registered Slave Table Corresponding to
Node Address 62 Slave
Registered Slave Table Corresponding to
Node Address 63 Slave
A-22 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Appendices z
CIO n+20 to n+23 (Normal Slave Table)
The device variable for CJ-series Unit that corresponds to all bits of 4 words from CIO n+20 to n+23 is as follows:
CJ-series I/O memory address
Word address Bit
CIO n+20 to n+23
NJ-series device variables for CJ-series Unit
Variable name
0 to 15 for each word *_NormSlavTblSta
CJ-series function name
Normal Slave Table
Bits 0 to 15 in each word correspond to the bits of this CJ-series Unit device variable as follows:
• Bits 0 to 15 of CIO n+20 correspond to bits 0 to 15 of this CJ-series Unit device variable.
• Bits 0 to 15 of CIO n+21 correspond to bits 16 to 31 of this CJ-series Unit device variable.
• Bits 0 to 15 of CIO n+22 correspond to bits 32 to 47 of this CJ-series Unit device variable.
• Bits 0 to 15 of CIO n+23 correspond to bits 48 to 63 of this CJ-series Unit device variable.
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) A-23
Appendices
The device variable for CJ-series Units that correspond to bits 0 to 15 of 4 words from CIO n+20 to n+23 are as follows:
CJ-series I/O memory address
Word address
CIO n+20
Bit
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
NJ-series device variables for CJ-series Unit
Variable name
*_NormSlavTblNdSta[0]
*_NormSlavTblNdSta[1]
*_NormSlavTblNdSta[2]
*_NormSlavTblNdSta[3]
*_NormSlavTblNdSta[4]
*_NormSlavTblNdSta[5]
*_NormSlavTblNdSta[6]
*_NormSlavTblNdSta[7]
*_NormSlavTblNdSta[8]
*_NormSlavTblNdSta[9]
*_NormSlavTblNdSta[10]
*_NormSlavTblNdSta[11]
*_NormSlavTblNdSta[12]
*_NormSlavTblNdSta[13]
*_NormSlavTblNdSta[14]
*_NormSlavTblNdSta[15]
CJ-series function name
Normal Slave Table Corresponding to
Node Address 0 Slave
Normal Slave Table Corresponding to
Node Address 1 Slave
Normal Slave Table Corresponding to
Node Address 2 Slave
Normal Slave Table Corresponding to
Node Address 3 Slave
Normal Slave Table Corresponding to
Node Address 4 Slave
Normal Slave Table Corresponding to
Node Address 5 Slave
Normal Slave Table Corresponding to
Node Address 6 Slave
Normal Slave Table Corresponding to
Node Address 7 Slave
Normal Slave Table Corresponding to
Node Address 8 Slave
Normal Slave Table Corresponding to
Node Address 9 Slave
Normal Slave Table Corresponding to
Node Address 10 Slave
Normal Slave Table Corresponding to
Node Address 11 Slave
Normal Slave Table Corresponding to
Node Address 12 Slave
Normal Slave Table Corresponding to
Node Address 13 Slave
Normal Slave Table Corresponding to
Node Address 14 Slave
Normal Slave Table Corresponding to
Node Address 15 Slave
A-24 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Appendices
CJ-series I/O memory address
Word address
CIO n+21
Bit
0
1
2
5
6
3
4
13
14
11
12
15
9
10
7
8
NJ-series device variables for CJ-series Unit
Variable name
*_NormSlavTblNdSta[16]
*_NormSlavTblNdSta[17]
*_NormSlavTblNdSta[18]
*_NormSlavTblNdSta[19]
*_NormSlavTblNdSta[20]
*_NormSlavTblNdSta[21]
*_NormSlavTblNdSta[22]
*_NormSlavTblNdSta[23]
*_NormSlavTblNdSta[24]
*_NormSlavTblNdSta[25]
*_NormSlavTblNdSta[26]
*_NormSlavTblNdSta[27]
*_NormSlavTblNdSta[28]
*_NormSlavTblNdSta[29]
*_NormSlavTblNdSta[30]
*_NormSlavTblNdSta[31]
CJ-series function name
Normal Slave Table Corresponding to
Node Address 16 Slave
Normal Slave Table Corresponding to
Node Address 17 Slave
Normal Slave Table Corresponding to
Node Address 18 Slave
Normal Slave Table Corresponding to
Node Address 19 Slave
Normal Slave Table Corresponding to
Node Address 20 Slave
Normal Slave Table Corresponding to
Node Address 21 Slave
Normal Slave Table Corresponding to
Node Address 22 Slave
Normal Slave Table Corresponding to
Node Address 23 Slave
Normal Slave Table Corresponding to
Node Address 24 Slave
Normal Slave Table Corresponding to
Node Address 25 Slave
Normal Slave Table Corresponding to
Node Address 26 Slave
Normal Slave Table Corresponding to
Node Address 27 Slave
Normal Slave Table Corresponding to
Node Address 28 Slave
Normal Slave Table Corresponding to
Node Address 29 Slave
Normal Slave Table Corresponding to
Node Address 30 Slave
Normal Slave Table Corresponding to
Node Address 31 Slave
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) A-25
Appendices
CJ-series I/O memory address
Word address
CIO n+22
Bit
0
1
2
5
6
3
4
13
14
11
12
15
9
10
7
8
NJ-series device variables for CJ-series Unit
Variable name
*_NormSlavTblNdSta[32]
*_NormSlavTblNdSta[33]
*_NormSlavTblNdSta[34]
*_NormSlavTblNdSta[35]
*_NormSlavTblNdSta[36]
*_NormSlavTblNdSta[37]
*_NormSlavTblNdSta[38]
*_NormSlavTblNdSta[39]
*_NormSlavTblNdSta[40]
*_NormSlavTblNdSta[41]
*_NormSlavTblNdSta[42]
*_NormSlavTblNdSta[43]
*_NormSlavTblNdSta[44]
*_NormSlavTblNdSta[45]
*_NormSlavTblNdSta[46]
*_NormSlavTblNdSta[47]
CJ-series function name
Normal Slave Table Corresponding to
Node Address 32 Slave
Normal Slave Table Corresponding to
Node Address 33 Slave
Normal Slave Table Corresponding to
Node Address 34 Slave
Normal Slave Table Corresponding to
Node Address 35 Slave
Normal Slave Table Corresponding to
Node Address 36 Slave
Normal Slave Table Corresponding to
Node Address 37 Slave
Normal Slave Table Corresponding to
Node Address 38 Slave
Normal Slave Table Corresponding to
Node Address 39 Slave
Normal Slave Table Corresponding to
Node Address 40 Slave
Normal Slave Table Corresponding to
Node Address 41 Slave
Normal Slave Table Corresponding to
Node Address 42 Slave
Normal Slave Table Corresponding to
Node Address 43 Slave
Normal Slave Table Corresponding to
Node Address 44 Slave
Normal Slave Table Corresponding to
Node Address 45 Slave
Normal Slave Table Corresponding to
Node Address 46 Slave
Normal Slave Table Corresponding to
Node Address 47 Slave
A-26 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Appendices
The device variable for CJ-series Units that correspond to bits 0 to 15 of 4 words from CIO n+20 to n+23 are as follows:
CJ-series I/O memory address
Word address
CIO n+23
Bit
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
NJ-series device variables for CJ-series Unit
Variable name
*_NormSlavTblNdSta[48]
*_NormSlavTblNdSta[49]
*_NormSlavTblNdSta[50]
*_NormSlavTblNdSta[51]
*_NormSlavTblNdSta[52]
*_NormSlavTblNdSta[53]
*_NormSlavTblNdSta[54]
*_NormSlavTblNdSta[55]
*_NormSlavTblNdSta[56]
*_NormSlavTblNdSta[57]
*_NormSlavTblNdSta[58]
*_NormSlavTblNdSta[59]
*_NormSlavTblNdSta[60]
*_NormSlavTblNdSta[61]
*_NormSlavTblNdSta[62]
*_NormSlavTblNdSta[63]
CJ-series function name
Normal Slave Table Corresponding to
Node Address 48 Slave
Normal Slave Table Corresponding to
Node Address 49 Slave
Normal Slave Table Corresponding to
Node Address 50 Slave
Normal Slave Table Corresponding to
Node Address 51 Slave
Normal Slave Table Corresponding to
Node Address 52 Slave
Normal Slave Table Corresponding to
Node Address 53 Slave
Normal Slave Table Corresponding to
Node Address 54 Slave
Normal Slave Table Corresponding to
Node Address 55 Slave
Normal Slave Table Corresponding to
Node Address 56 Slave
Normal Slave Table Corresponding to
Node Address 57 Slave
Normal Slave Table Corresponding to
Node Address 58 Slave
Normal Slave Table Corresponding to
Node Address 59 Slave
Normal Slave Table Corresponding to
Node Address 60 Slave
Normal Slave Table Corresponding to
Node Address 61 Slave
Normal Slave Table Corresponding to
Node Address 62 Slave
Normal Slave Table Corresponding to
Node Address 63 Slave z
CIO n+24 (C200H Master Replacement Master Status 1)
The device variable for CJ-series Unit that corresponds to all bits of a word starting with CIO n+24 is as follows:
CJ-series I/O memory address
Word address
CIO n+24
Bit
0 to 15
NJ-series device variables for CJ-series Unit
*_CMstrSta
Variable name CJ-series function name
C200H Master Replacement Master Status 1 (The functions of bits 0 to 15 of CIO n+24 correspond to those of bits 0 to 15 of this CJ-series Unit device variable.)
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) A-27
Appendices
The device variables for CJ-series Units that correspond to bits 0 to 15 of a word starting with CIO n+24 are as follows:
CJ-series I/O memory address
Word address
CIO n+24
Bit
0
1
6
7
8
4
5
2
3
9 to 11
12
13
14
15
NJ-series device variables for CJ-series Unit
Variable name
*_CMstrMemErr
*_CMstrNdDupErr
CJ-series function name
Unit Memory Error
Node Address Duplicated/ Bus Off
Error
*_CMstrCfgErr
*_CMstrStruErr
*_CMstrSendErr
Reserved by system
Configuration Error
Structure Error
Send Error
*_CMstrIOErr
*_CMstrVefyErr
*_CMstrIOStopSta
*_CMstrMsgEnblSta
*_CMstrSListDsblSta
*_CMstrErr
*_CMstrIOCommSta
Communication Error
Verification Error
I/O Data Communications Not Running Status
Reserved by system
Message Communications Permitted
Invalid Scan List Data Flag
Error is occurring or Remote I/O
Communications is stopped due to error (Master Error)
Remote I/O Communications Flag
CPU Bus Unit Words Allocated in DM Area
z
D m (Communications Cycle Time Setup Table)
CJ-series I/O memory address
Word address
D m
Bit
0 to 15
NJ-series device variables for CJ-series Unit
Variable name
*_CommCycleTmCfg
CJ-series function name
Communications Cycle Time Setting z
D m+1 to m+7 (Master User-set Allocations Setup Table)
CJ-series I/O memory address
Word address
D m+1
Bit
0 to 7
D m+2
D m+3
D m+4
D m+5
D m+6
0 to 15
0 to 7
0 to 15
0 to 7
0 to 15
D m+7 0 to 15
NJ-series device variables for CJ-series Unit
Variable name
*_MstrAlocTblCfg[0]
CJ-series function name
OUT Block 1 Area
*_MstrAlocTblCfg[1]
*_MstrAlocTblCfg[2]
*_MstrAlocTblCfg[3]
*_MstrAlocTblCfg[4]
*_MstrAlocTblCfg[5]
*_MstrAlocTblCfgSta
First word in OUT Block 1
IN Block 1 Area
First word in IN Block 1
Allocation size setup table area
First word in the Allocation Size Setup
Table 1
Setting Results of Master User-set Allocations Setup
A-28 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Appendices z
D m+8 to m+14 (Slave User-set Allocations Setup Table)
CJ-series I/O memory address
Word address
D m+8
Bit
0 to 7
D m+9
D m+10
D m+11
D m+12
D m+13
D m+14
0 to 15
0 to 7
0 to 15
0 to 7
0 to 15
0 to 15
NJ-series device variables for CJ-series Unit
Variable name
*_SlavAlocTblCfg[0]
CJ-series function name
Slave OUT 1 Area
*_SlavAlocTblCfg[1]
*_SlavAlocTblCfg[2]
*_SlavAlocTblCfg[3]
*_SlavAlocTblCfg[4]
*_SlavAlocTblCfg[5]
*_SlavAlocTblCfgSta
First word in Slave OUT 1 Area
OUT 1 Area Size
Slave IN 1 Area
First word in Slave IN 1 Area
IN 1 Area Size
Setting Results of Slave User-set Allocations Setup z
D m+15 to m+18 (Communication Cycle Time Reference Table)
CJ-series I/O memory address
Word address Bit
D m+15
D m+16
D m+17
0 to 15
0 to 15
0 to 15
D m+18 0 to 15
NJ-series device variables for CJ-series Unit
Variable name CJ-series function name
*_CycleTmRefTblSta[0]
*_CycleTmRefTblSta[1]
*_CycleTmRefTblSta[2]
Communications cycle time setting value
Communications cycle time present value
*_CycleTmRefTblSta[3]
Communications cycle time maximum value
Communications cycle time minimum value z
D m+19 to m+30 (Master User-set Allocations Reference Table)
CJ-series I/O memory address
Word address Bit
D m+19
D m+20
0 to 7
0 to 15
D m+21
D m+22
D m+23
D m+24
0 to 15
0 to 7
0 to 15
0 to 15
D m+25
D m+26
D m+27
D m+28
D m+29
D m+30
0 to 7
0 to 15
0 to 15
0 to 7
0 to 15
0 to 15
NJ-series device variables for CJ-series Unit
Variable name CJ-series function name
*_MstrAlocRefTblSta[0]
*_MstrAlocRefTblSta[1]
OUT block 1 area
First word in OUT block 1
*_MstrAlocRefTblSta[2]
*_MstrAlocRefTblSta[3]
*_MstrAlocRefTblSta[4]
*_MstrAlocRefTblSta[5]
No. of bytes in OUT block 1
IN block 1 area
First word in IN block 1
No. of bytes in IN block 1
*_MstrAlocRefTblSta[6]
*_MstrAlocRefTblSta[7]
*_MstrAlocRefTblSta[8]
*_MstrAlocRefTblSta[9]
*_MstrAlocRefTblSta[10]
*_MstrAlocRefTblSta[11]
OUT block 2 area
First word in OUT block 2
No. of bytes in OUT block 2
IN block 2 area
First word in IN block 2
No. of bytes in IN block 2 z
D m+31 to m+42 (Slave User-set Allocations Reference Table)
CJ-series I/O memory address
Word address
D m+31
Bit
0 to 7
D m+32
D m+33
D m+34
D m+35
0 to 15
0 to 15
0 to 7
0 to 15
NJ-series device variables for CJ-series Unit
Variable name
*_SlavAlocRefTblSta[0]
CJ-series function name
Slave OUT 1 area
*_SlavAlocRefTblSta[1]
*_SlavAlocRefTblSta[2]
*_SlavAlocRefTblSta[3]
*_SlavAlocRefTblSta[4]
First word in Slave OUT 1 area
Slave OUT 1 area size
Slave IN 1 area
First word in Slave IN 1 area
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) A-29
Appendices
CJ-series I/O memory address
Word address
D m+36
Bit
0 to 15
D m+37
D m+38
D m+39
D m+40
D m+41
D m+42
0 to 7
0 to 15
0 to 15
0 to 7
0 to 15
0 to 15
NJ-series device variables for CJ-series Unit
Variable name
*_SlavAlocRefTblSta[5]
CJ-series function name
Slave IN 1 area size
*_SlavAlocRefTblSta[6]
*_SlavAlocRefTblSta[7]
*_SlavAlocRefTblSta[8]
*_SlavAlocRefTblSta[9]
*_SlavAlocRefTblSta[10]
*_SlavAlocRefTblSta[11]
Slave OUT 2 area
First word in Slave OUT 2 area
Slave OUT 2 area size
Slave IN 2 area
First word in Slave IN 2 area
Slave IN 2 area size z
D m+43 to m+74 (Slave Detailed Status)
m+43
D Bit 15 m+44
*_Nd1Sta (Node address 1)
*_Nd3Sta (Node address 3)
*_Nd63Sta (Node address 63)
Bit 08 Bit 07
:
*_Nd0Sta (Node address 0)
*_Nd2Sta (Node address 2)
*_Nd62Sta (Node address 62)
Bit 00 m+74
7 6 5 4 3 2 1 0
*_Nd62Err (Slave Error)
*_Nd62VefyErr (Slave Verification Error)
*_Nd62CfgErr (Slave Configuration Error)
*_Nd62IOErr (Slave Remote I/O Communications Error)
Reserved by system
*_Nd62COSSendErr (Master COS Send Error)
*_Nd62SListRegSta (Scan List Registration Flag)
*_Nd62IOCommSta (Remote I/O Communications Flag)
15 14 13 12 11 10 9 8
*_Nd63Err (Slave Error)
*_Nd63VefyErr (Slave Verification Error)
*_Nd63CfgErr (Slave Configuration Error)
*_Nd63IOErr (Slave Remote I/O Communications Error)
Reserved by system
*_Nd63COSSendErr (Master COS Send Error)
*_Nd63SListRegSta (Scan List Registration Flag)
*_Nd63IOCommSta1 (Remote I/O Communications Flag)
The device variables for CJ-series Units that correspond to bits 0 to 7 or 8 to 15 of each word are as follows:
The functions of bits 0 to 7 and 8 to 15 of each word correspond to the functions of bits 0 to 7 on the device variables for CJ-series Unit:
CJ-series I/O memory address
Word address
D m+43 0 to 7
Bit
D m+44
D m+45
8 to 15
0 to 7
8 to 15
0 to 7
D m+46
D m+47
8 to 15
0 to 7
8 to 15
0 to 7
8 to 15
NJ-series device variables for CJ-series Unit
*_Nd0Sta
Variable name CJ-series function name
Detailed Slave Status Table for Node Address 0
*_Nd1Sta
*_Nd2Sta
*_Nd3Sta
*_Nd4Sta
Detailed Slave Status Table for Node Address 1
Detailed Slave Status Table for Node Address 2
Detailed Slave Status Table for Node Address 3
Detailed Slave Status Table for Node Address 4
*_Nd5Sta
*_Nd6Sta
*_Nd7Sta
*_Nd8Sta
*_Nd9Sta
Detailed Slave Status Table for Node Address 5
Detailed Slave Status Table for Node Address 6
Detailed Slave Status Table for Node Address 7
Detailed Slave Status Table for Node Address 8
Detailed Slave Status Table for Node Address 9
A-30 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Appendices
CJ-series I/O memory address
Word address
D m+48 0 to 7
Bit
D m+49
D m+50
D m+51
D m+52
D m+53
D m+54
D m+55
D m+56
D m+57
D m+58
D m+59
D m+60
8 to 15
0 to 7
8 to 15
0 to 7
8 to 15
0 to 7
8 to 15
0 to 7
8 to 15
0 to 7
8 to 15
0 to 7
8 to 15
0 to 7
8 to 15
0 to 7
8 to 15
0 to 7
8 to 15
0 to 7
8 to 15
0 to 7
8 to 15
0 to 7
8 to 15
*_Nd11Sta
*_Nd12Sta
*_Nd13Sta
*_Nd14Sta
*_Nd15Sta
*_Nd16Sta
*_Nd17Sta
*_Nd18Sta
*_Nd19Sta
*_Nd20Sta
*_Nd21Sta
*_Nd22Sta
*_Nd23Sta
*_Nd24Sta
*_Nd25Sta
*_Nd26Sta
*_Nd27Sta
*_Nd28Sta
*_Nd29Sta
*_Nd30Sta
*_Nd31Sta
*_Nd32Sta
*_Nd33Sta
*_Nd34Sta
*_Nd35Sta
NJ-series device variables for CJ-series Unit
Variable name
*_Nd10Sta
CJ-series function name
Detailed Slave Status Table for Node Address
10
Detailed Slave Status Table for Node Address
11
Detailed Slave Status Table for Node Address
12
Detailed Slave Status Table for Node Address
13
Detailed Slave Status Table for Node Address
14
Detailed Slave Status Table for Node Address
15
Detailed Slave Status Table for Node Address
16
Detailed Slave Status Table for Node Address
17
Detailed Slave Status Table for Node Address
18
Detailed Slave Status Table for Node Address
19
Detailed Slave Status Table for Node Address
20
Detailed Slave Status Table for Node Address
21
Detailed Slave Status Table for Node Address
22
Detailed Slave Status Table for Node Address
23
Detailed Slave Status Table for Node Address
24
Detailed Slave Status Table for Node Address
25
Detailed Slave Status Table for Node Address
26
Detailed Slave Status Table for Node Address
27
Detailed Slave Status Table for Node Address
28
Detailed Slave Status Table for Node Address
29
Detailed Slave Status Table for Node Address
30
Detailed Slave Status Table for Node Address
31
Detailed Slave Status Table for Node Address
32
Detailed Slave Status Table for Node Address
33
Detailed Slave Status Table for Node Address
34
Detailed Slave Status Table for Node Address
35
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) A-31
Appendices
CJ-series I/O memory address
Word address
D m+61 0 to 7
Bit
D m+62
D m+63
D m+64
8 to 15
0 to 7
8 to 15
0 to 7
8 to 15
0 to 7
8 to 15
*_Nd37Sta
*_Nd38Sta
*_Nd39Sta
*_Nd40Sta
*_Nd41Sta
*_Nd42Sta
*_Nd43Sta
NJ-series device variables for CJ-series Unit
Variable name
*_Nd36Sta
CJ-series function name
Detailed Slave Status Table for Node Address
36
Detailed Slave Status Table for Node Address
37
Detailed Slave Status Table for Node Address
38
Detailed Slave Status Table for Node Address
39
Detailed Slave Status Table for Node Address
40
Detailed Slave Status Table for Node Address
41
Detailed Slave Status Table for Node Address
42
Detailed Slave Status Table for Node Address
43
The device variables for CJ-series Units that correspond to bits 0 to 7 and 8 to 15 of each word are as follows:
CJ-series I/O memory address
Word address Bit
D m+65 0 to 7
D m+66
D m+67
D m+68
D m+69
D m+70
D m+71
8 to 15
0 to 7
8 to 15
0 to 7
8 to 15
0 to 7
8 to 15
0 to 7
8 to 15
0 to 7
8 to 15
0 to 7
8 to 15
NJ-series device variables for CJ-series Unit
Variable name CJ-series function name
*_Nd44Sta
*_Nd45Sta
Detailed Slave Status Table for Node Address
44
Detailed Slave Status Table for Node Address
45
*_Nd46Sta
*_Nd47Sta
*_Nd48Sta
*_Nd49Sta
Detailed Slave Status Table for Node Address
46
Detailed Slave Status Table for Node Address
47
Detailed Slave Status Table for Node Address
48
Detailed Slave Status Table for Node Address
49
*_Nd50Sta
*_Nd51Sta
*_Nd52Sta
*_Nd53Sta
*_Nd54Sta
*_Nd55Sta
*_Nd56Sta
*_Nd57Sta
Detailed Slave Status Table for Node Address
50
Detailed Slave Status Table for Node Address
51
Detailed Slave Status Table for Node Address
52
Detailed Slave Status Table for Node Address
53
Detailed Slave Status Table for Node Address
54
Detailed Slave Status Table for Node Address
55
Detailed Slave Status Table for Node Address
56
Detailed Slave Status Table for Node Address
57
A-32 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Appendices
CJ-series I/O memory address
Word address
D m+72 0 to 7
Bit
D m+73
D m+74
8 to 15
0 to 7
8 to 15
0 to 7
8 to 15
*_Nd59Sta
*_Nd60Sta
*_Nd61Sta
*_Nd62Sta
*_Nd63Sta
NJ-series device variables for CJ-series Unit
Variable name
*_Nd58Sta
CJ-series function name
Detailed Slave Status Table for Node Address
58
Detailed Slave Status Table for Node Address
59
Detailed Slave Status Table for Node Address
60
Detailed Slave Status Table for Node Address
61
Detailed Slave Status Table for Node Address
62
Detailed Slave Status Table for Node Address
63
The device variables for CJ-series Units that correspond to bits 0 to 15 of each word are as follows:
CJ-series I/O memory address
Word address Bit
D m+43, m+44 to m+74
0 of each word
1 of each word
2 of each word
3 of each word
4 of each word
5 of each word
6 of each word
7 of each word
NJ-series device variables for CJ-series Unit
Variable name CJ-series function name
Slave Error for node address 0, 2 to 62 *_Nd0Err,
*_Nd2Err,
to
*_Nd62Err
*_Nd0VefyErr,
*_Nd2VefyErr,
to
*_Nd62VefyErr
Slave Verification Error for node address 0, 2 to
62
*_Nd0CfgErr,
*_Nd2CfgErr,
to
*_Nd62CfgErr
*_Nd0IOErr,
*_Nd2IOErr,
to
*_Nd62IOErr
Slave Configuration Error for node address 0, 2 to 62
Slave Remote I/O Communications Error for node address 0, 2 to 62
Reserved by system
Master COS Send Error for node address 0, 2 to
62
*_Nd0COSSendErr,
*_Nd2COSSendErr,
to
*_Nd62COSSendErr
*_Nd0SListRegSta,
*_Nd2SListRegSta,
to
*_Nd62SListRegSta
*_Nd0IOCommSta,
*_Nd2IOCommSta,
to
*_Nd62IOCommSta
Scan List Registration Flag for node address
0, 2 to 62
Remote I/O Communications Flag at node address 0, 2 to 62
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) A-33
Appendices
The device variables for CJ-series Units that correspond to bits 0 to 15 of each word are as follows:
CJ-series I/O memory address
Word address
D m+43, m+44 to m+74
Bit
8 of each word
9 of each word
10 of each word
11 of each word
12 of each word
13 of each word
14 of each word
15 of each word
Variable name
*_Nd1Err,
*_Nd3Err,
to
*_Nd63Err
*_Nd1VefyErr,
*_Nd3VefyErr
to
*_Nd63VefyErr
*_Nd1CfgErr,
*_Nd3CfgErr,
to
*_Nd63CfgErr
*_Nd1IOErr,
*_Nd3IOErr,
to
*_Nd63IOErr
NJ-series device variables for CJ-series Unit
CJ-series function name
Slave Error for node address 1, 3 to 63
Slave Verification Error for node address
1, 3 to 63
Slave Configuration Error for node address 1, 3 to 63
Slave Remote I/O Communications Error for node address 1, 3 to 63
Reserved by system
Master COS Send Error for node address
1, 3 to 63
*_Nd1COSSendErr,
*_Nd3COSSendErr,
to
*_Nd63COSSendErr
*_Nd1SListRegSta,
*_Nd3SListRegSta,
to
*_Nd63SListRegSta
Scan List Registration Flag for node address 1, 3 to 63
*_Nd1IOCommSta,
*_Nd3IOCommSta,
to
*_Nd63IOCommSta
Remote I/O Communications Flag at node address 1, 3 to 63
A-34 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Appendices
A-2 DeviceNet Connections
DeviceNet has several different protocols for remote I/O communications between Master and Slave devices. Connections are units used to manage those protocols.
There are four kinds of DeviceNet remote I/O communications protocols (connections): Poll, bit–strobe,
COS (change of state), and cyclic. CJ-series DeviceNet Units support all four types.
The connection used by the DeviceNet Unit is automatically selected if the CX-Integrator is not used. If you use the CX-Integrator, you can automatically select the connection by the DeviceNet Unit, or you can specify the connections for each slave. You can set up to two connections. COS and cyclic connections cannot be specified at the same time.
Note If you use COS and cyclic connections, do not connect multiple Master Units on one network.
The characteristics of each connection are outlined in the following table.
Connection
Poll
Bit-strobe
COS (Change of
State)
Characteristics
Used for basic I/O.
Used for input of 8 bytes or less. Sends broadcasting requests from master and receives input from slaves.
Communications occur at regular cycles (heartbeat timer) and the connection is determined by the master or slave sending the data.
You can send data only when required, which reduces the network communications load.
You can use this connection to send data to the master or slave if the master or slave data changes.
COS connections are given priority over poll and bit-strobe connections, which may result in a longer communications cycle time due to the higher frequency of COS connections used to send data or large amounts of data sent with the use of COS. Therefore, COS connections are effective when changes to data are infrequent (approximately 100 ms min.), or to give higher priority to small amounts of data.
For DeviceNet Units, you can decide the transmission timing in the user program.
The following points apply for CJ-series DeviceNet Units:
If the master *_MstrCOSSendCmd (Master COS Send Switch) is changed to TRUE, remote I/O communications output data can be sent every time from the master using COS to the slaves that support COS.
If *_Sw2SlavCOSSendCmd (Slave COS Send Switch) is set to TRUE, you can send remote I/O communications output data every time from the slave using COS to the master (input data from the perspective of the master).
Even if the software switch is not changed to TRUE, you can perform the COS communications using regular cycles (heartbeat timer) simultaneously.
Note COS and cyclic connections cannot be used at the same time.
Cyclic
Note This CJ-series DeviceNet Unit supports COS.
Communications timing is determined by regular cycles (heartbeat timer).
Masters and slaves send output or input data in regular cycles.
Cyclic connections are have higher priority than poll or bit-strobe connections, which may result in a longer communications cycle time due to large amounts of data sent with the use of cyclic connections. Therefore, cyclic connections are effective when changes to data are infrequent, or the amount of data to be sent is small.
A-35 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Appendices
Connections Using Allocations
With CX-
Integrator
Without CX-
Integrator
Allocation method
User-set allocations from the CX-Integrator
Contents
The user can select the connection to be used for each node address with the CX-Integrator e.g., poll could be used for data and COS could be used for status. You can specify automatic selection or user selection. You can use two connections simultaneously for one slave
(but you cannot use COS and cyclic simultaneously.)
Only 1 connection, automatically selected by the DeviceNet Unit.
(Either a polling or bit-strobe connection is used.)
Fixed allocation
(scan list disabled or enabled)
User-set allocations using device variables for CJ-series
Unit
Only 1 connection, automatically selected by the DeviceNet Unit based on the I/O area set in the Master User-set Allocations Setup
Table.
Setting Connection Type
The settings for remote I/O communications connections differ depending on the allocation method, as outlined below.
z
Fixed Allocations or User-set Allocations Using Device Variable for CJ-series
Unit
The Master CJ-series DeviceNet Unit automatically selects either poll or bit-strobe, whichever makes the communications cycle time shortest.
z
User-set Allocations Using the CX-Integrator
The Master CJ-series DeviceNet Unit can make an automatic selection, the same as above, or the user can select up to two connections for a Slave. The setting method is outlined below.
1
Select the Master Node in the Network Configuration Window in the CX-Integrator.
2
Select Device – Parameters – Edit – All Masters and select the corresponding Slave. Click the
Detailed Settings Button.
3
On the Connection Tab Page shown below, select a check box.
• Automatic selection
• User selection
Select up to two connections from poll, bit–strobe, COS and cyclic. COS and cyclic connections cannot be used at the same time.
A-36 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Appendices
Output data using poll connections and output data using COS or cyclic connections are transmitted using the same frame. Therefore set the same output size (bytes) when you combine poll and COS or poll and cyclic.
Additional Information
The COS/cyclic heartbeat timer is the smallest transmission interval for COS or cyclic connections. You can set it for each corresponding slave.
For details on using the CX-Integrator, refer to the CP CS/CJ/CP/NSJ CX-Integrator Ver.2.
@ Operation
Manual (Cat. No. W464).
Connection Path
Connection path are parameters that specify the type of I/O data in the slaves. Depending on the type of slave, the internal I/O data type may be able to be selected. For the relationships between the selected applicable connections and the applicable connections per I/O area words (block), refer to the
.
The connection path settings will differ depending on the allocation method, as outlined below.
Fixed Allocations or User-set Allocations Using Device Variable for CJ-series
Unit
Connection path settings cannot be made.
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) A-37
Appendices
User-set Allocations Using the CX-Integrator
The CX-Integrator can be used to set the type of I/O data in the slave, using the connection path.
The user can use this method to specify the I/O data type within the slave with which they would like perform master and remote I/O communications.
The connection path is saved by the CX-Integrator to the CJ-series DeviceNet Unit scan list and when the remote I/O communications are started, the connection path is set to the slave via the
DeviceNet network.
Master
Slave
I/O data
Connection
Connection path
Data 1 Data 2
A-38 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Appendices z
Master COS Send Switch
COS transmission is possible only for User-set allocations using the CX-Integrator.
When required, you can output the remote I/O output data from the master to a specified slave.
In this case, sending output data at the communications cycle timing to the specified slave by other connections selected automatically or by the user (only when using the CX-Integrator) is performed.
In this case, the communications timing is not dependant on the communications cycle time but it is dependant on the CPU Unit cycle time.
Note When a master or slave sending data with COS communications must handle large quantities of data or when data is sent frequently using COS communications, the communications cycle time may actually be longer than when using poll communications. This can have a large impact on the performance of remote I/O communications and delay responses. Therefore, give ample consideration to the system performance when using COS.
DeviceNet Units use the Master COS Send Switch in the allocated CIO Area words to execute COS transmissions from the master to slaves. The procedure is outlined below.
Step 1
Before executing COS transmission, the connection for the destination slave must be set to COS in the master scan list, using the CX-Integrator.
Step 2
If the bits associated with the node address of *_MstrCOSSendCmd (Master COS Send Switch) or the array variables associated with the node address, *_MstrCOSSendNdCmd[0] to
*_MstrCOSSendNdCmd[63] are changed to TRUE, sending OUT data is triggered independently of the communication cycle.
COS send switch OFF to ON
I/O refresh Time
CPU Unit user program
COS send instruction
DeviceNet Unit
Communications cycle time
Communications cycle time
Communications cycle time
Communications cycle time
Slave
I/O using normal connection COS output
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) A-39
Appendices
You can change multiple bits to TRUE simultaneously and you can send output data to multiple node addresses simultaneously.
The following diagram shows the transmission timing. After the COS send instruction is sent to the
DeviceNet (at the I/O refresh timing for the CPU Unit), the COS transmission is executed to each slave immediately after the refresh (remote I/O communications), which is performed with each slave during the communications cycle. Therefore, when there are a lot of destination slaves, the COS send timing may be delayed in order of the node addresses.
Multiple COS send switches (node address #1, #2, #3) changed to
FALSE to TRUE
I/O refresh Time
CPU Unit user program
COS send instruction
DeviceNet Unit
Node #1 Node #2 Node #3 Node #4 Node #1
COS
#1
Node #2
COS
#2
Node #3
COS
#3
Node #4
Communications cycle time Communications cycle time
Slave # 1
Slave # 2
Slave # 3
: I/O using normal connection
: Output using COS (sent to fit in between normal cycles)
A-40 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Appendices
A-3 DeviceNet Explicit Message Send
Command for Other Manufacturer
Nodes
A-3-1 Explicit Message Send (2801)
Sends a DeviceNet explicit message to a specified object and receives a response.
z
Command Block
Command code
Class ID
Service code
Destination node address
Instance ID
534 bytes max.
Service data z
Response Block
• When a normal response is returned for the executed explicit message:
534 bytes max.
Command code
End code No. of bytes received
Service data
Service code
Source node address (local node)
• When an error response is returned for the executed explicit message:
Command code
End code No. of bytes received
Error code
(Fixed at 94 Hex)
Source node address (local node)
• When the explicit message execution failed or timed out:
Command code
End code
A-41 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Appendices z
Parameter Details
[Destination Node Address] (Command)
Specifies the node address of the explicit message destination.
The node address of the local Master Unit is specified as the input variables DstNetAdr (Destination network address) in the SendCmd instruction when the Explicit Message Send command is sent, but the node address of the actual destination is specified here.
[Service Code] (Command, response)
For commands, the service code defined by the DeviceNet is specified.
For normal responses, the value for which bit 15 of the service code specified in the command turns
ON is returned. For error responses, 94 hex, which indicates an error, is returned.
[Class ID] (Command)
Specifies the class ID for the explicit message destination.
[Instance ID] (Command)
Specifies the instance ID for the explicit message destination.
[Service Data] (Command, response)
For commands, specifies the data defined by the service code.
For responses, returns the data defined by the service code.
[No. of Bytes Received] (Response)
Returns the number of bytes received after Source (local node) Node Address.
[Source (local node) Node Address] (Response)
Returns the local node DeviceNet node address that was the source of the explicit message.
[Error Code] (Response)
Returns the error code defined by the DeviceNet.
z
Explanation
• The Explicit Message Send command sends a DeviceNet-defined explicit message to an OMRON
Special I/O Slave Unit or a DeviceNet Slave manufactured by another company and receives a response.
• The input variables DstNetAdr (Destination network address) in the SendCmd instruction specifies the local node DeviceNet Master Unit when the Explicit Message Send command is sent. The actual destination node is specified with the use of the Destination Node Address in the Explicit
Message Send command.
Additional Information
• Refer to DeviceNet Specifications for explicit message parameter details.
• For information on explicit messages for OMRON slave, refer to the DRT2 Series DeviceNet
Slaves Operation Manual (Cat. No. W404).
• Contact the ODVA to obtain copies of the DeviceNet specification.
ODVA's URL: http://www.odva.org/
A-42 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Appendices
A-4 Multi-vendor Applications
This appendix provides precautions and reference material needed when you use DeviceNet (Compo-
Bus/D) Units as DeviceNet components in a multi-vendor environment.
z
Connecting another Company's DeviceNet Slaves to an OMRON Master
For connecting another Company's DeviceNet Slaves to an OMRON Master, consult the document attached to another Company's DeviceNet slave.
If a Slave has an EDS file, you can install it in the CX-Integrator to enable handling it just like an
OMRON DeviceNet Slave.
In particular, be sure to determine the number of words in the OMRON Master Unit that another
Company's DeviceNet Slave requires for input and output.
With Connection Object instance 2 (Polled I/O Connection) of another company's DeviceNet slave, you can find the number of I/O words allocated in the OMRON Master from the "Produced Connection Size" and "Consumed Connection Size" as shown below. You can allocate up to 100 words to inputs and another 100 words to outputs.
Produced Connection Size
This is the amount of memory (usually in bytes) allocated as input.
Consumed Connection Size
This is the amount of memory (usually in bytes) allocated as output.
If the connection size is an even number of bytes, the number of allocated words is: (bytes
÷
2).
If the connection size is an odd number of bytes, the number of allocated words is: [(bytes +1) ÷ 2)].
If the connections size is zero (0), no words are allocated.
For Connection Object instance 3 (Bit Strobed I/O Connection) of the DeviceNet Slave, you can find the number of input words allocated in the OMRON Master from the "Produced Connection Size" as shown below.
Produced Connection Size
This is the amount of memory (usually in bytes) allocated as input.
If the connection size is an even number of bytes, the number of allocated words is: (bytes
÷
2).
If the connection size is an odd number of bytes, the number of allocated words is: [(bytes +1) ÷ 2)].
z
Connecting to another Company's Configurator
When another company's configurator (a tool that makes environment settings on DeviceNet Masters and Slaves) is connected, it will be able to read settings from OMRON Masters and Slaves but not change them.
When another company's configurator is used, we recommend you create an OMRON DeviceNet
Slave EDS file (a file that contains each Slave's parameters and operating information). Refer to the
OMRON DeviceNet Slave device profile as well as the Configurator's manual for details on creating an EDS file.
A-43 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Appendices
Master Unit Device Profile
General data
Physical conformance data
Communications data
Compatible DeviceNet Specifications
Vendor name
Device profile name
Manufacturer revision
Network current consumption
Connector type
Physical insulation
Supported indicators
MAC ID setting
Default MAC ID
Baud rate setting
Volume I - Release 2.0
Volume II - Release 2.0
OMRON Corporation
Communication Adapter
1.1
24 VDC, 30 mA max.
Open plug
Yes
Module, Network
Rotary switch
63
DIP switch
Vendor ID = 47
Profile number = 12
Supported baud rates 125 kbit/s, 250 kbit/s, and 500 kbit/s
Predefined Master/Slave connection set Group 2 client
Group 2 only client
Group 2 server
Dynamic connection support (UCMM) Yes
Explicit message fragmentation support Yes
Object Mounting
z
Identity Object (01 Hex)
Object class Attribute
Service
Not supported
Not supported
Item ID content
Get
(read)
Yes Object instance Attribute 1 Vendor
2 Product type
3 Product code
Yes
Yes
4 Revision Yes
5 Status (bits supported) Yes
Service
6 Serial number
7 Product name
8 State
DeviceNet Service
Yes
Yes
No
05 Reset
0E Get Attribute Single
No
No
No
Set
(write)
No
No
No
No
No
Value
47
12
CJ1W-DRT21: 05
1.1
---
Unique for each Unit
CJ1W-DRM21
---
Parameter option
None
None
A-44 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Appendices z
Message Router Object (02 Hex)
Object class Attribute
Service
Object instance Attribute
Service
Not supported
Not supported
Not supported
Not supported
Vendor specification addition No z
DeviceNet Object (03 Hex)
Object class
Item ID content
Get
(read)
Yes
Set
(write)
No Attribute 1 Revision
Service DeviceNet service Parameter option
0E Get_Attribute_Single No
2
Item
Service
3 BOI
ID content
Object instance Attribute 1 MAC ID
2 Baud rate
4 Bus–off counter
Get
(read)
Yes
Yes
Yes
Yes
5 Allocation information Yes
6 MAC ID switch changed
No
No 7 Baud rate switch changed
8 MAC ID switch value No
(write)
No
No
No
No
No
No
No
Set
No
9 Baud rate switch value No
DeviceNet service
No
Parameter option
0E Get_Attribute_Single No
4B Allocate_Master/
Slave_Connection Set
No
4C Release_Master/
Slave_Connection Set
No
0
0
---
---
---
---
---
---
--z
Connection Object (05 Hex)
Object class Attribute
Service
Max. number of instances
Not supported
Not supported
203
Value
Value
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) A-45
Appendices
Object instance
1
Section Information
Max. No. of instances
1 Instance type
Production trigger
Transport type
Transport class
Attribute
Explicit Message
Cyclic
Server
3
Service
---
1 State
ID content
2 Instance_type
3 Transport_class_trigger
4 Produced_connection_ID
5 Consumed_connection_ID
6 Initial_comm_characteristics
7 Produced_connection_size
8 Consumed_connection_size
Get
(read)
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Set
(write)
No
No
No
No
No
No
No
No
9 Expected_packed_rate
12 Watchdog_timeout_action
13 Produced_connection_path_ length
Yes
Yes
Yes
Yes
Yes
No
14 Produced_connection_path
15 Consumed_connection_path_ length
Yes
Yes
16 Consumed_connection_path Yes
17 Production_inhibit_time
DeviceNet service
No
No
No
Yes Yes
Parameter option
05 Reset
0E Get_Attribute_Single
10 Set_Attribute_Single
No
No
No
Value
---
0
83 hex
---
---
21 hex
553
Format 16-16: 557
Format 8-8: 555
Format 16-8, 8-16:
556
---
1 or 3
0 empty
0 empty
---
A-46 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Appendices
Object instance
2
Section Information
Instance type
Production trigger
Transport type
Transport class
Attribute
Polled I/O
Cyclic
Server
2
Service
ID content
1 State
2 Instance_type
3 Transport_class_trigger
4 Produced_connection_ID
5 Consumed_connection_ID
6 Initial_comm_characteristics
7 Produced_connection_size
8 Consumed_connection_size
9 Expected_packed_rate
Get
(read)
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Set
(write)
No
No
No
No
No
12 Watchdog_timeout_action
13 Produced_connection_path_ length
14 Produced_connection_path
Yes
Yes
15 Consumed_connection_path_ length
Yes
Yes
16 Consumed_connection_path Yes
17 Production_inhi_bit_time Yes
DeviceNet service
05 Reset
No
No
No
No
No
Yes
Parameter option
No
0E Get_Attribute_Single
10 Set_Attribute_Single
No
No
No
No
No
Yes
Max. No. of instances
1
---
0
4
*2
---
---
---
1
*1
---
1
82 hex
Value
20 94 24 01 hex
4
20 94 24 01 hex
---
*1 Number of input bytes used by Slave.
*2 Number of output bytes used by Slave.
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) A-47
Appendices
Object instance
3
Section Information
Max. No. of instances
1 Instance type
Production trigger
Transport type
Transport class
Attribute
Bit Strobed I/O
Cyclic
Server
2
Service
---
ID content
1 State
2 Instance_type
3 Transport_class_trigger
4 Produced_connection_ID
5 Consumed_connection_ID
6 Initial_comm_characteristics
7 Produced_connection_size
8 Consumed_connection_size
9 Expected_packed_rate
0E Get_Attribute_Single
10 Set_Attribute_Single
Get
(read)
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
No
Set
(write)
No
No
No
No
No
No
No
No
Yes
12 Watchdog_timeout_action
13 Produced_connection_path_ length
14 Produced_connection_path
Yes
Yes
15 Consumed_connection_path_ length
Yes
Yes
16 Consumed_connection_path Yes
17 Production_inhibit_time Yes
DeviceNet service
05 Reset
No
No
No
No
No
Yes
Parameter option
No
---
1
82 hex
2
*
---
---
0
0
8
--empty
4
Value
20 94 24 01 hex
---
* Number of input bytes used by Slave.
A-48 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Appendices
Object instance
4
Section Information
Max. No. of instances
1 Instance type
Production trigger
Transport type
Transport class
Attribute
COS/cyclic I/O
Cyclic
Client
0 (no ACK)/2 (with ACK)
ID content
Service
---
1 State
2 Instance_type
3 Transport_class_trigger
4 Produced_connection_ID
5 Consumed_connection_ID
6 Initial_comm_characteristics
Get
(read)
Yes
Yes
Yes
Yes
Yes
Yes
Set
(write)
No
No
No
No
No
No
Value
---
*
02 hex (with Cyclic
ACK)
12 hex (with COS
ACK)
00 hex (no Cyclic
ACK)
10 hex (no COS
ACK)
---
*
---
---
0
4
FFFF hex (no
ACK)
01 hex (with ACK)
0F hex (no ACK)
7 Produced_connection_size
8 Consumed_connection_size
9 Expected_packed_rate
12 Watchdog_timeout_action
13 Produced_connection_path_ length
14 Produced_connection_path
15 Consumed_connection_path_ length
Yes
Yes
16 Consumed_connection_path Yes
Yes
Yes
Yes
Yes
Yes
17 Production_inhibit_time
DeviceNet service
05 Reset
0E Get_Attribute_Single
10 Set_Attribute_Single
No
No
Yes
No
No
No
No
No
Yes Yes
Parameter option
No
No
No
20 94 24 01 hex
0 (no ACK)
4 (with ACK) empty (no ACK)
20 2B 24 01 (with
ACK)
---
* Number of input bytes used by Slave.
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) A-49
Appendices
A-50
Object instance
5 and above
Section Information
Instance type
Production trigger
Transport type
Transport class
Attribute
Explicit Message/ I/O Message
Cyclic
Server
0/2/3
Service
---
ID content
1 State
2 Instance_type
3 Transport_class_trigger
4 Produced_connection_ID
5 Consumed_connection_ID
6 Initial_comm_characteristics
7 Produced_connection_size
8 Consumed_connection_size
9 Expected_packed_rate
Get
(read)
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Set
(write)
No
No
No
No
No
12 Watchdog_timeout_action
13 Produced_connection_path_ length
14 Produced_connection_path
Yes
Yes
15 Consumed_connection_path_ length
Yes
Yes
16 Consumed_connection_path Yes
17 Production_inhi_bit_time Yes
DeviceNet service
05 Reset
No
No
No
No
No
Yes
Parameter option
No
0E Get_Attribute_Single
10 Set_Attribute_Single
No
No
No
No
No
Yes
---
---
---
---
---
*1
*2
---
---
---
---
---
---
---
---
Max. No. of instances
199
Value
*1 The following table shows the instance type by communications type.
Communications type
Explicit Message
I/O
0
1
Instance type
*2 The following table shows the transport class trigger by connection type.
Format
Poll client
COS (M) client
COS (M) server
Cyclic (M) client
Cyclic (M) server
22 hex
Transport_class_trigger
12 hex (with ACK)/10 hex (no ACK)
92 hex (with ACK)/90 hex (no ACK)
02 hex (with ACK)/00 hex (no ACK)
82 hex (with ACK)/80 hex (no ACK)
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Appendices
Object instance
1 (CIO area)
Service
Object instance
3 (DM area)
Service
Object instance
4 (WR area)
Service
Object instance
5 (HR area)
Service
Object instance
6 (AR area)
Service
Object instance
7 (TIM/
CNT area)
Object instance
8-20
(EM0 to
EMC area)
Service
Service
Bit-strobe client
Explicit client
Explicit server
Format z
PLC Object (2F Hex)
Object class Attribute
Service
22 hex
23 hex
83 hex
Transport_class_trigger
Not supported
Not supported
DeviceNet service
1C Block String Read
1D Block StringN Read
1E Block String Write
1F Block StringN Write
1C Block String Read
1D Block StringN Read
1E Block String Write
1F Block StringN Write
1C Block String Read
1D Block StringN Read
1E Block String Write
1F Block StringN Write
1C Block String Read
1D Block StringN Read
1E Block String Write
1F Block StringN Write
1C Block String Read
1D Block StringN Read
1E Block String Write
1F Block StringN Write
1C Block String Read
1D Block StringN Read
1E Block String Write
1F Block StringN Write
1C Block String Read
1D Block StringN Read
1E Block String Write
1F Block StringN Write
Parameter option
Logical Area Address Length
Logical Area Address Length
Logical Area Address
Logical Area Address
Logical Area Address Length
Logical Area Address Length
Logical Area Address
Logical Area Address
Logical Area Address Length
Logical Area Address Length
Logical Area Address
Logical Area Address
Logical Area Address Length
Logical Area Address Length
Logical Area Address
Logical Area Address
Logical Area Address Length
Logical Area Address Length
Logical Area Address
Logical Area Address
Logical Area Address Length
Logical Area Address Length
Logical Area Address
Logical Area Address
Logical Area Address Length
Logical Area Address Length
Logical Area Address
Logical Area Address
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) A-51
Appendices
Note The refresh area types are shown in the following table.
PLC area
CIO
DM
WR
HE
EM (bank 0)
EM (bank 1)
EM (bank 2)
EM (bank 3)
EM (bank 4)
EM (bank 5)
EM (bank 6)
EM (bank 7)
EM (bank 8)
EM (bank 9)
EM (bank 10)
EM (bank 11)
EM (bank 12)
F
10
11
12
D
E
B
C
13
14
9
A
5
8
1
3
4
Refresh area type Refresh address
CIO 0000 to CIO 6143
D00000 to D32767
W000 to W511
H000 to H511
E0_00000 to E0_32767
E1_00000 to E1_32767
E2_00000 to E2_32767
E3_00000 to E3_32767
E4_00000 to E4_32767
E5_00000 to E5_32767
E6_00000 to E6_32767
E7_00000 to E7_32767
E8_00000 to E8_32767
E9_00000 to E9_32767
EA_00000 to EA_32767
EB_00000 to EB_32767
EC_00000 to EC_32767
A-52 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Index
I
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) Index-1
Index
Index
Numerics
7-segment indicator
....................................................... 2-4
A
Allocation size setup table
........................................... 3-55
Allocations Setting Table
............................................. 3-51
Assumed cause
........................................................... 9-36
AT specification
............................................................. 3-4
AT specification destination
........................................... 3-2
Automatic Slave Connection
............................. 3-32 ,
B
Backing Up Unit Setup File
........................................... 7-3
Baud Rate
..................................................................... 2-7
Bit-Strobe
.......................................................... 5-12
Bus Off Detected
......................................................... 9-55
Bus Off Error
............................................................... 3-27
C
C200H Master Replacement Master Status
,
C200H Master Replacement Master Status 1
Calculating Guidelines for I/O Response Times
Characteristics of remote I/O communication
CIO Area
.......................................................................A-2
Communication Cycle Time Reference Table
Communication Cycle Time Setting
Communication Error
(C200H Master Replacement Area)
Communications connector
........................................... 2-8
Communications Cycle Time Reference Table Clear
Switch
............................................................... 3-17
,
Communications Cycle Time Setting
..........................A-28
Communications Cycle Time Setting
Failed
..................................................... 3-37
,
Communications Cycle Time Setting Switch
,
Configuration Error
(C200H Master Replacement Area)
Configurator
.................................................................A-43
Connection Path
..........................................................A-37
Connection type
.................................................4-11
,
Controller error
............................................................ 9-35
Controller reset
............................................................ 4-31
COS
................................................................... 5-12
COS Send Failed
............................................... 3-43
COS/cyclic heartbeat timer setting
.............................. 1-11
CPU Unit watchdog timer error
................................... 9-29
Cyclic
...........................................................................A-35
Cyclic connection
........................................................ 5-12
Index-2
D
Data Exchange with the CPU Unit
................................ 3-2
Detailed Slave Status Table
................................3-51
,
Detailed status of slave
............................................... 3-51
Device data check function
.......................................... 1-11
Device name
.................................................................. 3-5
Device type
.................................................................. 4-11
Device variable for CJ-series Unit
DIP switch
...................................................................... 2-6
Disconnect/Connect Switch
............................... 3-24 ,
DM Area
........................................................................A-2
Dot indicator
.................................................................. 2-2
E
EEPROM
..................................................................... 1-11
Error code
.............................................................2-4
,
Error history (registration yes/no)
................................ 1-23
Error History Registered Flag
............................ 3-32 ,
Error is occuring
(C200H Master Replacement Area)
Error is occurring or Remote I/O Communications is stopped due to error (Master Error)
Establishing connections
...........................9-45
,
Event
........................................................................... 9-35
Event code
.................................................................. 9-36
Event level
................................................................... 9-36
Event Log
.................................................................... 9-35
Event name
................................................................. 9-36
Explicit message
........................................................... 6-2
Explicit message communication
.................................. 1-7
F
File Read/Write Error
................................ 3-32
Fixed allocation
.................................... 1-7
,
I
I/O Bus check error
..................................................... 9-32
I/O Data Communications Not Running Status
(C200H Master Replacement Area)
I/O Data Communications Status
,
I/O Map
.......................................................................... 3-5
I/O port
...................................................................3-2
I/O setting check error
................................................. 9-32
Indicator
......................................................................... 2-4
Indicator status
.......................................................8-8
Invalid Message Timer List Error
Invalid Scan List Data
.................................................. 9-43
Invalid Scan List Data Error
............................... 3-34
Invalid Scan List Data Flag
(C200H Master Replacement Area)
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
Index
Invalid Setup Data
.....................................3-40 ,
M
maintenance
............................................................... 9-60
Master COS Send Switch
.......................... 3-23
Master Disable Switch
.........................................3-13
Master Enable Switch
..........................................3-13
Master Error (C200H Master Replacement Area)
Master Fixed Allocation Area Setting
Failed
.....................................................3-36
Master Fixed Allocation Setting 1/2/3 Switch
Master Function Enable/Disable Failed
Master Function Enabled Status
Master Function Error
........................................3-26
Master I/O Allocation Status
....................................... 3-38
Master I/O Refresh Error
...........................3-35
Master Status 1
..................................................3-33
Master Status 2
..................................................3-38
Master User-set Allocations Reference Table
Master User-set Allocations Setup Table
Master User-set Allocations Switch
Master User-set Allocations User Setting
Failed
.....................................................3-35
Memory Card Backup function
.................................... 1-11
Memory used for CJ-series Unit
................................. 1-17
Message Communications
............................................ 6-2
Message Communications Permitted
(C200H Master Replacement Area)
Message communications time
................................... 8-10
Message monitoring timer
............................................. 6-5
MS indicator
.................................................................. 2-3
MS LED
......................................................................... 2-3
N
Network Power Error
.................................3-28
Node address
.............................................................. 3-55
Node Address Duplicated Error
Node Address Duplicated/Bus Off Error
Node Address of The Remote Master for Slave Communication
................................3-45
Node Address Switch
.................................................... 2-6
Normal Slave Table
............................................3-47
NS indicator
.................................................................. 2-3
O
Online Status
.....................................................3-30 ,
P
PLC Object
.................................................................. 6-16
Poll
.....................................................................5-12 ,
Power OFF retention
..................................................... 1-7
Product code
............................................................... 4-11
R
Registered Slave Table
......................................3-46
Remote I/O and Slave Communication
Remote I/O Communications
Error
............................................. 3-34
Remote I/O Communications Error for OUT/IN
Remote I/O Communications Flag
.............................. A-28
Remote I/O Communications for OUT/IN
Remote I/O Communications Start Switch
Remote I/O Communications Status
Remote I/O Communications Stop Switch
Remote I/O Data Communications Flag
(C200H Master Replacement Area)
......................... 3-50
Remote I/O Master Specification
.................................. 4-5
Restarting Remote I/O Communication
Restoring Unit Setup File
.............................................. 7-3
Routing Table Error
...................................3-29
S
Scan list
...................................................................... 4-11
Scan List Clear Switch
....................................... 3-10
Scan List Disabled
...................................................... 4-12
Scan List Disabled Status
........................................... 3-31
Scan List Enable Switch
............................................. 3-10
Scan List Enabled
....................................................... 4-12
Scan List Register/Clear Failed
Send Error
(C200H Master Replacement Area)
Send Timeout Error
...................................3-29
SendCmd instruction
............................................ 1-11
Setting Results of Master User-set Allocations
Setup
......................................................3-53
Setting Results of Slave User-set Allocations
Setup
......................................................3-56
Slave COS Send Failed
.............................................. 9-58
Slave COS Send Switch
......................................3-21
Slave detailed status
..................................................... 3-2
Slave Enable Switch
............................................3-19
Slave Fixed Allocation Area Setting
Failed
......................................................3-42
Slave Fixed Allocation Setting 1/2/3 Switch
Slave Function Enable/Disable Failed
Slave Function Enabled
.....................................3-32
Slave Function Error
..........................................3-27
Slave I/O Allocation Status
.................................3-45
Slave I/O Refresh Error
.............................3-41
Slave Status 1
....................................................3-39
Slave Status 2
....................................................3-45
Slave Stop Switch
................................................3-19
Slave User Allocation Area Setting Failed
Slave User Allocations Switch
............................ 3-21
Slave User-set Allocations Area Setting Failed
Slave User-set Allocations Reference Table
Slave User-set Allocations Setup Table
Slave User-set Allocations User Setting Failed
Software Switch
..................................................... 3-2
Software Switch 1
................................................ 3-9
I
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497) Index-3
Index
Software Switch 2
.................................................3-9
,
Special Unit Setup Editing
........................................... 3-51
Starting Remote I/O Communication
.......................... 4-31
Status
...................................................................3-2
,
Stop remote I/O communication upon communication error
............................................................................ 2-7
Stopping Remote I/O Communication
......................... 4-31
Structure Error
....................................................3-33
,
Structure Error
(C200H Master Replacement Area)
Sysmac Studio
............................................................ 1-15
System startup time
...................................................... 8-8
System-defined variable
.......................................3-2
,
T
Temporary Setting Switch for Communications
Cycle Time
........................................................ 3-16
,
U
Unit Configuration
.......................................................... 3-5
Unit Error
........................................................... 3-26
Unit Memory Error
.................................... 3-27
,
Unit Memory Error
(C200H Master Replacement Area)
Unit No. Switch
.....................................................2-5
,
Unit number duplication
............................................... 9-20
Unit Restart
................................................................... 3-2
Unit Setup File Backup Switch
............................ 3-22
,
Unit Setup File Restore Switch
............................ 3-22
,
Unit Status 1
...................................................... 3-25
Unit Status 2
...................................................... 3-30
User program
................................................................ 3-4
User-defined variable
.............................................3-2
User-set Allocation (Master Communications)
User-set Allocation (Slave Communications)
V
Vendor
......................................................................... 4-11
Verification Error
.................................................3-33
,
Verification Error
(C200H Master Replacement Area)
Index-4 CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
OMRON Corporation
Industrial Automation Company
Tokyo, JAPAN
Contact: www.ia.omron.com
Regional Headquarters
OMRON EUROPE B.V.
Wegalaan 67-69-2132 JD Hoofddorp
The Netherlands
Tel: (31)2356-81-300/Fax: (31)2356-81-388
OMRON ELECTRONICS LLC
One Commerce Drive Schaumburg,
IL 60173-5302 U.S.A.
Tel: (1) 847-843-7900/Fax: (1) 847-843-7787
Authorized Distributor:
OMRON ASIA PACIFIC PTE. LTD.
No. 438A Alexandra Road # 05-05/08 (Lobby 2),
Alexandra Technopark,
Singapore 119967
Tel: (65) 6835-3011/Fax: (65) 6835-2711
OMRON (CHINA) CO., LTD.
Room 2211, Bank of China Tower,
200 Yin Cheng Zhong Road,
PuDong New Area, Shanghai, 200120, China
Tel: (86) 21-5037-2222/Fax: (86) 21-5037-2200
© OMRON Corporation 2011 All Rights Reserved.
In the interest of product improvement, specifications are subject to change without notice.
Cat. No. W497-E1-03 0812
ダウンロード
ドキュメントの公開リンク
広告