meadl-devel team mailing list archive

[Jorge Silva <jorge.silva@xxxxxxxxxxx>]

Hola Ambuj,

  This is a good overview, the Morse part is something we haven't
thought about yet and seems fitting with your interests. Could you
please do the following:

1. Sign up to the wiki: http://tiny.cc/k2hjn
2. Start a blueprint: http://tiny.cc/addspec so we can flush out the
specifications of a Morse to text solution
3. Add a link to the wiki from the blueprint you created (is part of the
form). Something like http://wiki.scyp.atrc.utoronto.ca/w/MorseInput
will work
4. Add placeholders for the sections of the spec on the wiki link you
created above. Add at least the following:
  * Goal
  * Requirements
  * Implementation
5. Send a message to the mailing list: meadl-devel@xxxxxxxxxxxxxxxxxxx
to let everybody know what you are working on (including links to the
blueprint and the wiki page).

Once this is done we can get started with the research for the spec,
which, depending on what we find, might take a couple of weeks... then
comes coding.

Something else you should know is that the serial port profile we are
using with the bluetooth connection makes the channel look like a serial
RS232 port on both sides. That means we should research previous work on
Morse-type protocols implemented over RS232. That way we won't have to
reinvent the wheel.

cheers!
Jorge

On 05/14/2010 06:16 PM, Ambuj Varshney wrote:
> Hi Jorge,
> 
> I have been going through mEADL wiki located at :
> http://wiki.scyp.atrc.utoronto.ca/w/MEADL
> 
> I have gone through basic tutorial on Bazaar, and have a fairly descent
> understanding of it.
> 
> Naively based on my understanding of mEADL, I feel I can best contribute to
> programming of Arduino board.
> 
> Programming Arduino, is much simpler to what I have been doing here.
> 
> Arduino defines its own programming language and IDE , which is very simple
> to program, as it provides higher level primitives which make life
> considerable simpler for people with little experience in programming
> microcontroller - compared to using pure C and manipulating ports , bits and
> register.
> 
> I am more comfortable working at relatively lower level of abstraction -
> working with ports and registers; So, I would have to learn Arduino
> programming language but it shouldn't be difficult as I have a fairly good
> idea of how things work underneath those higher level calls.
> 
> My Naive understanding of how things would work is -
> 
> Arduino board receives input from ACU of the wheel chair of status of
> different switches, based on which microcontroller would interpret these and
> send appropriate command to the manager application on Mobile device using
> Bluetooth.
> 
> Manager application on Mobile device would based on input perform different
> operation - like chosing a certain application, taking input.
> 
> Issue then that would need designing is -
> 
> - Reading Input from ACU interpreting it, sending it in an appropriate form
> and format to the Manager application using bluetooth which would need
> writing code for reading status from ACU and communicating with Manager
> using bluetooth.
> 
> - For taking Text Input - In case of Morse code  scheme - Interpreting input
> of ACU(Switch Gesture) and sending relevant text to Manager
> 
> Above would be interpreted at Microcontroller and relevant text sent to
> Manager application.
> 
> - For taking Text Input using OSK - The keys would be interpreted as
> different way to traverse keyboard and relevant location would be sent.
> 
> The task I could work on -
> 
> (a) At Microcontroller/Arduino side -  Interfacing with ACU , Interpreting
> switches states and sending relevant command to manager application; Taking
> Text Input using Switch Gesture ( We would need to define switch gesture we
> want to use  for this ), Interpreting text and sending it to Manager
> application.
> 
> (b) Manager side (Android ? ) - Working on Interface to receive and
> interpret command(s) from Arduino-BT board , and based on command/text
> received performing desired action. ( OSK maybe )
> 
> 
> P.S : The above may sound bit vague, I am still understanding the problem
> space.
> 
> Thanks,
> Ambuj Varshney
> 
> 
> 
> linuxondesktop.blogspot.com
> everything related to running linux on desktop
>