<?xml version="1.0" encoding="UTF-8"?>
<!--Generated by Squarespace Site Server v5.9.1 (http://www.squarespace.com/) on Tue, 09 Feb 2010 08:48:30 GMT--><rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:rss="http://purl.org/rss/1.0/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:cc="http://web.resource.org/cc/"><rss:channel rdf:about="http://n5fdl.com/davids-blog/"><rss:title>N5FDL's Amateur Radio and Emcomm Blog</rss:title><rss:link>http://n5fdl.com/davids-blog/</rss:link><rss:description>David Coursey's blog about amateur "ham" radio and emergency communications.</rss:description><dc:language>en-US</dc:language><dc:date>2010-02-09T08:48:30Z</dc:date><admin:generatorAgent rdf:resource="http://www.squarespace.com/">Squarespace Site Server v5.9.1 (http://www.squarespace.com/)</admin:generatorAgent><rss:items><rdf:Seq><rdf:li rdf:resource="http://n5fdl.com/davids-blog/2010/1/26/yaesu-confirms-ftm-350r-troubles.html"/><rdf:li rdf:resource="http://n5fdl.com/davids-blog/2010/1/25/ftm-350r-bad-navigation-video.html"/><rdf:li rdf:resource="http://n5fdl.com/davids-blog/2010/1/25/the-ftm-350r-navigation-doesnt-work.html"/><rdf:li rdf:resource="http://n5fdl.com/davids-blog/2010/1/24/odd-ftm-350r-behavior.html"/><rdf:li rdf:resource="http://n5fdl.com/davids-blog/2010/1/22/arrls-97113-wording.html"/><rdf:li rdf:resource="http://n5fdl.com/davids-blog/2010/1/19/arrl-to-offer-own-97113-wording.html"/><rdf:li rdf:resource="http://n5fdl.com/davids-blog/2010/1/19/arrl-to-seek-97113-change.html"/><rdf:li rdf:resource="http://n5fdl.com/davids-blog/2010/1/18/n5fdlcom-handles-haiti-hw-inquiry.html"/><rdf:li rdf:resource="http://n5fdl.com/davids-blog/2010/1/15/yaesu-ftm-350r-update.html"/><rdf:li rdf:resource="http://n5fdl.com/davids-blog/2010/1/15/question-are-you-using-depiction.html"/></rdf:Seq></rss:items></rss:channel><rss:item rdf:about="http://n5fdl.com/davids-blog/2010/1/26/yaesu-confirms-ftm-350r-troubles.html"><rss:title>Yaesu Confirms FTM-350R Troubles</rss:title><rss:link>http://n5fdl.com/davids-blog/2010/1/26/yaesu-confirms-ftm-350r-troubles.html</rss:link><dc:creator>David Coursey, N5FDL</dc:creator><dc:date>2010-01-26T17:20:05Z</dc:date><dc:subject>APRS Radios Reviews Yaesu ftm-350r</dc:subject><content:encoded><![CDATA[<p>This morning, I received an e-mail from Yaesu tech support telling me they had reproduced the NAVIgation problems that I&#8217;ve been experiencing and reporting on. Yaesu USA has sought help from Japan in dealing with the problem.</p>
<p>Do you suppose this radio was actually tested before it was released? How difficult is it drive around and see if the navigation function points in the right direction?</p>
<p>It appears the radio cannot be changed with a firmware upgrade, so I am expecting they may all need to go back to the factory. As I remember, there was also a recall of VX-8&#8217;s when they were released.</p>
]]></content:encoded></rss:item><rss:item rdf:about="http://n5fdl.com/davids-blog/2010/1/25/ftm-350r-bad-navigation-video.html"><rss:title>FTM-350R Bad Navigation Video</rss:title><rss:link>http://n5fdl.com/davids-blog/2010/1/25/ftm-350r-bad-navigation-video.html</rss:link><dc:creator>David Coursey, N5FDL</dc:creator><dc:date>2010-01-26T05:00:51Z</dc:date><dc:subject>APRS Radios Reviews Yaesu ftm-350r</dc:subject><content:encoded><![CDATA[<p>As a demonstration for Yaesu, I drove around and documented the problems I am having with the NAVI feature of the new FTM-350R receiver. I misspeak a couple of times&#8212;reversing left and right&#8212;but the video clearly shows what I am describing and I repeat the correct information a number of times. Also, I had another crash tonight, while the radio was running in my parked car.</p>
<p>&nbsp;</p>
<p><object width="480" height="295"><param name="movie" value="http://www.youtube.com/v/igbN2jUZsRU&hl=en_US&fs=1&rel=0"></param><param name="allowFullScreen" value="true"></param><param name="allowscriptaccess" value="always"></param><embed src="http://www.youtube.com/v/igbN2jUZsRU&hl=en_US&fs=1&rel=0" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="480" height="295"></embed></object></p>
<p>&nbsp;</p>
]]></content:encoded></rss:item><rss:item rdf:about="http://n5fdl.com/davids-blog/2010/1/25/the-ftm-350r-navigation-doesnt-work.html"><rss:title>The FTM-350R: Navigation Doesn't Work</rss:title><rss:link>http://n5fdl.com/davids-blog/2010/1/25/the-ftm-350r-navigation-doesnt-work.html</rss:link><dc:creator>David Coursey, N5FDL</dc:creator><dc:date>2010-01-25T21:52:31Z</dc:date><dc:subject>APRS Radios Reviews Yaesu ftm-350r</dc:subject><content:encoded><![CDATA[<p><span class="thumbnail-image-float-right ssNonEditable"><span><a href="javascript:showFullImage('/display/ShowImage?imageUrl=%2Fstorage%2Fpost-images%2Fiphone-20100124165326-1.jpg%3F__SQUARESPACE_CACHEVERSION%3D1264456512411',450,600);"><img src="http://n5fdl.com/storage/thumbnails/2632218-5497370-thumbnail.jpg?__SQUARESPACE_CACHEVERSION=1264456533524" alt="" /></a></span><span class="thumbnail-caption" style="width: 152px;">Click for larger image</span></span>This photo illustrates&#8212;you have to take my word for it until I can post a video&#8212;how my FTM-350R will not properly navigate to a &#8220;point&#8221; stored in the radio&#8217;s memory. In this case, I want to navigate to WY6E-11, which is ahead of me and off to the left.</p>
<p>However, the display clearly shows the destination &#8220;D&#8221; as being behind me and off to the right.</p>
<p>The error changes depending on the direction of travel.</p>
<p>Going north, the target error is to the right but north and south seem to be ahead and behind, where they should be.</p>
<p>Going west, a target that should be ahead displays as behind and vice versa. But, when when due south, appears properly in the display. Until you drive past, when the destination becomes ahead of you when it&#8217;s really behind. Not to worry, when the destination was in front, it displayed as behind.</p>
<p>I am talking to Yaesu about this.</p>
]]></content:encoded></rss:item><rss:item rdf:about="http://n5fdl.com/davids-blog/2010/1/24/odd-ftm-350r-behavior.html"><rss:title>Odd FTM-350R Behavior</rss:title><rss:link>http://n5fdl.com/davids-blog/2010/1/24/odd-ftm-350r-behavior.html</rss:link><dc:creator>David Coursey, N5FDL</dc:creator><dc:date>2010-01-24T21:08:51Z</dc:date><dc:subject>APRS Radios Reviews ftm-350r</dc:subject><content:encoded><![CDATA[<p>I need the help of my fellow FTM-350R owners to figure out whether I am doing something wrong or if this radio has a real problem. (No, the crashing issue has not recurred).</p>
<p><span class="Apple-style-span">OK, I want to use the NAVI function to drive to a location or &#8220;point&#8221; as the radio calls it. I have received a packet from a friend at his house. I saved the location as a point. </span></p>
<p>I am now navigating to the point. I am south of the point, headed north, the NAVI screen (which I think is &#8220;heading up&#8221; on the display) shows me heading toward the point.</p>
<p>The point is two blocks off the road I am on. It is to the west (left on the display) of the road. But, as I get closer, instead of deviating to the left (west) and pointing toward the point, the target moves right (east) about the same number of degrees as is should me moving to the left.</p>
<p>When I am going west (and the target is north of me) it seems to do the same thing, moving the target northeast when it should be moving northwest.&nbsp;</p>
<p>When I drive to the target, I get the GOAL indication as I would expect.</p>
<p>Can someone attempt to reproduce this behavior? It must be something I&#8217;ve set-up wrong, but with these lousy manuals, who can tell?</p>
]]></content:encoded></rss:item><rss:item rdf:about="http://n5fdl.com/davids-blog/2010/1/22/arrls-97113-wording.html"><rss:title>ARRL's 97.113 Wording</rss:title><rss:link>http://n5fdl.com/davids-blog/2010/1/22/arrls-97113-wording.html</rss:link><dc:creator>David Coursey, N5FDL</dc:creator><dc:date>2010-01-22T16:32:07Z</dc:date><dc:subject></dc:subject><content:encoded><![CDATA[<p>Here is the proposed wording for an amendment to 97.113 that was passed by the ARRL&#8217;s Board of Directors at its 1-15/16 meeting:</p>
<blockquote>
<p><span class="Apple-style-span" style="border-collapse: collapse; font-family: arial,sans-serif; font-size: 13px;">&sect;97.113 Prohibited Transmissions<br />(a) No amateur station shall transmit:<br />**********<br />(3) Communications in which the station licensee or control operator has a pecuniary interest, including communications on behalf of an employer, except that the station licensee or control operator may, on behalf an employer, participate in emergency preparedness and disaster drills that include amateur operations for the purpose of emergency response, disaster relief or the testing and maintenance of equipment used for that purpose. Amateur operators may, however, notify other amateur operators of the availability for sale or trade of apparatus normally used in an amateur station, provided that such activity is not conducted on a regular basis;</span></p>
</blockquote>
<p><span class="Apple-style-span" style="border-collapse: collapse; font-family: arial,sans-serif; font-size: 13px;">This is not terrible wording and having spent weeks working on wording, that is no small feat&#8212;especially for a large committee. Frankly, I was 50/50 on whether the League would support a change to 97.113. It will be interesting to read the final minutes of the meeting and see how the debate went.</span></p>
<p><span class="Apple-style-span" style="border-collapse: collapse; font-family: arial,sans-serif; font-size: 13px;">My main concern about this wording is that its too wordy (amateurs may participate in drills that include amateurs!). The lack of breaking the paragraph into pieces makes it seem like swap nets have something to do with emergency response (at least remove the &#8220;however&#8221; from the next sentence).<br /></span></p>
<p><span class="Apple-style-span" style="border-collapse: collapse; font-family: arial,sans-serif; font-size: 13px;">The major failing is that there is no provision for the employee who runs the RACES program to talk on the radio about the program, or to its members about program &#8220;business&#8221; such as meetings, outside of organized drills and exercises. I am pretty sure the wording does include regularly-scheduled nets and such but don&#8217;t understand why the &#8220;testing&#8221; wording is necessary. Is testing so special that it needs to be called out?</span></p>
<p><span class="Apple-style-span" style="border-collapse: collapse; font-family: arial,sans-serif; font-size: 13px;">I am sure others have the same sort of complaints about our wording, which I&#8212;of course&#8212;think is much better. Heck, wording we didn&#8217;t use is better than this. But, it is not bad wording. It does accomplish the task and the FCC is unlikely to use anyone&#8217;s wording but its own. Any proposed wording is just to make sure the FCC understands the issue and what you want to accomplish.<br /></span></p>
<p><span class="Apple-style-span" style="border-collapse: collapse; font-family: arial,sans-serif; font-size: 13px;">It is good to have the ARRL involved on &#8220;the right side&#8221; of this issue. I hope the FCC will soon assign an RM number and designate comment periods so we can get this change into the rules. It is my fervent hope the League won&#8217;t feel the need to file a petition of its own and possibly delay the process.<br /></span></p>
]]></content:encoded></rss:item><rss:item rdf:about="http://n5fdl.com/davids-blog/2010/1/19/arrl-to-offer-own-97113-wording.html"><rss:title>ARRL to Offer Own 97.113 Wording</rss:title><rss:link>http://n5fdl.com/davids-blog/2010/1/19/arrl-to-offer-own-97113-wording.html</rss:link><dc:creator>David Coursey, N5FDL</dc:creator><dc:date>2010-01-20T04:44:45Z</dc:date><dc:subject>97.113 ARRL Appropriate Use Controversies</dc:subject><content:encoded><![CDATA[<p>Before spending lots of time high-fiveing and thanking the ARRL BoD, consider this:</p>
<p>The Board passed preferred wording for changes to 97.113 and that wording has not been released.</p>
<p>This raises the possibility that to mark its territory (after helping to create the problem) the League will file its own petition rather than try to get this issue handled as quickly as possible.</p>
<p>I expect to see the wording in a few days, when the actual minutes of the meeting are published. I hope they won&#8217;t pose a problem.</p>
<p>Having spent weeks working with Gordon West and Tom Blackwell (primary author) on the wording in our petition, plus getting lots of feedback from the field, I know you can&#8217;t just pick some nice-sounding words.</p>
<p>We will see what Newington does.</p>
]]></content:encoded></rss:item><rss:item rdf:about="http://n5fdl.com/davids-blog/2010/1/19/arrl-to-seek-97113-change.html"><rss:title>ARRL to Seek 97.113 Change</rss:title><rss:link>http://n5fdl.com/davids-blog/2010/1/19/arrl-to-seek-97113-change.html</rss:link><dc:creator>David Coursey, N5FDL</dc:creator><dc:date>2010-01-19T21:40:25Z</dc:date><dc:subject>97.113 ARRL Controversies</dc:subject><content:encoded><![CDATA[<p>From ARRL.org&#8217;s <a class="offsite-link-inline" href="http://www.arrl.org/news/stories/2010/01/19/11294/?nc=1﻿" target="_blank">official report</a> on the Board of Directors meeting (1/15-16):</p>
<blockquote>
<p>The Board instructed the ARRL staff to seek a change in Section 97.113(a)(3) of the FCC rules to permit amateurs, on behalf of an employer, to participate in emergency preparedness and disaster drills that include Amateur operations.&nbsp;</p>
</blockquote>
<ul>
</ul>
<p>On behalf of the petitioners, Gordon West, WB6NOA, Tom Blackwell, N5GAR, and myself, thank you to the ARRL BoD for supporting the effort to change a rule that actually hampers our emergency response.</p>
<p>I will add additional commentary later when I am back in the shack.</p>
]]></content:encoded></rss:item><rss:item rdf:about="http://n5fdl.com/davids-blog/2010/1/18/n5fdlcom-handles-haiti-hw-inquiry.html"><rss:title>N5FDL.COM Handles Haiti H&amp;W Inquiry</rss:title><rss:link>http://n5fdl.com/davids-blog/2010/1/18/n5fdlcom-handles-haiti-hw-inquiry.html</rss:link><dc:creator>David Coursey, N5FDL</dc:creator><dc:date>2010-01-18T16:11:37Z</dc:date><dc:subject>Incidents Traffic Handling haiti</dc:subject><content:encoded><![CDATA[<p><span class="Apple-style-span" style="font-family: arial,sans-serif; font-size: 13px;">I was surprised last night to receive an e-mail request to handle a welfare inquiry from the family of Fr. John Hinault, HH6JH, who has reportedly been on the air since the earthquake. </span></p>
<p>His cousin, Rev. Armand Hinault, said he heard that Fr. Hinault was alive and had been on his ham radio and was apparently alive.</p>
<p><span class="Apple-style-span" style="font-family: arial,sans-serif; font-size: 13px;">
<div>Fr. Hinault must have Googled his brother and found the situation reports that I posted on on this site, from which he contacted me.</div>
<div><span class="Apple-converted-space">&nbsp;</span></div>
<div>This morning, I contacted one of the net controls for the International Assistance and Traffic Net (14,300), where HH6JH reportedly checked in. The NCS, Bob, KC4TVO, agreed to handle the request and follow up with Rev. Hinault. Hopefully, the contact will be made.</div>
<div></div>
<div>Interesting story about how e-mail, website, Google, email, telephone, and amateur radio (the last miles) are combining to provide emergency welfare communications.&nbsp;</div>
<div></div>
<div>Thanks to John, AF6JP, for checking HF for me last night right after I got the message from Rev. Hinault.</div>
</span></p>
<table>
<tbody>
<tr>
<td style="margin: 0px; font-family: arial,sans-serif;"><br /></td>
<td style="margin: 0px; font-family: arial,sans-serif;"><br /></td>
<td style="margin: 0px; font-family: arial,sans-serif;"><br /></td>
<td style="margin: 0px; font-family: arial,sans-serif;"><br /></td>
<td style="margin: 0px; font-family: arial,sans-serif;"><br class="Apple-interchange-newline" /></td>
</tr>
</tbody>
</table>
]]></content:encoded></rss:item><rss:item rdf:about="http://n5fdl.com/davids-blog/2010/1/15/yaesu-ftm-350r-update.html"><rss:title>Yaesu FTM-350R Update</rss:title><rss:link>http://n5fdl.com/davids-blog/2010/1/15/yaesu-ftm-350r-update.html</rss:link><dc:creator>David Coursey, N5FDL</dc:creator><dc:date>2010-01-15T21:12:28Z</dc:date><dc:subject>APRS Radios Reviews ftm-350r</dc:subject><content:encoded><![CDATA[<p>As of today, I have not had any additional crash incidents. I have heard from a reader who has experienced crashes and hope to get an update.</p>
<p>However, my lack of crashes could be a lack of &#8220;on time&#8221; for the radio, which has not seen lots of use. With the help of Dan, N6VLG, I now have a longer Ethernet cable to connect the radio head to the base unit. This will allow me to move the base unit closer to my Powerpole block and reduce by a number of feet the length of the power cord.</p>
<p>If the lock-ups are really a function of occasional voltage drops, then my problems should be over.</p>
<p>Yaesu has asked that I send the machine in for a look-see, which I will wait to do only if the problem recurs after I get the power lead shortened.</p>
<p>Otherwise, this is a very nice radio that has some changes that I hope can be fixed. I need to find out if Yaesu plans to provide firmware upgrades for this radio, or whether than is even possible. I was shocked to find out that adding additional APRS capabilities to the VX-8 requires changing physical componentry.</p>
<p>I will be talking about the radio and what it is like from a happy user perspective soon.</p>
]]></content:encoded></rss:item><rss:item rdf:about="http://n5fdl.com/davids-blog/2010/1/15/question-are-you-using-depiction.html"><rss:title>Question: Are you using Depiction?</rss:title><rss:link>http://n5fdl.com/davids-blog/2010/1/15/question-are-you-using-depiction.html</rss:link><dc:creator>David Coursey, N5FDL</dc:creator><dc:date>2010-01-15T21:10:10Z</dc:date><dc:subject></dc:subject><content:encoded><![CDATA[<p>The software app from www.depiction.com. If you are, please drop me a note. david@coursey.com</p>
]]></content:encoded></rss:item></rdf:RDF>