Art Interface Device logo   Project description  Development   Mailing List  Contact


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: AID: [OT] PIC OSC Client

From: Ian Smith-Heisters   heisters0x09.com
Date: Tue, 26 Oct 2004 17:12:29 -0700

: Sent via the Art Interface Device mailing list: aid@interaccess.org
: Use your "Reply All" to  reply to the list, "Reply" for private response

Thanks for the tips. Unfortunately I don't have the money to go any 
other route than PIC at this point. On the other hand, it's a high 
priority for us to do this from the ground up so we know its workings, 
and so it can be truly GPL. My colleauge that's covering the networking 
side of things thinks that he'll be able to implement UDP on his own, 
and has rejected ideas of getting premade code :)

That's good to know about the WiFi. It's more of a long term wish/goal 
than something that we're planning on doing, so it's no sweat.

The downside of all this is that it may take us quite some time to get 
it running and be very buggy for a long time after that, as things made 
from scratch tend to be. It may fail altogether. We'll see. Thanks for 
the advice, we'll keep you posted.

-Ian

Jeff Mann wrote:

> : Sent via the Art Interface Device mailing list: aid@interaccess.org
> : Use your "Reply All" to  reply to the list, "Reply" for private 
> response
>
> Ian Smith-Heisters wrote:
>
>> Please forgive me if this is not the right forum for this question, 
>> but I've been following AID for some time, and believe that it may be 
>> one of very few projects that has looked at implementing OSC on the 
>> Microchip PIC, citing mention of such a project at 
>> http://www.interaccess.org/aid/list/msg00502.html
>
>
> The "OSC on a PIC" was my own project that I demo'd at InterAccess; 
> I'm not really part of the AID group, mostly lurking on the list...
>
> I did implement a very simple OSC client on the PIC18F452, using the 
> iosoft tcp/ip stack. It uses UDP. Unfortunately I can't distribute it 
> because of iosoft's licencing terms.
>
> I'm not sure if there's a decent GPL tcp/ip stack for the PIC. You can 
> download the source to a good stack from Microchip, but it's not GPL 
> (and doesn't have WiFi/WLAN drivers). You might be better off looking 
> at the Atmel chips for GPL stuff (tcp/ip stack, compiler toolchain, 
> etc.). Have a look at the "Ethernut" project for an example of what 
> can be done. They even have a WiFi driver for it (although I don't 
> think it actually works) - don't assume that if you get something 
> working with ethernet, that it's easy to add WiFi.
>
> The most stress-free solution would be to use a Rabbit module. It has 
> a reasonable amount of RAM (eg. 512k vs. the PIC's 1.5k) which would 
> make it pretty easy to just port the existing OSC client/server 
> toolkit stuff (I know at least one person who's already done that). 
> It's cheap (starting around $60US), and saves you trying to solder a 
> 100+ pin surface-mount ethernet controller chip to your PIC board. The 
> downside is you have to buy a developer's kit (~300US, or ~$600 for 
> the WiFi kit), and it's not GPL.
>
> cu later <Jeff
>
> :      messages saved at http://www.interaccess.org/aid/list
> :      unsubscribe/help requests to mailto:Majordomo@interaccess.org



:      messages saved at http://www.interaccess.org/aid/list
:      unsubscribe/help requests to mailto:Majordomo@interaccess.org