At 3:20, I would recommennd explaining what is done incorrectly (what causes the problem) instead of just saying there tends to be errors with theparameter inPerTick.
For sure, to elaborate in some cases the division to calculate inches per tick is done incorrectly (Dividing ticks by inches instead of inches by ticks). Resulting in a value much larger than intended. However, in our case the forward and lateral push tests did not give us accurate tuning values, possibly due to wheel slip. This caused us to have to manually tune the values by making the robot move forward and backward / left and right one tile in code and changing the value until it moved the correct distance in real life. Thanks for pointing this out!
This video now has a part 2 to guide through the tuning process which comes after setup! Check it out! ruclips.net/video/x4WbBeTiCPg/видео.html
Just what I needed. 👍
At 3:20, I would recommennd explaining what is done incorrectly (what causes the problem) instead of just saying there tends to be errors with theparameter inPerTick.
For sure, to elaborate in some cases the division to calculate inches per tick is done incorrectly (Dividing ticks by inches instead of inches by ticks). Resulting in a value much larger than intended. However, in our case the forward and lateral push tests did not give us accurate tuning values, possibly due to wheel slip. This caused us to have to manually tune the values by making the robot move forward and backward / left and right one tile in code and changing the value until it moved the correct distance in real life. Thanks for pointing this out!