scf file is set as the default if you want this type of access. scf file, so you must make sure the correct. The Tag Engine will only use the current. However, an OPC client cannot specify which. The Tag Engine can then load any servers that the tags in that. When an OPC client launches the Tag Engine, the Tag Engine loads the current. At 30 I/O points, you should consider using LabVIEW DSC and the Tag Engine.īecause LabVIEW DSC is an OPC server, an OPC client can launch the Tag Engine. If you are going to have more than 30 I/O points, you will sacrifice efficiency using data sockets. Because LabVIEW Datalogging and Supervisory Control is an OPC Client, it is much more efficient at OPC operations. The LabVIEW DSC Engine (Tag Engine) takes care of OPC for you. OPC Server Functionality is provided by the separate NI OPC Servers software. See Connect LabVIEW to Any PLC Using OPC for more information on this process.Ĭommunicate to OPC Server with LabVIEW DSC 7.1 and previous using the Tag Engine Starting with LabVIEW 8.0, the LabVIEW DSC module extends the functionality of the Shared Variable Engine (SVE) to allow LabVIEW to serve as an OPC DA client.
See Using OPC UA Servers and Clients (DSC Module or Real-Time Module) for more information on this process.Ĭommunicate to OPC Server with LabVIEW DSC 8.0 and later using Shared Variables Starting with LabVIEW 2017, OPC UA Toolkit was released separately from the LabVIEW DSC Module and became a stand-alone LabVIEW toolkit. Additional Information Communicate to OPC UA Server with LabVIEW DSC 2013 - 2016 or LabVIEW 2017 OPC UA Toolkit using the OPC UA APIįrom LabVIEW 2013 to 2016, the LabVIEW DSC module contains an API for programmatically communicating with and exchanging data between OPC UA servers and clients.
0 kommentar(er)
