Right now we are programming and from here to there the robot starts acting weird and tries to fix it self. We can tell it may be the gyro fixing itself but we don’t want this to happen cause sometimes it fixes itself and makes our program hell worse. Is there a way to fix it.
That question makes absolutely no sense.
can you be more specific, what do you mean by “We can tell it may be the gyro fixing itself”
When our robot turns it stops at the end of the code and turns slowly to the left and right till the robot gets its desired angle.
ok, that’s better.
Are you using the drivetrain class and turnToHeading/turnFor functions ? or did you write the turning code yourself ?
No need to make us download your code, you may just press this button:
and it’ll ask you paste to paste it here
Or if you use blocks, you may just put a picture of your code into this thread
The drivetrain class is very generic, it works “ok” with simple trainer robots, but will struggle with larger and more complex competition robots that may also have gearing on their drive to make them faster. You can try slowing down the turns using setTurnVelocity, but that’s about all you can do without writing your own turning code.
We do, we have a PID but our gyro hates us and can’t seem to solve the issue of turning 90 even through we programmed it to go straight.
The gyro is like commander data, it has no emotions.
It doesn’t get happy, it doesn’t get sad. It just runs programmed.
Depends when in the Trek timeline:
In the film Star Trek Generations, Data finally installs the emotion chip he retrieved from Lore, and experiences the full scope of emotions. However, those emotions proved difficult to control and Data struggled to master them.