Lately, I have been been focused on trying to make my autonomous extremely accurate and fast. Many people say that going slow is how you make it accurate, but I need to be able to run everything very quickly to get a high score. Currently, I have a P controller(only P, not I or D), along with deadband assist to make sure the bot never stops. It also has autocorrection. My problem, however, is that it is much too slow. It moves quickly, but then it takes a lot of time autocorrecting. This wastes a lot of time.
I have done this with turning functions and drive forward and backward functions. I would appreciate any advice as to how to speed this up.
Robot Specs:
4 motor turbo Drive Base(more motors to be added)
2 motor mobile goal intake
quad encoders
single gyro
Here’s a really old VEX video (Elevation, 2008-2009), of a robot that used PID logic with line following to go faster the closer it was to the center of a line, and slower when it started to deviate. It used six of the old 3-wire motors geared to 3.6 feet per second. I’m surprised that so few teams try line-following anymore.
Our Chassis is very light and completely built with Aluminium and still the motors stall with 4 High Speed motors. No issues with running 4 Low Speed with 3:2 gear ratio. But, motors stalling with 4 high speed 3:2 gear ratio. I think you will have issues with Turbo speed motors.
I agree that the configuration isn’t particularly helpful this year. Last year it was almost meaningless. Both years it looked useful at first glance. It just didn’t hold up.
We did have some early season work both years where we used it. This year when some teams tried it there just wasn’t enough benefit to make up for the problem of how to mount it. To handle changing ambient light conditions it helps to mount the sensors really close to the floor. I think the recommendation what we’ve found is it works well at 1/4 to 1/8 inch off the floor. Turns out that really can get in the way of bouncing over the zone divide bars. It was possible to overcome that, but encoders, gyros, or both together work pretty well to overcome positioning problems.