[Gghc-discuss] Need to meet Monday to figure out what we do for the rest of the time

[Chris Ritzo]

In reference to project menagerie, :) If folks like this direction, I'll
push this to the repo as our TO DO LIST under documentation. - Chris

Given the remaining things that need to be done and that Jonathan's
suggestion is to stop prototyping on breadboards, I might suggest that we
begin working on the second prototype now. Please correct me if any of this
doesn't make sense:

While the advantage of the first one, breadboard style, would be to enable
software development, we should move forward with the hardware as a final
deliverable. We'll still have it fabricated and ready to be taken to the
next level once software is done.

In tandem, software development can continue on the code for each module.
This can be done via breadboard using the circuit planning that Jonathan's
done, and separately from the actual full prototype (at first). Assuming the
modules are meant to be modular, we can assume that the software for each
will be modular as well.

Perhaps these ideas will help focus a general discussion tonight. I can meet
later, after 5:30 sometime. Also, here's a start on tasks and possible
assignments:

1. fabricate all remaining components, begin assembly
(Jonathan, anyone else who can help)

2. software development on breadboarded modules
(Erich, Brian)
- decide which modules are essential, focus on software for core modules
first, then additional

3. organization, documentation, general help & assistance to both #1, #2
(Chris, Sam)
End user docs
- what is duinolab? (draft)
- how-to documentation (not started)
- what can I do with it? teaching plans, etc. poach the internet for
this(not started)

Project docs
- anything that needs to be submitted to element 14

On Sun, Apr 24, 2011 at 11:40 PM, Jonathan Manton <jmanton at illinois.edu>wrote:

> We need to have a discussion tomorrow evening on how the next 8 days are
> going to play out.  We are getting really, really close on this.  I'm
> getting really nervous.
>
> I am especially nervous about ordering stuff to build the final version, as
> that stuff would have to be ordered like Monday or Tuesday night.
>
> I'm also really brain-fried, so apologies in advance if I'm not making a
> lot of sense.
>
> I've been totally heads-down trying to get the hardware made.  It turns out
> there are just too many freakin' wires everywhere (72 LEDs, all the routing
> between the 18 different peripherals) to practically build the thing on
> breadboards.  So it needs to go on circuit boards.
>
> But there are a lot of other things that need to get done.  We don't seem
> to have much in the way of task organization for this, so I'm not even sure
> *what* has to be done.  We have a start on that (what Sam typed up), but it
> really needs to be taken to the next level, and someone needs to do a bit of
> organizing and project management.  I really can't do that, and have any
> chance in hell of getting this thing built in time for people to write
> software for it (new target - Wednesday).
>
> One thing I will say - as part of prototyping this thing, I *do* have
> Arduino code to turn on and off an indicator LED, and to do the actual
> switching of the peripherals.  I also have a detailed map of what pin on
> which controller (I/O or LED) maps to what LED or peripheral actually on a
> board (current version at
> http://tech.chambana.net/projects/duinolab/wiki/Pinouts).
>
> You can design software assuming that you will have a simple, 1-line piece
> of code to turn a light on or off, or to switch a peripheral on or off.
> _______________________________________________
> Gghc-discuss mailing list
> Gghc-discuss at lists.chambana.net
> http://lists.chambana.net/mailman/listinfo/gghc-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.chambana.net/pipermail/gghc-discuss/attachments/20110425/5947a520/attachment-0001.html>