So, assuming we built and deployed code to the cRIO, and it’s set to run at startup…
How can we edit it? Or remove it so we can upload something else? I’m a little hazy on how permanent a “run at startup deployment” actually is. Would we be able to simply designate new code, after it’s built, to run at startup? And then that would just over write whatever is already there and ‘running’ ?
The code that you see in labview is called “source code” and exists on your PC in a directory usually named after the project that you have open.
What runs on the robot is an executable form of your project. When you deploy as Run At Startup, it executable is replaced with the new executable based on your source code.
When you edit, you are editing the source code on your PC.
I very, very strongly suggest that your students stop and watch the Tip Jar Video Tutorials #5 through #8 (inclusive) before proceeding any further. This will give your students a good minimum understanding of the basics.
Regards,
Mike
So, as I understand it, if we re-deploy updated code, it will automatically replace the current executable that’s residing witin the cRIO? As long as it’s set to Run At Startup?
BTW: We did watch all the LVMastery videos, 5-12 (I believe Mr. Zimmer is on 12 now anyways…). We got so much out of them, and thought they were so good, that we sent the hyperlink to our Regional Director here in Pittsburgh, which she then sent to the other Pittsburgh-based teams.
That is my understanding as well. You have to deploy as Run at Startup. If you just Run, it will not be permanent.
BTW, Mr. Zimmer is up to #16… Good stuff!
Best of luck,
Mike
All you have to do is re-build the code to do the changes. It’s not worth building the code if you make changes every 20 mins.