No Robot Code

Technical NI LabVIEW
1

We are using LABview and it says that we are deploying the main program… the one that was already built in. However, when we switch to the Driver mode, it says NO ROBOT CODE and will not let us do anything. We have tried restarting and installed all the new updates. How have you guys solved this problem?? What is the code in the first place???::ouch::

2
  1. Create a new Robot project, or use one you’ve already created.
  2. In the Project Explorer window that comes up under “RT CompactRIO Target (10.27.61.02)” you’ll see “Build Specifications” (not the one under “My Computer”).
  3. Under Build Specifications right click on “FRC Robot Boot-up Deployment”
  4. Click “Build”
    *]When that’s done in the same place click on “Run as startup”
3

This could also be caused by an incorrect or corrupted image on the cRio. I would recommend re-imaging the cRio with the v19 image that is part of the latest update. My team (677) had the same problem as you, and this cured the problem.

4

I also think you are missing the step mentioned above of selecting run as startup. It also takes the Crio a few minutes (1-3) to start up and load the code when you turn it on.

5

One thing that may be confusing some teams.

When you log out of developer mode to get to the driver account, the development tools such as Eclipse or LabVIEW will stop running. So when you log in as driver, there truly is no code running on the cRIO because the LV process was stopped.

To develop code and drive from the same computer, stay in developer account and use the Start menu to launch the Driver Station. This will allow for debugging and rapid code changes. But do not expect to do this at a competition field.

Once the code does what you like and you are no longer developing, build, deploy, run as startup, and then log out and simply use the driver account.

Also, since the classmate screen is quite small, if you have a second laptop, you may wish to use it for development and simply leave the classmate for the driver account. Plug both computers into the blue cisco router and give the development computer a 10.xx.yy.6 IP.

Greg McKaskle

6

Thanks for this information. I too have the same problem and now its all fix. Thank you Mr. McLeod

7

Same issue… and nothing mention in this post is working yet. We are using the same cRio as last year. We tried to re-image the cRio but it gave us an error stating that our IP was not correct.

We are currently trying to re-format the cRio. We put the cRio in safe mode and are currently re-formatting. The cRio has been in the reformating mode for over an hour. Is this normal?

Any other advice if this does not work?

Thanks in advance!

8

That sounds like a pretty specific indication of what needs to be fixed. Are you using the Classmate to do the reimage, or some other computer? If the Classmate, have you set your team number properly? If a different computer, did you set the IP address to the right value for your team (e.g. 10.21.47.6)?

9

We are using the Classmate.

We have set the IP to 10.21.47.06. The DS shows that we DO have communications but DON’t have code.

We have done a “Build” and “Run as startup” under the “FRC Robot Boot-up Deployment” as suggested earlier.

We have run the updates for LabView and the DS.

The exact message we get when we try to Reconfig the cRio is “The specified IP address is unreachable. Ensure that the IP address is on the correct subnet.”

We tried to ReFormat the cRio but after 6 hour the battery to the robot died.

Now what?

10

That’s not right. The Classmate sets its IP address to 10.x.y.5 based on the team number you enter in the Driver Station window.

“The specified IP address is unreachable. Ensure that the IP address is on the correct subnet.”

It sounds like you might have tried to change the Classmate’s IP address manually and set the subnet mask to 255.255.255.0 by mistake. The cRIO has the address 10.0.0.2 for a moment during the reimaging process, and that won’t be reachable. The quick fix would be to change the mask to 255.0.0.0, but the correct fix is to run the Driver Station software and change the team number to 2147 (you might have to change it to something else first and set it back).

11

We’re having the same problem here as well, although we’re in the Developer account.

I tried setting the code we’re using as startup, but no effect was seen.

We’re using NI LabVIEW.