Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Arduino I2C pin inputs

Received: by 10.224.207.137 with SMTP id fy9mr1452845qab.6.1332300710463;
        Tue, 20 Mar 2012 20:31:50 -0700 (PDT)
X-BeenThere: nycresistormicrocontrollers@googlegroups.com
Received: by 10.229.117.204 with SMTP id s12ls533891qcq.7.gmail; Tue, 20 Mar
 2012 20:31:46 -0700 (PDT)
Received: by 10.224.186.204 with SMTP id ct12mr1462157qab.0.1332300706879;
        Tue, 20 Mar 2012 20:31:46 -0700 (PDT)
Received: by 10.224.186.204 with SMTP id ct12mr1462155qab.0.1332300706861;
        Tue, 20 Mar 2012 20:31:46 -0700 (PDT)
Return-Path: <SRS0=punk5H=B4=joelmurphy.net=j...@eigbox.net>
Received: from bosmailout09.eigbox.net (bosmailout09.eigbox.net. [66.96.184.9])
        by gmr-mx.google.com with ESMTP id a39si168772qch.0.2012.03.20.20.31.46;
        Tue, 20 Mar 2012 20:31:46 -0700 (PDT)
Received-SPF: pass (google.com: domain of SRS0=punk5H=B4=joelmurphy.net=j...@eigbox.net designates 66.96.184.9 as permitted sender) client-ip=66.96.184.9;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of SRS0=punk5H=B4=joelmurphy.net=j...@eigbox.net designates 66.96.184.9 as permitted sender) smtp.mail=SRS0=punk5H=B4=joelmurphy.net=j...@eigbox.net
Received: from bosmailscan15.eigbox.net ([10.20.15.15])
	by bosmailout09.eigbox.net with esmtp (Exim)
	id 1SACH4-0007FP-Om
	for nycresistormicrocontrollers@googlegroups.com; Tue, 20 Mar 2012 23:31:46 -0400
Received: from bosimpout01.eigbox.net ([10.20.55.1])
	by bosmailscan15.eigbox.net with esmtp (Exim)
	id 1SACH4-0004xG-Cg
	for nycresistormicrocontrollers@googlegroups.com; Tue, 20 Mar 2012 23:31:46 -0400
Received: from bosauthsmtp08.eigbox.net ([10.20.18.8])
	by bosimpout01.eigbox.net with NO UCE
	id o3Xm1i0040ASroS013XmxA; Tue, 20 Mar 2012 23:31:46 -0400
X-Authority-Analysis: v=2.0 cv=eq1oOPVX c=1 sm=1
 a=A3zUCNFCKP+koWYGDHRF9A==:17 a=mVUNWMl9DSsA:10 a=8WZVj894va4A:10
 a=EhW6YxB_YQIA:10 a=wPvRtVj6AAAA:8 a=4RBUngkUAAAA:8 a=W8JJFe1bAAAA:20
 a=IFESS1FGP-Berp4drqsA:9 a=9_75qGBuddqc2r2bhGcA:7 a=CjuIK1q_8ugA:10
 a=CCA_6-gVaX8A:10 a=c4S9Whzb7AQA:10 a=lPeZflLEKNMA:10 a=Bm6qEjDGwGEA:10
 a=HinNof0eKZKeOImH1fAA:9 a=t8r2daZCoEan9zbEmfsA:7 a=QEXdDO2ut3YA:10
 a=_W_S_7VecoQA:10 a=BF10AaGwQl41phDg7WSPyA==:117
X-EN-OrigOutIP: 10.20.18.8
X-EN-IMPSID: o3Xm1i0040ASroS013XmxA
Received: from mobile-166-137-138-120.mycingular.net ([166.137.138.120] helo=[10.73.196.105])
	by bosauthsmtp08.eigbox.net with esmtpsa (TLSv1:AES128-SHA:128)
	(Exim)
	id 1SACH1-0001dB-0u
	for nycresistormicrocontrollers@googlegroups.com; Tue, 20 Mar 2012 23:31:46 -0400
Subject: Re: [NYCR:Microcontrollers] Arduino I2C pin inputs
References: <27e0eab4-14d5-4975-b3d0-6e193e7af...@l7g2000vbw.googlegroups.com> <08C50D4211D3490F868915B78AB1D...@yang.dk> <BFFCA8A1-EF04-4507-B509-296697E32...@joelmurphy.net>
From: Joel Murphy <j...@joelmurphy.net>
Content-Type: multipart/alternative;
	boundary=Apple-Mail-92AE2003-645F-4234-A43A-3F73B5B6947F
X-Mailer: iPhone Mail (9B176)
In-Reply-To: <BFFCA8A1-EF04-4507-B509-296697E32...@joelmurphy.net>
Message-Id: <8951849C-9EB4-4B97-9E8E-287789AD0...@joelmurphy.net>
Date: Tue, 20 Mar 2012 23:33:39 -0400
To: "nycresistormicrocontrollers@googlegroups.com" <nycresistormicrocontrollers@googlegroups.com>
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)
X-EN-UserInfo: a667314a0114b5ec32e04f6a05b45bef:2bb7908071dbf1c3aebaceaf84cc6430
X-EN-AuthUser: j...@joelmurphy.net
Sender: Joel Murphy <j...@joelmurphy.net>
X-EN-OrigIP: 166.137.138.120
X-EN-OrigHost: mobile-166-137-138-120.mycingular.net


--Apple-Mail-92AE2003-645F-4234-A43A-3F73B5B6947F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Meant to add the only other issue is timing. datasheets will have a good sta=
rting point for trial and error to get a workable clock with delays. Longer t=
ransmission streams, longer tweeking.... But totally doable. I wrote a softw=
are I2C in PICBasic years ago.

Making the world safe for robots
-----------
Any noise in the prior signal has been inserted by the iThing

On Mar 20, 2012, at 11:18 PM, Joel Murphy <j...@joelmurphy.net> wrote:

> I2C is implemented in hardware on arduino pins A4 and A5. A whole pile of c=
ontrol registers make it easy to run the protocol with internal flags and in=
terrupts. Its fairly complex The back and forth -ness of it, with acknowledg=
e bits flying (or not flying) every where and changing pin MODE statesWire l=
ibrary mucks about in those control registers, so it's not possible to run W=
ire on anyy other pins.=20
> Your next recourse software. There's plenty of I2C waveform data out there=
 and in the datasheet for the DS1307 to make it doable. The bits and bytes c=
ommands in arduino make the code easy to debug.
>=20
> Making the world safe for robots
> -----------
> Any noise in the prior signal has been inserted by the iThing
>=20
> On Mar 20, 2012, at 10:11 PM, Guan Yang <g...@yang.dk> wrote:
>=20
>> I am pretty sure Wire uses hardware support for I2C that requires those p=
articular pins. In theory you could implement I2C like SoftwareSerial for as=
ync serial, that would run on any pin (or any pin with an interrupt), but I h=
aven't seen such an implementation.
>>=20
>> What's on those pins? Can you move it?
>> On Tuesday, March 20, 2012 at 21:00, Adrienne Humblet wrote:
>>=20
>>> Hi,
>>>=20
>>> I'm trying to hook up a DS1307 RTC chip to an Arduino Uno. The DS1307
>>> uses the I2C bus which requires 2 connection to the Arduino. The
>>> Wire.h library (which is what the Arduino uses for I2C protocol)
>>> expects the SDA (serial data) and SCK (serial clock) connections in
>>> the Analog 4 and Analog 5 pins of the Arduino.
>>>=20
>>> Does anyone know how to make it such that the Wire library expects SDA
>>> and SCK in other pins? Pins A4 and A5 are already taken up by other
>>> non I2C devices.
>>>=20
>>> Does anyone know what I'm talking about?
>>>=20
>>> I thought it would be easy, but when I look in Wire.h I don't see any
>>> pin assignments.
>>>=20
>>> Thanks!
>>> -Adrienne
>>>=20
>>> --
>>> You received this message because you are subscribed to the Google Group=
s "NYCResistor:Microcontrollers" group.
>>> To post to this group, send email to nycresistormicrocontrollers@googleg=
roups.com.
>>> To unsubscribe from this group, send email to nycresistormicrocontroller=
s+unsubscribe@googlegroups.com.
>>> For more options, visit this group at http://groups.google.com/group/nyc=
resistormicrocontrollers?hl=3Den.
>>=20
>> --=20
>> You received this message because you are subscribed to the Google Groups=
 "NYCResistor:Microcontrollers" group.
>> To post to this group, send email to nycresistormicrocontrollers@googlegr=
oups.com.
>> To unsubscribe from this group, send email to nycresistormicrocontrollers=
+unsubscribe@googlegroups.com.
>> For more options, visit this group at http://groups.google.com/group/nycr=
esistormicrocontrollers?hl=3Den.
> --=20
> You received this message because you are subscribed to the Google Groups "=
NYCResistor:Microcontrollers" group.
> To post to this group, send email to nycresistormicrocontrollers@googlegro=
ups.com.
> To unsubscribe from this group, send email to nycresistormicrocontrollers+=
unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/nycre=
sistormicrocontrollers?hl=3Den.

--Apple-Mail-92AE2003-645F-4234-A43A-3F73B5B6947F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head></head><body bgcolor=3D"#FFFFFF"><div>Meant to add the only othe=
r issue is timing. datasheets will have a good starting point for trial and e=
rror to get a workable clock with delays. Longer transmission streams, longe=
r tweeking.... But totally doable. I wrote a software I2C in PICBasic years a=
go.<br><br>Making the world safe for robots<div>-----------</div><div>Any no=
ise in the prior signal has been inserted by the iThing</div></div><div><br>=
On Mar 20, 2012, at 11:18 PM, Joel Murphy &lt;<a href=3D"mailto:joel@joelmur=
phy.net">j...@joelmurphy.net</a>&gt; wrote:<br><br></div><div></div><blockqu=
ote type=3D"cite"><div><div>I2C is implemented in hardware on arduino pins A=
4 and A5. A whole pile of control registers make it easy to run the protocol=
 with internal flags and interrupts. Its fairly complex The back and forth -=
ness of it, with acknowledge bits flying (or not flying) every where and cha=
nging pin MODE statesWire library mucks about in those control registers, so=
 it's not possible to run Wire on anyy other pins.&nbsp;</div><div>Your next=
 recourse software. There's plenty of I2C waveform data out there and in the=
 datasheet for the DS1307 to make it doable. The bits and bytes commands in a=
rduino make the code easy to debug.<br><br>Making the world safe for robots<=
div>-----------</div><div>Any noise in the prior signal has been inserted by=
 the iThing</div></div><div><br>On Mar 20, 2012, at 10:11 PM, Guan Yang &lt;=
<a href=3D"mailto:g...@yang.dk">g...@yang.dk</a>&gt; wrote:<br><br></div><di=
v></div><blockquote type=3D"cite"><div>
    <div id=3D"reply-content">I am pretty sure Wire uses hardware support fo=
r I2C that requires those particular pins. In theory you could implement I2C=
 like SoftwareSerial for async serial, that would run on any pin (or any pin=
 with an interrupt), but I haven't seen such an implementation.
    </div><div id=3D"reply-content"><br></div><div id=3D"reply-content">What=
's on those pins? Can you move it?</div>
    <div id=3D"813F2572B7C944B4828E61B73578A929"></div>
    =20
    <p style=3D"color: #A0A0A8;">On Tuesday, March 20, 2012 at 21:00, Adrien=
ne Humblet wrote:</p>
    <blockquote type=3D"cite" style=3D"border-left-style:solid;border-width:=
1px;margin-left:0px;padding-left:10px;">
        <div id=3D"quoted-message-content"><div><div>Hi,</div><div><br></div=
><div>I'm trying to hook up a DS1307 RTC chip to an Arduino Uno. The DS1307<=
/div><div>uses the I2C bus which requires 2 connection to the Arduino. The</=
div><div>Wire.h library (which is what the Arduino uses for I2C protocol)</d=
iv><div>expects the SDA (serial data) and SCK (serial clock) connections in<=
/div><div>the Analog 4 and Analog 5 pins of the Arduino.</div><div><br></div=
><div>Does anyone know how to make it such that the Wire library expects SDA=
</div><div>and SCK in other pins? Pins A4 and A5 are already taken up by oth=
er</div><div>non I2C devices.</div><div><br></div><div>Does anyone know what=
 I'm talking about?</div><div><br></div><div>I thought it would be easy, but=
 when I look in Wire.h I don't see any</div><div>pin assignments.</div><div>=
<br></div><div>Thanks!</div><div>-Adrienne</div><div><br></div><div>-- </div=
><div>You received this message because you are subscribed to the Google Gro=
ups "NYCResistor:Microcontrollers" group.</div><div>To post to this group, s=
end email to <a href=3D"mailto:nycresistormicrocontrollers@googlegroups.com"=
>nycresistormicrocontrollers@googlegroups.com</a>.</div><div>To unsubscribe f=
rom this group, send email to <a href=3D"mailto:nycresistormicrocontrollers+=
unsubscribe@googlegroups.com">nycresistormicrocontrollers+unsubscribe@google=
groups.com</a>.</div><div>For more options, visit this group at <a href=3D"h=
ttp://groups.google.com/group/nycresistormicrocontrollers?hl=3Den">http://gr=
oups.google.com/group/nycresistormicrocontrollers?hl=3Den</a>.</div></div></=
div>
        =20
        =20
        =20
        =20
    </blockquote>
    =20
    <div>
        <br>
    </div>

<p></p>

-- <br>
You received this message because you are subscribed to the Google Groups "N=
YCResistor:Microcontrollers" group.<br>
To post to this group, send email to <a href=3D"mailto:nycresistormicrocontr=
ollers@googlegroups.com">nycresistormicrocontrollers@googlegroups.com</a>.<b=
r>
To unsubscribe from this group, send email to <a href=3D"mailto:nycresistorm=
icrocontrollers+unsubscribe@googlegroups.com">nycresistormicrocontrollers+un=
subscribe@googlegroups.com</a>.<br>

For more options, visit this group at <a href=3D"http://groups.google.com/gr=
oup/nycresistormicrocontrollers?hl=3Den">http://groups.google.com/group/nycr=
esistormicrocontrollers?hl=3Den</a>.<br>


</div></blockquote>

<p></p>

-- <br>
You received this message because you are subscribed to the Google Groups "N=
YCResistor:Microcontrollers" group.<br>
To post to this group, send email to <a href=3D"mailto:nycresistormicrocontr=
ollers@googlegroups.com">nycresistormicrocontrollers@googlegroups.com</a>.<b=
r>
To unsubscribe from this group, send email to <a href=3D"mailto:nycresistorm=
icrocontrollers+unsubscribe@googlegroups.com">nycresistormicrocontrollers+un=
subscribe@googlegroups.com</a>.<br>

For more options, visit this group at <a href=3D"http://groups.google.com/gr=
oup/nycresistormicrocontrollers?hl=3Den">http://groups.google.com/group/nycr=
esistormicrocontrollers?hl=3Den</a>.<br>


</div></blockquote></body></html>=

--Apple-Mail-92AE2003-645F-4234-A43A-3F73B5B6947F--