Startup application configured to launch missing when RT target booted

[DrewCommPower]

I am using LabView 2011 and I am deploying a build specification to a cFP-2220.  I have set the build to run as startup and I have the proper vi loaded as the startup.  When I try to deploy my build, I get the error in the picture attached.  I can select apply and the build will continue to deploy and work without an issue.  My problem is that I most often deploy my code by accessing the files on the cfp target and inserting the file into the startup folder.  What does this error really mean?  How do I fix it?  Thanks!

[nathand]

I believe that error message is telling you that when you last booted the Fieldpoint unit, the startup application was missing.  Are you deleting the startup application, rebooting, then re-deploying?  If so, don't delete the startup application, or unset it as startup prior to deleting it.

[DrewCommPower]

When I ftp into the cFP-2220, I delete the old files and copy over the new files and then reboot it. (The code is not starting on bootup when I do this, this is my issue)

When I deploy from the project, I dont delete any files.

[nathand]

The error you're seeing says the startup application didn't exist when you booted the Fieldpoint, which is consistent with you saying that the code doesn't start when you boot after you ftp it there.  That suggests that you're not copying the right files to the right places, or it's not getting named properly.  Which files are you copying, and to which locations?

You might be able to look at the log file for the Fieldpoint (don't remember the steps offhand, but you can get to it within the LabVIEW project, be patient while the log file loads) and see if there's a more detailed description of the error including which file was not present.

[KHartley]

Drew,

When you set to run at start up LabVIEW takes care of most of these settings but when you deploy a rtexe without run at startup or manually deploy a rtexe via ftp or another method you need to change the ni-rt.ini.

Please see the following KB on what settings to change. 

How do I deploy a Startup Executable to my RT controller

http://digital.ni.com/public.nsf/allkb/B37FA04A1CB84B6C862571A30060EF03

[DrewCommPower]

I have attached a view of the files that I am copying over and a view of my .ini file. 

The project has 2 cFP-2220s.  I am copying over the RT build for the other cFP-2220 through the ftp and I am not having any issues with that starting up after bootup.  Could it be that I am having a problem with a dependency that is not making it into both RT build specifications?  I will attach an expanded view of my project as well.  The log files didn't log any errors.

[KHartley]

Drew,

If you use the run at startup to deploy does the program run fine? Did you modify the ini file yourself? What program did you use to modify the ini file? Try deploying the another project and see if the the controller will start up the rtexe.

[DrewCommPower]

Running as a startup does work.  I never modify the .ini and I've been deploying the RT through the ftp for years.  I have messed around with the .ini  file some since I've had this propblem, but I have reformatted the cFP-2220 since then.  When I was modifying it, I was opening it up in notepad.  The first part of the project has an RT build, and that deployed fine through the ftp installation method.

[nathand]

In your screenshot you show the filename being "...(Ver 1.21a).rtexe" but the INI file says "...(Ver 1.21).rtexe".  That difference in the 'a' in the filename will do it.

[DrewCommPower]

That very well coulve been the problem.  I changed the target filename to its defualt of "startup.rtexe".   Now when I have a new revision I wont need to deal with a name change.  Therefore I wont have that filename mixup. Thanks for helping me spot my error.