Ron,

XMIT was always required in FSK-D and PSK-D modes. These are “VOX-only” modes, 
like hit-the-key CW, for historical reasons. 

Several PTT assertion cases were improved long ago, and this code has been in 
use by thousands of of K3/K3S users. Please contact me directly to describe the 
exact sequence of operations you’re trying to use so I can try to duplication 
the problem.

tnx
Wayne
N6KR


> On Sep 14, 2017, at 8:33 AM, n6ee <r...@csustan.edu> wrote:
> 
> This change which disables XMIT in FSK D mode, which Wayne described as
> intentional, has apparently broken the ability to assert PTT via CAT
> commands.  I need this in order to implement a new feature in Writelog which
> requires PTT via CAT in the FSK D mode.  
> 
> I have proven on ten different Remote Ham Radio stations that the new FSK D
> mode feature in Writelog works just fine with older K3 firmware but does not
> work on three RHR stations which have had their firmware upgraded to 5.5 or
> later.  
> 
> How far back do we need to go with restoring the older firmware that worked? 
> And, how do you restore to older firmware on the K3? Is their an archive
> somewhere of old firmware releases and will they load ok with the K3
> Utility?
> 
> Thanks and 73,
> Ron N6EE
> 
> 
> 
> --
> Sent from: http://elecraft.365791.n2.nabble.com/
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:Elecraft@mailman.qth.net
> 
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
> Message delivered to n...@elecraft.com

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:Elecraft@mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to arch...@mail-archive.com

Reply via email to