Revisited: Glitch when using USB Keyboard on P3 to

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Revisited: Glitch when using USB Keyboard on P3 to

Nolan Kienitz
I've been having a timing issue of sorts that somewhat parallels Keith's observations.

I've been working closely with Elecraft support as well as Wayne (directly) and we're still scratching our heads.

My problem goes away when I revert back to FW V5.38 ... any FW V5.50 and newer lets my intermittent 'audio reduction/drop' problem show up.

73 - Nolan Kienitz ... KI5IO


Message: 24
Date: Sat, 19 Nov 2016 18:26:54 -0600
From: "[hidden email]" <[hidden email]>
To: <[hidden email]>
Subject: [Elecraft] Revisited: Glitch when using USB Keyboard on P3 to
        send CW via K3
Message-ID: <EC793A51B22E4D71AF8C1C0E868948B9@dellquadcore>
Content-Type: text/plain; charset="iso-8859-1"

Well, it seems I was a little fast in determining that setting the P3
"Transmit Timeout" to 1000, fixed the issue.  It actually just masks the
underlying problem, but doesn't really fix it.

The problem is that the K3 is not staying in transmit long enough for CW
characters to be sent.  The correct character is being sent to the K3, but
the K3 truncates the character by turning off transmit too soon.  Setting
this timer to 1000 (milliseconds) just gives the K3 a little extra time to
stay in transmit, but created another problem for me.

While running my P3 with this timer at 1000 and the K3 at MCU 5.60 and P3 at
MCU 1.60, I encountered an issue.  On occasion my P3 'text' macros would
stop transmitting after 1 second.  Weird thing was, this wouldn't happen all
the time, but once it did start, it would continue until the rig was turned
off.  Sometimes simple things like a band change would trigger this to
occur.  I increased the timer to 20,000 (20 seconds) and that resolved this
Macro issue, but created a different issue.  I tried to let Elecraft
troubleshoot this, but they could not recreate it, and they wanted me to
send my P3 back to them.

This had all worked fine, until I upgrade my K3 and P3 firmware a month ago.
If you look in your PC, you can figure out what your previous version of F/W
were.  Simply deleting the newer hex files, allows you to re-flash your old
versions.

Just for grins, I flashed the P3 back to 1.29 first.  This did NOT fix it.
Rolling the K3 back to 5.14 fixed it.  I looked through the F/W updates
between 5.14 and 5.60, and nothing popped out dealing with this directly,
but I suspect the code for the vox in the K3 was changed somewhere to fix
something else, causing the issue with the P3.

Bottom line is everything works fine now using these old F/W versions.

Hallelujah!

Keith
K9GL

73,
        Nolan Kienitz  -  KI5IO
        SKCC - 9532C
        NAQCC – 6230
        FISTS – 14948


______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]
73  -  Nolan Kienitz,  KI5IO