|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||
|
|||
|
Re: No Robot Code
Hey my team had the same problem this year. I found that restarting the robot after building and deploying fixed our problem.
I think it's worth a try ![]() |
|
#2
|
|||||
|
|||||
|
Re: No Robot Code
If you use the Run As Startup command instead of Deploy, the robot will be rebooted as part of the process. There's never really a good reason to use the Deploy command in LabVIEW.
|
|
#3
|
|||
|
|||
|
Re: No Robot Code
We used LabView to load the code on the robot, we used Robot Main.vi to load on the cRIO
|
|
#4
|
||||
|
||||
|
Re: No Robot Code
Quote:
To do that, you need to use the project explorer, move to the bottom item "Build Specifications", and click the "+" symbol to expand it. Right click on the item that was revealed, then click "build". Once the build is complete, right click again and click "Run as startup". This will place your compiled code onto the cRIO so that it executes whenever the cRIO is powered on. Last edited by Tom Line : 04-04-2013 at 15:34. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|