<?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: Circuit Description</title>
	<atom:link href="http://eksfiles.net/digital-setting-circles/circuit-description/feed/" rel="self" type="application/rss+xml" />
	<link>http://eksfiles.net</link>
	<description>Putting the &#34;Ek&#34; in &#34;Geek&#34;</description>
	<lastBuildDate>Tue, 10 Aug 2010 11:59:23 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Dave</title>
		<link>http://eksfiles.net/digital-setting-circles/circuit-description/comment-page-1/#comment-325</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Thu, 11 Mar 2010 12:52:18 +0000</pubDate>
		<guid isPermaLink="false">http://test.eksfiles.net/?page_id=212#comment-325</guid>
		<description>R6-12 can be omitted completely (there&#039;s no need to tie those pins to VCC because there are internal pullup resistors). Also, you can obtain another PIC from FAR Circuits--just email them and ask for a price.</description>
		<content:encoded><![CDATA[<p>R6-12 can be omitted completely (there&#8217;s no need to tie those pins to VCC because there are internal pullup resistors). Also, you can obtain another PIC from FAR Circuits&#8211;just email them and ask for a price.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Craig Combes</title>
		<link>http://eksfiles.net/digital-setting-circles/circuit-description/comment-page-1/#comment-324</link>
		<dc:creator>Craig Combes</dc:creator>
		<pubDate>Thu, 04 Mar 2010 04:13:13 +0000</pubDate>
		<guid isPermaLink="false">http://test.eksfiles.net/?page_id=212#comment-324</guid>
		<description>Hi Dave,
I got the Bluetooth module today and it&#039;s a surface  mount module that would look much nicer properly mounted on a new board, so I&#039;m going to do a new board (after I wire into your current board to make sure it works).
I was reviewing your schematic and I was wondering if you felt that R6-R12 were really necessary? Can&#039;t those pins all be tied to VCC directly? Also, how could I go about getting another PIC?

Thanks!

Craig Combes</description>
		<content:encoded><![CDATA[<p>Hi Dave,<br />
I got the Bluetooth module today and it&#8217;s a surface  mount module that would look much nicer properly mounted on a new board, so I&#8217;m going to do a new board (after I wire into your current board to make sure it works).<br />
I was reviewing your schematic and I was wondering if you felt that R6-R12 were really necessary? Can&#8217;t those pins all be tied to VCC directly? Also, how could I go about getting another PIC?</p>
<p>Thanks!</p>
<p>Craig Combes</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave</title>
		<link>http://eksfiles.net/digital-setting-circles/circuit-description/comment-page-1/#comment-308</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Sat, 13 Feb 2010 01:53:01 +0000</pubDate>
		<guid isPermaLink="false">http://test.eksfiles.net/?page_id=212#comment-308</guid>
		<description>1) The z command sets the encoder resolutions (ticks per axis revolution):

A = declination resolution low byte
B = declination resolution high byte
C = right ascension resolution low byte
D = right ascension resolution high byte

declination resolution is 256*B + A
right ascension resolution is 256*D + C

So if the resolution on the declination axis is 4000, then the high byte is 15 and the low byte is 160 (15*256 + 160 = 4000).

2) declination position is 256*B + A, and right ascension is 256*D + C.</description>
		<content:encoded><![CDATA[<p>1) The z command sets the encoder resolutions (ticks per axis revolution):</p>
<p>A = declination resolution low byte<br />
B = declination resolution high byte<br />
C = right ascension resolution low byte<br />
D = right ascension resolution high byte</p>
<p>declination resolution is 256*B + A<br />
right ascension resolution is 256*D + C</p>
<p>So if the resolution on the declination axis is 4000, then the high byte is 15 and the low byte is 160 (15*256 + 160 = 4000).</p>
<p>2) declination position is 256*B + A, and right ascension is 256*D + C.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Willy</title>
		<link>http://eksfiles.net/digital-setting-circles/circuit-description/comment-page-1/#comment-307</link>
		<dc:creator>Willy</dc:creator>
		<pubDate>Sat, 13 Feb 2010 00:32:58 +0000</pubDate>
		<guid isPermaLink="false">http://test.eksfiles.net/?page_id=212#comment-307</guid>
		<description>Hello,

I need more information for communications protocol :
I have 2 encoders with 4000 ticks, so

1) if i send the command &#039;zABCD&#039;, what is the value of A,B,C and D ?

2) if i send the command &#039;h&#039;, i receive &#039;ABCD&#039;. The declination position is Ax256+B ?

Thanks for your help.</description>
		<content:encoded><![CDATA[<p>Hello,</p>
<p>I need more information for communications protocol :<br />
I have 2 encoders with 4000 ticks, so</p>
<p>1) if i send the command &#8216;zABCD&#8217;, what is the value of A,B,C and D ?</p>
<p>2) if i send the command &#8216;h&#8217;, i receive &#8216;ABCD&#8217;. The declination position is Ax256+B ?</p>
<p>Thanks for your help.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
