Rookie Issue...

[ConcreteKahuna]

Hey all,
Rookie team here, we're having trouble with our benchtop setup. We have wired everything according to the "Getting started" Manual and followed the instructions given. But when we try to control it using the sample code given with NetBeans ("DefaultCodeProject")

Our communications appear to be functioning, all our green lights are lit and the cRIO registering on our PC, but when we run the code nothing happens, the Jaguars get no signal.

Everything is enabled, but we are not using the classmate, but a seperate computer. Thanks for the help

[EricH]

Have you checked your 37-pin cable for proper assembly? http://www.usfirst.org/sites/default...structions.pdf

What color are the Jaguar lights, and are they blinking?

[ConcreteKahuna]

yeah we had to mod our cable, and our jaguars are blinking yellow but are not going solid as is said in the manual.

[andreboos]

What is the robot signal light doing (right next to the power connector for the Digital Sidecar)? If it's off, it's probably an issue with your DB37 cable.

[EricH]

Reseat your PWM cables; that might do the trick. (Also check how they're going in.)

[ConcreteKahuna]

Originally Posted by EricH

Reseat your PWM cables; that might do the trick. (Also check how they're going in.)

we did that multiple times, we wired the lamp and it is completely off. I double checked the DB37 cable and it is correct. We're quite confused

[EricH]

Originally Posted by ConcreteKahuna

we did that multiple times, we wired the lamp and it is completely off. I double checked the DB37 cable and it is correct. We're quite confused

The RSL should not be off if the robot is on, period. That's telling me that something is wrong in one of three places:
a) the 20A power circuit to the Sidecar (though if the other lights are on, that's not it).
b) the DB37 cable isn't connected correctly. There are checks you can do to verify that signals get through the cable correctly.
c) there isn't connection in the cRIO itself, or the module is in the wrong slot (it should be in slot 2).

It could also be a code issue, but I doubt it.

[ConcreteKahuna]

Originally Posted by EricH

The RSL should not be off if the robot is on, period. That's telling me that something is wrong in one of three places:
a) the 20A power circuit to the Sidecar (though if the other lights are on, that's not it).
b) the DB37 cable isn't connected correctly. There are checks you can do to verify that signals get through the cable correctly.
c) there isn't connection in the cRIO itself, or the module is in the wrong slot (it should be in slot 2).

It could also be a code issue, but I doubt it.

We tested our cable with a multimeter and it read clean. The cRio has the following lights on: "power", "ACT Link", "10/100" and the two lights on the breakout.What could be wrong with the cRIO?

--UPDATE

So we've pretty much established that the cable is further defective after plugging in the sidecar straight into the module and getting the light to..well, light. My only question is that the light was blinking although the jumper was properly installed, is that supposed to happen? Thanks for the help!

[ConcreteKahuna]

anyone?

[Mark McLeod]

The RSL blink pattern tells what state the robot is in. The patterns last year were:

• Fast Blink = cRIO not communicating with Driver Station
• Slow Blink = disabled
• Short on/long-off Blink = either low battery or no code & disabled
• Long on/short off blink = Teleop mode
• Solid on = Autonomous mode

[ConcreteKahuna]

we we're actually getting a fast blink, but we didnt have the robot communicating when we tested, so im assuming that explains the blink. We ordered a new cable and hopefully that will solve our issue. Thanks!

[Alan Anderson]

Originally Posted by ConcreteKahuna

My only question is that the light was blinking although the jumper was properly installed, is that supposed to happen?

What jumper?

If the light is blinking, your 37-pin cable is probably fine.