ooPIC S in the loop. Otherwise the high value data and clock resistors
need to be used. No one can explain this oddity, but it has something
to do with the PIC 16F877a part.
DLC
red71956 wrote:
> Hi
> The explanantion of the bug (in the Programming Guide section on DDE
> regarding linking 2 Oopics together) is unclear to me.
> Will using 22k to 33k pullup resistors on the data and clock lines of
> the I2C 'usually' allow communication to succeed with 2 Oopic Rs?
> Or is an Oopic 'S' needed AND the pullups? Is the remark about using
> 2.7k pullup resistors on the Data and Clock lines superceded by
> the 'Bug Workaround'?
> I THINK it reads EITHER an Oopic S OR the pullups have to be on the I2C
> network, with an Oopic S being the more certain method of getting 2 R
> boards to talk together.
> Am I parsing the explanation too much?
> I just don't want to release the 'magic smoke' from my boards!
> Thanx in advance!
>
>
>
>
> Yahoo! Groups Links
>
>
>
--
------------------------------------------------------
Dennis Clark ooPIC Tech Support
www.oopic.com
------------------------------------------------------
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/oopic/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/oopic/join
(Yahoo! ID required)
<*> To change settings via email:
mailto:oopic-digest@yahoogroups.com
mailto:oopic-fullfeatured@yahoogroups.com
<*> To unsubscribe from this group, send an email to:
oopic-unsubscribe@yahoogroups.com
<*> Your use of Yahoo! Groups is subject to:
No comments:
Post a Comment