Instructions
Table Of Contents
- 1 Preface
- 2 Safety
- 3 Preparation
- 4 About Anybus Communicator
- 5 Installation
- 6 Configuration Quick Guide
- 7 Communicator Configuration
- 7.1 Connecting 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 Templates
- 7.8 Nodes and Transactions
- 7.9 High Level Network Settings
- 7.10 Naming the Host
- 7.11 Station Name
- 7.12 I/O Data Map
- 7.13 Apply Configuration
- 7.14 Use an Existing Configuration
- 8 PLC Configuration
- 9 Verify Operation
- 10 Use Cases
- 11 Maintenance
- 12 Troubleshooting
- 13 Technical Data
- A Reference Guides
Troubleshooting 112 (124)
12.1.2 Event Log
How To Analyze the Information
The log follows the FIFO principle, first in and first out. The oldest (first) value is processed first.
Time (d:hh:mm:
ss.ms)
The date and time when the event occurred.
Message
A brief description of the event.
Severity
The severity of the event occurred.
For description of the symbols, refer to Communicator Status Monitor, p. 84.
Source 0 Communicator
1
High level network, PROFINET
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: If the node name is 5, number 5 is displayed in the Sub-source column.
To clear the current log, click Clear log.
Anybus
®
Communicator
™
User Manual
SCM-1202-176 1.0 en-US