<?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"
	>
<channel>
	<title>Comments on: Binary clock</title>
	<atom:link href="http://blog.tjugotre.org/2008/04/15/binaeruhr/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.tjugotre.org/2008/04/15/binaeruhr/</link>
	<description>\o/</description>
	<pubDate>Sat, 22 Nov 2008 03:00:20 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Aditya</title>
		<link>http://blog.tjugotre.org/2008/04/15/binaeruhr/#comment-13837</link>
		<dc:creator>Aditya</dc:creator>
		<pubDate>Mon, 18 Aug 2008 06:53:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tjugotre.org/2008/04/15/binaeruhr/#comment-13837</guid>
		<description>Thanks a lot for all your help. I tried changing the prescaler but that did not help so I changed the timer function a bit and now it works. Thanks a lot.</description>
		<content:encoded><![CDATA[<p>Thanks a lot for all your help. I tried changing the prescaler but that did not help so I changed the timer function a bit and now it works. Thanks a lot.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Valentin</title>
		<link>http://blog.tjugotre.org/2008/04/15/binaeruhr/#comment-13836</link>
		<dc:creator>Valentin</dc:creator>
		<pubDate>Sun, 17 Aug 2008 16:54:16 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tjugotre.org/2008/04/15/binaeruhr/#comment-13836</guid>
		<description>Try looking at your data sheet to see what you need to set to get your prescaler to 128, then you probably won't have to change the 128 to 1024. As for the hour thing - no idea, sorry.</description>
		<content:encoded><![CDATA[<p>Try looking at your data sheet to see what you need to set to get your prescaler to 128, then you probably won&#8217;t have to change the 128 to 1024. As for the hour thing - no idea, sorry.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aditya</title>
		<link>http://blog.tjugotre.org/2008/04/15/binaeruhr/#comment-13835</link>
		<dc:creator>Aditya</dc:creator>
		<pubDate>Sun, 17 Aug 2008 16:49:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tjugotre.org/2008/04/15/binaeruhr/#comment-13835</guid>
		<description>And it does not work. Some problem. Whenever I run the code as it is, just changing the frequency, then the clock runs very slow. And when I changed the overflow denominator to 1024, then it ran well, but the hours were changing every 20 minutes (20 minutes real time AND when the minute LEDs were 20, 40 and 60)

Any ideas? I can't figure out anything.</description>
		<content:encoded><![CDATA[<p>And it does not work. Some problem. Whenever I run the code as it is, just changing the frequency, then the clock runs very slow. And when I changed the overflow denominator to 1024, then it ran well, but the hours were changing every 20 minutes (20 minutes real time AND when the minute LEDs were 20, 40 and 60)</p>
<p>Any ideas? I can&#8217;t figure out anything.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aditya</title>
		<link>http://blog.tjugotre.org/2008/04/15/binaeruhr/#comment-13833</link>
		<dc:creator>Aditya</dc:creator>
		<pubDate>Sun, 17 Aug 2008 16:15:53 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tjugotre.org/2008/04/15/binaeruhr/#comment-13833</guid>
		<description>I am using the internal clock for now. 4MHz... I will be buying a crystal later. I changed the frequency to 4MHz and retained the rest of the code as it is. Now, I am connecting the buttons to VCC and then I will test it. 

Thanks...</description>
		<content:encoded><![CDATA[<p>I am using the internal clock for now. 4MHz&#8230; I will be buying a crystal later. I changed the frequency to 4MHz and retained the rest of the code as it is. Now, I am connecting the buttons to VCC and then I will test it. </p>
<p>Thanks&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Valentin</title>
		<link>http://blog.tjugotre.org/2008/04/15/binaeruhr/#comment-13832</link>
		<dc:creator>Valentin</dc:creator>
		<pubDate>Sun, 17 Aug 2008 16:11:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tjugotre.org/2008/04/15/binaeruhr/#comment-13832</guid>
		<description>Uh, 20 minutes in real time or when the minute LEDs are at 20 minutes?</description>
		<content:encoded><![CDATA[<p>Uh, 20 minutes in real time or when the minute LEDs are at 20 minutes?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Valentin</title>
		<link>http://blog.tjugotre.org/2008/04/15/binaeruhr/#comment-13831</link>
		<dc:creator>Valentin</dc:creator>
		<pubDate>Sun, 17 Aug 2008 16:11:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tjugotre.org/2008/04/15/binaeruhr/#comment-13831</guid>
		<description>The buttons are connected to VCC.
What is your frequency? You should really only change that - if setting it to the correct frequency doesn't work, try setting it to others until the seconds are fine.</description>
		<content:encoded><![CDATA[<p>The buttons are connected to VCC.<br />
What is your frequency? You should really only change that - if setting it to the correct frequency doesn&#8217;t work, try setting it to others until the seconds are fine.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aditya</title>
		<link>http://blog.tjugotre.org/2008/04/15/binaeruhr/#comment-13830</link>
		<dc:creator>Aditya</dc:creator>
		<pubDate>Sun, 17 Aug 2008 16:04:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tjugotre.org/2008/04/15/binaeruhr/#comment-13830</guid>
		<description>:( You are right... making it 1024 has made the hour LEDs change their state every 20 minutes....</description>
		<content:encoded><![CDATA[<p> <img src='http://blog.tjugotre.org/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' /> You are right&#8230; making it 1024 has made the hour LEDs change their state every 20 minutes&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aditya</title>
		<link>http://blog.tjugotre.org/2008/04/15/binaeruhr/#comment-13829</link>
		<dc:creator>Aditya</dc:creator>
		<pubDate>Sun, 17 Aug 2008 15:21:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tjugotre.org/2008/04/15/binaeruhr/#comment-13829</guid>
		<description>Okay... thanks. But I think something is missing here... I changed the CPU_F to 4MHz and then the overflow to CPU_F/1024/1 and the clock is working great. :-&#124;

One last thing (sorry to bother you again and again... and again) but, how do I connect the interrupt switches? PortB1 - Switch - Ground OR PortB1 - Switch - VCC?

Aditya</description>
		<content:encoded><![CDATA[<p>Okay&#8230; thanks. But I think something is missing here&#8230; I changed the CPU_F to 4MHz and then the overflow to CPU_F/1024/1 and the clock is working great. <img src='http://blog.tjugotre.org/wp-includes/images/smilies/icon_neutral.gif' alt=':-|' class='wp-smiley' /><br />
One last thing (sorry to bother you again and again&#8230; and again) but, how do I connect the interrupt switches? PortB1 - Switch - Ground OR PortB1 - Switch - VCC?</p>
<p>Aditya</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Valentin</title>
		<link>http://blog.tjugotre.org/2008/04/15/binaeruhr/#comment-13828</link>
		<dc:creator>Valentin</dc:creator>
		<pubDate>Sun, 17 Aug 2008 14:19:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tjugotre.org/2008/04/15/binaeruhr/#comment-13828</guid>
		<description>No, don't change any of the other constants - I'm calculating these through F_CPU. So if you set the overflow variable to 2*F_CPU/128 after halving F_CPU, the two changes negate each other. You do not want that ;)
If the frequency of the CPU is halved, the overflow value gets reached half as fast - but by also halving F_CPU, the overflow value gets halved too, so it doesn't take any longer after all. Sorry about the crappy explanation, but I hope that you understand it anyway.
Also, you can use the reply link at the bottom of a post - that way, all the replies are in one thread.</description>
		<content:encoded><![CDATA[<p>No, don&#8217;t change any of the other constants - I&#8217;m calculating these through F_CPU. So if you set the overflow variable to 2*F_CPU/128 after halving F_CPU, the two changes negate each other. You do not want that <img src='http://blog.tjugotre.org/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> If the frequency of the CPU is halved, the overflow value gets reached half as fast - but by also halving F_CPU, the overflow value gets halved too, so it doesn&#8217;t take any longer after all. Sorry about the crappy explanation, but I hope that you understand it anyway.<br />
Also, you can use the reply link at the bottom of a post - that way, all the replies are in one thread.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aditya</title>
		<link>http://blog.tjugotre.org/2008/04/15/binaeruhr/#comment-13827</link>
		<dc:creator>Aditya</dc:creator>
		<pubDate>Sun, 17 Aug 2008 13:59:27 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tjugotre.org/2008/04/15/binaeruhr/#comment-13827</guid>
		<description>So, none of the other parameters are linked with it? I mean, I saw that timer overflow is F_CPU/128/1 I thought as F_CPU is now halved, I might have to set the overflow as 2F_CPU/128/1.... I will be buying a crystal soon...</description>
		<content:encoded><![CDATA[<p>So, none of the other parameters are linked with it? I mean, I saw that timer overflow is F_CPU/128/1 I thought as F_CPU is now halved, I might have to set the overflow as 2F_CPU/128/1&#8230;. I will be buying a crystal soon&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
