I'm working on a basketball score keeping project and would like your advice on the best way to approach this.
The project consists of two elements:
1. A basketball hoop
needs to detect when ball has passed the ring > was thinking of an IR beam break sensor.
(optionally it could also detect the direction the ball passed the ring > two ir sensors?).
needs to detect when ball hits the board / ring > was thinking of an Fast Vibration Sensor Switch
when either happens board lights up > LED strips.
needs to keep track of score (ignore 3 pointers etc, just count the number of balls that passed the ring).
needs some way of resetting
I'm guessing one arduino uno / mega board should suffice for this.
2. 4 Screens displaying the score
should be able to display score / rss feeds / play animations / videos
should respond instantly when a point is detected.
keeps track of overall statistics
content needs to be able to change remotely
I don't see much issues wiring-up and programming the first part, my main concern is the communication between the two. Ideally they would need to work on remote locations over the internet. I'm a noob when it comes to networking.
What would be your approach?
I'm considering to hook up the arduino to a pc, use the pc to generate a website and display that website on he screens through two raspberry pi's. Do you think that makes sense?
I assume You've seen real basketball games? I would drop the idea applying any equippment to the basket. If duncing players don't pull the sensor down the bounces, mechanical shocks will shorten the lite of such a device. A human finger pressing a button would be the safest.
Yes I've seen real basketball games The application here is not real game context but is more an art installation, 3 pointers, etc don't matter. Nevertheless, shock resistance and longevity something to think about.
So far I have been able to use arduino + firmata + P5.js + P5.bots to make a website that responds instantly to sensor input and counts button presses. This works fine on localhost, but if i connect to the that pc through another device on the same network I get a static version of the website.
You can use two break beam sensors, perpendicular to one another, crossing at the middle of the hoop right above (or below) it. That way when the ball falls through the hoop it breaks both beams, but only when it falls through both beams are broken. If you miss the hoop only one (or no) beam gets broken. No sensor on the hoop!
You may have wrong counts when the ball bounces off the hoop, or a few times on the hoop before falling through. That can be addressed with basic button debounce code - just make the timeout in which new triggers are ignored a bit longer than the common 10-50 ms as used for buttons.
The application here is not real game context but is more an art installation, 3 pointers, etc don't matter. Nevertheless, shock resistance and longevity something to think about.