Skip to content
admalledd edited this page Feb 7, 2012 · 2 revisions

We have many ways for the suit to connect to its internal electronics and also talk to the game server so long as:

  • communicates to the server over TCP/IP
  • can handle json encoding/decoding
  • able to communicate to the atmega328's in some fashion (no matter what if you change the processor you need to re-write the communication to them)
  • display data to a screen of some sort
  • process fast enough to keep up with all this work
  • make noises (gun shots, power down etc.)

current plan is to go with the RPI which is a awesome computing platform that only costs 35$. however, it is not complete on its own for the processing, we must also add WIFI and a display. (input as well, but that is part of the atmega mesh)

For wifi a simply wifi USB dongle that is compatible can be used (any ideas on suit tracking using wifi?)

The real hurdle will be the screen and the GPIO breakout. The screen will probably be some simple phone screen replacement or a small HDMI screen or even a USB screen (full color screen is recommended, got to be able to look more modern than 18x2 LCDs). the GPIO breakout that will let us communicate to the atmega's will probably not be the GERT board being developed by the RPI foundation, simply because it is a very general part and thus costs more and is complicated. The plan that is currently recommended is to use the I2C bus and use the RPI as a master polling all the atmega's for information as well as updating the RGBLED's

other options that remain in my notbook: Android phone with one of these methods of communication to the atmega's:

  • ADK (IOIO or otherwise)
  • ADB (arduino USB required)
  • dailtone (use the audio in/out of the android to communicate, sadly means no noise from the android)
Clone this wiki locally