<?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 MK-1 V1.22 Beta update</title>
	<atom:link href="http://www.hamgadgets.com/blog/2010/07/new-mk-1-v1-22-beta-update/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.hamgadgets.com/blog/2010/07/new-mk-1-v1-22-beta-update/</link>
	<description>News and updates about HamGadgets products</description>
	<lastBuildDate>Fri, 01 Apr 2011 14:55:44 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Dale, N0XAS</title>
		<link>http://www.hamgadgets.com/blog/2010/07/new-mk-1-v1-22-beta-update/comment-page-1/#comment-1033</link>
		<dc:creator>Dale, N0XAS</dc:creator>
		<pubDate>Tue, 20 Jul 2010 15:09:55 +0000</pubDate>
		<guid isPermaLink="false">http://hamgadgets.com/blog/?p=259#comment-1033</guid>
		<description>Roy,

I&#039;ll look into the items you mentioned.  I&#039;m not able to replicate the first one; when I set F=99 and L=Y, I still get the speed readout just fine.  You are definitely running 1.21 still, though...  you may want to check to make sure your mk1upgr.hex file is normal (should look like the example below).  Sometimes the files get corrupted  when going between Windows, Mac or Linux.  A valid HEX file should look similar to this:

&lt;code&gt;:0408000024EF63F08E
:080808005DEF04F000000000A8
:100810000000000000000000056ED8CF06F0E0CF19
:1008200007F00001E9CF0DF0EACF08F0E1CF09F0C1
:10083000E2CF0AF0D9CF0BF0DACF0CF0F3CF14F0FF
:10084000F4CF15F0FACF16F000C00FF001C010F091&lt;/code&gt;</description>
		<content:encoded><![CDATA[<p>Roy,</p>
<p>I&#8217;ll look into the items you mentioned.  I&#8217;m not able to replicate the first one; when I set F=99 and L=Y, I still get the speed readout just fine.  You are definitely running 1.21 still, though&#8230;  you may want to check to make sure your mk1upgr.hex file is normal (should look like the example below).  Sometimes the files get corrupted  when going between Windows, Mac or Linux.  A valid HEX file should look similar to this:</p>
<p><code>:0408000024EF63F08E<br />
:080808005DEF04F000000000A8<br />
:100810000000000000000000056ED8CF06F0E0CF19<br />
:1008200007F00001E9CF0DF0EACF08F0E1CF09F0C1<br />
:10083000E2CF0AF0D9CF0BF0DACF0CF0F3CF14F0FF<br />
:10084000F4CF15F0FACF16F000C00FF001C010F091</code></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roy Lehner, WA2SON</title>
		<link>http://www.hamgadgets.com/blog/2010/07/new-mk-1-v1-22-beta-update/comment-page-1/#comment-1032</link>
		<dc:creator>Roy Lehner, WA2SON</dc:creator>
		<pubDate>Tue, 20 Jul 2010 14:29:49 +0000</pubDate>
		<guid isPermaLink="false">http://hamgadgets.com/blog/?p=259#comment-1032</guid>
		<description>Hello Dale,

I&#039;ve loaded the V1.22 program into my MK-1.  I THINK  I installed this update correctly----when I query the MK-1 as to the version it responds V1.21R. Hmmm.

Just a few items which I have noticed about my MK-1.   

IF:
  F=99
  L=Y  (letter spacing enabled)
THEN:
  The M1 + M3 SPEED CHECK BECOMES INOPERATIVE.  

OR IF:
  F=0
  L=Y (letter spacing enabled)
THEN:
  The M1 + M3 SPEED CHECK IS OK, but the LETTER SPACING (L) becomes 
   disabled.

When using the LETTER SPACE feature (which is extremely user friendly) there will on occasion be an extended pause between words; almost like a word space feature.  This is very random and does not occur very often.  At first I thought rf might be sneaking into the MK-1 however, this happens at very low power levels.  My only other guess is that the Ten-Tec switching power supply, that powers the MK-1, may be introducing some noise into the keyer---I&#039;ll let you know what I find.  Worthy of note is that my Pico-Keyer, which is powered from several &#039;AAA&#039; cells does not exhibit this same pause but once every few weeks of use.

I found the TIMING (T) function extremely interesting.  If the range could be extended a few more steps, to say, 10 or 12 this would help prevent an extra 
unintentioned dot from being sent.  I use type &#039;A&#039; keying and on occasion when sending a character that ends in a dash I neglect to release the dot paddle in time resulting in an extra dot (i.e.  the letter  &#039;A&#039; comes out as a &#039;R&#039;).  The Pico-Keyer (V3.6) that I use is set up perfectly in this area.

Dale, I know you are very busy and for this reason I don&#039;t expect an answer to the above; just check out things and see what you can do.

I appreciate your efforts in marketing and refining keyers.  When Mr. Curtis passed on I thought this was the end for REAL keyers cw ops could enjoy.

                                                    Thanks/73, Roy, WA2SON
                                                     e-mail  wa2son@toast.net</description>
		<content:encoded><![CDATA[<p>Hello Dale,</p>
<p>I&#8217;ve loaded the V1.22 program into my MK-1.  I THINK  I installed this update correctly&#8212;-when I query the MK-1 as to the version it responds V1.21R. Hmmm.</p>
<p>Just a few items which I have noticed about my MK-1.   </p>
<p>IF:<br />
  F=99<br />
  L=Y  (letter spacing enabled)<br />
THEN:<br />
  The M1 + M3 SPEED CHECK BECOMES INOPERATIVE.  </p>
<p>OR IF:<br />
  F=0<br />
  L=Y (letter spacing enabled)<br />
THEN:<br />
  The M1 + M3 SPEED CHECK IS OK, but the LETTER SPACING (L) becomes<br />
   disabled.</p>
<p>When using the LETTER SPACE feature (which is extremely user friendly) there will on occasion be an extended pause between words; almost like a word space feature.  This is very random and does not occur very often.  At first I thought rf might be sneaking into the MK-1 however, this happens at very low power levels.  My only other guess is that the Ten-Tec switching power supply, that powers the MK-1, may be introducing some noise into the keyer&#8212;I&#8217;ll let you know what I find.  Worthy of note is that my Pico-Keyer, which is powered from several &#8216;AAA&#8217; cells does not exhibit this same pause but once every few weeks of use.</p>
<p>I found the TIMING (T) function extremely interesting.  If the range could be extended a few more steps, to say, 10 or 12 this would help prevent an extra<br />
unintentioned dot from being sent.  I use type &#8216;A&#8217; keying and on occasion when sending a character that ends in a dash I neglect to release the dot paddle in time resulting in an extra dot (i.e.  the letter  &#8216;A&#8217; comes out as a &#8216;R&#8217;).  The Pico-Keyer (V3.6) that I use is set up perfectly in this area.</p>
<p>Dale, I know you are very busy and for this reason I don&#8217;t expect an answer to the above; just check out things and see what you can do.</p>
<p>I appreciate your efforts in marketing and refining keyers.  When Mr. Curtis passed on I thought this was the end for REAL keyers cw ops could enjoy.</p>
<p>                                                    Thanks/73, Roy, WA2SON<br />
                                                     e-mail  <a href="mailto:wa2son@toast.net">wa2son@toast.net</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

