Searching \ for '[PIC]: Communication Between Multiple PIC16F877' in subject line. ()
Make payments with PayPal - it's fast, free and secure! Help us get a faster server
FAQ page: techref.massmind.org/techref/microchip/devices.htm?key=16F
Search entire site for: 'Communication Between Multiple PIC16F877'.

Exact match. Not showing close matches.
PICList Thread
'[PIC]: Communication Between Multiple PIC16F877'
2001\11\06@014142 by Donovan Parks

flavicon
face
Hello,

I am using 3 PIC16F877 in a project and the need limited communication between them.  Specifically, there is a "master" PIC that needs to communicate with two "slave" PICs.  These "slave" PICs never need to talk to each other or to the "master" PIC.  What would be the recommended protocol for implementing this small network (I2C, SPI, multi-drop serial(?), PSP)?  I need to send approximately four bytes of data to each "slave" PIC at 10Hz.

Thanks,
Donovan Parks

--
http://www.piclist.com#nomail Going offline? Don't AutoReply us!
email spam_OUTlistservTakeThisOuTspammitvma.mit.edu with SET PICList DIGEST in the body


2001\11\06@074746 by Olin Lathrop

face picon face
>>
I am using 3 PIC16F877 in a project and the need limited communication
between them.  Specifically, there is a "master" PIC that needs to
communicate with two "slave" PICs.  These "slave" PICs never need to talk to
each other or to the "master" PIC.
What would be the recommended protocol for implementing this small network
(I2C, SPI, multi-drop serial(?), PSP)?  I need to send approximately four
bytes of data to each "slave" PIC at 10Hz.
<<

You total data rate requirement is only 40 bytes/second, which is very low.
I consider IIC the best architecture for this kind of situation for clock
rates up to 400Kbits/second.  You could do IIC at 100KHz clock.  This keeps
everything at very comfortable limits and still allows for significant
future expansion.  The reason for chosing IIC is that the low level protocol
includes addressing and it's handled directly by the PIC hardware.  Don't
forget the extra cap on the SDA line.


********************************************************************
Olin Lathrop, embedded systems consultant in Littleton Massachusetts
(978) 742-9014, .....olinKILLspamspam@spam@embedinc.com, http://www.embedinc.com

--
http://www.piclist.com#nomail Going offline? Don't AutoReply us!
email listservspamKILLspammitvma.mit.edu with SET PICList DIGEST in the body


2001\11\06@093920 by James Paul

picon face
Donovan

If it were me doing this, I would bus the PSP of all three chips together.
That would make it simple and fast.  Of course you don't mention how many
pins you have available for communication, but I would go for the PSP
solution if I had the pins available.   If I didn't, I'd probably go with
I2C.  That would only use two pins.  Anyway, that's what I would do.
Hope it helps.

                                             Regards,

                                               Jim


{Quote hidden}

--
http://www.piclist.com#nomail Going offline? Don't AutoReply us!
email EraseMElistservspam_OUTspamTakeThisOuTmitvma.mit.edu with SET PICList DIGEST in the body


2001\11\06@232026 by James Caska

flavicon
face
Hi Donovan,

Virtual Breadboard V1.1 now has a PIC16F877, Tutorial 20 pretty much does
exactly what you desribe using I2C Master and 3 Slaves

Take a look :-)

www.virtualbreadboard.com/READ/vbb/Help/Packages/PICMICROS/Tutorials/
Features/PIC16F87X/Tutorial%2020/Tutorial%2020.htm


Regards,
James Caska
caskaspamspam_OUTvirtualbreadboard.com http://www.virtualbreadboard.com
ujVM - 'The worlds smallest java virtual machine'

{Original Message removed}

2001\11\07@194915 by Donovan Parks

flavicon
face
Hello,

> You total data rate requirement is only 40 bytes/second, which is very
low.
> I consider IIC the best architecture for this kind of situation for clock
> rates up to 400Kbits/second.  You could do IIC at 100KHz clock.  This
keeps
> everything at very comfortable limits and still allows for significant
> future expansion.  The reason for chosing IIC is that the low level
protocol
> includes addressing and it's handled directly by the PIC hardware.  Don't
> forget the extra cap on the SDA line.

Extra cap on the SDA line?  Is this cap something specific to the PIC16F877
(it isn't meantioned in the Philips I2C-bus specification).  What value of
cap should I be using and why?  Thanks.

Donovan

--
http://www.piclist.com hint: To leave the PICList
@spam@piclist-unsubscribe-requestKILLspamspammitvma.mit.edu


More... (looser matching)
- Last day of these posts
- In 2001 , 2002 only
- Today
- New search...