<?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: New CED &#039;M2&#039; Chronograph</title>
	<atom:link href="https://bulletin.accurateshooter.com/2007/04/new-ced-m2-chronograph/feed/" rel="self" type="application/rss+xml" />
	<link>https://bulletin.accurateshooter.com/2007/04/new-ced-m2-chronograph/</link>
	<description>from AccurateShooter.com</description>
	<lastBuildDate>Fri, 03 Apr 2026 15:50:21 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=4.1.26</generator>
	<item>
		<title>By: Matt_D</title>
		<link>https://bulletin.accurateshooter.com/2007/04/new-ced-m2-chronograph/comment-page-1/#comment-43566</link>
		<dc:creator><![CDATA[Matt_D]]></dc:creator>
		<pubDate>Tue, 19 Nov 2013 20:34:35 +0000</pubDate>
		<guid isPermaLink="false">http://accurateshooter.wordpress.com/2007/04/20/new-ced-m2-chronograph/#comment-43566</guid>
		<description><![CDATA[The CED M2&#039;s processor has a clock speed of 48 MHz. Which makes its error rate per clock cycle (given a 3000 fps bullet) 0.0125% (0.375 fps), not 0.6%.

The Shooting Chrony chronographs all have a 1 MHz processor, the slowest of any chrono on the market.  And if you&#039;ll bother to dig in and read their documentation, you&#039;ll find that the 0.5% error rate they advertise is with a 2000 fps bullet.  Which extrapolates to 0.75% at 3000 fps, at which velocity the average error would be 22.5 fps.  So good luck with your dreams of hand loading to a single-digit SD when your chrono randomly introduces 20+ fps errors.

If a Shooting Chrony is a bargain worth the money, then I suppose you could say the same for the Ford Pinto.  That you are satisfied with yours only can mean either your requirements or your standards are very, very low.]]></description>
		<content:encoded><![CDATA[<p>The CED M2&#8217;s processor has a clock speed of 48 MHz. Which makes its error rate per clock cycle (given a 3000 fps bullet) 0.0125% (0.375 fps), not 0.6%.</p>
<p>The Shooting Chrony chronographs all have a 1 MHz processor, the slowest of any chrono on the market.  And if you&#8217;ll bother to dig in and read their documentation, you&#8217;ll find that the 0.5% error rate they advertise is with a 2000 fps bullet.  Which extrapolates to 0.75% at 3000 fps, at which velocity the average error would be 22.5 fps.  So good luck with your dreams of hand loading to a single-digit SD when your chrono randomly introduces 20+ fps errors.</p>
<p>If a Shooting Chrony is a bargain worth the money, then I suppose you could say the same for the Ford Pinto.  That you are satisfied with yours only can mean either your requirements or your standards are very, very low.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Josh Benin</title>
		<link>https://bulletin.accurateshooter.com/2007/04/new-ced-m2-chronograph/comment-page-1/#comment-53</link>
		<dc:creator><![CDATA[Josh Benin]]></dc:creator>
		<pubDate>Sat, 21 Apr 2007 17:51:18 +0000</pubDate>
		<guid isPermaLink="false">http://accurateshooter.wordpress.com/2007/04/20/new-ced-m2-chronograph/#comment-53</guid>
		<description><![CDATA[I read with much interest your recent blog article on the new CED &#039;M2&#039; Chhronograph, and the included comments on chronograph accuracy - interesting because chronographs are the one handloaders&#039; tool which we cannot check.  I encourage you to complete the comparative test between chronographs you mentioned.  While it won&#039;t be conclusive, it certainly should be interesting.
	A couple of comments on your concern with the extreme spreads from your Shooting Chrony are appropriate.  If a chronograph uses a 1 foot screen spacing (common among lower-cost models), and a 1 mHz clock (this is a guess), a 3000 fps projectile takes 1/3000 of a second to cross the screens, the clock counts 333 cycles, and a +/- 1 count error will be 2/333 or 0.6%.  This equates to 18 fps and compares with the 0.5% error Shooting Chrony claims in their website.  On this basis alone, you should not be especially concerned with the ES values of 30-50 fps you mentioned.  They are reasonable compared with instrumental accuracy.  If you want better data, drill the pivot rivets out of your Shooting Chrony, lengthen the cable, and increase the screen spacing to 5 or 10 feet for a low-cost accuracy improvement of 5 to 10X.
	Better yet, forget about ES altogether - statisticians have already solved the problem.  The standard deviation, while not intuitive, is exactly what you want, and given a sufficient sample, will not be affected by measurement errors described above.  Your chronograph probably already calculates the SD for you.  Use it.  Chances are, 95% of your shots will be within 2 SD of the average, or chances are 1 shot in 20 won&#039;t be.
	No, I have no association with Shooting Chrony, although I do own one and think that for $55 it was a great bargain.  Understand that it&#039;s a tool for the casual user, not a lab instrument, its limitations are exactly as you&#039;ve described, and the work-around is either lengthen the spacing, or just forget ES and use the SD.]]></description>
		<content:encoded><![CDATA[<p>I read with much interest your recent blog article on the new CED &#8216;M2&#8242; Chhronograph, and the included comments on chronograph accuracy &#8211; interesting because chronographs are the one handloaders&#8217; tool which we cannot check.  I encourage you to complete the comparative test between chronographs you mentioned.  While it won&#8217;t be conclusive, it certainly should be interesting.<br />
	A couple of comments on your concern with the extreme spreads from your Shooting Chrony are appropriate.  If a chronograph uses a 1 foot screen spacing (common among lower-cost models), and a 1 mHz clock (this is a guess), a 3000 fps projectile takes 1/3000 of a second to cross the screens, the clock counts 333 cycles, and a +/- 1 count error will be 2/333 or 0.6%.  This equates to 18 fps and compares with the 0.5% error Shooting Chrony claims in their website.  On this basis alone, you should not be especially concerned with the ES values of 30-50 fps you mentioned.  They are reasonable compared with instrumental accuracy.  If you want better data, drill the pivot rivets out of your Shooting Chrony, lengthen the cable, and increase the screen spacing to 5 or 10 feet for a low-cost accuracy improvement of 5 to 10X.<br />
	Better yet, forget about ES altogether &#8211; statisticians have already solved the problem.  The standard deviation, while not intuitive, is exactly what you want, and given a sufficient sample, will not be affected by measurement errors described above.  Your chronograph probably already calculates the SD for you.  Use it.  Chances are, 95% of your shots will be within 2 SD of the average, or chances are 1 shot in 20 won&#8217;t be.<br />
	No, I have no association with Shooting Chrony, although I do own one and think that for $55 it was a great bargain.  Understand that it&#8217;s a tool for the casual user, not a lab instrument, its limitations are exactly as you&#8217;ve described, and the work-around is either lengthen the spacing, or just forget ES and use the SD.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
