4-7 Errors that May Occur in Remote I/O Communications. Omron Sysmac CS/CJ Series DeviceNet Units
Add to my manuals
292 Pages
Omron Sysmac CS/CJ Series DeviceNet Units are powerful and versatile devices that offer a range of features and capabilities to meet the needs of a variety of applications. These units are designed to provide reliable and efficient communication between DeviceNet networks and PLCs. With their rugged construction and easy-to-use design, they are ideal for use in industrial automation environments.
advertisement
Errors that May Occur in Remote I/O Communications
Section 4-7
4-7 Errors that May Occur in Remote I/O Communications
The following errors may occur during remote I/O communications.
Condition
Error occurs in fixed allocations with the scan list disabled
Error
Structure
Error Flag
(word n+12, bit 04) turns
ON
Error occurs in either fixed or user-set allocations with the scan list enabled
Verification
Error Flag
(word n+12, bit 00) turns
ON
Details Results
Duplicate I/
O area
I/O area range exceeded
Unsupported
Slave
No slaves present
I/O size mismatched
Incorrect vendor
Incorrect device type
Incorrect product code
Incorrect connection bus
Unsupported connection
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.
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.
Reconnect with the error slave and continue remote I/O communications.
Indicators 7segment display
d0 MS: Not related
NS:
Flashes red d1 d2 d5 d6 d6 d6 d6 d6 d6
122
Errors that May Occur in Remote I/O Communications
Section 4-7
Condition
Fixed or user-set allocations
Error Details Results Indicators 7segment display
d9 I/O communications error 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.)
Reconnect with the error Slave and continue remote I/O communications.
*1
Network power error
Send timeout
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
Duplicated node address
Bus OFF detected
The master node address is the same address as another node.
Bus OFF error was detected.
Master scan list logic error The master scan list data is incorrect.
MS: Not related
NS:
Flashes red
MS: Not related
NS: Goes out
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).
MS: Not related
NS:
Flashes red
MS:
Flashes red
NS: Not related
E0
E2
F0
F1
E8
Note
Remote I/O communications will stop (7-segment display: 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.
123
Errors that May Occur in Remote I/O Communications
Section 4-7
124
SECTION 5
Remote I/O Slave Communications
This section describes the remote I/O communications performed as a DeviceNet slave by the DeviceNet Unit.
5-1 Slave Remote I/O Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-1-1 Allocation Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-1-2 Remote I/O and Slave Communications Specifications . . . . . . . . . .
5-1-3 Procedures for Using Remote I/O Slave Communications . . . . . . .
5-3-1 Connection Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-3-3 Connection Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
125
advertisement
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Key Features
- Support for both explicit and implicit messaging
- Extensive diagnostics and error handling capabilities
- Flexible addressing options
- Baud rate up to 500 kbps
- Supports up to 64 nodes per network
- Rugged construction for harsh industrial environments
- Easy-to-use design for quick and easy setup
Related manuals
Frequently Answers and Questions
What are the dimensions of the CS1W-DRM21(-V1) DeviceNet Unit?
What is the maximum number of nodes that can be connected to a DeviceNet network?
What is the baud rate of the DeviceNet Unit?
advertisement
Table of contents
- 2 CS-series DeviceNet Unit: CS1W-DRM21(-V1) CJ-series DeviceNet Unit: CJ1W-DRM21
- 4 Notice:
- 8 About this Manual:
- 10 Warranty
- 14 PRECAUTIONS
- 15 1 Intended Audience
- 15 2 General Precautions
- 15 3 Safety Precautions
- 16 4 Operating Environment Precautions
- 17 5 Application Precautions
- 19 6 Conformance to EC Directives
- 22 SECTION 1 Features and System Configuration
- 23 1-1 Overview of DeviceNet
- 40 1-2 DeviceNet Unit Features
- 47 1-3 Specifications
- 54 1-4 Comparison with Previous Models
- 58 1-5 Outline of the Configurator
- 61 1-6 Basic Operating Procedures
- 67 1-7 List of Usage Methods by Purpose
- 70 SECTION 2 Nomenclature and Installation
- 71 2-1 Nomenclature and Functions
- 76 2-2 Installing the DeviceNet Unit
- 82 SECTION 3 Allocated CIO and DM Words
- 83 3-1 Overview of Word Allocations
- 85 3-2 Allocated CIO Area Words
- 105 3-3 Allocated DM Area Words
- 116 SECTION 4 Remote I/O Master Communications
- 117 4-1 Master Remote I/O Communications
- 124 4-2 Scan List
- 126 4-3 Fixed Allocations
- 132 4-4 User-set Allocations
- 141 4-5 Starting and Stopping Remote I/O Communications
- 141 4-6 Example of Ladder Programming for Remote I/O Communications
- 143 4-7 Errors that May Occur in Remote I/O Communications
- 146 SECTION 5 Remote I/O Slave Communications
- 147 5-1 Slave Remote I/O Communications
- 150 5-2 Fixed Allocations
- 151 5-3 User-set Allocations
- 158 SECTION 6 Message Communications
- 159 6-1 Overview
- 166 6-2 FINS Commands and Responses
- 170 6-3 Using FINS Message Communications
- 182 6-4 Sending Explicit Messages
- 189 6-5 Receiving Explicit Messages
- 202 SECTION 7 Other Functions
- 203 7-1 Connecting to the CX-Programmer via the DeviceNet
- 207 7-2 Memory Card Backup Functions
- 210 7-3 Simple Backup Function
- 214 SECTION 8 Communications Timing
- 215 8-1 Remote I/O Communications Characteristics
- 221 8-2 Message Communications
- 226 SECTION 9 Troubleshooting and Maintenance
- 227 9-1 Troubleshooting with the DeviceNet Unit Indicators
- 245 9-2 Error Log Functions
- 249 9-3 Troubleshooting
- 252 9-4 Maintenance and Replacement
- 256 Appendix A Allocation Differences from C200H DeviceNet Master Units
- 262 Appendix B DeviceNet Connections
- 268 Appendix C FINS Commands and Responses for DeviceNet Units
- 274 Appendix D Multi-vendor Applications
- 284 Appendix E DeviceNet Explicit Message Send Command for Other Manufacturer Nodes
- 286 Index
- 290 Revision History