This Forum is Dedicated For all The Object Oriented PIC Lovers .......... The concept behind OOPic is straight forward. Use preprogrammed multitasking Objects from a library of highly optimized Objects to do all the work of interacting with the hardware. Then write small scripts in Basic, C, or Java syntax styles to control the Objects. During operation, the Objects run continuously and simultaneously in the background while the scripts run in the foreground telling the objects what to do.

Tuesday, April 15, 2008

Re: [oopic] Multiple I2C EEPROMS

Yes, this is perfectly OK and I've done it. Just track your addresses
and sure you don't conflict with the E0 (program) EEPROM.

DLC

tinslwc wrote:
> Has anyone ever attempted to use more than two EEPROMS on one OOPic.
> If I am reading the object correctly, you should be able to reconfigure
> the wiring to the A0, A1, A2 connections on the EEPROM chips to define
> a different I2C address and then when you specify the node in your
> program, you would use the actual address, not the constants E0 & E1.
> Are there two I2C controllers on the OOPic or do the on board EEPROMs
> use the same I2C bus as the IO lines (Lines 19 & 20). Just curiosity
> getting the best of me.
>
>
> ------------------------------------
>
> 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:

http://docs.yahoo.com/info/terms/

No comments: