WriteToFile Notification in StruxureWare Building Operation 1.0 and 1.1 only sends events to the text file, when no alarm entry is in the Alarmview. Alarm Cycle definition in resolution.
StruxureWare Building Operation 1.0 and 1.1
WriteToFile Notification in StruxureWare Building Operation 1.0 and 1.1 only sends events to the text file, when no alarm entry is in the Alarmview.
One creates an Alarm with priority 111 and define the acknowledgement to single additionally create a WriteToFile Notification that sends priority 111 events to a named text file.
When the first time trigger the alarm it will be written to the text file. Resetting the alarm is not send to the file.
When the alarm is triggered again, it will not be sent to the text file.
As long as the alarm is not acknowledged from the Alarmview no further entries will be sent to the text file.
This function as designed in in release 1.0 and in 1.1. The notification is sent once per alarm cycle. In release 1.2 we have changed the behavior to send notification according to whatever the user wants.
This is the design of the releases 1.0 and 1.1. Work-around is to select the alarm and on the User Action Tab, select NO for the Type of acknowledgement.
Note: The alarm cycle is, from that the alarm goes to Alarm state (from Normal state) until it goes back to Normal state(note not to Reset state).