I've checked all voltages and all cables and they are all perfect. The issue is either in the cRIO, the modules, the sidecart, or the code. Here is the code I used for getting a Jaguar to spin:
Code:
Jaguar * jag1;
jag1 = new Jaguar(1,1);
jag1->SetSafetyEnabled(false);
jag1->Set(1.0);
Wait(9.0);
jag1->Set(0.0);
To get a Victor to spin:
Code:
Victor * vex1;
vex1 = new Victor;
vex1->SetSafetyEnabled(false);
vex1->Set(1.0);
Wait(9.0);
vex1->Set(0.0);
Both result in the controllers sitting there with blinking orange lights indicating they are not getting a signal. I have debugging setup and the net console over lan and it isn't spitting out any error messages. Now to try to see if is even allocating a Jaguar or Victor I did the following:
Code:
Jaguar *jag1;
jag1 = new Jaguar(1,1);
jag1 = new Jaguar(1,1);
And it tells me the pwm is already initialized meaning the light should be solid yellow if I am not mistaken BUT IT STAYS BLINKING. Its like the cRIO thinks its doing something but in reality the motor controller never gets the signal. This is a rather big issue as the only way we can drive anything is through using the RobotDrive class.
Any thoughts on what this could be an issue with? It's really weird.
If someone uses c++ and could compile a program that spins a motor on pwm 1 on a Jaguar controller for a few seconds and send me the ".out" file so I can try it I would be very grateful. Perhaps the compiler is borked. At this point I have run out of ideas as even the PWM class gets no response from anything and the hardware appears to be in perfect working order.