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.

Thursday, December 6, 2007

Re: [oopic] Re: Speed of I2C clock in OOPic R

Richard,

I remember measuring this once, you are close. The I2C speed is not
high since it is bit-banged.

DLC

rtstofer wrote:

>--- In oopic@yahoogroups.com, "Samitha Ransara" <samitharansara@...>
>wrote:
>
>
>>Hi,
>>Can anyone tell me the clock speed of I2C bus used in OOPic R module?
>>because this is essential when communicating two microcontrollers
>>
>>
>(such as
>
>
>>OOPic and Microchip Pic ex: 16F877A) via I2C bus.
>>
>>Thank you very much.
>>
>>
>>Regards,
>>Samitha Ransara
>>
>>
>
>Unless you are connecting two OOPIcs with oDDELink, you won't be using
>the internal I2C hardware. You will be using the bit-banged local I2C
>bus that also connects to the EEPROM. It is quite SLOW! Maybe 16 kHz
>or so...
>
>Richard
>
>
>
>
>
>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: