Manual
Table Of Contents
- Anybus® Communicator™ - EtherNet/IP™ to Modbus RTU/Serial
- Table of Contents
- 1. Preface
- 2. Safety
- 3. Preparation
- 4. About Anybus Communicator
- 5. Installation
- 6. Configuration Quick Guide
- 7. Communicator Configuration
- 7.1. Connect the Communicator
- 7.2. Access the Built-In Web Interface From HMS IPconfig
- 7.3. Access the Built-In Web Interface From a Web Browser
- 7.4. Communicator Built-In Web Interface Overview
- 7.5. General Subnetwork Settings
- 7.6. About Transaction Templates
- 7.7. Build Transaction Template
- 7.8. Nodes and Transactions
- 7.9. High Level Network Settings
- 7.10. I/O Data Map
- 7.11. Configuration Notes
- 7.12. Apply Configuration
- 7.13. To Use an Existing Configuration
- 7.14. To Use an Communicator Classic Configuration
- 8. PLC Configuration
- 9. Verify Operation
- 10. Use Cases
- 11. Maintenance
- 12. Troubleshooting
- 13. Technical Data
- 14. Reference Guides
12.1.3. Event Log
Figure 113. Event log page example
How To Analyze the Informaon
The log follows the FIFO principle, rst in and rst out. The oldest (rst) value is processed rst.
Time (d:hh:mm:ss.ms) The date and me when the event occurred.
Message A brief descripon of the event.
Severity The severity of the event occurred.
For descripon of the symbols, see Communicator Status Monitor (page 92).
Source 0 Communicator
1 High level network, EtherNet/IP
2 Subnetwork, Serial RS-232/485
Sub-source The nodes connected to the subnetwork and the PLC connected to the high level network.
If there is a problem with a node the node name is displayed in the Sub-source column.
Example 6. Sub-source number
If the node name is 5, number 5 is displayed in the Sub-source column.
To clear the current log, click Clear log.
Diagnoscs Anybus
®
Communicator
™
- EtherNet/IP
™
to Modbus RTU/Serial
SCM-1202-152 Version 1.12 Page 123 of 133