... | ... | @@ -287,7 +287,7 @@ When running this way, the robot is far from reliable, since the smallest error |
|
|
Likewise, any changes in the environment (track) will almost certainly result in a failed run. We encountered dust and dirt at some point on the track, which made one of the wheels spin out. This made the robot drive off at a slight angle, something that made it drive off the track on the way down again.
|
|
|
Theoretically the fastest possible run for this rigid type of hard coded approach would be 27 seconds, but the robot itself is not able to accelerate accurately at that speed (x3), as one wheel often spins out. This is because of lack of grip of the cheap rubber tyres and the robot trying to accelerate instantly to the required speed.
|
|
|
|
|
|
[![image alt text](https://youtu.be/k87g1pU_4cc)
|
|
|
[![image alt text](http://img.youtube.com/vi/k87g1pU_4cc/0.jpg)](http://www.youtube.com/watch?v=k87g1pU_4cc)
|
|
|
##### Fig. 19 - video showing the “proper” run (featuring Rasmus as assistance)
|
|
|
|
|
|
| Pros | Cons |
|
... | ... | |