Connecting to the cRIO

[tohlizzle]

I need help connecting to the CRIO. I have never been able to deploy code to it an need to to test line following.

NetBeans displays the following and then simply freezes:

CompilerOracle: exclude com/sun/squawk/Method.getParameterTypes
CompilerOracle: exclude com/sun/squawk/SymbolParser.getSignatureTypeAt
CompilerOracle: exclude com/sun/squawk/SymbolParser.stripMethods
[translating suite image [closed: false, parent: squawk] ...]
### Excluding compile: com.sun.squawk.Method::getParameterTypes
### Excluding compile: com.sun.squawk.SymbolParser::getSignatureTypeAt
[Including resource: META-INF/MANIFEST.MF]
Romizer processed 99 classes and generated 4 files.

Please help. Thank you in advance.

[Robby Unruh]

Have you imaged your cRIO? Added the FRC plugins to Netbeans? Are you connected to the robot locally or wirelessly? Does the router on your robot have a 10.XX.YY.ZZ static ip address?

So many questions!

[tohlizzle]

The robot's IP address is 10.9.0.2 and my computer's is 10.9.0.7. The computer is connected to the robot by an ethernet cable that is connected to a wireless router that is connecteed to the cRIO. I just updated my plugins for NetBeans and restarted NetBeans. I do not know what "imaging the cRIO" is or how to do it or what a "static ip address" is.

[Robby Unruh]

Originally Posted by tohlizzle

The robot's IP address is 10.9.0.2 and my computer's is 10.9.0.7. The computer is connected to the robot by an ethernet cable that is connected to a wireless router that is connecteed to the cRIO. I just updated my plugins for NetBeans and restarted NetBeans. I do not know what "imaging the cRIO" is or how to do it or what a "static ip address" is.

Try plugging directly in to the cRIO (with the ethernet cable) and run the cRIO Imaging Tool on your desktop. You'll have to image your cRIO to run the Java code.

If the ethernet cable doesn't work, try a crossover cable.

[tohlizzle]

I get the same problem with a direct connection to the cRIO:

CompilerOracle: exclude com/sun/squawk/Method.getParameterTypes
CompilerOracle: exclude com/sun/squawk/SymbolParser.getSignatureTypeAt
CompilerOracle: exclude com/sun/squawk/SymbolParser.stripMethods
[translating suite image [closed: false, parent: squawk] ...]
### Excluding compile: com.sun.squawk.Method::getParameterTypes
### Excluding compile: com.sun.squawk.SymbolParser::getSignatureTypeAt
[Including resource: META-INF/MANIFEST.MF]
Romizer processed 99 classes and generated 4 files.

Then NetBeans freezes.

What is a crossover cable and what does it look like?

[Robby Unruh]

Originally Posted by tohlizzle

What is a crossover cable and what does it look like?

Not too sure myself. We're lucky enough to have a mentor who knows what he's doing with these kinds of things on the team. Take a look at the Wikipedia article if you have ethernet cables to spare, you have to re-wire them yourself.

http://en.wikipedia.org/wiki/Ethernet_crossover_cable

[Patrickwhite]

You shouldn't have to use a crossover cable to connect to the cRIO from a computer.
If you try and deploy the code without being connected to the robot, does it give you the same error? If so, it's probably a problem with your installation. If a reinstall of both NetBeans and the plugins doesn't solve the problem, try deploying from another computer to see if you get the same result.

[Robby Unruh]

Originally Posted by Patrickwhite

You shouldn't have to use a crossover cable to connect to the cRIO from a computer.
If you try and deploy the code without being connected to the robot, does it give you the same error? If so, it's probably a problem with your installation. If a reinstall of both NetBeans and the plugins doesn't solve the problem, try deploying from another computer to see if you get the same result.

Our team couldn't get it working with an everyday old ethernet cable, but I guess that could've just been bad luck on our part.

[flameout]

Some computers, such as the Classmate, have autodetecting hardware, so you can use a straight-through cable on them (we use the Classmate to image, and Linux machines to program).

To connect straight to the cRIO, you either need a crossover or an autodetecting port. If in question, use a crossover. Hopefully you have one lying around (you can hold both ends in the exact same orientation side-by-side. Iff the order of the colors (some wires are striped) match, it's a straight-through. If they are scrambled (some will still be right), then it's a crossover. If none of them match, you're doing it wrong )

Have you imaged the cRIO yet? (If no-one on your team knows, then you haven't).

What do you mean when you say that NetBeans "freezes"?

I hope this helps.