Multiple Process Alarm Logging

[andrew_t]

I have a system consisting of two separate server processes, both of which generate alarms that must be logged (so they can be printed out at a later date).  However, only one of the process actually logs alarms.  When I request that alarms be printed, I receive printouts of all 'Process 1' Alarms, but none for 'Process 2'.

Any thoughts?  Is there a global process setting that has somehow been disabled?

Thanks,

Andrew

[Prashanth]

Hi Andrew,

I would check to see you filter option settings while printing by going into File->Print->Alarms & Events... and this brings up a pop-up window and in the lower left hand corner there is a 'Filter Options...' button. Hope this helps!

Regards,
Prashanth 

[andrew_t]

Hi there,

I have no filter activated within the settings.  Is there anything else that would restrain this?  As I mentioned, all the alarms appear within the alarms window.

[Prashanth]

Hi Andrew,

There seems to be some thing basic thats missing here. It seems like a setting in Lookout development environment that seems to cause this behavior. However, there is no specific setting in Lookout that I can think off that is designed to accomplish a behavior like that you are seeing. [execpt for the filter options]

Here are things that I would try to isolate the issue.

• Check to see if you have both your processes under 'Selected Processes' section in Alarms->Select Processes...
• Do you have any _ (underscore) in your process names? If you do, remove the _ and see if the issue persists
• Log alarms from both processes - Does this change the behavior ?
• Close both of your processes that you have developed. Create 2 new processes - add a Pot object to processes and configure an alarm condition to trigger if value goes over a cirtain limit on both the pots. Now try to replicate the issue with these new processes.
• See if your processes behaves the same way on a different copy of Lookout (on another machine). This will tell us if the issue follows the process or the development environment settings

Regards,
Prashanth

[andrew_t]

Thanks Prashanth,

Turned out the problem was due to an underscore within my process name.  Everything cleared up once this was removed.

Regards,

Andrew