Quote:
Originally Posted by MathMaven
As lead programmer, please let me make a clarification:
We simplified the code to the simplest possible driving code. Several of our drive train Victors still failed to run. We even loaded two previous versions of our code that ran the same Victors perfectly in previous tests. Those same Victors still failed to run.
I believe this is conclusive evidence that the code changes were not the issue.
|
With conflicting information it's difficult to troubleshoot.
"Several" of your drivetrain Victors "fail to run". How many is "several"? And what exactly does "fail to run" mean? Is the problem repeatable and is it always the same "several" that "fail to run"? What is the LED doing on the fail-to-run Victors?
Put your robot securely up on blocks and run the following tests.
Take a cheap handheld digital voltmeter set to an appropriate DC scale and probe the power input to one of the several fail-to-run Victors. If it's not roughly 12 volts then trace it backwards to find the problem. If it is roughly 12 volts then measure the voltage across the Victor's M+ M- power output terminals, using the same DC scale when the motor is being commanded full forward. If it's roughly 12 volts (or -12 volts) and your motor is not turning, you may have a bad motor, or you may have excessive friction in the drivetrain, or you may have 2 motors fighting each other. Post here for more details. If you don't get +/-12 volts, then pull the PWM cable from the Victor input and measure the voltage between the black and white pins. Post results here.