180 likes | 302 Views
Express Interface. Migration from Classic OPC to OPC Xi with Advosol Components and Tools. About Advosol Advosol Inc. specializes in OPC .NET components since 2002 and offers the most complete set of high quality OPC .NET components for software developers and system integrators.
E N D
Express Interface Migration fromClassic OPC to OPC Xi with Advosol Components and Tools
About AdvosolAdvosol Inc. specializes in OPC .NET components since 2002 and offers the most complete set of high quality OPC .NET components for software developers and system integrators. About OPCSupporting thousands of products users we saw that most difficulties with OPC were actually issues with the underlying DCOM communication. The OPC XML DA specification and Tunneller products address this issue but don’t offer a general solution.The OPC UA specification focuses on multi-platform and comprehensive data modeling features and introduces new complexities. About XiIn spring of 2009 Advosol joined a group of companies in an effort to specify a simple .NET based communication interface with the functionality of OCP DA, AE and HDA. In September 2009 an implementation of the ExpressInterface specification was demonstrated at the Emerson Exchange Show.In November 2009 the OPC Foundation decided to adopt the ExpressInterface specification as an OPC standard.The Xi specification and a base Xi server implementation layer remains publicly available.
Migration to XiDesigning products for the new OPC Xi specification Advosol recognized the fact that there are thousands of classic OPC application in use and Xi will have to co-exist with these applications.Converter Software Modulesare one way to achieve interoperability between Xi and classic OPC applications.Existing applications don’t have to be modified. However, there is an additional module to install and maintain and DCOM communication is not eliminated.Dual-Mode Componentssupport Xi and classic OPC within the application process. New applications can support Xi and classic OPC without additional development effort. DCOM is completely eliminated in the Xi communication.Advosol offers several Xi converters and dual-mode component products.
Classic OPC Using components with a .NET wrapper, client and server applications can be developed as .NET applications. The Advosol OPCDA.NET client component provides .NET classes for OPC DA server access. OPC DA Client Application DCOM The Advosol DANSrv toolkit has a generic server that handles the DCOM client interface and a .NET plug-in assembly for the application specific server functionality. OPC DA Server
Classic OPC and OPC Xi The development of classic OPC and Xi applications is very similar. The components provide an easy to use abstract interface with .NET classes. The Advosol PaXi client component provides .NET classes for OPC Xi server access.All Xi specified features are supported. OPC DA Client Application OPC Xi Client Application WCF DCOM The Advosol XiPLUS Xi server toolkit has a generic server that handles the WCF client interface and uses the same application plug-in assembly as the DANSrv OPC DA server toolkit. OPC DA Server OPC Xi Server
Classic OPC and OPC Xi inter-operation through converters OPC DA Client Application OPC Xi Client Application DCOM WCF The Advosol XiTOCO Xi Server acts as an OPC Xi-DA Converter. The Advosol OXS Exchange Server can act as an OPC DA-Xi Converter. WCF DCOM OPC Xi-DAConverter OPC DA-XiConverter WCF DCOM OPC DA Server OPC Xi Server
XiTOCO Xi Converter to Classic OPC Xi Server that converts to/from OPC DA, AE, HDA Configurationof the Xi server WCF communicationThe configuration utility is provided with the XiTOCO converter server.
XiTOCO Child Server Configuration The child server configuration defines the OPC server ID and optionally how it’s accessed.The Name defines how the server is identified in the Xi InstanceID.To minimize DCOM issues the converter should be installed on the same machine as the OPC server. If the converter handles multiple server then this is not always possible and Host details are required.
XiTOCO Xi Server Mode Settings • Run Modes: • Process • Windows Service • IIS Hosted • Trace Log: • Console • Event Log • File • Trace Level: • All • Error • Warning • Off
Classic OPC and OPC Xiinter-operation through converters OPC DA Client Application OPC Xi Client Application DCOM WCF The Advosol XiTOCO Xi Server acts as an OPC Xi-DA Converter. The Advosol OXS Exchange Server can act as an OPC DA-Xi Converter. WCF DCOM OPC Xi-DAConverter OPC DA-XiConverter WCF DCOM OPC DA Server OPC Xi Server
OXS Exchange Server Configuration The OXS Exchange Server acts as an DA to Xi Converter when it runs as an OPC DA server and is configured for one ore multiple OPC Xi child servers. The configuration defines the item structure in the OXS server and how they Xi server objects are mapped to the OPC DA server items.
OXS Child Server Configuration The OXS child server configuration defines the Xi server access details.Depending on the Xi server configuration the Xi server access can be secure with password or certificate authentication.
WCF Communication Preferences The OXS child server configuration can define the Xi server communication in more detail by specifying the preferred Xi server endpoints or binding schemes.
DA/Xi Client Component This dual-mode component gives the client application access to OPC DA and Xi servers through the same API.The widely used OPCDA.NET client component for .NET OPC DA applications can beextended with the DANW-Xi option for Xi server access. Existing OPCDA.NET based client applications can be upgraded with Xi support without having to be modified.New applications can be developed to support OPC DA and Xi server access without external converters. .NET Client Application The DA-Xi converter is part of the client process.DCOM is completely eliminated in Xi server access. OPCDA.NET DANW-Xi DCOM WCF OPC DA Server OPC Xi Server
OPCDA.NETComponent for .NET OPC DA Clients • Layered set of classes for handling OPC DA servers • .NET wrapper works in 32-bit and 64-bit mode • Project creation wizards and many samples • OPCDA.NET V7.1 has hooks for the Xi option DANW-Xi Option • The DANW-Xi option supports access to OPC Xi servers without need for an external converter • DCOM eliminated for Xi server access DANW-Xi Option Xi Server
XiPLUS Server Toolkit OPC Xi Client • The generic XiPLUS server handles the Xi client WCF interface • The abstract application interface simplifies the server implementation • The user can implement only DA or combinations of DA, AE, HDA functionality. • The generic XiPLUS server works: • In 32-bit or 64-bit mode • As a process • As a Windows Service • IIS hosted • The plug-in DLLs can also be used with the Advosol DANSrv/HDANSrv classic OPC server toolkits. WCF XiPLUSGeneric OPC Xi Server Application specificPlug-in DLLfor DA / AE features Application specificPlug-in DLLfor HDA features Devices Database
Server Toolkits for Xi and OPC DA / A&E OPC Xi Client • The application specific server features are in the plug-in .NET assembly. • The same plug-in DLL can be used with the OPC DA and the OPC Xi server. OPC DA/AE Client WCF DCOM XiPLUSGeneric OPC Xi Server DANSrv / DANSrvAEGeneric OPC DA/AE Server Application specificPlug-in DLL Application specificPlug-in DLL
Server Toolkits for Xi and OPC HDA OPC Xi Client • The application specific server features are in the plug-in .NET assembly. • The same plug-in DLL can be used with the OPC DA and the OPC Xi server. • The XiPLUS server can simultaneously use the HDA plug-in and the DA/AE plug-in. OPC HDA Client WCF DCOM XiPLUSGeneric OPC Xi Server HDANSrvGeneric OPC HDA Server Application specificPlug-in DLL Application specificPlug-in DLL