deploy SV library as part of cRIO startup.rtexe

[faustina]

I'm trying to deploy a SV library as part of the startup.rtexe for my cRIO.  How can this be done?  Enclosed are screen shots of my build properties.

[Queue-tip]

The following KnowledgeBase article outlines the process for deploying shared variables which are a component of an .rtexe :

'How Do I Deploy Network Shared Variables from a Compiled Executable'

http://digital.ni.com/public.nsf/allkb/04D9A85B6967EE87862571140065EEC6

Hope this helps!

~ Q ~

[faustina]

I did not follow any of the suggestions in the white-paper.  I found making sure the "Disable Autodeploy Variables" was not check resolved the issue.

[faustina]

Okay I'm thorougly confused. 

I sucombed and had my startup.rtexe programmatically deploy the SV library according to http://digital.ni.com/public.nsf/websearch/04D9A85B6967EE87862571140065EEC6?OpenDocument. 

When the cRIO-9024 is powered down, I still see it in Distributed System Manager.  There is no content, but it seems to be on the net. I find this confusing since the ethernet ports should have no power.

When the cRIO-9024 is powered up, I do not see the SV library even though startup.rtexe programmatically deploys it.  I do see NI_ChassisIO, NI_SystemState, System, and Mod2-Mod6 (NI 9485) and Mod7 (NI 9205).

I know the startup.rtexe is running and writing to the SVs in the SV library be examining the block diagram using 'Operate>Debug Application or Shared Library...'  2 of the SVs in the SV library are boolean flags.

Users communicate with the cRIO-9024 through stand-alone applications running on other PCs.  How will they know the status of the startup.rtexe if they cannot read the boolean flags that are part of the SV library hosted on the cRIO-9024?

[faustina]

One final thing ... if I start a stand-alone application from one of the PCs, then the SV library appears in DSM.  However, none of the boolean flag variables are being updated.

[faustina]

I do notice that when a variable is written to by a stand-alone application, that variable gets deployed?  Since on of the flags is only written to by the startup.rtexe it never gets deployed.

[Queue-tip]

I am having some trouble understanding what you are asking. Could you please condense the core issue into a single post? Thanks.

[faustina]

Why, even though I programmatically deploy the SV library in startup.rtexe, does it not show up in DSM when the cRIO powers up?

[Queue-tip]

Are you sure your application is running upon startup? Toggling the User LED is a good tactic to ensure that the .rtexe is actually executing.

NI Community: Toggle User LED on cRIO Target'

https://decibel.ni.com/content/docs/DOC-29852

Can you access those shared variables from a VI running on the host machine?

What version of Distributed System Manager are you using?

[faustina]

I don't believe I'm making myself clear.   I want to deploy a SV library with my startup.rtexe on my cRIO.  This will enable users to see the status and time from an .exe on from their PC.  The SV library will not deploy with the startup.rtexe.  I'm pretty sure the startup.rtexe is running because if I run an .exe from a PC the SV library shows up in the DSM but not all the variables seem to be deployed.  Also, I can bring up the VI running on the cRIO in debug mode.  Hopefully the enclosed PPT will help explain.