Operation Of A Bacnet Module - Mitsubishi Electric MELSEC iQ-R User Manual

Operation of a BACnet module

Operation at startup
A BACnet module initializes an access block for Event interaction with '0' at the startup of the module.
Operation when an Event notification is received
■ Storage of an Event notification to an access block for Event interaction
• When an Event notification is received from the send source object set to an access block for Event interaction, a BACnet
module stores the received Event notification to the access block for Event interaction while the CONTROL is '0' (idling).
Then, '1' (Event notification reception complete) is stored to the CONTROL.
• If a new Event notification is received while the CONTROL is '1' (Event notification reception complete), the new Event
notification will be discarded without storing to the access block for Event interaction.
• With the following setting, an access block for Event interaction can be updated (overwritten) every time
when a new Event notification is received. This makes it unnecessary to store '0' to the CONTROL (b15)
after reading data.
Set '1' to "RecDataOverwriteEventLink" in [Settings]  [Basic Information]  [BACnet Detail Setting] button
 [Edit] button  "Interaction".
■ Interaction with BACnet monitoring function
By setting the following item, when an Event notification is received from the property specified with the BACnet monitoring
function, a BACnet module stores the property values to an access block for BACnet monitoring.
Set '1' to "MonitorDataSetByEvent" in [Settings]  [Basic Information]  [BACnet Detail Setting] button  [Edit] button 
"Interaction".
The data included in the received Event notification is written to the corresponding property of an access block for BACnet
monitoring.
Data included in Event notification
NotificationClass
NotifyType
ToState
StatusFlags
An EventValues parameter included in an Event notification corresponds to properties for each EventType.
The relations between the parameters and the properties of each EventType are as follows:
EventType Main object that uses
EventType
EventType (change-of-state) BI, BV, MI, MV
EventType (command-failure) BO, MO
EventType (out-of-range) AI, AO, AV
Precautions
• Be sure to store '0' (idling) to the CONTROL (b15) after reading the data of an Event notification.
The Status and Data are not updated while the CONTROL (b15) is '1' (Event notification reception complete). (Page
155 Storage of an Event notification to an access block for Event interaction)
Property of an access block for BACnet
monitoring
NotificationClass
NotifyType
EventState
StatusFlags
Information in EventValues
parameter
new-state binary-value
unsigned-value
CommandValue
FeedbackValue
exceeding-value
deadband
exceeded-limit
Remarks



A StatusFlags is always included in an EventValues.
Property of an access block for BACnet
monitoring
PresentValue of BI/BV
PresentValue of MI/MV
PresentValue of BO/MO
FeedbackValue of BO/MO
PresentValue of AI/AO/AV
Deadband of AI/AO/AV
ToState is HighLimit: HighLimit of AI/AO/AV
ToState is LowLimit: LowLimit of AI/AO/AV
1 FUNCTIONS
1.8 Event Interaction Function
1
155