Benchtop test not working
 

Hi, i am looking for some suggestions as to why our benchtop test is not running the motors on the robot. After running the Robot Main.vi, the drivers station IS finding communication, robot code, joystick 1 and 2, and our team number. When we click enable for teleoperated there isn't movement from the motors, nor is there any change in the jaguars' status lights. We know the robot system (wiring, motors, etc.) are set up correctly as we had a functional robot before updating labview, labview utilities, and the drivers station. We have also updated the crio image. Any suggestions as to why there is no output to the jaguars? Thanks!

Re: Benchtop test not working
 

Many teams received a defective DB37 cable, the cable that goes from the cRIO to the digital sidecar.

Either, use one of the ones from the previous year, or you can rework it following these instructions.

That is to say, if you updated the hardware on your test bench.

Re: Benchtop test not working
 

It sounds to me like you're trying to use an older robot to test on. Did you move the cRio modules around to the new correct positions when you reimaged? Did you change your open commands in your begin.vi so that they are using the correct (new) module numbers?

Re: Benchtop test not working
 

Where in the begin.vi do i see the module numbers? Everything seems to be fine we have communication and robot code, the modules are in the right place but when we push the joysticks forward, nothing happens. Any information would be great! Thanks!

Re: Benchtop test not working
 

Before you continue, could you answer a couple of questions?

1) What is the RSL light on the Sidecar doing?
2) What are the Jaguar lights doing? (translation: are they even getting a signal?)

That could have a large impact on what the problem is. At this point, it could be the DB37 cable, the Sidecar itself, the Jaguars, the PWMs, or something in the code. Those lights will limit the number of places that need checking.

Re: Benchtop test not working
 

Never mind, we got it running, the problem was our new DB37 cable was bad. Thanks for the reply though.