No Robot Code

[SchrödingersCat]

Our team is having the same problem. We installed LabVIEW update 2.1 and Driver-station update 1.1 on the Classmate, updated the cRIO image to v20. We can only connect with the driver station while LabVIEW is not loaded (we cannot run the code in a real time connection). It still displays "No Robot Code".

Any ideas would be lovely.

[Mark McLeod]

What messages or response do you get when you push the "Run" button on Robot Main.vi?

Originally Posted by SchrödingersCat

Our team is having the same problem. We installed LabVIEW update 2.1 and Driver-station update 1.1 on the Classmate, updated the cRIO image to v20. We can only connect with the driver station while LabVIEW is not loaded (we cannot run the code in a real time connection). It still displays "No Robot Code".

Any ideas would be lovely.

[SchrödingersCat]

Originally Posted by Mark McLeod

What messages or response do you get when you push the "Run" button on Robot Main.vi?

It seems to deploy correctly. I have a indicator on the Iteration Count within the while loop in Robot Main.vi, and it increments about once per second (as the driver station is not connected).

When I attempt to start the Driver Station, the connection between the cRIO and LabVIEW times out and stops entirely. Then the Driver Station connects, and still says, "No Robot Code".

[Alan Anderson]

Originally Posted by SchrödingersCat

It seems to deploy correctly. I have a indicator on the Iteration Count within the while loop in Robot Main.vi, and it increments about once per second (as the driver station is not connected).

When I attempt to start the Driver Station, the connection between the cRIO and LabVIEW times out and stops entirely. Then the Driver Station connects, and still says, "No Robot Code".

Have the Driver Station application running before you try to run the robot code.

[SchrödingersCat]

Originally Posted by Alan Anderson

Have the Driver Station application running before you try to run the robot code.

I can try this, but I believe LabVIEW wouldn't connect at all with the Driver Station already running (and connected).

[Mark McLeod]

You have Exited the Driver Station in the Driver users account and are running it only in the Developer account aren't you?

Not switching back to the Driver account to run the Driver Station.

[SchrödingersCat]

Originally Posted by Mark McLeod

You have Exited the Driver Station in the Driver users account and are running it only in the Developer account aren't you?

Not switching back to the Driver account to run the Driver Station.

Yes, I hold SHIFT while windows comes up so I login only the Developer account, and run the Driver Station while in Developer.

[Mark McLeod]

Sounds weirdly like only one app can use the network connection at a time.
You can also try turning off the Classmate wireless while you are trying this, so we know it isn't port confusion.

Have you changed the Classmate much, if at all, from it's original condition by installing third-party software?

[SchrödingersCat]

Originally Posted by Mark McLeod

Sounds weirdly like only one app can use the network connection at a time.
You can also try turning off the Classmate wireless while you are trying this, so we know it isn't port confusion.

Have you changed the Classmate much, if at all, from it's original condition by installing third-party software?

No, in fact, I just used the Restoration Key and installed all the updates.

[SchrödingersCat]

Got it working. I created a new blank cRIO FRC Project with all the updates installed, and magically everything works.

[Mark McLeod]

Might have been a mix of old version code then.

Good news.

[SchrödingersCat]

Originally Posted by Mark McLeod

Might have been a mix of old version code then.

Good news.

Actually, the old code from before I re-imaged the Classmate worked perfectly now that everything was properly installed.