Quote:
Originally Posted by Alan Anderson
It isn't a common problem. If you are getting significantly different response on the two sides of your drive base, something is wrong with the hardware. It would be better to fix the cause rather than patch it with software.
|
i don't know how much of a difference this makes, but we're going 4WD (for omni/mecanum), so i assume any difference in motor output becomes a lot more noticeable more quickly than it would with plain tank. i would love for there to be a non-software solution for this, but it has plagued our last few bots and we don't know where else to look.
Quote:
Originally Posted by j.cole
if they arent the same then adjust the speed of the motors until they are.
|
Quote:
Originally Posted by Mark McLeod
Scale the motor inputs just before they get into the tank/arcade/holonomic drive vi's. Using the LabVIEW PID functions.
|
ah, but how is this done? the PID suggestion seems interesting, but how do we actually get inside the devref to do all this? just unbundle and go through the Motors array? at that point scaling could be trivial (i.e. just multiply) but is there a nicer way to actually get that far?