> > Unfortunately I have never gotten reliable NACKs,
> > most of my slaves never seem to NACK, which can be a pain since I can't
> use
> > that method to detect if they are there, but that's OK. I am
> also working
> > through a PC interface. TTYL
>
> Well, the above get's me confused.  You're saying that "most of my slaves
> never seem to NACK" .  That's quite normal.  If the Slave comes at the end
> of it's data-space, *most* of them just wrap-around, sending you the very
> first byte.
>
> Why do you want to have a NACK from a Device ?  The presence of an ACK is
> the proof that a Device is present.  A NACK can mean that there is no
> Device present at the choosen address, or that the Device does
> not want any
> more data ...  Take your pick. (meaning, it's not the way to go)
>
> Send a Write-address, and see if it get's ACK-ed.  If so , there is an
> Device present.  If not, ... well, you get the picture :-)

        Yes that's what I meant, none of my slaves seems to ACK, which is OK since
I use another method to detect them. TTYL

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.