Format Of Access Blocks For Event Interaction - Mitsubishi Electric MELSEC iQ-R User Manual

Format of access blocks for Event interaction

The following shows the buffer memory format of access blocks for Event interaction, including data ranges and availability of
reading/writing data from a CPU module.
When creating a program, read the offset value in the following table with the start buffer memory address displayed with a
configuration function.
R: Read-only, W: Write-only, R/W: Read/Write
Offset Name
+0 STATUS b15
b14 to
b13
b12 to
b10
b9 to
b7
b6
b5
b4
b3
b2
b1
b0
+1 EventTyp b15
e/Priority
b14
b13
b12
b11
b10
b9
b8
b7 to
b0
CONTROL
NotifyType
FromState
ToState
AckRequired

Existence of the StatusFlags in Event
notification
StatusFlags InAlarm
of Event
Fault
notification
Overridden
OutOfService
EventType CHANGE_OF_LIFE_SAFE
TY
BUFFER_READY
OUT_OF_RANGE
FLOATING_LIMIT
COMMAND_FAILURE
CHANGE_OF_VALUE
CHANGE_OF_STATE
CHANGE_OF_BITSTRING
Priority
*1
Description
The reception status of an Event
notification is stored.
0: Idling
1: Event notification reception
complete
The type of received Event notification
is stored.
0: Alarm
1: Event
2: AckNotification
The status before an Event
occurrence is stored.
0: Normal
1: Fault
2: Offnormal
3: HighLimit
4: LowLimit
5: LifeSafetyAlarm
7: No data
The status after an Event occurrence
is stored.
0: Normal
1: Fault
2: Offnormal
3: HighLimit
4: LowLimit
5: LifeSafetyAlarm
7: No data
The AckRequired property value of a
NotificationClass object is stored.
0: False
1: True
Not used
The information on whether a
StatusFlags is included or not in an
Event notification is stored.
0: None
1: Exist
0: False, 1: True
0: False, 1: True
Always 0
0: False, 1: True
0: False, 1: True
0: False, 1: True
0: False, 1: True
0: False, 1: True
0: False, 1: True
0: False, 1: True
0: False, 1: True
0: False, 1: True
The priority of an Event is stored.
Appendix 7 Data Block Formats
R/W Initial Data range
value

R/W 0
R 0 
APPX
295
A