Quote:
Originally Posted by meltbox360
I have the same problem minus the lights. I have gotten it to run using the default code example however using the simplerobot example nothing works. Furthermore it appears as if using the Jaguar class does something with the relay pins since one of the lights lights up next to the number 1 when I do something like this:
Code:
Jaguar * jag1;
jag1 = new Jaguar(1);
jag1->Set(1.0);
Wait(2.0);
jag1->Set(0.0);
At least lately that led has been lighting up. Noticed once before all the leds lit up so its some funky stuff going on. My first move at this point after trying countless things for weeks is going to be replacing the cable from the module to the sidecar. I'll post back to tell you if it changes anything.
Also I failed to mention using RobotDrive works perfectly. I use it with tank drive and two controllers. One last thing. Motors refuse to go full speed forward but will go full speed backwards with that config. It just started happening after working fine for a while. Don't know if any of these other things could be similar to what you are experiencing but I'm listing them just to find out if we could have a similar issue.
EDIT: Another note. I have had no success with SimpleRobot only with IterativeRobot. More strangeness. I don't see why it would be a hardware problem but none of this seems at all logical to me. I should also note my setup is EXACTLY like the getting started with frc control setup is. Instead of having 2 Jaguars with one on pwm 1 and one on pwm 2 I have 1 jaguar on pwm1. |
If your talking about the selonoid lights on the selonoid module, I believe the default robot code make those flash to show the operation of the selonoids. That is the "SolenoidLEDsKITT" function.
For these kind of problems it is best to debug in sections by process of elimination.
First off take the pwm connector going to your side car and plug it into a vex controller or some remote control car type receiver and see if you can make it go. We actually have an rc receiver fir this purpose.
If it moves then the problem will lie either in the side car or code.
If it does not move, change the pwn cable or jaguar.
If it does move, you have to make sure the side car module is in the correct slot. You can do this by running the FRC 2012 cRIO Imaging Tool. This will will light up in red what modules are missed placed and if you wave your mouse over the slots it tells you what you can or cannot plug in. The netconsole is also good for this too as it will give you errors if the modules are plugged in wrong. You can have a bad side car, but that is rare I think. I have had a lot of bad pwm cables in the past and I am glad to have moved on to can. You should not have to change this code for it to work. I dout its the code.