Thanks Mike,

It looks like we will have one pic collecting data from a number of other
pics.  Thus, SPI sounds like the best solution provided we have enough pins
on the master for CS.  Can you recommend any sources of information for
implementing SPI amongst several pics?

Thanks again,
Donovan

> The advantages of SPI are: higher bit rate (Megabits/s possible on some
> devices), more simple and robust protocol (i.e. no start or stop
> conditions).  It is also more simple to bit bash SPI in software than I2C.
>
> The downsides of SPI are: Chip Select wire needed for every slave device.
> If you have several slaves, you'll be using up pins on your PIC pretty
> quickly.
>
> It sounds like you are going to require a Multimaster bus, which is
possible
> with I2C and Microchip even have an app note on this.
> I don't know about SPI and multi-master systems, it should be possible
with
> some kind of arbitration.  However, if your network 'o' PIC's really need
to
> talk to each other, i.e. any PIC and send and recieve to/from any other
PIC,
> then SPI is going to be hard work to implement.  I'd suggest sticking to
> I2C.
>
> Regards
>
> Mike
>
> --
> http://www.piclist.com hint: PICList Posts must start with ONE topic:
> [PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads
>
>
>

--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads