The OPC UA Server API that I mentioned is a LabVIEW API which used to come as part of the DSC module but as of 2017 is a standalone toolkit (OPC UA Toolkit). OPC-DA (Data Access) – Provides access to real-time data. So like I mentioned in the LAVA post, the NI OPC Server standalone application will not accept non-NI DA or UA clients.This data is typically stored in files, databases, or remote telemetry systems. OPC-HDA (Historical Data Access) – This is used to retrieve historical process data for analysis.OPC AE ( Alarms and Events) – OPC AE servers are used to accept and exchange process alarms and events.The Following are some of the OPC specifications that are used in Industries, In addition to improving OPC server and client connections, the OPC datahub can connect any OPC server or client to other applications as well, including Excel, a web browser, or any other database. The OPC datahub is designed in such a way to handle all those connections.
NI OPC SERVER EXAMPLE PC
The combination of OPC server and OPC client supports many connections. Why cannot NI make those simple tests: PC A with a 3d party OPC server (Applicom is a good example) and PC B with Labview 8.20 (DS and DSC to be used) and go step by step in the DCOM and all other peculiar settings needed to make it work and publish the details of the procedure, a link to the OPC foundation document is not enough to make it. OPC tunneling – In this method, the OPC client is connected to an OPC server over a network.OPC bridging – In this method, the OPC server is connected with another OPC server to share data.
0 kommentar(er)
