Quote:
Originally Posted by Greg McKaskle
You don't mention making that app the startup. As long as you've done this once, and use the same build name, I don't think you need to do it each time, but then again I usually do it, and I've never seen a cRIO not run what I told it. So my only suggestion would be to do a Set as Startup after your deploy and see if that is possibly the reason.
Greg McKaskle
|
When I tried it at FLR it wouldn't work no matter what I did, even deploying twice and such. I've done what you sugessted at least once, and running it in realtime gave me a "no code" on the driver station. Building and deploying is the only solution I could get working.
Any idea what the issue is? I even tried different Driver Stations And cRIOs
anyways the temp solution will work for now