11-10-2011 05:34 PM
Thank you very much Hornless rhino!!!
I tested your your advice before applying it into my vision application i.e. see computing data feedback
It is a vi which shows the present value and the value of it 2 seconds later, with a ew valu replacing it!
Now it is easy to use this principle into my experiement and with ease I have suceeded. Attatched is the code! But it doesnt work well because when I do not move the penny, it still outputs a speeds in meters/second. I am sure that the because of my lighting and contrast - it is detecting more objects than just the penny and so due to this, the x y coordinates keep changeing.
Oh - thanks for the "continous play" solution you resolved. Im soo silly, I can not beleive how careless I could be by making the while exit condition as "continue if true". Thanks for pointing this out to me.
Now all the basic steps are done. Actually I inserted a delay of 2 seconds to see if the algorithm was working correctly in the penny experiment. However, I think the current vision script I am using is not good, so will use the script I have attatched in this post. Will progress onto tomorrow/weekend and tweak my code so that I only JUST detect my penny.
.................
So only a few steps now before I move to stereovision. At the moment, logitec have still not replied to me about the query I sent them about how the focus length changes whn the lens is turned say half ways. Once I get this information, and sort my final steps on the penny experiment - I shall actually begin to compute stereovision.
Then the challenge will be to implemnt it onto the ball of course. Anyways, I will post again soon, and any tips in advance will be great.
Saqib