EasyManua.ls Logo

Mitsubishi Electric MELSEC iQ-R - Operation of a Bacnet Module

Mitsubishi Electric MELSEC iQ-R
306 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
1 FUNCTIONS
1.8 Event Interaction Function
155
1
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.
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:
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)
Data included in Event notification Property of an access block for BACnet
monitoring
Remarks
NotificationClass NotificationClass
NotifyType NotifyType
ToState EventState
StatusFlags StatusFlags A StatusFlags is always included in an EventValues.
EventType Main object that uses
EventType
Information in EventValues
parameter
Property of an access block for BACnet
monitoring
EventType (change-of-state) BI, BV, MI, MV new-state binary-value PresentValue of BI/BV
unsigned-value PresentValue of MI/MV
EventType (command-failure) BO, MO CommandValue PresentValue of BO/MO
FeedbackValue FeedbackValue of BO/MO
EventType (out-of-range) AI, AO, AV exceeding-value PresentValue of AI/AO/AV
deadband Deadband of AI/AO/AV
exceeded-limit ToState is HighLimit: HighLimit of AI/AO/AV
ToState is LowLimit: LowLimit of AI/AO/AV

Table of Contents

Related product manuals