FP program not running independently

[krummelt1]

Hello

I currently have the attached program that runs well with cFP when I am running the code off the computer. However, when I build the program to the cFP it does not function the same way. Is there something in the code that is keeping it from running the way I expect? Is there a setting somewhere that I can check to ensure it does run once it is uploaded?

Take a look and give me your thoughts on it.
Thanks
TK

[tst]

I'm reposting my response from the main LV board:

I can't look at your code at the moment (no LV here) but if you target the FP from the PC and run the program it should (as well as I know) run exactly the same as it does when run indepedently. There are a few things I can suggest:
1. Make sure when you build your app that it's set to auto run when the cFP is turned on (in the application builder window).
2. I usually use one of the LEDs on the module itself (A-D) and write a small piece of code to blink that LED. If the LED blinks, the code is running.
3. Open MAX, go to remote systems and find your cFP. Right click on it and select "File Tranfer". Tranfer Startup.exe from c:\ni-rt\startup on the module to the same directory on your C drive. Then, when you use LV to connect to that module, LV will connect to that running program and you can see its front panel. Keep in mind that you need to do this everytime you build your app.
4. If you have any more questions, I suggest you post them in the Fieldpoint board. FP knowledgable people are more likely to see it. Also, if it's related to this, post a link to this thread.

[Aaron_G]

TK,

How does it not function the same way when running embedded in an exe as when running embedded in the development environment?

When you embed an executable into a FieldPoint target, there is an option entitled Launch At Start-up. This is also accessible by targeting the FP controller in the LabVIEW Development Environment and then choosing Tools--> RT Target Options --> Misc. If this box is not selected, then even though an executable may be in the FieldPoint module, it will not be started at power-up. Whenever you build an executable into a FieldPoint unit, the executable will not start automatically until the next reset of the module (programmatic reset or power cycle).

Regards,
Aaron