>Here's the real crunch : when doing a multiple PIC project, where the PICs
>talk to each other, to pass this information between different MPLAB
>processes (tricky, but do-able!)

OLE! What everyone will say when they do it that way? :)

Its not that tricky to do the message passing, it is the sorting out where
it comes from/goes to is the tricky part. Probably have to do it by naming
signals. Also have to have a processor speed synchronisation - if two
processors are running at the same speed then you want them to run
approximately in step in the simulation, not one appearing to be at 4MHz and
one at 3.8MHz when both are spec'd at 4.

The other thing I would like to see is the configuration file for a given
piece of code maintaining pin names for that processor so when you go to the
stimulus menu you can see immediately which pin to toggle instead of
relating Pushbutton_2 to RB.0 in your head.

--
http://www.piclist.com hint: To leave the PICList
mailto:piclist-unsubscribe-request@mitvma.mit.edu