The MK6 Event log accessible from the localhost in iternet explorer trigger each event twice.

All the logs are showing no errors and all the settings in the config.dat file are correct, but I have always the same beahvior, every record (event) is logged twice.

Has someone had the same experience before?

Thanks,
Giovanni

 

Giovanni, Is this something that just started happening recently, or has it been going on for a long time? Does this happen on all HMI's or only a particular HMI? Most events and alarms will always have 2 occurrences. The first occurrence is when the event or alarm goes "true" or to a 1 state. Then when the alarm or event goes "false" or to a 0 state you will see it again. Possibly including a screen shot of the alarm/event log will help to diagnose this issue.

 

Mike, this issue just started happening recently andis only on one of the 4 HMIs I have here. You're right for the alarm logging but in this case is different. Here attached an extract of the event log to better understand which is my problem, you can see each event has two row exactly the same (timestamp, status, etc).

07-OCT-2008 22:54:46.778 G4 0 Q 0251 ALM Fire fight.& gas monit.systems fault alarm - stck
07-OCT-2008 22:54:46.778 G4 0 Q 0251 ALM Fire fight.& gas monit.systems fault alarm - stck
07-OCT-2008 22:55:18.178 G4 1 Q 0080 ALM Accessory Encl. doors open Alarm
07-OCT-2008 22:55:18.178 G4 1 Q 0080 ALM Accessory Encl. doors open Alarm
07-OCT-2008 22:55:19.818 G4 1 Q 0162 ALM ENCLOS.(ACCESS.COMP.) PRESS.LOW ALARM
07-OCT-2008 22:55:19.818 G4 1 Q 0162 ALM ENCLOS.(ACCESS.COMP.) PRESS.LOW ALARM
07-OCT-2008 22:55:26.698 G4 0 Q 0162 ALM ENCLOS.(ACCESS.COMP.) PRESS.LOW ALARM
07-OCT-2008 22:55:26.698 G4 0 Q 0162 ALM ENCLOS.(ACCESS.COMP.) PRESS.LOW ALARM
07-OCT-2008 22:55:28.098 G4 0 Q 0080 ALM Accessory Encl. doors open Alarm
07-OCT-2008 22:55:28.098 G4 0 Q 0080 ALM Accessory Encl. doors open Alarm
07-OCT-2008 23:00:16.901 G4 0 Q 0078 ALM Fire fighting CO2 discharge valves closed alarm
07-OCT-2008 23:00:16.901 G4 0 Q 0078 ALM Fire fighting CO2 discharge valves closed alarm
07-OCT-2008 23:03:01.581 G4 0 Q 0093 ALM BN Rack II Cumulative Alarm slots 2 to 11
07-OCT-2008 23:03:01.581 G4 0 Q 0093 ALM BN Rack II Cumulative Alarm slots 2 to 11
07-OCT-2008 23:03:51.141 G4 0 Q 0402 ALM HS shaft NDE BRG very high vibration TRIP
07-OCT-2008 23:03:51.141 G4 0 Q 0402 ALM HS shaft NDE BRG very high vibration TRIP
07-OCT-2008 23:04:16.340 G4 0 Q 0128 ALM LUBE OIL COOLER DAMPERS IN MANUAL CTRL ALARM
07-OCT-2008 23:04:16.340 G4 0 Q 0128 ALM LUBE OIL COOLER DAMPERS IN MANUAL CTRL ALARM

Thanks

 

Giovanni, I can't say that I have seen this before on any of our machines. Have you done any modifications to this or other workstations that may have coincided with this starting? Have you tried rebooting this machine? Have there been any changes to the network that coincide with this starting? Most of these are just ideas jumping into my head. Have you looked at the alarm.dat and event.dat files and compared them to another HMI? I will keep thinking, and possibly some more info from you, or the thoughts from CSA or another will get you somewhere.

 

Mike,

I tried already everything you mentioned but with no result. I cannot understand what is causing this issue.

Thanks anyway for your help.