OPC AE and DA Name issue
I am having some problems while integrating a third party OPC server into 800xA. I have uploaded OPC DA and it creates a structure in the control structure, which is identical to the one in the OPC Server, this is good.
I can also succesfully upload OPC AE from the service structure, however I am unable to 'link' the OPC AE alarms to OPC DA. The AE alarms cannot find an object, and creates a new object under lost and found when the alarm is activated, is there some setting i am missing? or anyway to fix this? I dont want to make a source translator extension to 800xA.
Voted best answer
I agree with Rob, for 800xA to properly attach an alarm to an object one unique match "OPC AE SourceName" vs 800xA object name must be made.
Apart from trying a match with regular object name, the Controller Name is also attempted.
This is e.g. utilized by 800xA for Advant Master where the MB300 Uploader creates Controller Name aspects and populates them with the source name used by the OPC AE server "objectname(net decade:node number)", e.g. 51-AIC104(2:51).
If there aren't too many objects you should be able to create & populate the Controller Name aspects manually.
Another option would be to obtain the System 800xA SDK (Software Development Kit) and implement a custom Source Tracking plugin for the Event Collector service. This requires extensive knowledge about 800xA - and I'm afraid that no official support/user's guides exist. There might be an option to let R&D implement it through the "customer funded development" program. Please speak to your regional ABB sales representative for a quotation.
A last alternative could be to customize the interceptor (by clicking on the New+Edit buttons just to the right of the arrow above) and change the Default Root Node from [Control Structure]Root/Lost and Found to something more appropriate for you.
800xA for Advant Master's object interceptor settings:
Names are "linked" using the "Object Name" field of the AE message using a very simple object search.
When the alarm message is received, the alarm handler searches the entire system for an object with the same name as the "name" field in the alarm message. The Object must exist and it must be unique. Duplicate object names break the search.
Check the "Name" field in your alarm message and use the "Search" tool to check if you find 0,1 or more objects for that name. If one of the duplicate objects is in the Lost+found then just delete that object and try again. Do NOT delete the lost+found Root object ( Actually its probably OK, but this used to cause problems in some older 800xA versions)
I have attached a picture of how the AE alarm objects appear, they have the full path from the opc server as name, see picture 1.
The DA structure is a hierarchy(picture 2), what I need is the AE alarm to have just the last bit as the object/source name eg. 'Ind1' so it would be found in the control structure. But i dont know if this is possible to do without some sort of translator.
You have duplicate names ....
The Alarms are coming up for "Ind1", "Ind2", "Ind3" etc. The AE service expects the "Name" field of the AE message to be the parent of those objects ie "INDGGIO1". Only the parent name is unique.
If you have access to the PLC program then this should be a simple problem to fix.
What text appears in the AE message for the object name. Use a third party OPC AE Client to read this.
Thanks alot for your answers, the controller name aspect solutions works pretty good, only issue is that after an upload i would need to use bulk data manager and change the controller names, or perhaps i can make a change in the uploader somehow.
We are looking into developing a source translator with service/R&D, but we need to check for other alternatives first.
I have already modified the interceptor settings, so it will populate where i want it to, when i have modified the controller name aspects in the control structure objects created by OPC DA Uploader to the same as the AE source name, it works.