This example demonstrates how to display internally generated fault messages using the standard DM1 pop-up messaging system and System Events and Variables.
To start with the DM1 pop-up messaging system is exported from the standard PV780 template config then imported into this example configuration. Instructions are in the notes of the configuration.
NOTE: When exporting then importing Configuration Components any actions associated with a SYSTEM EVENT or a System Variables "Fire on Change" will not be passed on and must be recreated manually. It is always a good idea to browse through any system events and variables that may be associated with the task at hand to capture any actions that may need to be recreated manually as is in the case of the DM1 pop-up messaging.
This example makes use of the DM1 Application which will store the internally generated message in the DM1List using the DM1.InternalSPN, DM1.InternalFMI variables among others to contain the fault message data and the action DM1SetIntrenalFault to move the data into the List and signal an active fault is present. Please make note of a limitation in that only one internal DM1 message can be stored in the list. If more than one internal fault is active at a time the first one is the only one that can be displayed.
For the internal DM1 messaging example a variable is monitored by a Activity Program to see if minimum or maximum limits are exceeded. If they are then the appropriate Internal DM1 variables are set and Events fired. See the notes in the configuration for a step by step description of what is needed to to generate internal DM1 messages.
This configuration was created in 2.9.23044 for a PV780.
In this version the fault must be active for 5 seconds before the DM1 fault will activate. This is accomplished by adding a second activity program to set a flag after the fault has been active for more than 5 seconds.