Raymond Choat wrote:
>
>Got it fixed. Something you said gave me the idea to look more at my timing
>of things. Then I got the idea that maybe the slave is not fast enough
>putting the _busy signal to low (showing busy) that would have the Master
>wait. So I just added the pause below and it worked. Thanks for bouncing
>the
>ball with me.
>

Glad to see that you got things working. As long as your speed requirements
aren't particularly high, this approach will certainly work. Giving the
slave enough time to recognize and respond to its incoming command will let
your master always see a valid '_busy' signal.

If you encounter a similar situation with tighter speed constraints, you may
find that using a fixed delay is too slow to meet your comm  requirements.
In that case, a 'wait for busy', 'wait for not busy' handshake mechanism
will allow communication to run as fast as your slaves will allow.

Regards, Bob

_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp

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