<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Introduction to I2C</title>
	<atom:link href="http://www.uchobby.com/index.php/2008/09/16/introduction-to-i2c/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.uchobby.com/index.php/2008/09/16/introduction-to-i2c/</link>
	<description>Microcontrollers Electronics Hobby</description>
	<lastBuildDate>Tue, 24 Jan 2012 09:58:33 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: grinan</title>
		<link>http://www.uchobby.com/index.php/2008/09/16/introduction-to-i2c/comment-page-1/#comment-1452</link>
		<dc:creator>grinan</dc:creator>
		<pubDate>Wed, 15 Oct 2008 01:02:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.uchobby.com/index.php/2008/09/16/introduction-to-i2c/#comment-1452</guid>
		<description>well at first glance i would say that there is not a wire library for the attiny.  I don&#039;t think that the 13a will do i2c, although the data sheet says that you can use SPI to communicate with it.  That may be worth investigating.</description>
		<content:encoded><![CDATA[<p>well at first glance i would say that there is not a wire library for the attiny.  I don&#8217;t think that the 13a will do i2c, although the data sheet says that you can use SPI to communicate with it.  That may be worth investigating.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sushi</title>
		<link>http://www.uchobby.com/index.php/2008/09/16/introduction-to-i2c/comment-page-1/#comment-1451</link>
		<dc:creator>Sushi</dc:creator>
		<pubDate>Sun, 12 Oct 2008 15:17:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.uchobby.com/index.php/2008/09/16/introduction-to-i2c/#comment-1451</guid>
		<description>Now, if I want to setup an I2C network between my Arduino and an ATTiny13A, how would I do that? I don&#039;t think there is any type of wire library for the ATTiny. Is there?</description>
		<content:encoded><![CDATA[<p>Now, if I want to setup an I2C network between my Arduino and an ATTiny13A, how would I do that? I don&#8217;t think there is any type of wire library for the ATTiny. Is there?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Berni</title>
		<link>http://www.uchobby.com/index.php/2008/09/16/introduction-to-i2c/comment-page-1/#comment-1450</link>
		<dc:creator>Berni</dc:creator>
		<pubDate>Tue, 23 Sep 2008 05:14:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.uchobby.com/index.php/2008/09/16/introduction-to-i2c/#comment-1450</guid>
		<description>Well you could be running I2C at a too high speed, your line between them may be too long (I2C is only ment for a meter or two)Or a too big / too small pull up resistor

When you have 20 on the line you have to always wait while the line is busy so you don&#039;t transmit when someone else is already transmitting.

Also for this thing it may be better to use something called a CAN network.It works with a 2 wire twisted pair cable and goes  up to 1Mbit and up to 300m.(So if you renovate your house remember to put a twisted pair cable over the whole house and do some really cool house automatisation)</description>
		<content:encoded><![CDATA[<p>Well you could be running I2C at a too high speed, your line between them may be too long (I2C is only ment for a meter or two)Or a too big / too small pull up resistor</p>
<p>When you have 20 on the line you have to always wait while the line is busy so you don&#8217;t transmit when someone else is already transmitting.</p>
<p>Also for this thing it may be better to use something called a CAN network.It works with a 2 wire twisted pair cable and goes  up to 1Mbit and up to 300m.(So if you renovate your house remember to put a twisted pair cable over the whole house and do some really cool house automatisation)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: grinan</title>
		<link>http://www.uchobby.com/index.php/2008/09/16/introduction-to-i2c/comment-page-1/#comment-1449</link>
		<dc:creator>grinan</dc:creator>
		<pubDate>Tue, 23 Sep 2008 05:02:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.uchobby.com/index.php/2008/09/16/introduction-to-i2c/#comment-1449</guid>
		<description>I believe you will find I answered your question on the arduino forum, check here: http://www.arduino.cc/cgi-bin/yabb2/YaBB.pl?num=1220103333/20#20

This problem happens to me when I try to power both arduinos from usb at the same time.  To avoid this, I usually only use usb on one, the master, and the other i am running off of a separate power supply with no connection to the computer.</description>
		<content:encoded><![CDATA[<p>I believe you will find I answered your question on the arduino forum, check here: <a href="http://www.arduino.cc/cgi-bin/yabb2/YaBB.pl?num=1220103333/20#20" rel="nofollow">http://www.arduino.cc/cgi-bin/yabb2/YaBB.pl?num=1220103333/20#20</a></p>
<p>This problem happens to me when I try to power both arduinos from usb at the same time.  To avoid this, I usually only use usb on one, the master, and the other i am running off of a separate power supply with no connection to the computer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Seb</title>
		<link>http://www.uchobby.com/index.php/2008/09/16/introduction-to-i2c/comment-page-1/#comment-1448</link>
		<dc:creator>Seb</dc:creator>
		<pubDate>Mon, 22 Sep 2008 12:56:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.uchobby.com/index.php/2008/09/16/introduction-to-i2c/#comment-1448</guid>
		<description>Hi,

I&#039;ve set up a I2C with 2 arduino. Seems to be OK, messages are received but they are read with strange characters. Instead of reeiving &#039;hello &#039; i receive 6 characters looking like a quare. my grounds are connected each other diretly.

Any idea where the pb comes from ?

once this will be solve, if I have 20 arduino sending messages all together, will there be any trouble to get them ALL on the master receiver ?

Thanks

Seb</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>I&#8217;ve set up a I2C with 2 arduino. Seems to be OK, messages are received but they are read with strange characters. Instead of reeiving &#8216;hello &#8216; i receive 6 characters looking like a quare. my grounds are connected each other diretly.</p>
<p>Any idea where the pb comes from ?</p>
<p>once this will be solve, if I have 20 arduino sending messages all together, will there be any trouble to get them ALL on the master receiver ?</p>
<p>Thanks</p>
<p>Seb</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: grinan</title>
		<link>http://www.uchobby.com/index.php/2008/09/16/introduction-to-i2c/comment-page-1/#comment-1447</link>
		<dc:creator>grinan</dc:creator>
		<pubDate>Sun, 21 Sep 2008 19:36:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.uchobby.com/index.php/2008/09/16/introduction-to-i2c/#comment-1447</guid>
		<description>well, the best i can tell you about is arduino, and most devices that arduino connect to are configurable as to addressing.  You will need to check the manufacturers data sheet for other arduino devices.

You are allowed, i believe, up to 255 devices connected on the i2c bus.   As you can see in the code above, it&#039;s as simple as just giving it a number in arduino, with the master being 0 or undefined.

Check out this forum post, it touches briefly on addressing, http://www.arduino.cc/cgi-bin/yabb2/YaBB.pl?num=1221415715/6 If that doesn&#039;t help you, try searching the arduino forums via google or their built in search.

Most of my information came from the forums to begin with.

Hope that helps.</description>
		<content:encoded><![CDATA[<p>well, the best i can tell you about is arduino, and most devices that arduino connect to are configurable as to addressing.  You will need to check the manufacturers data sheet for other arduino devices.</p>
<p>You are allowed, i believe, up to 255 devices connected on the i2c bus.   As you can see in the code above, it&#8217;s as simple as just giving it a number in arduino, with the master being 0 or undefined.</p>
<p>Check out this forum post, it touches briefly on addressing, <a href="http://www.arduino.cc/cgi-bin/yabb2/YaBB.pl?num=1221415715/6" rel="nofollow">http://www.arduino.cc/cgi-bin/yabb2/YaBB.pl?num=1221415715/6</a> If that doesn&#8217;t help you, try searching the arduino forums via google or their built in search.</p>
<p>Most of my information came from the forums to begin with.</p>
<p>Hope that helps.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel</title>
		<link>http://www.uchobby.com/index.php/2008/09/16/introduction-to-i2c/comment-page-1/#comment-1446</link>
		<dc:creator>Daniel</dc:creator>
		<pubDate>Fri, 19 Sep 2008 23:07:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.uchobby.com/index.php/2008/09/16/introduction-to-i2c/#comment-1446</guid>
		<description>Is there an article somewhere that explains setting up addresses for i2c devices, and what to do about conflicting device addresses?</description>
		<content:encoded><![CDATA[<p>Is there an article somewhere that explains setting up addresses for i2c devices, and what to do about conflicting device addresses?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeronimo</title>
		<link>http://www.uchobby.com/index.php/2008/09/16/introduction-to-i2c/comment-page-1/#comment-1445</link>
		<dc:creator>Jeronimo</dc:creator>
		<pubDate>Wed, 17 Sep 2008 15:48:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.uchobby.com/index.php/2008/09/16/introduction-to-i2c/#comment-1445</guid>
		<description>Very good article, Simple and direct to the point .
Jeronimo
www.blogdoje.com.br
Avr,Arduino &amp; ARM</description>
		<content:encoded><![CDATA[<p>Very good article, Simple and direct to the point .<br />
Jeronimo<br />
<a href="http://www.blogdoje.com.br" rel="nofollow">http://www.blogdoje.com.br</a><br />
Avr,Arduino &amp; ARM</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: grinan</title>
		<link>http://www.uchobby.com/index.php/2008/09/16/introduction-to-i2c/comment-page-1/#comment-1444</link>
		<dc:creator>grinan</dc:creator>
		<pubDate>Wed, 17 Sep 2008 12:24:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.uchobby.com/index.php/2008/09/16/introduction-to-i2c/#comment-1444</guid>
		<description>Plese disreguard the last comment, i re-read your comment and missed your question totally.

the i2c bus is just two wires, called SCL and SDA. SCL is the clock line. It is used to synchronize all data transfers over the I2C bus. SDA is the data line. The SCL &amp; SDA lines are connected to all devices on the I2C bus. There needs to be a third wire which is just the ground or 0 volts. There may also be a 5volt wire is power is being distributed to the devices. Both SCL and SDA lines are &quot;open drain&quot; drivers. What this means is that the chip can drive its output low, but it cannot drive it high. For the line to be able to go high you must provide pull-up resistors to the 5v supply. There should be a resistor from the SCL line to the 5v line and another from the SDA line to the 5v line. You only need one set of pull-up resistors for the whole I2C bus, not for each device.

Also, I used 1.5k resistors, but any resistor should work from 1k up.

Hope that helps.</description>
		<content:encoded><![CDATA[<p>Plese disreguard the last comment, i re-read your comment and missed your question totally.</p>
<p>the i2c bus is just two wires, called SCL and SDA. SCL is the clock line. It is used to synchronize all data transfers over the I2C bus. SDA is the data line. The SCL &amp; SDA lines are connected to all devices on the I2C bus. There needs to be a third wire which is just the ground or 0 volts. There may also be a 5volt wire is power is being distributed to the devices. Both SCL and SDA lines are &#8220;open drain&#8221; drivers. What this means is that the chip can drive its output low, but it cannot drive it high. For the line to be able to go high you must provide pull-up resistors to the 5v supply. There should be a resistor from the SCL line to the 5v line and another from the SDA line to the 5v line. You only need one set of pull-up resistors for the whole I2C bus, not for each device.</p>
<p>Also, I used 1.5k resistors, but any resistor should work from 1k up.</p>
<p>Hope that helps.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: grinan</title>
		<link>http://www.uchobby.com/index.php/2008/09/16/introduction-to-i2c/comment-page-1/#comment-1443</link>
		<dc:creator>grinan</dc:creator>
		<pubDate>Wed, 17 Sep 2008 12:17:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.uchobby.com/index.php/2008/09/16/introduction-to-i2c/#comment-1443</guid>
		<description>the two resistors are necessary, those are 10k pullup resistors.  You need one pullup on both the sda and scl from 5+.

I have read in several places that you can enable the internal pullup resistors on the atmega, but it failed miserably for me each time i tried.. i could never establish clear communication.. it was intermittent at best.

Hope that helps, thanks for the kind comment.</description>
		<content:encoded><![CDATA[<p>the two resistors are necessary, those are 10k pullup resistors.  You need one pullup on both the sda and scl from 5+.</p>
<p>I have read in several places that you can enable the internal pullup resistors on the atmega, but it failed miserably for me each time i tried.. i could never establish clear communication.. it was intermittent at best.</p>
<p>Hope that helps, thanks for the kind comment.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

