crio takes a long time to start an executable

[Ujjval Shah]

i have an exe which i deploy on crio and select a vi to run as startup vi during making the build

whenever i reboot the system the vi takes atleast 45 seconds to start..

what can be the reason for it?

Thanks.

Regards,

Ujjval

[spiyah]

I am havng a similar problem. But mine takes around 3 to 4 minutes. It did not always take this long. This issue started about 2 months ago.

[AMP12]

I believe that is just the nature of the cRIO which starts a deployed application.  I haven't done hundreds of these, but the handful that I have built and worked on all take about 45-60 seconds to boot up and start running.

This is in the deployed, "run as start up" condition.  When using in conjunction with the development environment it can take much less, depending on the size of your code, the number of changes, etc. 

[AMP12]

Spiyah, I didn't see the date on the original post.  I haven't witnessed 3-4mins that I recall in the past.  But more importantly, you mention that is has changed to that since about 2 months ago?  That seems odd that it would change.

Are you loading some data file at the startup of your program that may be growing over time?

[spiyah]

The Crio does not load any files. It does read about 30 network shared varaibles that are located on a network drive on startup.

[Craig_]

If you enable console out on the controller and read the serial data through a null modem cable you can very accurately see the systems boot order and it loading installed services.

To decrease time the only thing you really can do is uninstall unneeded software.