|
Once you know how to implement what you want, there are always two challenges: the first is putting "it" together, and then after it's assembled, the larger problem seems to be "where did you leave the remote?". There are solutions for finding remotes already, so were not going to work on this problem.
Overcoming the initial inertial problem of "it works without the remote control" (would you even try to use a TV without a remote today?), implementation requires a full understanding of mechanical, electrical, and control logic for your application. We have implemented an entry control systems using a mobile phone whose number (Automatic Number Identification, ANI) is screened against a list eligible entrants - and we use it every day. What's new in this application, is someone who put together the electro-mechanical door opener with control database and the telecommunications network. And it seems to be a lot easier to keep track of the mobile phone than it is the typical remote; and if all else fails, you can "call" it, and unlike children, it usually answers when you do.
We would prefer to use a computer based browser interface to manage and control security or heating systems, or placing food orders, although you will soon find mobile phone (communicators?) with larger displays capable of doing this as well. The solutions for these are architecturally similar. They all require good user interfaces, databases where relevant access and authentication is contained, control logic, and legacy database and process interfaces. Again, putting it together and making it work is what we enjoy doing.
Let us know if we can help your bring your products to life.
|
