Last year my team had a horrendous code and one of our biggest issues was that it was so inconsistent sometimes it would score 70 and other times it wouldn’t score any due to drifting and it would drive too little or too much. However my team does not fully understand how to use the brain inertial. Any tips and tricks?
The drifting may have been caused by overheating or by the shaft being out of the motor so whenever u code check the motor temperature and if the shafts are out
There are many ways to use the brain inertial.
- The simplest starts with it being in the drivetrain setup, so that the turns have a little more accuracy.
- The next step involves having the inertial plus left and right motors as separate entities, and writing code to do more accurate turns using things like the Caution Tape precise turn code to get more accurate turns, and their related drive straight code to, well, drive straight and potentially overcome some build issues.
- The last steps build on #2 and go to a full PID (of which you can search here in the forums and find many posts). This tends to be the most accurate, but also the most difficult overall.
It’s important to note that build quality can make a lot of difference in the repeatability of a robot’s operation. Having insufficient axel support, or a wobbly or off-center robot can cause a lot of unpredictable/less repeatable behavior. Techniques above help smooth out the small issues or differences in motors, but build quality should be the “step 0” to check first.
Also @Gigabyte , IQ motors don’t have temperature as something to be able to read, beyond simple touch test.
2 Likes