800xA -Alarm management system interface
How can we do the 800Xa 5.1 interface with Alarma management system through OPC server when there is two 800xa domain talking to AMS system by using same domain user name(800xAService).what DCOM setting needds to be follwed?Can we provide OPC SURROGATE id to AMS system to fetch alarms from our system or can third party system fetch alarm by entering our prog ID?
Voted best answer
Alarm and events are delivered via OPC AE - no surrogate service provided by System 800xA. Client need to run locally on the server to be able to browse & connect to the OPC AE server of 800xA. Some tricks can be done with Windows registry to allow remote launch of an OPC AE client but this is not a documented feature of System 800xA.
The 800xA Alarm Logger service can be used to print alarm and events to a paper based printer. Some use 3rd party software to emulate printers, this may work but is not the intended purpose of the Alarm Logger feature (which was made to print on paper only).
Alarm Analysis (KPI) is a licensed option in System 800xA. The KPIs are delivered over OPC DA and is array based (not all OPC clients are capable of handling arrays). Two separate connections from AMS to 800xA is required, one per system.
The OPC surrogate is a suitable accesspoint, a requirement for DCOM connection if client is running on a separate computer. The System 800xA Configuration User's Guide, 3BDS011222-510 gives help.
To avoid messing with DCOM settings, an OPC tunneller can be used.
Remember that asynchronous OPC data transfer over DCOM (i.e. without tunneller) requires DCOM adjustments on both server and client side. I have attached a document detailing what settings that are required.