DSC shared variable deployment not working in LabVIEW Executable

[jstan]

Hello,

I am using DSC to pass data back and forth between a PC and PLC via OPC server.  In the developer environment everything works fine but the compiled executable of my main vi isn't exchanging data with the PLC upon launch.  I checked the options to deploy at application execution and undeploy at application exit but it still isn't working.  I know it's deployment related because when I launch the executable and then deploy my IO server library from the project in the developer environment the application and PLC connection starts working.  I have the 2017 versions of LabVIEW, LabVIEW Runtime, DSC, DSC RTS, and NI OPC Servers 2016 all installed and licensed.  Windows firewall is disabled and I have tried running the compiled application as an administrator.

This issue has cropped up in the recent past on other machines I use and I can't figure out why.  I am not building my applications any differently on machines where the PC-PLC data exchange is successful.  Any tips?  Also, is there a way to get the deployment progress screen on my application to stay visible after it's complete like you can with the development vi?  I don't know if there is anything on the progress screen that could indicate what the problem is because it runs and closes too fast.

[AndresVZ]

Hello, if everything works fine on the development environment but not on the execution the problem is most likely that something is getting left behind on the building process. 

Here is some documentation on Building Applications Created with the LabVIEW DSC Module, that's basically a check list on building the app, what to include in the app and how to transport it.

In the same document there is also a reference to Support Files to Include when Building a LabVIEW DSC Module Application so you can check if you're really including all the files you need in the build.

Hope it helps

 

[jstan]

I appreciate the reply but those links don't appear to address my issue.  I agree that something missing from the build makes the most sense but I don't have any .scf, .ini, .cfg, .iak, or .ccdb files in my project.  All my "Source Files" are vis and sub-vis (the Inclusion Type is "Include if referenced") and there's a io-server (.lvlib file type) that is added in the "always included" section.  The second link you posted lists a whole bunch of files and types that aren't in my source files listing so I assume they aren't relevant to my application.

[natasftw]

You're likely missing the runtime on the deployed systems.  I know you mentioned it in your initial post.  But, this is the most common problem when seeing these issues.  It's important to note it requires a license per PC.  It's also important to be aware the DSC mentioned while building an installer is something different.  You'll need to install the DSC RTS from its specific media on each PC you deploy to (as well as license each one of those).

Can you confirm you've taken those steps on the deployed machines?  Specifically, can you confirm you've done so with the matching year RTS?

[jstan]

Yes DSC runtime is installed and licensed on on this machine.  In this instance the development machine and the deployed machine are the same.  See attached screenshots of local licenses and installed packages.  Labview Runtime 32-bit 2017 SP1 f4 is also inPackage ManagerLicense Managerstalled.