[Gghc-discuss] Software task - get two arduinos talking with I2C, and design a protocol

[Brian Duggan]

Ah, I get it. Thanks, I didn't understand what the specific implications
were, but that cleared it up.

On 4/17/11 4:58 PM, Jonathan Manton wrote:
> No, no change of platform.  
> 
> First, the user still plugs their own arduino in.  So we still need all the unos, one for each duinolab.  My suggestions are about the part of the 'lab that controls the LCD, the 72 LEDs, and the switches to connect/disconnect the knobs/buttons/etc to the breadbord or the user's arduino.
> 
> What I'm suggesting for that is plug-and-play arduino compatible.  Someone else (the sanguino project) has already done all the work to port the arduino bootloader, and all the compiled user code is binary compatible.  The differences are there, but very slight.  So we can use the unos for development.  We might have to change pin assignments later in the code (uno has 20 i/o pins, this has 32), but those should be #defines at the top of the code.
> 
> 
> 
> On Apr 17, 2011, at 3:50 PM, Brian Duggan <bcdugga at gmail.com> wrote:
> 
>> In Jonathan's last mail he suggested switching platforms... he'll have
>> to show me since I didn't follow everything.
>>
>> So if we're using different packages in the final product that aren't
>> full-fledged Arduinos, can we use the Unos in the Makerspace to develop
>> this communication lib? Or do we need different hardware?
>>
>> On 4/17/11 2:27 PM, Colten Jackson wrote:
>>> So I'm sitting at radio marias on my laptop programming and my waiter
>>> says "hey, doing some coding? I've been getting into arduinos myself"
>>> and I say "you know, there's a club..." so we've got another guy very
>>> excited about helping out. Just wanted to throw a quick story up on here.
>>> On Apr 17, 2011 1:56 PM, "Jonathan Manton" <jmanton at illinois.edu
>>> <mailto:jmanton at illinois.edu>> wrote:
>>>>
>>>> We need to have 2 arduinos talking using I2C (using digital pins
>>> *other* than 0 and 1, so it should use the SoftwareSerial library).
>>> Also, we need an I2C protocol that is compatible with the LED
>>> controllers, and can turn on and off the LEDs, turn on and off the
>>> analog and digital switches, and display stuff on the LCD.
>>>>
>>>> _______________________________________________
>>>> Gghc-discuss mailing list
>>>> Gghc-discuss at lists.chambana.net <mailto:Gghc-discuss at lists.chambana.net>
>>>> http://lists.chambana.net/mailman/listinfo/gghc-discuss
>>>
>>>
>>>
>>> _______________________________________________
>>> Gghc-discuss mailing list
>>> Gghc-discuss at lists.chambana.net
>>> http://lists.chambana.net/mailman/listinfo/gghc-discuss
>>
>> -- 
>> Brian Duggan
>> Technical Projects Developer
>> UC Independent Media Center
>> http://www.ucimc.org | 631 223 8442
>> _______________________________________________
>> Gghc-discuss mailing list
>> Gghc-discuss at lists.chambana.net
>> http://lists.chambana.net/mailman/listinfo/gghc-discuss

-- 
Brian Duggan
Technical Projects Developer
UC Independent Media Center
http://www.ucimc.org | 631 223 8442