During CitectSCADA installation:
In-Process OPC Server
|
In-Proc OPC Server
|
||
|---|---|---|
|
Application ID (AppID) |
Citect.OPC |
|
|
Class ID (CLSID) |
{BA198B61-32E3-11d1-A1B5-00805F35623C} |
|
|
Binary file |
CtOpc32.dll |
|
|
Interfaces |
DA 1.0 Custom Interface: |
|
|
OPCServer: |
IOPCServer IOPCBrowseServerAddressSpace (optional) |
|
|
OPCGroup: |
IOPCItemMgt IOPCGroupStateMgt IOPCSynchIO IOPCASynchIO IDataObject |
|
|
DA 2.0 Custom Interface: |
||
|
OPCServer: |
IConnectionPointContainer IOPCItemProperties |
|
|
OPCGroup: |
IOPCAsyncIO2 IConnectionPointContainer |
|
|
System Requirements |
2000, XP and Windows Server 2003 |
|
|
Server Organization |
Flat (OPC_NS_FLAT) |
|
|
Implemented Categories |
OPC DA Servers v1.0 |
{63D5F430-CFE4-11D1-B2C8-0060083BA1FB} |
|
OPC DA Servers v2.0 |
{63D5F432-CFE4-11D1-B2C8-0060083BA1FB} |
|
Local/Remote OPC Server
|
Local / Remote OPC Server
|
||
|---|---|---|
|
Application ID (AppID) |
Citect.OPCRemote |
|
|
Class ID (CLSID) |
{ BA198B62-32E3-11d1-A1B5-00805F35623C} |
|
|
Binary file |
CtOpc32.exe |
|
|
Interfaces |
DA 1.0 Custom Interface: |
|
|
OPCServer: |
IOPCServer IOPCBrowseServerAddressSpace (optional) |
|
|
OPCGroup: |
IOPCItemMgt IOPCGroupStateMgt IOPCSynchIO IOPCASynchIO IDataObject |
|
|
DA 2.0 Custom Interface: |
||
|
OPCServer: |
IOPCCommon IConnectionPointContainer IOPCItemProperties |
|
|
OPCGroup: |
IOPCAsyncIO2 IConnectionPointContainer |
|
|
System Requirements |
2000, XP and Windows Server 2003 |
|
|
Server Organization |
Flat (OPC_NS_FLAT) |
|
Note: In the OPC architecture, each variety of server is allocated a unique identifier, known as a Class ID. OPC Clients use these 128-bit numbers, frequently displayed in the form 6B29FC40-CA47-1067-B31D-00DD010662DA, to access the particular vendor's OPC Server. To make it easier for users, these numbers are often referred to by a more manageable string identifier called a ProgID (Program Identifier). These identifiers usually take the form Vendor.Application with an optional version number appended; for example, the CitectSCADA OPC Server ProgID is Citect.OPC.
Once successfully installed, the CitectSCADA OPC Server is ready for use. The OPC interface that OPC Clients access starts automatically when you start the CitectSCADA runtime environment. Further configuration is only necessary where the CitectSCADA OPC Server will be accessed by a remote OPC Client. See Configuring Remote Access to the CitectSCADA OPC Server for more information.