<?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/"
		xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: RFM12 Tutorial &#8211; Part2</title>
	<atom:link href="http://blog.strobotics.com.au/2008/06/17/rfm12-tutorial-part2/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.strobotics.com.au/2008/06/17/rfm12-tutorial-part2/</link>
	<description>Where Photographer and Geek merge......</description>
	<lastBuildDate>Sun, 18 Dec 2011 11:07:23 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: chippchipp</title>
		<link>http://blog.strobotics.com.au/2008/06/17/rfm12-tutorial-part2/comment-page-3/#comment-1175</link>
		<dc:creator>chippchipp</dc:creator>
		<pubDate>Sun, 18 Dec 2011 11:07:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.everythingrobotics.com/?p=135#comment-1175</guid>
		<description>hi,
The last time I contacted you was Dec 2010.
Now have my project working fully and I think I understand about 55% of the workings of the RFM12b.
The two modules communicate 100% no problems.
One thing I have notice. 
I replaced my original Rfm 12b modules with two new rfm12b which I purchased in july 2011. 
After power up i found problems with the first second and maybe third communication data packet occurs now and then but after say the fourth data packet the two modules  will communicate continuously, not missing any data thereafter until I power off and power up or I move one of the modules out and then back in range.
I reverse fitted the new  modules (swapped them round on my embedded application) and guess what.
I modules communicated perfectly from power up??
Have you seen this or have any ideas to what to change to debug or tune this out.
The two modules are embedded on exactly the same pcbs..
Just one module acts as the master and the other the slave.
I have increased the preambles.No change 
Are there any parameters which you could point me to look at

Thanks
Chippchipp</description>
		<content:encoded><![CDATA[<p>hi,<br />
The last time I contacted you was Dec 2010.<br />
Now have my project working fully and I think I understand about 55% of the workings of the RFM12b.<br />
The two modules communicate 100% no problems.<br />
One thing I have notice.<br />
I replaced my original Rfm 12b modules with two new rfm12b which I purchased in july 2011.<br />
After power up i found problems with the first second and maybe third communication data packet occurs now and then but after say the fourth data packet the two modules  will communicate continuously, not missing any data thereafter until I power off and power up or I move one of the modules out and then back in range.<br />
I reverse fitted the new  modules (swapped them round on my embedded application) and guess what.<br />
I modules communicated perfectly from power up??<br />
Have you seen this or have any ideas to what to change to debug or tune this out.<br />
The two modules are embedded on exactly the same pcbs..<br />
Just one module acts as the master and the other the slave.<br />
I have increased the preambles.No change<br />
Are there any parameters which you could point me to look at</p>
<p>Thanks<br />
Chippchipp</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen Eaton</title>
		<link>http://blog.strobotics.com.au/2008/06/17/rfm12-tutorial-part2/comment-page-3/#comment-1167</link>
		<dc:creator>Stephen Eaton</dc:creator>
		<pubDate>Wed, 28 Sep 2011 01:43:51 +0000</pubDate>
		<guid isPermaLink="false">http://blog.everythingrobotics.com/?p=135#comment-1167</guid>
		<description>@Amir  I&#039;ve not used the non-fifo mode but it appears in the documentation that you need to set ef=0 and use pin 7 to get access to the incoming data for Rx and for Tx you need to use pin 6 to send your data.</description>
		<content:encoded><![CDATA[<p>@Amir  I&#8217;ve not used the non-fifo mode but it appears in the documentation that you need to set ef=0 and use pin 7 to get access to the incoming data for Rx and for Tx you need to use pin 6 to send your data.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Amir</title>
		<link>http://blog.strobotics.com.au/2008/06/17/rfm12-tutorial-part2/comment-page-3/#comment-1166</link>
		<dc:creator>Amir</dc:creator>
		<pubDate>Tue, 27 Sep 2011 14:20:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.everythingrobotics.com/?p=135#comment-1166</guid>
		<description>hi 
how can I used Rfm12 In No fifo mode?
Iwant read data direct. no in fifo register</description>
		<content:encoded><![CDATA[<p>hi<br />
how can I used Rfm12 In No fifo mode?<br />
Iwant read data direct. no in fifo register</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scurvyrat &#8212; Reading the ARSSI pin on the Si4221/HopeRF 12B</title>
		<link>http://blog.strobotics.com.au/2008/06/17/rfm12-tutorial-part2/comment-page-3/#comment-1154</link>
		<dc:creator>Scurvyrat &#8212; Reading the ARSSI pin on the Si4221/HopeRF 12B</dc:creator>
		<pubDate>Tue, 14 Jun 2011 21:52:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.everythingrobotics.com/?p=135#comment-1154</guid>
		<description>[...] has been a bunch written about this signal. You can read about it here (German, with photo), here and here. There is work to translate this signal to an OOK [...]</description>
		<content:encoded><![CDATA[<p>[...] has been a bunch written about this signal. You can read about it here (German, with photo), here and here. There is work to translate this signal to an OOK [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ulf_l</title>
		<link>http://blog.strobotics.com.au/2008/06/17/rfm12-tutorial-part2/comment-page-3/#comment-1144</link>
		<dc:creator>ulf_l</dc:creator>
		<pubDate>Thu, 30 Dec 2010 10:42:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.everythingrobotics.com/?p=135#comment-1144</guid>
		<description>Hello

You wrote &quot;nFFS – If pulled high then the FIFO is selected&quot;. As I understood the datasheet the pin must be pulled low to select the FIFO.

Ulf</description>
		<content:encoded><![CDATA[<p>Hello</p>
<p>You wrote &#8220;nFFS – If pulled high then the FIFO is selected&#8221;. As I understood the datasheet the pin must be pulled low to select the FIFO.</p>
<p>Ulf</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen Eaton</title>
		<link>http://blog.strobotics.com.au/2008/06/17/rfm12-tutorial-part2/comment-page-3/#comment-1105</link>
		<dc:creator>Stephen Eaton</dc:creator>
		<pubDate>Fri, 10 Dec 2010 01:55:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.everythingrobotics.com/?p=135#comment-1105</guid>
		<description>@chippchipp

Yes I can certainly appreciate what rfm12 newbies go through.  the biggest problems is what comes first the chicken or the egg, e.g. is the problem in the Tx, or is it in the Rx side of things.  

I certainly agree with you.  I could not have got my original design working without an oscilloscope watching the CLK and the MOSI/MISO  however this was a pain as I only have a two channel CRO, I&#039;ve since treated myself to a logic analyser that can decode SPI and find this invaluable when I troubleshoot.

When I get around to finishing off the tutorials I&#039;ll look at putting some timing diagrams on.

stephen...</description>
		<content:encoded><![CDATA[<p>@chippchipp</p>
<p>Yes I can certainly appreciate what rfm12 newbies go through.  the biggest problems is what comes first the chicken or the egg, e.g. is the problem in the Tx, or is it in the Rx side of things.  </p>
<p>I certainly agree with you.  I could not have got my original design working without an oscilloscope watching the CLK and the MOSI/MISO  however this was a pain as I only have a two channel CRO, I&#8217;ve since treated myself to a logic analyser that can decode SPI and find this invaluable when I troubleshoot.</p>
<p>When I get around to finishing off the tutorials I&#8217;ll look at putting some timing diagrams on.</p>
<p>stephen&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: chippchipp</title>
		<link>http://blog.strobotics.com.au/2008/06/17/rfm12-tutorial-part2/comment-page-3/#comment-1104</link>
		<dc:creator>chippchipp</dc:creator>
		<pubDate>Tue, 07 Dec 2010 14:49:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.everythingrobotics.com/?p=135#comment-1104</guid>
		<description>Hi Stephen
I have been researching and developting an application using the RFM12B.The data on this module is not good,
What i have noticed is a Digital signal analyzer or scope  is required becasue of the lacking data sheets as to correct program flow.
What would be a good start is if an experience rfm developer(yourself)  could provide  timing diagrams showing the state of lines 
NSEL,SCK,SDI,SDO,nIRQ, and VDI in relationship to el,et,synthersizer/pa etc,etc when running a sample program.
Now i am using a scope things are becoming much easier to grasp
Chippchipp</description>
		<content:encoded><![CDATA[<p>Hi Stephen<br />
I have been researching and developting an application using the RFM12B.The data on this module is not good,<br />
What i have noticed is a Digital signal analyzer or scope  is required becasue of the lacking data sheets as to correct program flow.<br />
What would be a good start is if an experience rfm developer(yourself)  could provide  timing diagrams showing the state of lines<br />
NSEL,SCK,SDI,SDO,nIRQ, and VDI in relationship to el,et,synthersizer/pa etc,etc when running a sample program.<br />
Now i am using a scope things are becoming much easier to grasp<br />
Chippchipp</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: realheaven</title>
		<link>http://blog.strobotics.com.au/2008/06/17/rfm12-tutorial-part2/comment-page-3/#comment-1081</link>
		<dc:creator>realheaven</dc:creator>
		<pubDate>Mon, 04 Oct 2010 16:14:33 +0000</pubDate>
		<guid isPermaLink="false">http://blog.everythingrobotics.com/?p=135#comment-1081</guid>
		<description>@ geo 116

you may choose RFM12 instead of RFM12B because RFM12 can run well at 5V so there&#039;s only one power supply for the two devices and to manipulate those RF is the same.</description>
		<content:encoded><![CDATA[<p>@ geo 116</p>
<p>you may choose RFM12 instead of RFM12B because RFM12 can run well at 5V so there&#8217;s only one power supply for the two devices and to manipulate those RF is the same.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: RFM12 Tutorial &#8211; Part1</title>
		<link>http://blog.strobotics.com.au/2008/06/17/rfm12-tutorial-part2/comment-page-3/#comment-1069</link>
		<dc:creator>RFM12 Tutorial &#8211; Part1</dc:creator>
		<pubDate>Mon, 26 Jul 2010 14:00:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.everythingrobotics.com/?p=135#comment-1069</guid>
		<description>[...] Next &#8211; Part 2 [...]</description>
		<content:encoded><![CDATA[<p>[...] Next &#8211; Part 2 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen Eaton</title>
		<link>http://blog.strobotics.com.au/2008/06/17/rfm12-tutorial-part2/comment-page-3/#comment-1068</link>
		<dc:creator>Stephen Eaton</dc:creator>
		<pubDate>Thu, 22 Jul 2010 03:25:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.everythingrobotics.com/?p=135#comment-1068</guid>
		<description>@geo

The RFM12B has 5V tolerant I/O, however in saying that I wouldn&#039;t leave it running at 5V for an application as it may shorten it&#039;s life.  When I first started development I didn&#039;t use shifters etc and all ran ok.</description>
		<content:encoded><![CDATA[<p>@geo</p>
<p>The RFM12B has 5V tolerant I/O, however in saying that I wouldn&#8217;t leave it running at 5V for an application as it may shorten it&#8217;s life.  When I first started development I didn&#8217;t use shifters etc and all ran ok.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.523 seconds -->

