Why use OPC XML-DA?
OPC XML-DA provides the foundation for multi-platform interoperability because it is based on XML instead of the Windows specific DCOM. It simplifies sharing and exchange of data amongst the various levels of the plant hierarchy (low level devices and up to enterprise systems), and to a wider range of platforms. Unlike previous OPC data access specifications, the OPC XML-DA specification describes data exchange in an environment which assumes no persistent connection between the client and the server. This makes it suitable for a much wider range of communication systems and, since XML is text based it passes firewalls. The XML-DA Bridge combines the Server Side gateway with the XDAGW-CS Client Side Gateways to allow OPC-DA clients access to remote OPC-DA servers. Running on .NET 3 (WCF) the communication can be configured for: – ASP.NET2 web service compatibility – high performance TCP or named Pipe transport – secure data transfer using X.509 certificates or other mechanisms The XML-
Related Questions
- In MiMiC v2.8, OPC parameters can be simulated using the /OPC designation in the Tag name. Can the user simulate OPC parameters in MiMiC v3 and do they consume SIO tags?
- In the past, there were conversion issues with using from simulations developed for the VIM to the DeltaV Simulate OPC drivers. Has this been addressed in MiMiC v3?
- What problems can be solved with Advanced OPC Data Logger?
