Communication Event Log; Communications Event Log - Mitsubishi FX3U Series User Manual

Hide thumbs Also See for FX3U Series:
Table of Contents

Advertisement

FX
Series Programmable Controllers
3U
User's Manual - MODBUS Serial Communication Edition
9.5

Communication Event log

This section details the communication event log details for the MODBUS slave device.
9.5.1

Communications event log

1. Communications event log information in the communication status area
If configured in D8415/D8435 and D8416/D8436 the event log data is displayed in the communication status
area. The events of the event log are stored to the communication status area as shown below. For more
information on Communication Status refer to Section 6.4.
D8415 = 11H - i.e. store event counter and event log into D devices
D8416 = 100 - i.e. head device is set to D100
D100-
D109
D110
D111
event log byte 1
D112
event log byte 3
D113
event log byte 5
D141
event log byte 61
D142
event log byte 63
Note
If the number of communications event logs exceeds 64, the oldest log is deleted and the latest log is stored
to Communications event log 0.
2. Communications event log response format if ADPRW command is used (For command
code 0x0C "get communication event log")
When executing the ADPRW command (command code 0x0C "Get Communication Event Log") the slaves
response data is stored in the following format:
Example: Read event log from slave 4
ADPRW K4, H0C, K0, K0, D2000
FFFFH = programming command in process
D2000
0000H = no program. Command in process
D2001
D2002
D2003
D2004
event log byte 1
D2005
event log byte 3
D2006
event log byte 5
D2034
event log byte 61
D2035
event log byte 63
Note
If the number of communications in the event log exceeds 64, the oldest log is deleted and the latest log is
stored to Communications event log 0.
94
High byte
Low byte
Event and Error counter.
For details refer to Section 6.4
event log length in bytes
event log byte 0
event log byte 2
event log byte 4
event log byte 60
event log byte 62
High byte
Low byte
Programming state
(always 0000H in case of FX
Event counter
Bus message counter
event log length in bytes
event log byte 0
event log byte 2
event log byte 4
event log byte 60
event log byte 62
New values
Old values
slave)
3U
New values
Old values
9 Slave Specification
9.5 Communication Event log

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents