Hi,
I am fairly new to and illiterate in electronics. But I can be stubborn and am able to learn. I have set my mind to building the following device:
SHORT PROJECT DESCRIPTION
My goal is to have a programmable controller device which incorporates two element groups: 1: An acceleration-sensor and 2: a group of push-buttons and which acts in the following two scenarios (with scenario 1 being my intermediate goal, and scenario 2 another, more advanced goal) :
Scenario 1:
(1) Map Push-Buttons on the controller to keyboard keyboard-keys on a pc/laptop and
(2) map acceleration-sensor data to KEYBOARD KEYS on a pc/laptop
Scenario2:
(1) Map Push-Buttons on the controller to keyboard keyboard-keys on a pc/laptop and
(2) map acceleration-sensor data to MOUSE-MOVEMENT on a pc/laptop
ADDITIONAL CONDITIONS:
- The controller must transmit the data wirelessly.
- By programmable I mean e.g. something like a Sparkfun Pro Micro (https://www.sparkfun.com/products/12640) so I can configure different mappings of buttons to keys and different settings for how to handle the acceleration-sensor data.
(Like, control different games with the same device and be able to adjust sensitivity / acceleration-sensor data processing) - Acceleration sensor and the push buttons are disjoint - they do not reside in the same place and are not connected by cables. Actually, they behave like two different, isolated controllers which transmit their data independently and wirelessly. The push buttons form a group (like a handheld device with a few buttons).
- Acceleration sensor and the push buttons send data simultaneously and it must be processed simultaneously.
For clarification and to explain what I have thunk so far, please consider the attached image below.
WHAT I HAVE THUNK SO FAR:
- A pro micro seems to be a cost-efficient device which comes pre-configured to act as a keyboard, so I don’t have to mess with firmware and bootloaders to convince another board to act as a keyboard. Also, I have a pro micro, and the button-press to keyboard-mapping works like a charm (albeit, not wirelessly yet).
- There are so many wireless solutions. Which ones are best suited for my project?
2.1. Infrared looks tempting. Seems easy to use and the range limitations are not a problem. I dont need the controller more than a few feet away from the receiver. But it is only a solution for the push-buttons, right? Will I have to aim with the infrared transmitter, or will it work regardless of where I point it at?
2.2. For 433 MHz there are many ready-made solutions cheaply available, e.g. with four push-buttons. But I have read about regulatory limitations. 433 MHz can only be used for signalling for a short period of time and then it must be silent. I think.
2.3. 2.4 GHz seems to be the gold standard, which comes at a prize (in terms of being complicated to use/program and expensive equipment/modules)
2.4. Bluetooth for the acceleration-sensor data (and maybe also for the push-buttons? HC-05 modules seem inexpensive. - Why an accelerometer and no Gyro? Accelerometers seem easier to use and inexpensive. The adxl 345 looks very promising for my needs (love the built-in tap and double-tap functionality!): http://bildr.org/2011/03/adxl345-arduino/
MY QUESTIONS, WOES AND WORRIES:
a. Can the pro micro receive, process and transmit all this data simultaneously? It seems like it can, but I am not sure if with all wireless-technologies (e.g. only one Rx pin on the pro micro) chatting simultaneously if this will work.
b. What are the appropriate wireless-technologies for my uses?
c. Is bluetooth my solution? Is it possible to have two incoming bluetooth data-streams into my Pro Micro?
d. am I am on a stupid track with the Pro Micro, and there are much better solutions?
Any help would be greatly appreciated.
Thanks and regards!
Schroedingers_Kater
