Hello all!
We are running some autonomous code and our robot sometimes gets stalled out on the yellow floor goal. When we give it the slightest nudge, the robot continues with the code as normal.
Does anyone have an easy coding solution to this challenge? Your help would be much appreciated! 
Best,
Michael
My first thought is that perhaps the robot isn’t getting enough traction on the floor at that point? So your little nudge might be just enough to help it grab/drive. You could try increasing the velocity just to get off the floor goal in your code. (You can then lower the velocity again if needed.)
It’s probably also a good idea to make sure that the floor goal itself is flat on the field surface, and not warped or bent in any way. I hope that’s helpful!
Extremely helpful! Our floor goal is a little warped and we are using omni wheels on both front and back which is most likely affecting traction. Perhaps we will try changing the front wheels to balloon tires first and then increasing the velocity as we have it decreased to help with accuracy. Thank you so much for taking the time to share this!
Hi @Michael_Saccone , if changing the tires doesn’t work, you might try using a motor timeout block or command in your code. They will prevent the motors from spinning indefinitely. I’m not sure if you are using blocks or Python, but here are links to the VEX API entries for each:
If you have any questions, please let me know!
I had the same issue with my team boys. With trial and error, we found that the problem with the Brain. If your Autonomous code is little bigger, for some reason the instruction is not going to the brain about the next step in the code. We tried changing wheels, field elements, etc. Nothing helped. After we change brain to a new one, the issue stopped coming. Hope it could be the same case for you!
