I've been designing a wireless controller off and on (mostly off) for a while. Mine uses a touch screen to reduce the number of mechanical switches. Truth be told, I really don't need one. It's just a side project.
It works just like the wireless service at a Starbucks. There may be 10 people on the network, but you only get the information you request. You are automatically assigned a unique ID number (address) that is sent with every request. The computer reads this number, processes you request and sends it back with the same address.
For a wireless launch controller, the trick is that you send a command string from the launch controller to a microcontroller at the pad. The microcontroller decodes the command string verifies it's talking to the right microcontroller and launches the indicated pad(s).
This eliminates the chance of an unintended launch.
The microcontroller at the pad also sends a command string back to the launch controller with a report of which pads have continuity.
I believe most wireless chips have a built in, unique address to prevent the chance of any crosstalk. But even still, without the proper command, nothing would happen.
This is only one approach. I'm interested to hear what Flight4 comes back with.
By the way, to market a wireless launch controller, you would have to have it approved by the FCC and that is a whole different ball of wax...........
Last edited by Bone Daddy; 8th April 2011 at 03:15 AM.
Reason: Promoted Flight4 to Flight5. A well deserved promotion sir.
My life's goal is to be an idiot savant. So far, I'm only halfway there.