800xA FOR MOD300 IM Events Archive
I have an 800xA system at version 5.1 rev.A
with 4 pairs of Connectivity nodes with 800xA for MOD300 software
Due to the problem explained in the following bulletin (3BUA003379 Rev. D)
we have Controllers with AC460 CPU with normal time whilst the client/server
machines are 1 hour ahead..
We do not update di controller software till know anc just adjusted the controller clock
with bugs . We recently discovered that with this offset between cpu clock
and windows machines clock the IM software fails to "archive" alarms
whilst events are archived correctly.
I wonder what does this depends on and if anyone observede this strange
behaviour. I would to know if there is something to do as a momentary remedial
to correct this situation.
The bulletin 3BUA003379 Rev. D did not report any problem regarding
the IM History software.
I would really appreciate an info from the "IM History software Guru"
Geoff Ledin .. :)
Any suggestion will be appreciated.
I am assuming that when you refer to IM "Archiving", that you are actually talking about recording the A/E messages in the IMMSGLOG, and not doing an actual IM Archive function. Based on this, for the IM to work correctly in recording A/E Messages, the Timestamps for the messages MUST be within a very small time frame of the actual time. With the AC460 Controller being one hour before the time of the IM node, as I believe you have stated, the messages will NOT be recorded. You should use the previously mentioned Bulletin and set the clocks of the Controllers to match the Server nodes. It is assumed that for your system that this resulted from a Day-Light Savings time change. If this information does not resolve your issue, please open a Support Case with your local ABB Service group and this will be forwarded to the appropriate person if it cannot be resolved locally.
Also as a FYI, I was not directly involved but my colleague had an issue where double alarms were coming in through the Connectivity server pairs. More than likely the offset of time between CSs, could not distinguish the same alarm and it appearred twice in the alarm list (with slightly different times)