Just use an i2c bus or spi bus for everything. In i2c every device has an address so you can communicate with each one over the same bus so you only need one. Same with spi except you have enable lines which makes things a bit simpler.
You should not need to add more interfaces or chips unless you need more I/O pins imo.
Last edited by marto on Sat Apr 02, 2011 11:41 am; edited 1 time in total
Sat Apr 02, 2011 11:01 am
dyrodium Experienced Roboteer
Joined: 24 Aug 2004
Posts: 6476
Location: Sydney
I played with these during my robotics project, I didn't learn the programming side of things but regarding controlling with I2C it was dead easy, easy to address and control.
http://www.sparkfun.com/products/8579
They sell a USB to I2C converter too which works well. _________________ ( •_•)
Joined: 16 Jun 2004
Posts: 11802
Location: Sydney, NSW
That's another good reason for using I2C; I have one of the Max blinkm boards that can be used as a totem-pole countdown. Keep in mind that I am a complete noob compared to most of the forum members, so this as much a learning exercise as building a practical product.
Sat Apr 02, 2011 11:44 am
seanet1310
Joined: 08 Nov 2006
Posts: 1265
Location: Adelaide
There is a lot of info on the net about I2C. Your MCU probably has some libraries if it had a servo one.
A lot have I2C registers that make life somewhat easier.
Best way to learn is jump in with a task _________________ Remember to trust me, I am an Engineer.
Joined: 16 Jun 2004
Posts: 11802
Location: Sydney, NSW
If anyone else needs more serial ports then they have, the MAX3100 is an ideal solution - SPI in, RS 232 out. Use some select lines and you could have dozens of serial ports
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum