No Robot Code

[Mark McLeod]

Have you set your team number in the Setup tab?

Exit the Driver account and start the Driver Station application in the Developer account anyway.
When it's running go look at the IP address under Network Connections through the Windows Start menu. See if your IP has been set to 10.16.91.5

[SidneySalvo]

Our number is actually 1691. I will check the IP tomorrow when i get the chance, however when i run the DS on the developer account, it not only says "No Robot Code" but also "No Communication" ><

[Mark McLeod]

How is the Classmate connected, communications-wise, to the cRIO-wireless, direct Ethernet cable?

Try turning off the wireless and direct connecting for now if you aren't already.

The communication problem could be contributing to your Robot Code issue.
There really shouldn't be any difference between accounts, so that bears investigating.

[SidneySalvo]

ok i will see if that works. i think i have tried it once before but after the updates something may have changed...anyother suggestions?

[Mark McLeod]

Have you made any changes to the Classmate setup?
Installed any non-FIRST code?

Swapped out cables?
Tried it on a different PC?

[SidneySalvo]

Originally Posted by Mark McLeod

Have you made any changes to the Classmate setup?
Installed any non-FIRST code?

Swapped out cables?
Tried it on a different PC?

No changes that i know up, we had to reformat it using the flash drive just before i got started. (we now keep a password on it...stupid freshmen)

as too non-FIRST code, i do not beilieve so but i was following the instructions to create the FRC project, and that is what i've been trying to download to the cRIO. i didn't read that there were any changes that had to be made so i haven't made any.

we are using all of the ethernet cables we have currentally.

one other thing that could be the problem...could the cRIO not be running the code because we don't have the correct moduals inserted in it in the right places

[Alan Anderson]

Originally Posted by SidneySalvo

No changes that i know up, we had to reformat it using the flash drive just before i got started.

You must apply the LabVIEW and Driver Station updates before communication will work properly. See http://www.usfirst.org/frccontrolsystem for links.

[Mark McLeod]

Originally Posted by SidneySalvo

One other thing that could be the problem...could the cRIO not be running the code because we don't have the correct modules inserted in it in the right places

Your code would still run, it just wouldn't work right if the modules weren't where they are supposed to be.

[SidneySalvo]

I have applied those two updates and also re imaged the cRIO afterwards. i don't have a clue what else to try!

After forming the project are there any changes that need to be applied to make it work?

can someone send a decent quality pic of their cRIO?

[SidneySalvo]

Very Sorry to double post, but i wanted to get this back to the top so it won't just dissappear because our problem still isn't fixed but i have learned more.

So two things have changed:

1:I can now run the DS on the developer account and the "Communications" light is now green when i do that.

2: I tried to simply run the Robot Main.vi on the cRIO and that gave me the green light on the "Robot Code" light and allows me to run the motors using the joysticks. However, when i click run as startup it still tells me that "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".

[Mark McLeod]

Originally Posted by SidneySalvo

However, when i click run as startup it still tells me that "No Robot Code"

The part that stumps me is there are no error messages, either on the build or on the "Run as startup"

At the conclusion of "Run as startup" it asks you to reboot the cRIO, correct? The permanent code won't take effect until the cRIO is rebooted, while the temporary "Run" is the opposite and takes effect immediately, but goes away when the robot is rebooted.