<div>So I have the physical holding designed and can meet sometime tomorrow to work on it and make sure if it needs alterations. I can then begin working on some of the documentation.....case use, step by step, and some of the others. </div>
<div> </div><div>If you want to meet tom. call or txt 217 402 0488. You will get me much faster by phone </div><div> </div><div>Sam<br><br></div><div class="gmail_quote">On Sun, Apr 24, 2011 at 11:40 PM, Jonathan Manton <span dir="ltr"><<a href="mailto:jmanton@illinois.edu">jmanton@illinois.edu</a>></span> wrote:<br>
<blockquote style="margin: 0px 0px 0px 0.8ex; padding-left: 1ex; border-left-color: rgb(204, 204, 204); border-left-width: 1px; border-left-style: solid;" class="gmail_quote">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.<br>
<br>
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.<br>
<br>
I'm also really brain-fried, so apologies in advance if I'm not making a lot of sense.<br>
<br>
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.<br>
<br>
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).<br>
<br>
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 <a href="http://tech.chambana.net/projects/duinolab/wiki/Pinouts" target="_blank">http://tech.chambana.net/projects/duinolab/wiki/Pinouts</a>).<br>
<br>
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.<br>
_______________________________________________<br>
Gghc-discuss mailing list<br>
<a href="mailto:Gghc-discuss@lists.chambana.net">Gghc-discuss@lists.chambana.net</a><br>
<a href="http://lists.chambana.net/mailman/listinfo/gghc-discuss" target="_blank">http://lists.chambana.net/mailman/listinfo/gghc-discuss</a><br>
</blockquote></div><br>