11-16-2009 08:19 AM
I deployed my application to the compact Field Point as Run at Startup; however, it is not starting after the cFP is rebooted. I know that it is not starting because the water pump in my system is not being turned on and ABCD lights of the cFP are not lighting (I put in code to turn those on at different stages in the application so I could easily tell where the code at).
I have verified that the application is in the correct path name and that the ini file is set for the application to run at startup.
Here is the LVRT section of the ni-rt.ini file:
[LVRT]
CDIntervalTicks=55
LABVIEWRTDir=/c/ni-rt/system
memoryChecking=False
PATH=/c/ni-rt/system/;/c/ni-rt/;
RTCPULoadMonitoringEnabled=True
RTEnetRcvMode=2
RTTarget.ApplicationPath=/c/ni-rt/startup/startup.rtexe
RTTarget.EnableFileSharing=True
RTTarget.IPAccess="+*"
RTTarget.TimeZone=CST6CDT
RTTarget.VIPath=/c/ni-rt/startup
server.tcp.access="+*"
server.tcp.serviceName="Main Application Instance/VI Server"
StartupDlls=sysstatepublisher.out;niserial.out;c:\ni-rt\system\FPLVMgr.out;taggerrt.out;
WebServer.Enabled=True
webservices.SecurityAPIKey="PqVr/ifkAQh+lVrdPIykXlFvg12GhhQFR8H9cUhphgg=:pTe9HRlQuMfJxAG6QCGq7UvoUpJzAzWGKy5SbZ+roSU="
webservices.ValidTimestampWindow=15
RTTarget.LaunchAppAtBoot=True
Any ideas?
11-17-2009 01:36 PM
Hi Carol,
Are you deploying this from a project? What do you see in the Distributed System Manager for your remote system? Below is a link that might be helpful. Is your controller still connected to the network when you restart it? Please take a look at this and repost if you still run into problems.
Startup EXE not Launching on Real-Time (RT) Target at Controller Reset
http://digital.ni.com/public.nsf/allkb/52E943F7D6E7C0578625720A001DDF6E?OpenDocument
Nick Keel
Applications Engineering
National Instruments
11-24-2009 02:17 PM
Hello NAKeel,
Yes I am deploying from a project. I checked the Distributed System Manager and below is what I saw:
CPU/Memory
CPU 0 Usage
Total: 100% High 1.17% Normal 98.8%
Memory Usage 35.335%
VI states tab
target-singlerate.vi BAD
target-singlerate.vi is my main vi of my real time function. I am not sure why it is giving a status as bad. The system functions correctly when I run the vi from the project.
I think my controller is still connected to the network because I was able to use the Distributed System Manager to read the information. I do not remove any network cables from the controller after deploying the application.
Carol
11-24-2009 04:28 PM
Luckily RT targets support debuggable executables.
This should help: http://digital.ni.com/public.nsf/allkb/8DA679805915DE40862572D5007B2F70
Are you using VI server to launch VIs by chance?
Just to make sure, when the application is run in development mode, does it work perfectly fine.
11-24-2009 05:00 PM
Brian,
After reading your post, I tried the remote debug. I started the Remote Debugger and when I clicked the Connect button, I received the following error "Compiler error. Report this problem to National Instruments Tech Support. GlobalWriter is not referencing a VI"
The application does run when I press the run button of the VI under my project on the host computer. Since it goes through deploying all the files and shared variable library to the target, I assume that the application is running on the target and updating the front panel on the screen.
I do have VI server enabled on the target, if that is what you were asking.
Carol