Big Problem: "No Code" displayed on Classmate?

[Straberrie]

Hi,

The laptop that the team used to code and program broke, so we got a new computer. I loaded all the software on it and executed the updates provided on the FIRST website. I set up the static IP address to be what it has been on the previous computer ( 10.3.75.6).

Currently I am having a problem with the Crio. I used to be able to connect to the Crio from the previous laptop without a crossover, using Crio's first port. Now, with this computer, I had to use the Cross over. After i finally got the Crio to connect to the computer ( i pinged it after i connected it through the crossover), I decided to re-image the crio and used the 2010 version 20. The re-imaging was successful and the new IP allocated to the crio was 10.3.75.2. I reset the robot. I loaded the code to the Crio by connecting the computer to the Crio through a cross over ( port 1). The download was succesful. I reset the robot again.

Then, i connected the crio to the classmate now just using an ethernet, not dealing with the cross over, through port 1. I got the robot to communicate with the driver station, but the Crio Image appeared as "Unavailable" and there was "No Robot Code" when in fact I "successfully" loaded the code to the crio just moments ago.

Do any of you know what this problem could be caused by? Am i missing anything?

Any help would be really appreciated!

[apalrd]

1. What language. Java and C++ act VERY differently from LabVIEW.

2. If LabVIEW, I assume you did a full build and download?

3. I generally use a switch when tethering, so I can connect my laptop and the Driver Station at the same time.
3b. If you set the IP of your laptop to 10.3.75.5, you can install FRC Driver Station (Run the latest version of the DS Update to install it from scratch), and run DS in a window on your computer. This is super helpful when a switch is not available or you lack power to run a switch.


I don't think you missed anything. I would try to format the controller when imaging it, and downloading code again. I don't know if C++ suffers from this issue, but LabVIEW has a nasty tendency to crash the robot when the user code is too big.

[Straberrie]

Originally Posted by apalrd

1. What language. Java and C++ act VERY differently from LabVIEW.

2. If LabVIEW, I assume you did a full build and download?

3. I generally use a switch when tethering, so I can connect my laptop and the Driver Station at the same time.
3b. If you set the IP of your laptop to 10.3.75.5, you can install FRC Driver Station (Run the latest version of the DS Update to install it from scratch), and run DS in a window on your computer. This is super helpful when a switch is not available or you lack power to run a switch.


I don't think you missed anything. I would try to format the controller when imaging it, and downloading code again. I don't know if C++ suffers from this issue, but LabVIEW has a nasty tendency to crash the robot when the user code is too big.

Thank you for replying!

1) I am using C ++
2) Well I did build and download XD And i used the correct .out in the preferences for windriver.
3) Thank you for the tip! That would be useful; except, I want to get it to work as is now. I'll keep this in mind for after this is fixed.

I don't know if the problem has anything to do with me using a cross over cable, but it does connect.

And i formatted the controller when re-imaging the crio. I selected the 2010 version 20 update, and the classmate still displayed "not available" for crio image.

[Radical Pi]

are you able to ftp into the cRIO? If so, try enabling NetConsole and check if any errors are being spit out

[Straberrie]

Originally Posted by Radical Pi

are you able to ftp into the cRIO? If so, try enabling NetConsole and check if any errors are being spit out

XD TO be entirely honest I haven't done the above before... ever. I guess this will be a good time to start, I'll attempt it tomorrow! Thank you for the advise.