Hi All,
I've just started a project which initially involves automating the goal keeper on a Foosball table. It took us little time to write the software (Openframeworks + openCv) however the hardware is proving challenging and I would love to hear some of your advice.
Let's start with some numbers; given that the max speed for the ball is 10m/s and that the striker is 30cm away from the goal, this means for the best shot we need to achieve a response time of 0.030 seconds, or 30ms.
The software was coded in a way that the keeper always stays aligned with the ball. Therefore in the worst case scenario, if the ball is kicked at a maximum 20degree angle then the keeper has to travel 5cm within 30ms or a speed of 166cm/s.
Are these kind of response time/speeds realistic, if so can someone point me in the right direction? I've currently got a servo hooked up the Arduino (standard firmata) which is controlled by Openframeworks but it seems awfully slow.
Here's the current setup setup I've got so far:
I have a belt driven linear actuator powered by a nema 22 which I'll have full stepping at 8000 pulses/s giving me a max speed of 24m/s, hypothetically, I'd have to increase the number of teeth to 140 to achieve the target 166cm/s.
I appreciate this is a lot of info, but my electronics/motors experience is fairly limited and your input is much appreciated!
Thanks,
Charles
Belt and mounts not shown but the servo will be fixed to the rod and to the sliding guide rail. The belt will loop all the way round.
I've just started a project which initially involves automating the goal keeper on a Foosball table. It took us little time to write the software (Openframeworks + openCv) however the hardware is proving challenging and I would love to hear some of your advice.
Let's start with some numbers; given that the max speed for the ball is 10m/s and that the striker is 30cm away from the goal, this means for the best shot we need to achieve a response time of 0.030 seconds, or 30ms.
The software was coded in a way that the keeper always stays aligned with the ball. Therefore in the worst case scenario, if the ball is kicked at a maximum 20degree angle then the keeper has to travel 5cm within 30ms or a speed of 166cm/s.
Are these kind of response time/speeds realistic, if so can someone point me in the right direction? I've currently got a servo hooked up the Arduino (standard firmata) which is controlled by Openframeworks but it seems awfully slow.
Here's the current setup setup I've got so far:
I have a belt driven linear actuator powered by a nema 22 which I'll have full stepping at 8000 pulses/s giving me a max speed of 24m/s, hypothetically, I'd have to increase the number of teeth to 140 to achieve the target 166cm/s.
I appreciate this is a lot of info, but my electronics/motors experience is fairly limited and your input is much appreciated!
Thanks,
Charles
Belt and mounts not shown but the servo will be fixed to the rod and to the sliding guide rail. The belt will loop all the way round.