PCO 2.2 - OPC and IP21

[Private_Member_17892]

Hi,

We are looking at connecting to IP21 via PCO OPC DA connector.

Can PCo only poll the IP21 OPC server for eventing or can one set up the IP21 OPC server to advise PCO on data changes for

eventing purposes ?

Also what is required on the server where PCo is installed to enable OPC connectivity, for browsing the IP21 we have established that you need the following dlls in the PCo system directory :

cimsrvapi.dll

CimWin32Util.dll

infoplus21_api.dll

ip21admin_client.dll

ip21ezrpcw32.dll

ip21winrpc32.dll

libc21.dll

PCo is running on Windows server 2008 R2 and the IP21 is not on the same box.

thanks

[former_member192939]

Hi Morne

Please follow the installation guide.

Install the OPC core components redistributable, if it doesnt come with the OPC Server installation on the ip21 machine.

For the dlls, during the installation process of PCo your selection should provide with all the necessary ddl's.

I dont think you can setup something on IP21 to advice PCo.

Regards

Ajay

[Private_Member_17892]

Thanks AJ,

We are facing another issue. Using the standard IP21 connector in PCo we can configure the required aliases and tags to view.

But if we use the OPC DA connector the tags itself appears as a folder (name space) and selecting it to add it then does not work when adding the tag item / name space to the alias in the source system confifuration (instead of showing as a tag it shows as a folder)

Then when setting up the subscription items in the agent and browsing the address root all tags are still namespaces (folders) ?

Thus we cannot link any tags.

a. Is there documentation that might explain how this work

b. Is there a setting that we are missing somewhere ?

We tested with a Matricon simulator and OPC server and we could get this to work , but IP21 OPC connections seems to be an issue.

Any ideas ?

[former_member192939]

I donot have access to PCo now ..

Try playing with "Force Flat Namespace" check mark and manually enter the tag (main.machine.machine1)

Regards

Ajay.

[Private_Member_17892]

Hi,

We tried it but no luck.

Is there something that needs to beconfigured on the IP21 tag it self maybe to expose it self maybe ?

[Private_Member_17892]

Hi ,

I got it working to be able to get the notification working. Although one still cannot browse the IP21 tags, and all tags are still shown as a name space.

a. I installed the Matricon IP21 OPC server on the same box as IP21 Historian.

b. I connected to the IP21 server and configured new aliases in the Matricon IP21 OPC server to look at the IP21 tags

c. I then configured PCo OPC DA agent to look at the Matricon IP21 OPC server and got the subscriptions to work, and PCo can browse the MAtricon IP21 OPC server tags that I configured , so the browsing seems to work via this OPC server

d. Then I tried to fire up the OPC DA agent in PCo that I previously configured to look at the Aspentech IP21 OPC server, and the configuration now started to work (still can't browse the tags)

e. I uninstalled the Matricon IP21 OPC server and the configuration in step d. still worked.

So the conclusion is that the Matricon IP21 OPC server did some sort of a configuration that made the orginal configuration functional, this however now leaves me the question of what did this driver do to get things working.

Now I sit with a new challenge I have PCo installed on a seperate server and in a different domain as the IP21 OPC server.

What I have so far

1. The Same local user on both the PCo box and the IP21 OPC server with Admin rights

2. I can see the IP21 OPC server from the PCo box and access it

But the issue is as soon as I fire up the Agent to run it fails to start with the following error:

ConnectivityAgentProxy|"The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly.

Below is the PCo Log file:

Date Time| Machine| Thread ID| Process ID| Process Name| Event Type| Source| Message| Stack Trace

2012/02/24 04:12:01 PM|.|8|7888|IP21_OPC_DA|Information|AgentBase|Start ignored. Agent state = Faulted|""

2012/02/24 04:12:01 PM|.|6|7888|IP21_OPC_DA|Information|Host|WCF service is started.|""

2012/02/24 04:12:01 PM|.|6|7888|IP21_OPC_DA|Error|Host|failed to create ConnectivityAgentProxy|"The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly. Server stack trace: at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc) at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs) at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation) at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message) Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at SAP.Manufacturing.Connectivity.IPCoAgentControl.Start() at SAP.Manufacturing.Connectivity.ConnectivityAgentProxy.Start() at SAP.Manufacturing.Connectivity.WcfHost.Start()"

2012/02/24 04:12:01 PM|.|8|7888|IP21_OPC_DA|Error|ServiceFaultManager|Manufacturing Fault: REASON = The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly. ; SEVERITY = Fatal|""

2012/02/24 04:12:01 PM|.|8|7888|IP21_OPC_DA|Verbose|AgentBase|beginning PublishSubscribe CommunicationMode initialization...|""

2012/02/24 04:12:00 PM|.|8|7888|IP21_OPC_DA|Verbose|AgentBase|starting...|""

2012/02/24 04:12:00 PM|.|6|7888|IP21_OPC_DA|Information|Host|implicitly calling start on the hosted IConnectivityAgent service contract|""

2012/02/24 04:11:59 PM|.|6|7888|IP21_OPC_DA|Information|Host|using default NetTcpBinding endpoint for internal IConnectivityAgent proxy|""

2012/02/24 04:11:59 PM|.|6|7888|IP21_OPC_DA|Verbose|Host|Service endpoints:|""

2012/02/24 04:11:59 PM|.|6|7888|IP21_OPC_DA|Verbose|Host|SAP.Manufacturing.Connectivity.Agents.Opc.Da.OpcDaAgent is running with the following endpoints:|""

2012/02/24 04:11:58 PM|.|6|7888|IP21_OPC_DA|Information|Host|WCF service is starting.|""

2012/02/24 04:11:58 PM|.|1|7888|IP21_OPC_DA|Verbose|OpcDaAgent|Creating the OPC DA agent.|""

2012/02/24 04:11:58 PM|.|1|7888|IP21_OPC_DA|Verbose|BrowserSessionManager|Created browse manager.|""

2012/02/24 04:11:58 PM|.|1|7888|IP21_OPC_DA|Verbose|OpcDaAgent|Creating the OPC DA agent.|""

2012/02/24 04:11:58 PM|.|1|7888|IP21_OPC_DA|Verbose|BrowserSessionManager|Created browse manager.|""

2012/02/24 04:11:58 PM|.|1|7888|IP21_OPC_DA|Verbose|Host|Running [IP21_OPC_DA] as a windows service...|""