Chief Delphi

Chief Delphi (http://www.chiefdelphi.com/forums/index.php)
-   Programming (http://www.chiefdelphi.com/forums/forumdisplay.php?f=51)
-   -   Implementing Traction Control for an advantage in the 2009 game (http://www.chiefdelphi.com/forums/showthread.php?t=71172)

krupinski 09-01-2009 23:46

Re: Implementing Traction Control for an advantage in the 2009 game
 
I'm not sure who said it but i know some one mentioned before about using an accelerometer to sense drift and turn the wheels perpendicular to the direction of unwanted travel... my team also had a similar idea but threw it out ( for now) due to the fact that this will only make a difference if the deflection of the floor is a [i]relatively[i] significant amount.. We started to reconsider when we found the regolith is over the carpet (or so we've heard) but are still unsure if it will have any useful effect.. if the floor doesn't deflect enough you get the same effect by just locking the wheels, or are we misunderstanding this concept?

RandomStyuff 10-01-2009 09:52

Re: Implementing Traction Control for an advantage in the 2009 game
 
If there is a project for trying to implement a common code base for the base of this an ABS-system-like idea, my team has a couple of programmers who would be willing to help... it could really be an interesting project to implement it together in a codebase for everyone

rsisk 19-01-2009 22:02

Re: Implementing Traction Control for an advantage in the 2009 game
 
Wow, what a thread. Wish I understood what half of it meant, although I did get a chance to learn the first, second, third derivatives of wheel positon are velocity, acceleration, and jerk.

We just started working on this today. We use a potentiometer to measure the rate the wheels are turning. If we see an increase of > 20% in the rate, we reduce the power to the wheels by 20%. Power keeps reducing until the rotational rate gets back below 20%.

May not be absolutely perfect, but we will hopefully get enough of an advantage to beat the teams that don't have traction control.

Unfortunately I think this puts us in the 'tinkerer' category isn't the second first derivative of tinkerer = engineer once you add in the velocity heading towards being able to calculate the results?

MikeE 20-01-2009 07:02

Re: Implementing Traction Control for an advantage in the 2009 game
 
Quote:

Originally Posted by rsisk (Post 804098)
Unfortunately I think this puts us in the 'tinkerer' category isn't the second first derivative of tinkerer = engineer once you add in the velocity heading towards being able to calculate the results?

Tinkerer + math => engineer

Bongle 20-01-2009 07:07

Re: Implementing Traction Control for an advantage in the 2009 game
 
We're going with a reverse-ABS route for our first attempt:
-If slippage detected, reduce motor power somewhat, then gradually increase it again

Slippage will be detected by comparing the reported acceleration of our encoders with the reported acceleration from our accelerometer.

IKE 20-01-2009 08:40

Re: Implementing Traction Control for an advantage in the 2009 game
 
For the Tinkerers out there. Please keep one thing in mind. ABS, ESP, Stability control..... All of these get tuned by very skilled evaluator/engineers. I have a friend who does this work for Bosch. Testing and tuning is not simply tinkering, it is engineering. They do however had a pretty good idea of what their algoritms need to look like and then tune them in.

IKE

Adam Y. 20-01-2009 19:21

Re: Implementing Traction Control for an advantage in the 2009 game
 
Quote:

Originally Posted by MikeE (Post 804261)
Tinkerer + math => engineer

This is the only field where being a tinkerer will mean that your robot will end up in twenty thousand little itty bitty pieces as it thrashes it around because your tinkering resulted in a system that mathematically would blow up the world (An Texas Instruments engineers words not mine) if it were not for the fact that your robot is powered by a battery.

waialua359 21-01-2009 22:16

Re: Implementing Traction Control for an advantage in the 2009 game
 
Our programmer challenged our 2 year driver to try and beat the traction controlled robot from one side of our field to the other.
The driver lost EVERY time!!

In conclusion, implement it if you can........:D :D

DonRotolo 21-01-2009 23:19

Re: Implementing Traction Control for an advantage in the 2009 game
 
Quote:

Originally Posted by rsisk (Post 804098)
We use a potentiometer to measure the rate the wheels are turning.

A potentiometer? Not exactly an optimal sensor, look up "encoder" for a better choice
Quote:

Originally Posted by rsisk (Post 804098)
first derivative of tinkerer = engineer once you add in the velocity heading towards...

Quote:

Originally Posted by MikeE (Post 804261)
Tinkerer + math => engineer

The difference between a Tinkerer and an Engineer is that the Engineer will be able to tell you the results before you start.

agmlego 22-01-2009 12:03

Re: Implementing Traction Control for an advantage in the 2009 game
 
Our team is looking into implementing an algorithm we found for a four-independent-wheel-drive electric vehicle ETS, using four encoders and a gyroscopic yaw-rate sensor. We will be enhancing it with the accelerometer to detect sideways skid and report to the driver, if not correct it.

EricS-Team180 22-01-2009 16:25

Re: Implementing Traction Control for an advantage in the 2009 game
 
Quote:

Originally Posted by agmlego (Post 805865)
Our team is looking into implementing an algorithm we found for a four-independent-wheel-drive electric vehicle ETS, using four encoders and a gyroscopic yaw-rate sensor. We will be enhancing it with the accelerometer to detect sideways skid and report to the driver, if not correct it.

Right now Warren B and I are trying to get our arms around Paul's "middle income" solution. But for those of you going for the "super rich" solution, I have found a few interesting places to look:

http://scholar.lib.vt.edu/theses/ava...ed/Thesis2.pdf

and here's some observer and alpha-beta filter explanations:

http://www.mstarlabs.com/control.html


Check out "rough Data, Smooth signals" and "When One feedback isn't enough"

I expect SPAM'll compete with the "middle income" solution at the Florida regional

cool stuff
Eric

agmlego 23-01-2009 09:08

Re: Implementing Traction Control for an advantage in the 2009 game
 
Hey, cool! I will definitely have the guys look in on those.

Bongle 23-01-2009 09:26

Re: Implementing Traction Control for an advantage in the 2009 game
 
Just a note:
We went to implement our accelerometer/encoder solution last night, and it wasn't as good as expected. This was partly because I hadn't totally thought it through and thought that simply comparing accelerations was going to be sufficient. I failed to realize the obvious fact that the encoder acceleration would not STAY above the accelerometer acceleration for long, so it is not a good way of telling when the wheelspin stopped. It was an excellent way of telling when your wheel started spinning, but since you can't easily detect when they stop spinning, the algorithm as I described it is not ideal.

We're going to have to get a bit more complicated, with either an estimated velocity from the accelerometer or a trailing wheel to get this working properly.

Jared Russell 23-01-2009 10:11

Re: Implementing Traction Control for an advantage in the 2009 game
 
You can try integrating the acceleration signal to get velocity, and then comparing velocities to detect slip. The problem is that a noisy accelerometer signal looks even worse once it's integrated. For this and other reasons (one being the simplicity of an apples to apples speed comparison in code), non-driven encoder wheels lead to a better solution to this problem in my opinion.

Bongle 23-01-2009 10:34

Re: Implementing Traction Control for an advantage in the 2009 game
 
Quote:

Originally Posted by Abwehr (Post 806474)
You can try integrating the acceleration signal to get velocity, and then comparing velocities to detect slip. The problem is that a noisy accelerometer signal looks even worse once it's integrated. For this and other reasons (one being the simplicity of an apples to apples speed comparison in code), non-driven encoder wheels lead to a better solution to this problem in my opinion.

Yeah, that's exactly what I'm thinking. Even with our rolling-average filtering, the accelerometer is ridiculously noisy.


All times are GMT -5. The time now is 12:23.

Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi