-Brain is on latest firmware
-Using block code
-Using an inertial sensor
-I have already tried switching out the inertial sensor
Ok, let’s begin!
So, I’ve been having an issue for a few months that has been taking a toll on our autonomous codes. Sometimes, when the robot is set to turn a specific amount, the PID doesn’t initiate, and it turns too far. We have tried multiple things to counteract this, such as adding a stop driving block before the turn, a 5ms wait block, and switching it to “turn to rotation”, but none have permanently resolved the issue. Please help! Attached is a picture of the code and a video of the “phantom” happening.
It might have something to do with it turning slightly when it hits the first ring. I would try to manually do something to make it course-correct with the inertial sensor so it knows exactly how much it needs to turn to get back.
So, the issue doesn’t happen every time, and you can tell when it happens by the robot turning and then immediately driving again without correcting itself (It also turns farther than you set it when the issue happens). Are you suggesting that we add, for example, a “turn to rotation” block after the turn incase the issue occurs?
