Configuring The FSGateway To Act As An OPC Server in The Control Software System
Configuring The FSGateway To Act As An OPC Server in The Control Software System
Response
1- Go to the System Management Console “SMC”, then DAServer Manager, then ArchestrA.FSGateway.3.
2- Expand ArchestrA.FSGateway.
3- From the Device tab, you can create, modify, delete, export and import aliases into actual data source items so
it can be used directly in the OPC client.
Below an example:
Name: This column defines the alias names to actual data source items.
Item Reference: The actual data source item names defined in this column.
Use the format like the below example in the Item Reference.
VMGR01_IADI.COMPND_001.AIN_001.PNT
VMGR01_IADI is the IA Series Integrator that provides connectivity to Control Core Services.
The I/A Series Device Integration Object is installed and deployed on all Foxboro Evo Control workstations as
part of the Control Software’s installation. The object is instantiated as an ArchestrA application object and
assigned to an application engine. The Device Integration Object is not assigned to an area. The installation
program names the object and the host application engine by Appending _IADI and _AppE respectively, to the
workstation name (letterbug).
I have tried in the lab the Matrikon Explorer OPC client as below.
Open the Matrikon Explorer then add new group “G1” (this name can be changed), then add items to that group.
In the Available Items in server “ArchestrA.FSGateway.3” tab click on the New_ArchestrA_000, then all the
aliases tags that created in the device tab will appear directly in the available tags Tab, like below.
Open the Matrikon Explorer, add new group “G2” (this name can be changed) then add items to that group.
New_ArchestrA_000.VMGR01_IADI.COMPND_001.AIN_001.PNT
VMGR01_IADI is the IA Series Integrator that provides connectivity to Control Core Services.