Seemed like a simple enough task. Too simple, in fact. After working up a straightforward program and defining the base hardware, we naturally progressed to planning a Wi-Fi interface so the counter could be accessed and reset remotely. That would require a simple web page, and maybe a couple hours of programming. We even evaluated a solar powered charger to obviate the need for a plug-in charger.
With plans in hand, we stood back, looked at the hardware and software involved, and the total cost. Then, we revisited the requirements. After a sanity check, we decided the complex Arduino-enabled survey device was overkill.
Starting over without a preconceived product, we identified a solution of five digital mechanical tally counters (or clickers) sold for coaches. We found suitable counters ranging from $2 to $5 each on Amazon. The counters — each the size of a walnut — easily fit on a plastic face plate with cutouts for each counter. And it worked. No batteries to worry about. No programming. And fully reusable counters once the survey was finished. Sure, there was no web interface and no way to check the tally at home on a smartphone, but there wasn’t a need.
The take-away from my experience was to avoid preconceived solutions to new problems. Sometimes expertise in one area unnecessarily narrows the range of options that should be considered when assessing a problem.
The caveat, of course, is that you shouldn’t pass up a chance to learn and expand your skill set. If your goal is to learn to work with an Arduino or other microcontroller and you have the time and funds, then go for it. Given the challenge above, why not have that Wi-Fi interface? Or, automatic cloud upload?
Go wild with the web interface, with visual and audible alarms, and graphics. Just don’t lose touch with what features and functions are really required. Experimenting is fantastic, but know when and how to apply your skills to practical problem solving. NV