RE: {foxray} Foxray/System Auditor crash dumps/logs

[ricardoabech]

Hi Andrew,

If you want to Doble click the tag names, it will not work on the simplified GUI  (the one that starts the foxray with only the MADB GUI).

Try the main foxray instead if you want to access the tag data

 This should work better and  no error.

I will fix the error to do not allow double click or just show the block parameters on a list

Thanks 

Sent via the Samsung Galaxy S® 6, an AT&T 4G LTE smartphone

-------- Original message --------

From: Andrew Mackenzie <and...@andrewcraigmackenzie.com>

Date: 7/5/16 6:14 PM (GMT-05:00)

To: LimeWare foxray™ <limewar...@googlegroups.com>

Subject: {foxray} Foxray/System Auditor crash dumps/logs

Hi All,

Every now and then I experience crashes in Foxray/SA and I'm presented with a dialogue (see attached image).

What I'm wanting to know is do the reports get sent back to Limeware/Invensys automatically or are the reports stored somewhere so they can be manually submitted?

This particular crash occurred when attempting to edit the consequence.

Thanks,

Andrew

--
You received this message because you are subscribed to the Google Groups "LimeWare foxray™" group.
To unsubscribe from this group and stop receiving emails from it, send an email to limeware-foxr...@googlegroups.com.
To post to this group, send email to limewar...@googlegroups.com.
Visit this group at https://groups.google.com/group/limeware-foxray.
For more options, visit https://groups.google.com/d/optout.

[Andrew Mackenzie]

Hi Ricardo,

I'm not sure what you mean by the simplified GUI. In my case I have:

1. started foxray by running 'SystemAuditorlauncher.exe'
2. I can't remember if I launched MADB from the 'System Management' panel or via double clicking the 'Master Alarm Database' link on a block
3. setting the filter '(BLOCK LIKE 11BE1023%)'
   

I've had another, possibly related error when trying to set the response time. I've copied the log to the clipboard this time and attached the dump.

1. Added Impact to alarm
2. Set max response time to 10 minutes
3. Pressed 'Apply Changes'

Thanks again,

Andrew

[ricardoabech]

Can you try to run systemauditor.exe instead of the launcher and see if the problem also happens?

You have have a -madb argument on your launcher call shortcut. 

Sent via the Samsung Galaxy S® 6, an AT&T 4G LTE smartphone

-------- Original message --------

From: Andrew Mackenzie <and...@andrewcraigmackenzie.com>

Date: 7/5/16 6:59 PM (GMT-05:00)

To: LimeWare foxray™ <limewar...@googlegroups.com>

[Andrew Mackenzie]

Ok, I tried the following:

1) Launch Foxray via 'SystemAuditor.exe' (did not use a shortcut, executed directly from folder)

2) Open MADB via 'Master Alarm Database' link in 'System Management' panel

3) Click filter button on MADB 'BLOCK' column

4) Set filter to 'like 11LC10041'

5) Selected the filtered block (PIDA)

6) Selected 'Rationalization' tab

7) Selected HMA alarm

8) Selected 'Impact' tab

9) Set 'Max Response Time' to 10 minutes

10) Clicked 'Apply Changes'

Log attached

[ricardoabech]

Do you have impacts and severity especially configured on the impact tab?

[Andrew Mackenzie]

I have selected a single severity/impact from preconfigured severeties/impacts (configured through the MADB menu Configuration>Manage ...)

[ricardoabech]

Have you configured the priority matrix as well?

[Andrew Mackenzie]

This might be the issue

[Andrew Mackenzie]

Ok, I can confirm completing the priority matrix has resolved the error on the Impacts tab:

 

[Joe Riccardi]

Ricardo, 

I have dozens of Foxray sites I support and I have never heard of "impacts and severity".  Something new? What are we missing? No hurry on a response...

Joe

Sent from my iPhone

[ricardoabech]

Hi Joe,

This was always there. But it is only used when foxray is used for alarm management rationalization work.

It is under master alarm database option on the Right menu.

[Andrew Mackenzie]

Hi Ricardo,

I managed to replicate the original error I was getting:

1. Enter an impact
2. Double click the impact to invoke an edit
3. Press 'Apply'

The error does not seem to occur when using the 'Edit' button

The error also occurs on the other tabs (causes, consequences)

Log attached.

Thanks,

Andrew

On Wednesday, 6 July 2016 08:35:25 UTC+10, ricardoabech wrote:

[ricardoabech]

Thanks Andrew,

CUrrently working on redoing the MADB editor and this should fix the observed issues. The new madb will improve the user experience by allowing all edits in the same tab and also allow max response time in matrix priority to be a text instead of time range

It should be released this month. I will keep you posted.