This user has no status.
This user has no status.
Member
I'd like to disagree. To move the racket fast enough is the easiest part. It can move so much quicker. The hardest part imho in this setup is to adjust the racket angle corectly to counter the spin and speed. We do it by adjusting our distance to the table, the force of our stroke and counterspinning the ball with full swing topspin. The robot is more or less blocking. So angle is crucial and subtle miscalculation can result in the ball flying of the table...
Sent from my SM-G935F using Tapatalk
No. To beat a world champion, the easiest and cheapest part is is probably the racket angle actually.
The motor required to change racket angle is extremely simple, small, fast and accurate. They are also relatively cheap. Also the calculation in determining the racket angle is relatively simple and quick to perform. Actually calculations to perform any of the tasks required to beat a world champion would be fast enough on any reasonable consumer grade GPU from the current or previous architectures.
To hit back a shot from the optimal position for a sequence of wide balls to differing parts of the table (or just fast balls from 1 point in space to another different point in space over a long distance), the entire racket must move from one exact position to another exact position metres away in three domensional space within a very short period of time. Accelerating and decelerating at great rates reliably spanned over multiple motors gets exponentially more difficult and expensive as the distance increases. If they are to keep the current set up (which I don't think they will), the frame needs to increase massively in size in all 3 dimensions, the issue here is that the lever lengths also increase therefore the accuracy of the motor must also increase and then calibration and tolerances start to become the issue. Some motors from the exact same production run simply won't be able to work with each other due to tolerances alone.
The motor setup required to do this are large, expensive and as far as I'm aware nothing exists right now to do something like that that is priced within reason, but it is Omron, so what would I know.
Also make note that Dan is aware of the robot's current deficiencies, moving to wide angles, quickly, hence why he never hits it wide and fast when possible, except maybe once.
Also, I'm surprised the robot actually needs sensors on the racket. Since cnn video rec is good and fast enough to be able to determine velocity, path and angle, I would say this must be done due to time constraints on the project since they're focusing mainly on the mechatronics side of this as opposed to the machine learning side of things. Well, I hope so.
Last edited: