Imapct if I delete obsolete propagation aspect via repair function of consistency checker tool?
we use System 800xa 5.1 FP4 with connection to Advant controller.
I have run the consistency check and I come across a lot of errors that can be fixed automatically. I took one element to see how the automatically solution works. The following picture shows the error.
If the system performs the repair, the following screen appears.
My question is, what was executed here by the system, and may have further consequences (for example, for the alarm and operation, display, usability, and so on).
I have made the changes on a virtual system. Can I make them on a process system without generating errors?
Thanks in advance to all.
Repair may be a delicate matter (typically "success" or "not working/problem returns" but it could also rarely make a problem go worse). Ergo: don't apply repair in large scale until you have proven the repair to succeed (like in this case).
Please consider using the stand-alone Consistency Checker app (can be launched by a button to the far right of the application bar of Plant Explorer) which is more modern (but the basics and repair feature should be the same).
Controller Name aspects are created and populated by Upload (800xA for Advant Master) or engineering tools (e.g Control Builder M) and used by the Event Collector service's interceptors to match incoming A&E with objects you have uploaded/created.
In 800xA for Advant Master, the Controller Name consists of Object Name + a suffix (MB300 net decade:node number), e.g. the object AIC71_1 typically has Controller Name AIC71_1 (1:71) if the MB300 network number is 11 thru 19 and controller node number is 71.
Only objects in the Control Structure need Controller Name aspects. Having obsolete or erroneous Controller Name aspects where they should not be may cause alarms to be attached to incorrect objects.
Please see the attached document I use when teaching the E143 Troubleshooting System 800xA Expert Workshop.