I am occasionally getting an alarm message that is getting stuck on the display (in hide view). I have changed the hide view to include a miniture version of the window in the DM1 display view. It shows all the same data (message number, total messages, spn, plug, text, etc.). When it gets stuck, it is green (no longer active) and the header shows message 1 of 0, and it dispalys all of the correct text, SPN, etc. (Dm1.ListPointer = 1 and DM1.TotalFaultsInList=0)

The problem is that when this happens, it is stuck this way until another valid alarm is generated or power is cycled. When I try to recall to the active DM1 view, nothing happens. I believe this is because the Dm1.TotalFaultsInList is 0.

I think this is a timing issue. I notice it happens when a new alarm becomes active when I am acknowledging several alarms in the system, all of which are green and are no longer active. It appears that the application is already in the process of acknowledging and clearing the previously active alarm, when a new one becomes active and clears. This goes alaong with the random alarm issue, as those are the ones that I am clearing out.

The display does not go to the DM1 main faults view when the recall button is pressed, because the DM1-DM1GoToFirst action causes a variable write failure and DM1.VariablesWriteFail Transitions back to the initial state in the DM1 state machine.

I am going to move the transition DM1.VariablesWriteFail to be in parallel with DM1.VariablesWriteOk to force the transition back to the main faults view, since it can only be called from the recall view.