|
Re: vEx PWM Motor Response
Like the other folks I got a big deadband (even though I seem to remember that VexLABS claimed that there is no deadband...) and the non-linear curves.
My RPMs went DOWN in a region near 255 and 0.
I folded the plot in the middle to try to overlay one curve (0-127) on the other (127-255). That is when I found out that 127-X doesn't have the same RPMs or slope as 127+X.
I suppose this shouldn't be a big surprise, but it causes a big headache if you try to autonomously drive straight by using shaft encoders to measure distance and toggling each motor between a set point and that set point +/-1 to even out distance traveled.
When I got to the end of the above paragraph I just couldn't bear the thought of using EasyC to write the code I needed. So... now I need to find the time to get familiar enough with the PIC to just use straight C compiled and loaded with the MPLab MCC18 compiler and the IFI loader.
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
|