Driver's Station not communicating with cRio

[Alexandstein]

We have been attempting to run our Labview code on our cRio board for days but it hasn't been working. I recently found out you had to open the driver's station to run it. So I did that, but, while Labview seems to be able to communicate with the cRio, the Driver's station keeps saying "No Robot" every time we try to enable it.
Any help would be greatly appreciated!

[seannoseworthy]

First, you would want to make sure that you have the DS plugged into your router and the gaming adapter plugged into port 1 of the cRio and are both powered. If everything is good there make sure you team number on the DS is set as this becomes your ip. If that's not it check that all your ip's are set correctly throughout the whole control system. Also check your cables with a cable tester if you still cant get communication.

[Greg McKaskle]

From your description, I believe you really want to run the LabVIEW robot code and the DS at the same time. To do that, keep logged into the developer account, from LabVIEW run your code. From the Start menu, launch the driver station. You should see the robot ready to run but disabled.

A somewhat common situation teams have run into is logging out of the developer account to start the driver station. This aborts LabVIEW and the code running on the robot.

Greg McKaskle

[Alexandstein]

Originally Posted by Greg McKaskle

From your description, I believe you really want to run the LabVIEW robot code and the DS at the same time. To do that, keep logged into the developer account, from LabVIEW run your code. From the Start menu, launch the driver station. You should see the robot ready to run but disabled.

A somewhat common situation teams have run into is logging out of the developer account to start the driver station. This aborts LabVIEW and the code running on the robot.

Greg McKaskle

I actually tried that but with no avail. I'm really hoping this isn't a cRio problem. (We're short of money)

[2544HCRC]

Can you ping the cRIO? from the start menu go to run, type in cmd, in the command prompt window type ping 10.xx.yy.2 where xxyy is your team#. This will tell you if the IP address is set and responding.

We had similar problems, but we reimaged for the third time, loaded the software a bit differently, and we then seemed to be working. I wish I could help more, but I am very new to this and know it can be very frustrating!

[Mark McLeod]

Just to confirm the steps you're taking, here is a simplified process.

Setup:

• Classmate wired via Ethernet to cRIO port 1
• cRIO powered up
• E-stop button plugged into Classmate
• Log out of Driver account using "Exit" on the bottom right of the Setup tab
• Log in to Developer account
• Start Driver Station from the Windows Programs menu
• Verify that your team number is set correctly on the Setup tab
• Verify on the Diagnostics tab the versions are correct:
  • DS Version 2010.01.06.00
  • cRIO Image FRC_2010_v19

Programming:

1. Start LabVIEW
2. Create a new Robot project setting your IP to 10.21.92.02
3. In the Project Explorer window that comes up under "RT CompactRIO Target (10.21.92.02)" you'll see "Build Specifications" (not the one under "My Computer").
4. Under Build Specifications right click on "FRC Robot Boot-up Deployment"
5. Click "Build"
6. Click on "Run as startup"

[Alexandstein]

Thanks everyone! Problem fixed!

[Mark McLeod]

But now you have to tell us what solved it.
Even if it's a simple answer, someone else is sure to beat their heads about a similar problem and your answer might help them.

[Alexandstein]

I had to change the target IP adress of the Driver's Station to match our team number.
Embarrassingly small error.