![]() Check the Enable diagnostics box in the Configure OPC Client I/O Server window under the Diagnostics tab.Make sure that your deployment computer has the proper DSC Run-Time System installed and licensed or the full DSC development module installed and licensed.You can check for proper licensing using NI License Manager. Make sure your NI OPC Server is licensed properly on the deployment computer.If the OPC server is hosted locally on both computers, make sure that the Machine field has localhost typed in as the input and that the Browse dropdown has Machine selected.This is important if we are using the local OPC Server on the deployment computer and we are not programmatically setting different OPC Server paths for EXE versus LabVIEW Development environment. The full path to the OPC server needs to be the same on the development computer as well as the deployment computer.SolutionIf you DSC stand-alone application can run without issue on your development computer but runs into issue connecting with the NI OPC Server on the deployment computer, be sure to check the below items as they are common issues that may cause this behavior:
0 Comments
Leave a Reply. |