single process shared variable - build executable

[lvrat]

I have two applications on same computer. Using single process shared variable with both application. When building executable the writer is updating the shared variable but the VI reading the shared variable does not read the values. The issue is only when creating and running executables. How to build two executables on same computer (and both are in same project) using single process shared variables?

The use of network shared variable is not needed as both applications are on the same computer but when building executable with network shared varaible it works, only single process shared variable does not work??

TIA

[crossrulz · Accepted solution]

Single Process Shared Variables work within the same application context.  When you are developing and both VIs are in the same project, they are in the same application context.  But two executables will have different application context.  So to communicate between the two executables, you have to use the network shared variables.

[lvrat]

Thanks, using network shared variables (custom cluster) to update GUI indicators which is in a separate application will it have lot of overhead? Seems like network shared varaible are not easily scalable, any other recomended approach which has been tried to provide scalability(if indicators are added or removed) and has less overhead.

[fboteroh]

Hi, I have like a similar issue. I have a SVE running in a cRIO-9074. Once the RT-vi is built and set as startup application, they are no more updated. I mean, the work as expected before compilation. What should I do?

FB 

[hnesmith]

Hey, This is an old forum. I recommend creating a new post in the Real-Time Measurement and Control forum since this is a cRio problem.