|
Re: [FTC]: [FTC] Motor Controller problems
Quote:
Originally Posted by michael714
We looked at the output signal with a scope and no matter what values we use in RobotC, we don't seem to get PWM, just on (12V) or off (0V) or full reverse (-12V). Is it possible we have a bad motor controller?
|
You appear to either be mixing two symptom-descriptions together, or making the mistake of thinking that the motors know how to decode PWM signals.
What I think you should see is this chain of signals.
NXTBrick --> HiTechnicBrick: See PWM, or I2C, or some such encoded signal
HiTechnicBrick --> BigMotor: See a signal that encodes speed and direction into a (relatively) slowly varying (from +12V to -12V) analog voltage.
If you are looking for PWM pulses at the 2-wire input to the big motors, I think you are looking for the wrong thing.
If you send proper commands to the HiTechnic Motor-Control brick, and it only produces full on +12V or full off (-12V), and if those signal aren't modulated in any way once they are on or off, then I think you might have a bad HiTechnic brick.
Blake
__________________
Blake Ross, For emailing me, in the verizon.net domain, I am blake
VRC Team Mentor, FTC volunteer, 5th Gear Developer, Husband, Father, Triangle Fraternity Alumnus (ky 76), U Ky BSEE, Tau Beta Pi, Eta Kappa Nu, Kentucky Colonel
Words/phrases  I avoid: basis, mitigate, leveraging, transitioning, impact (instead of affect/effect), facilitate, programmatic, problematic, issue (instead of problem), latency (instead of delay), dependency (instead of prerequisite), connectivity, usage & utilize (instead of use), downed, functionality, functional, power on, descore, alumni (instead of alumnus/alumna), the enterprise, methodology, nomenclature, form factor (instead of size or shape), competency, modality, provided(with), provision(ing), irregardless/irrespective, signage, colorized, pulsating, ideate
|