After opening and assembling the GoPiGo2, I noticed that the robot does move straight but always turns right (see the video of the Boxter straight line test below). The battery pack is on top of the canopy and the wheels have rubber bands as recommended by the previous forum posts.
After I ran the Boxter straight line test and submitted my response about the degree of turning, the Boxter software said that it has made some adjustments to my GoPiGo2 and I should run the test again to confirm that my GoPiGo2 moves straight now. However, as you can see from the 2nd straight line test, it was still turning right
@cleoqc, I tried to repeat this process 6 times but it only made it worse. This is very strange… Today my first test was almost perfect but already after 2 times running the straight line test, it was turning right really badly I was wondering if there are other adjustments that I could make using DexterOS?
Are you sure you didn’t run the trim process in the opposite way? Please run the trim process again, but do it the exact opposite way you did it before.
Beware that the trim process asks you to show the direction of your GoPiGo and not to which direction the robot has to be adjusted.
@RobertLucian, yes the trim process was done the right way. I have also tried the opposite way just to check but then the GoPiGo starts making circles. I was wondering if there is anything else that I could try?
Also, still in the Python IDE, you can run basic_test_all.py (in GoPiGo/Software/Python)
The options ‘tt’, ‘tw’ and ‘tr’ (trim test, trim write, trim read) can help you set the trimming beyond what the DexterOS gui can.
Thank you for the follow-up and sorry for the delay.
I’ve programmed the driving test for my GoPiGo2 as follows: drive forward for 8 seconds, pause for 1 second and then drive backward for 8 seconds. The straight line on the floor can be used as a guideline. Below are the videos of the trim procedure for different inputs of trim_write() (from the module easygopigo.py) :
The trim value of -7 looks best from this test although in the morning my best value was -6. The driving direction seems to be very sensitive to the smallest changes in the trim value. The backward driving is not ideal either and it’s probably due to the serious wobbling of the motor shafts (see my initial post). In the beginning the trim procedure was a bit confusing because trim_write(0) correspond to the value of 100 obtained by trim_read() and trim_write(-7) results in 93 from trim_read(). Now it’s clear how these values are obtained but it would make more sense to return the same values by trim_read().
The overall result is passable but I have to admit that I got a bit disappointed with the quality of the motors/encoders in GoPiGo2. As far as I understood, you have significantly improved them in the newest version of GoPiGo3 so I guess that’s the natural learning curve Thank you very much for your help and support on this forum!
Hello @cleoqc! I was wondering if the wobbling of the motor shafts (see the 3rd video in my first post) is typical for the GoPiGo2 motors and if it would make sense for me to try to order a motor replacement kit? Do you think it might improve the driving experience or is the issue mostly due to the encoders? If I decide to order a motor replacement kit, would it be possible to deliver it to Europe (Belgium) or do you maybe sell it in Europe via distributors? Thanks a lot!
I do not know if our European distributors still have the old motors. You could order a new set with us, however I’m not certain it will help all that much. The motors/encoders were the biggest improvment from version 2 to version 3.