<?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: Electrical Block Detection	</title>
	<atom:link href="https://blog.model-train-help.com/2021/06/electrical-block-detection.html/feed" rel="self" type="application/rss+xml" />
	<link>https://blog.model-train-help.com/2021/06/electrical-block-detection.html?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=electrical-block-detection</link>
	<description>Model railroads and model trains</description>
	<lastBuildDate>Wed, 11 Aug 2021 05:10:21 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
	<item>
		<title>
		By: The N-Scale Nerd		</title>
		<link>https://blog.model-train-help.com/2021/06/electrical-block-detection.html#comment-53834</link>

		<dc:creator><![CDATA[The N-Scale Nerd]]></dc:creator>
		<pubDate>Wed, 11 Aug 2021 05:10:21 +0000</pubDate>
		<guid isPermaLink="false">http://blog.model-train-help.com/?p=6154#comment-53834</guid>

					<description><![CDATA[If you haven&#039;t gone down the NCE path yet, check out Digikeijs and the DR5000 processor.

Their DR4088 is one super economical block detector. The interfacing is easy, screw terminals and the cable into the DR5000. 

For an economical launch into block detection this is the way to go.
To use NCE block detection products to monitor 16 blocks starts to get expensive.
Just wait till you see the cost of transponding with NCE!

Digikeijs have that solved with their DR5088 which is about A$12 per block for 16 blocks.
(You do have to talk Loconet but that&#039;s provided by the DR5000.)

Having been down the NCE path, I&#039;m a bit of a convert!]]></description>
			<content:encoded><![CDATA[<p>If you haven&#8217;t gone down the NCE path yet, check out Digikeijs and the DR5000 processor.</p>
<p>Their DR4088 is one super economical block detector. The interfacing is easy, screw terminals and the cable into the DR5000. </p>
<p>For an economical launch into block detection this is the way to go.<br />
To use NCE block detection products to monitor 16 blocks starts to get expensive.<br />
Just wait till you see the cost of transponding with NCE!</p>
<p>Digikeijs have that solved with their DR5088 which is about A$12 per block for 16 blocks.<br />
(You do have to talk Loconet but that&#8217;s provided by the DR5000.)</p>
<p>Having been down the NCE path, I&#8217;m a bit of a convert!</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Nigel		</title>
		<link>https://blog.model-train-help.com/2021/06/electrical-block-detection.html#comment-53595</link>

		<dc:creator><![CDATA[Nigel]]></dc:creator>
		<pubDate>Fri, 23 Jul 2021 06:06:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.model-train-help.com/?p=6154#comment-53595</guid>

					<description><![CDATA[You can contact David Fenton from megapointscontrollers.co.uk with your exact needs and hemight be able to advise you and the company ships worldwide.  I have used other products from him and they are excellent.  I&#039;ve no direct experience of his block detection products but what I think you&#039;d need are one detecter per block which then feed into a feedback module and then into a multipanel processor into which you&#039;d connect the LEDs.  

]]></description>
			<content:encoded><![CDATA[<p>You can contact David Fenton from megapointscontrollers.co.uk with your exact needs and hemight be able to advise you and the company ships worldwide.  I have used other products from him and they are excellent.  I&#8217;ve no direct experience of his block detection products but what I think you&#8217;d need are one detecter per block which then feed into a feedback module and then into a multipanel processor into which you&#8217;d connect the LEDs.  </p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
