<?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 for White Rose Engineering</title>
	<atom:link href="http://lackawanna.hackhut.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://lackawanna.hackhut.com</link>
	<description>Just another HackHut site</description>
	<lastBuildDate>Wed, 01 Aug 2012 05:19:35 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.5</generator>
	<item>
		<title>Comment on Easy I2C: Pull-ups optional by lackawanna</title>
		<link>http://lackawanna.hackhut.com/2011/10/10/easy-i2c/#comment-2096</link>
		<dc:creator>lackawanna</dc:creator>
		<pubDate>Wed, 01 Aug 2012 05:19:35 +0000</pubDate>
		<guid isPermaLink="false">http://lackawanna.hackhut.com/?p=375#comment-2096</guid>
		<description>It sounds like you are setting the external resistors right.  10k is sufficient at 100kHz, so 4.7k per line is more than enough.  It does not matter I believe where the pullup resistor is placed on the line - say either close to the AVR master or at the end next to the slave - since the line will be short enough to be considered lumped.  That is it will not behave as a transmission line where reflections will result should the line not be properly terminated at the master and the slave.  Maybe you are having problems because of the stk600.  Also don&#039;t enable the pull-up as I did in the code above.  That is make sure these two lines are omitted from your code:

SCL_PORT &#124;= _BV(SCL_BIT);   // enable pull up on TWI clock line
SDA_PORT &#124;= _BV(SDA_BIT);   // enable pull up on TWI data line

I should of pointed this out in my post.</description>
		<content:encoded><![CDATA[<p>It sounds like you are setting the external resistors right.  10k is sufficient at 100kHz, so 4.7k per line is more than enough.  It does not matter I believe where the pullup resistor is placed on the line &#8211; say either close to the AVR master or at the end next to the slave &#8211; since the line will be short enough to be considered lumped.  That is it will not behave as a transmission line where reflections will result should the line not be properly terminated at the master and the slave.  Maybe you are having problems because of the stk600.  Also don&#8217;t enable the pull-up as I did in the code above.  That is make sure these two lines are omitted from your code:</p>
<p>SCL_PORT |= _BV(SCL_BIT);   // enable pull up on TWI clock line<br />
SDA_PORT |= _BV(SDA_BIT);   // enable pull up on TWI data line</p>
<p>I should of pointed this out in my post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Easy I2C: Pull-ups optional by nippi1111</title>
		<link>http://lackawanna.hackhut.com/2011/10/10/easy-i2c/#comment-2091</link>
		<dc:creator>nippi1111</dc:creator>
		<pubDate>Tue, 31 Jul 2012 14:12:50 +0000</pubDate>
		<guid isPermaLink="false">http://lackawanna.hackhut.com/?p=375#comment-2091</guid>
		<description>hey,
i am using at2560.  .i dont want use internal  pullups.i am using bus at 100khz bus speed i hav used 2 4k7 pullups but i am not getting in which side should i give vcc to pull from slave or master.pls help will b highle apperiaciated and not to mention i am using stk600 and they use 2 different spi and voltage supplies and dont have common grnd or common vcc.any help,,,pls pls</description>
		<content:encoded><![CDATA[<p>hey,<br />
i am using at2560.  .i dont want use internal  pullups.i am using bus at 100khz bus speed i hav used 2 4k7 pullups but i am not getting in which side should i give vcc to pull from slave or master.pls help will b highle apperiaciated and not to mention i am using stk600 and they use 2 different spi and voltage supplies and dont have common grnd or common vcc.any help,,,pls pls</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Using V-USB and the HID Class (Part I of III) by Coda</title>
		<link>http://lackawanna.hackhut.com/2011/10/04/using-v-usb-and-the-hid-class-part-i/#comment-1735</link>
		<dc:creator>Coda</dc:creator>
		<pubDate>Sun, 10 Jun 2012 16:35:14 +0000</pubDate>
		<guid isPermaLink="false">http://lackawanna.hackhut.com/?p=87#comment-1735</guid>
		<description>Great article, and I concur; I&#039;ve made several V-USB projects with 12Mhz Resonators rather than crystals, and they seem to work fine. I have obtained a few 16 and 20Mhz resonators for future projects (if they work fine with V-USB why bother using crystals for non-V-USB projects that don&#039;t require strict timing...?)</description>
		<content:encoded><![CDATA[<p>Great article, and I concur; I&#8217;ve made several V-USB projects with 12Mhz Resonators rather than crystals, and they seem to work fine. I have obtained a few 16 and 20Mhz resonators for future projects (if they work fine with V-USB why bother using crystals for non-V-USB projects that don&#8217;t require strict timing&#8230;?)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Using V-USB and the HID Class (Part I of III) by lackawanna</title>
		<link>http://lackawanna.hackhut.com/2011/10/04/using-v-usb-and-the-hid-class-part-i/#comment-1712</link>
		<dc:creator>lackawanna</dc:creator>
		<pubDate>Tue, 05 Jun 2012 04:44:29 +0000</pubDate>
		<guid isPermaLink="false">http://lackawanna.hackhut.com/?p=87#comment-1712</guid>
		<description>It is noteworthy!  Thank you for the kind words as well.  I rather reserve the crystal for other precision uses rather than for the sake of the usb interface.</description>
		<content:encoded><![CDATA[<p>It is noteworthy!  Thank you for the kind words as well.  I rather reserve the crystal for other precision uses rather than for the sake of the usb interface.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Using V-USB and the HID Class (Part III of III) by lackawanna</title>
		<link>http://lackawanna.hackhut.com/2011/10/06/using-v-usb-and-the-hid-class-part-iiiiii/#comment-1711</link>
		<dc:creator>lackawanna</dc:creator>
		<pubDate>Tue, 05 Jun 2012 04:36:34 +0000</pubDate>
		<guid isPermaLink="false">http://lackawanna.hackhut.com/?p=324#comment-1711</guid>
		<description>Try running it using sudo.  See if that works.  Namely, try:

$ sudo ./simple

If that does work then you likely need to add a file to /dev/udev to make /dev/hidraw0 read-writable from user space.  See part two.  Otherwise if it doesn&#039;t work, make sure the usb device you connected to your computer is being recognized.  It should also create a /dev/hidraw0 device file when it registers itself as a hid device.  FYI, I found out that there is a function call in libusb which will force the kernel to release /dev/hidraw0 so libusb can use it.  I didn&#039;t mention that fact in my writeup unfortunately.  I only learned about it later.  It&#039;s a important point, nevertheless I believe you still have to be superuser to force the kernel to release it through libusb which is a big negative in my view.</description>
		<content:encoded><![CDATA[<p>Try running it using sudo.  See if that works.  Namely, try:</p>
<p>$ sudo ./simple</p>
<p>If that does work then you likely need to add a file to /dev/udev to make /dev/hidraw0 read-writable from user space.  See part two.  Otherwise if it doesn&#8217;t work, make sure the usb device you connected to your computer is being recognized.  It should also create a /dev/hidraw0 device file when it registers itself as a hid device.  FYI, I found out that there is a function call in libusb which will force the kernel to release /dev/hidraw0 so libusb can use it.  I didn&#8217;t mention that fact in my writeup unfortunately.  I only learned about it later.  It&#8217;s a important point, nevertheless I believe you still have to be superuser to force the kernel to release it through libusb which is a big negative in my view.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Using V-USB and the HID Class (Part III of III) by ChinnyxD</title>
		<link>http://lackawanna.hackhut.com/2011/10/06/using-v-usb-and-the-hid-class-part-iiiiii/#comment-1702</link>
		<dc:creator>ChinnyxD</dc:creator>
		<pubDate>Sun, 03 Jun 2012 14:41:37 +0000</pubDate>
		<guid isPermaLink="false">http://lackawanna.hackhut.com/?p=324#comment-1702</guid>
		<description>Very nice tutorial! But I have some trouble running the simple.c program. When i run the program it says: write: bad file descriptor.. Could anyone explain how to fix this??

Much appreciated!</description>
		<content:encoded><![CDATA[<p>Very nice tutorial! But I have some trouble running the simple.c program. When i run the program it says: write: bad file descriptor.. Could anyone explain how to fix this??</p>
<p>Much appreciated!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Using V-USB and the HID Class (Part I of III) by con-f-use</title>
		<link>http://lackawanna.hackhut.com/2011/10/04/using-v-usb-and-the-hid-class-part-i/#comment-1678</link>
		<dc:creator>con-f-use</dc:creator>
		<pubDate>Thu, 31 May 2012 16:05:22 +0000</pubDate>
		<guid isPermaLink="false">http://lackawanna.hackhut.com/?p=87#comment-1678</guid>
		<description>Thanks for this. It&#039;s well written article series!

However I&#039;ve found ceramic oscillators as well as the on board RC oscillator of (e.g.) the AtMega168 sufficient to run v-usb in 12MHz mode. I have tested it myself with the version of Jan 2012. Thought that might be noteworthy.</description>
		<content:encoded><![CDATA[<p>Thanks for this. It&#8217;s well written article series!</p>
<p>However I&#8217;ve found ceramic oscillators as well as the on board RC oscillator of (e.g.) the AtMega168 sufficient to run v-usb in 12MHz mode. I have tested it myself with the version of Jan 2012. Thought that might be noteworthy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Easy I2C: Pull-ups optional by lackawanna</title>
		<link>http://lackawanna.hackhut.com/2011/10/10/easy-i2c/#comment-1628</link>
		<dc:creator>lackawanna</dc:creator>
		<pubDate>Sun, 20 May 2012 02:25:44 +0000</pubDate>
		<guid isPermaLink="false">http://lackawanna.hackhut.com/?p=375#comment-1628</guid>
		<description>Here is the quote from Myke Predko: “I2C connections between the PIC microcontroller’s I2C SDA (data) and SCL (clock) pins is very simple, with just a pull-up on each line, as shown in Fig. 16.15. I typically use a 1-kohm resistor for 400-kHz data transfers and a 10kohm resistor for 100-kHz data rates.”</description>
		<content:encoded><![CDATA[<p>Here is the quote from Myke Predko: “I2C connections between the PIC microcontroller’s I2C SDA (data) and SCL (clock) pins is very simple, with just a pull-up on each line, as shown in Fig. 16.15. I typically use a 1-kohm resistor for 400-kHz data transfers and a 10kohm resistor for 100-kHz data rates.”</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Easy I2C: Pull-ups optional by lackawanna</title>
		<link>http://lackawanna.hackhut.com/2011/10/10/easy-i2c/#comment-1622</link>
		<dc:creator>lackawanna</dc:creator>
		<pubDate>Sat, 19 May 2012 04:39:55 +0000</pubDate>
		<guid isPermaLink="false">http://lackawanna.hackhut.com/?p=375#comment-1622</guid>
		<description>Thank you for the kind suggestion!  It is very appreciated.  You might want to consider one of the USB based xbees.  Or you can use the uart-based xbees and interface from your computer through a FTDI cable.  One of my best decisions ever was to buy a FTDI cable - it allowed me concentrate on AVR design instead of worrying about building a max232 circuit.  Your question seems to indicate you want to run a xbee off your computer.   

If however you want to run a xbee from your AVR you only need to use the UART, no level conversion is needed.  Anyway, you have spurned me to write a wireless article.  Until then see this site for a cool wireless/remote control design http://dl.dropbox.com/u/43021514/CWTD/RemoteControl/May15.html</description>
		<content:encoded><![CDATA[<p>Thank you for the kind suggestion!  It is very appreciated.  You might want to consider one of the USB based xbees.  Or you can use the uart-based xbees and interface from your computer through a FTDI cable.  One of my best decisions ever was to buy a FTDI cable &#8211; it allowed me concentrate on AVR design instead of worrying about building a max232 circuit.  Your question seems to indicate you want to run a xbee off your computer.   </p>
<p>If however you want to run a xbee from your AVR you only need to use the UART, no level conversion is needed.  Anyway, you have spurned me to write a wireless article.  Until then see this site for a cool wireless/remote control design <a href="http://dl.dropbox.com/u/43021514/CWTD/RemoteControl/May15.html" rel="nofollow">http://dl.dropbox.com/u/43021514/CWTD/RemoteControl/May15.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Easy I2C: Pull-ups optional by Bishal Paudel</title>
		<link>http://lackawanna.hackhut.com/2011/10/10/easy-i2c/#comment-1615</link>
		<dc:creator>Bishal Paudel</dc:creator>
		<pubDate>Fri, 18 May 2012 02:01:19 +0000</pubDate>
		<guid isPermaLink="false">http://lackawanna.hackhut.com/?p=375#comment-1615</guid>
		<description>Can you make a detailed post like this on XBee (using max232 for connection with X-CTU)?</description>
		<content:encoded><![CDATA[<p>Can you make a detailed post like this on XBee (using max232 for connection with X-CTU)?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
