> need to use I2C. It seems so silly to make the hardware I2C widget
in
> the PIC unusable to talk to other sensor devices. This is looking
like
> it might turn out to be a real pain. I am just wondering about the
> logic or whether Savage Innovations is considering making a change.
>
> --
>
> 73 de Brian, WB6RQN
> Brian Lloyd - brian HYPHEN wb6rqn AT lloyd DOT com
>
I wouldn't count on the change... Sometimes there is just a limit to
what the OOPic can be expected to do.
I certainly wouldn't plan on hanging more than a couple of I2C
devices on the local bus. I did some code for an I2C ultrasonic
ranger and an I2C based LCD display. The update rate was GRIM.
In any event, the hardware I2C module is fully capable of talking to
the EEPROM and a general purpose I2C bus. Why it wasn't used escapes
me. Maybe because the code was derived from an even earlier chip
that may not have had an I2C gadget.
There are other microcontrollers...
Richard
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