5 Replies Latest reply on Jul 23, 2014 1:33 PM by Gregor

    Problems with OPCtoPI Interface

    marco.zoccoli

      Hi all,

       

      we have an OPCtoPI interface which has to read data from an Opc Server through Matrikon. If we enter OPC Client and Matrikon explorer we can read data, but the interface seems not to work (Device Status is in "Inf Shutdown"), so data cannot be read by the interface.

       

      Could you please suggest any test we can do (like connection tests with OPC Server and Matrikon)? Have you got any idea about the cause of the issue?

       

      Thank you,

       

      Marco

        • Re: Problems with OPCtoPI Interface

          Hello Marco,

           

          Are you connecting the PI OPC Interface against your personal development PI System included with your vCampus subscription?

            • Re: Problems with OPCtoPI Interface
              marco.zoccoli

              Hi Gregor,

               

              my account is an Accenture subscription, while the OPC Interface is on PI which belongs to Enel Green Power (our client).

               

              Best Regards,

               

              Marco

                • Re: Problems with OPCtoPI Interface

                  Hello Marco,

                   

                  You can try if the interface is able to get data when running it in interactive mode. PI ICU supports launching an interface interactively. Alternatively, you can call the interface instances batch file in a command prompt.Please make sure the corresponding interface service is in "Stopped" status when running the instance interactively.

                   

                  If the interface works in interactive mode, the issue is likely with the identity the service is set up with.

                   

                  The best way to deal with interface issues, is contacting OSIsoft Technical Support for assistance. Please let us know if you want us to get a ticket for you.

                    • Re: Problems with OPCtoPI Interface
                      marco.zoccoli

                      Hi Gregor,

                       

                      thanks for your feedback, seems that there is an issue on Matrikon side.

                       

                      Regards,

                       

                      Marco

                        • Re: Problems with OPCtoPI Interface

                          Hello Marco,

                           

                          OPC communication is based on DCOM and setting up DCOM properly can be painful. On the other hand, DCOM is very powerful because it e.g. allows starting processes remotely and hence the granularity to set up DCOM configuration can be annoying. PI OPC Interface manual has a step by step guide about how to set up DCOM server and client side with a configuration that "works".

                           

                          There exist "mechanism" to get around DCOM e.g. by using a so called "Tunneler" which is a piece of software allowing to skip "annoying" DCOM configuration.

                           

                          Another approach that works pretty well is setting up a service account as local account on the server and the client node. Both accounts use the same name and password (I suggest choosing a super strong password). The OPC Server and the PI OPC Interface instance need to be configured to run with this service account. This should work with a single domain account too if both machines are member of the same domain. Please note that running PI OPC Interface with a service account may break the communication between interface, buffering and the receiving PI Server but PI Message logs should clearly identify issues.