Today I started to look to put the board I assembled yesterday into my Arduino Mega based remote control (viewtopic.php?f=21&t=7422&start=124
). Right now I am trying to decide on IO pin mapping. Will probably start it's own thread, or could continue on with the other thread as well...
What I am currently looking at doing is to experiment with leaving the XBEE on USART0 (which is also used by the FTDI breakout board). It will be interesting to see how reliable downloading new programs over XBEE works... Things like,need to reset XBEE to not be in packet mode, then reset processor... May be simpler to leave it off until the compile completes and then turn it on... Will experiment. This has the downside that you can be harder to debug as you can not output data to serial port... Will work on some solutions for this, plus some can be output using other things like the LCD.
Will use the 2nd USART to talk to the OLED
Analog pins A0-A5 will use for the Original 6 analogs (2 per each joystick and 2 sliders)
My Extended Analogs X0-X2 will use for new ones (rotation on joysticks, plus middle slider)
X3-X5 are Free
X7 - Voltage monitor.
Digital Pin: 0-7 will be used for keypad.
8,9,10,11 - Are the IO pins used by USART0 and 1
12-15 - Command buttons - If we get tight can reduce this down to one pin (add a row or Column to keypad), like I did with BAP version.
16-17 - Buttons on top of joysticks
18-20 - Are free - (May experiment with using a button to do a reset for download), but could this in keypad pages...
21 - Sound
(22-23 and A6-A7) - Are used in the MUX...
If we desire to try a parallel LCD We can easily reclaim some IO pins. The switches and buttons can be added to the keypad logic. Also can use X5-X5 and potentially X6 (Solder in pin for it) can be used for buttons as well, but would probably need external PU added. May be able to rig it using the underlying PU of A6/A7 when testing for these button... May experiment.
That is all for now... Thoughts?