Re: [Elecraft] WSJT-X Problem with K3S

2017-01-18 Thread David Anderson via Elecraft 

> On 17 Jan 2017, at 16:48, John Stengrevics  wrote:
> 
> Many thanks to all who provided their suggestions.
> 
> I decided to try Joe's (W4TV) suggestion and elect RTS.  That appears to have 
> solved the problem of the transmit staying on.
> 
> My only remaining problem is a 100 to 200 millisecond spillover into the next 
> sequence.  I have synched my Mac to time.nist.gov  and 
> the time.is  site shows that I am dead on. If anyone has any 
> suggestions, they would be much appreciated.


The Mac can be quite difficult to keep accurately time syncd using NTP, as it 
doesn’t always check the time from the best server and many other little snags 
like not checking very often sometimes.

If you have a reasonably modern version of the Mac OS then add some other NTP 
servers for your region to the Date & Time preferences, after the standard 
Apple one, separated by a comma. For example just add:

1.pool.ntp.org, 2.pool.ntp.org after whatever Apple has chosen.

In Europe I use

time.euro.apple.com, 1.uk.pool.ntp.org, 2.uk.pool.ntp.org

Please use your own region's ntp pool 

Uncheck "Set date and time automatically" and recheck it, it should update it.

Open a terminal window and type ntpq -p

You will get a list of the servers and their offsets (in ms) as well as other 
nerdy stuff. You will notice that NTP slowly drift corrects the clock. It only 
polls slowly so you have to be patient, but the good thing is it should learn.

Hope that helps

73

David GM4JJJ











__
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

Re: [Elecraft] WSJT-X Problem with K3S

2017-01-18 Thread David Anderson via Elecraft 
In MSK144 the T/R periods for meteor scatter are normally 15 seconds on 50 MHz, 
so it is important for all stations to have their clocks as accurate as they 
can, within half a second will do, but the closer the better.

Just to explain further, on meteorscatter it is possible for many stations to 
share the same frequency, as bursts are short and one station may not hear the 
same burst as another if they are in a slightly different location. We use 
conventions for which transmit period to use based on where we are beaming in 
one of the 4 quadrants. For example if beaming East or South we transmit on the 
second period so start at 15 secs after the top of the minute. 

This allows a couple of locals to both call CQ or work another station on the 
same frequency without hearing each other, but they are both able to hear and 
respond to any callers. If their clocks are a second or more out then there 
will be a slight overlap and the locals will interfere with each other for that 
short overlap time period. 

There will have to be a slight delay for relays and sequencers of course. There 
is a 200 ms software TX Delay between PTT being asserted and data sending in 
WSJT-X by default to allow relays to settle, though a hardware sequencer is a 
safer solution.

All of the above is covered in the online documentation for WSJT-X

http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-1.7.1-devel.html#SYSREQ

73 from David GM4JJJ

> On 17 Jan 2017, at 18:02, Nr4c  wrote:
> 
> Mine only transmits for around 42 seconds.   So should not impact the rec on 
> next minute. 
> 
> Sent from my iPhone
> ...nr4c. bill
> 
> 
>> On Jan 17, 2017, at 11:48 AM, John Stengrevics  
>> wrote:
>> 
>> Many thanks to all who provided their suggestions.
>> 
>> I decided to try Joe's (W4TV) suggestion and elect RTS.  That appears to 
>> have solved the problem of the transmit staying on.
>> 
>> My only remaining problem is a 100 to 200 millisecond spillover into the 
>> next sequence.  I have synched my Mac to time.nist.gov 
>>  and the time.is  site shows that I 
>> am dead on.  If anyone has any suggestions, they would be much appreciated.
>> 
>> 73,
>> 
>> John
>> WA1EAZ
>> 
>>> On Jan 13, 2017, at 1:53 PM, Guy Olinger K2AV  wrote:
>>> 
>>> Can't argue entirely with success, but often folks just want to put the 
>>> trouble In a cage so they can get on with having fun. I get that, it's a 
>>> hobby. For sure, been there done that. 
>>> 
>>> But all you have done for the moment is put the snarling dog in a cage 
>>> where it can't bite. If you ever run an amp the trouble is likely to return 
>>> in some form. You still have the snarling dog. 
>>> 
>>> And there are unanswered oddities like why the RFI only affected the one 
>>> sequence of commands. 
>>> 
>>> For others reading this thread, the exhortations for VOX or PTT are very 
>>> well taken, particularly where deciding on methodology is part of planning. 
>>> 
>>> Having a PTT and not-PTT signal available to the station *system* can be 
>>> very useful for such things as shutting off remote RX amps during transmit. 
>>> Many PC station programs like N1MM+ can add transfer delays only where they 
>>> apply, as do WinKey equipped devices which can apply CW key speed related 
>>> "word space" intervals. 
>>> 
>>> Not-PTT drives a simple circuit to supply a keyed 12 VDC supply that is 
>>> only on when it's safe from TX induced voltages, and can drive relays to 
>>> detune towers and de-resonate wires when RX. 
>>> 
>>> Given that the K3S board has both a USB/serial chip and a sound card on it, 
>>> no workable scheme proven robust for the K3 has to be discarded for the 
>>> K3S. 
>>> 
>>> All that aside, glad you you managed to cage the snarling dog, by whatever 
>>> means.  :>)
>>> 
>>> 73, Guy K2AV 
>>> 
>>> On Thursday, January 12, 2017, John Stengrevics >> > wrote:
>>> Three turns of the USB cable through a #43 ferrite and I am good to go at 
>>> full power (95 watts).
>>> 
>>> John
>>> WA1EAZ
>>> 
 On Jan 12, 2017, at 2:40 PM, Edward R Cole > wrote:
 
 Now that the thread has morphed to RFI:
> 
> __
> 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 gm4...@yahoo.co.uk
__
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:

Re: [Elecraft] WSJT-X Problem with K3S

2017-01-17 Thread John Stengrevics 
Bill,

I am on MSK144 and the transmit duration is 15 seconds.

John
WA1EAZ

> On Jan 17, 2017, at 1:02 PM, Nr4c  wrote:
> 
> Mine only transmits for around 42 seconds.   So should not impact the rec on 
> next minute. 
> 
> Sent from my iPhone
> ...nr4c. bill
> 
> 
>> On Jan 17, 2017, at 11:48 AM, John Stengrevics  
>> wrote:
>> 
>> Many thanks to all who provided their suggestions.
>> 
>> I decided to try Joe's (W4TV) suggestion and elect RTS.  That appears to 
>> have solved the problem of the transmit staying on.
>> 
>> My only remaining problem is a 100 to 200 millisecond spillover into the 
>> next sequence.  I have synched my Mac to time.nist.gov 
>>  and the time.is  site shows that I 
>> am dead on.  If anyone has any suggestions, they would be much appreciated.
>> 
>> 73,
>> 
>> John
>> WA1EAZ
>> 
>>> On Jan 13, 2017, at 1:53 PM, Guy Olinger K2AV  wrote:
>>> 
>>> Can't argue entirely with success, but often folks just want to put the 
>>> trouble In a cage so they can get on with having fun. I get that, it's a 
>>> hobby. For sure, been there done that. 
>>> 
>>> But all you have done for the moment is put the snarling dog in a cage 
>>> where it can't bite. If you ever run an amp the trouble is likely to return 
>>> in some form. You still have the snarling dog. 
>>> 
>>> And there are unanswered oddities like why the RFI only affected the one 
>>> sequence of commands. 
>>> 
>>> For others reading this thread, the exhortations for VOX or PTT are very 
>>> well taken, particularly where deciding on methodology is part of planning. 
>>> 
>>> Having a PTT and not-PTT signal available to the station *system* can be 
>>> very useful for such things as shutting off remote RX amps during transmit. 
>>> Many PC station programs like N1MM+ can add transfer delays only where they 
>>> apply, as do WinKey equipped devices which can apply CW key speed related 
>>> "word space" intervals. 
>>> 
>>> Not-PTT drives a simple circuit to supply a keyed 12 VDC supply that is 
>>> only on when it's safe from TX induced voltages, and can drive relays to 
>>> detune towers and de-resonate wires when RX. 
>>> 
>>> Given that the K3S board has both a USB/serial chip and a sound card on it, 
>>> no workable scheme proven robust for the K3 has to be discarded for the 
>>> K3S. 
>>> 
>>> All that aside, glad you you managed to cage the snarling dog, by whatever 
>>> means.  :>)
>>> 
>>> 73, Guy K2AV 
>>> 
>>> On Thursday, January 12, 2017, John Stengrevics >> > wrote:
>>> Three turns of the USB cable through a #43 ferrite and I am good to go at 
>>> full power (95 watts).
>>> 
>>> John
>>> WA1EAZ
>>> 
 On Jan 12, 2017, at 2:40 PM, Edward R Cole > wrote:
 
 Now that the thread has morphed to RFI:
> 

__
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

Re: [Elecraft] WSJT-X Problem with K3S

2017-01-17 Thread Nr4c 
Mine only transmits for around 42 seconds.   So should not impact the rec on 
next minute. 

Sent from my iPhone
...nr4c. bill


> On Jan 17, 2017, at 11:48 AM, John Stengrevics  
> wrote:
> 
> Many thanks to all who provided their suggestions.
> 
> I decided to try Joe's (W4TV) suggestion and elect RTS.  That appears to have 
> solved the problem of the transmit staying on.
> 
> My only remaining problem is a 100 to 200 millisecond spillover into the next 
> sequence.  I have synched my Mac to time.nist.gov  and 
> the time.is  site shows that I am dead on.  If anyone has 
> any suggestions, they would be much appreciated.
> 
> 73,
> 
> John
> WA1EAZ
> 
>> On Jan 13, 2017, at 1:53 PM, Guy Olinger K2AV  wrote:
>> 
>> Can't argue entirely with success, but often folks just want to put the 
>> trouble In a cage so they can get on with having fun. I get that, it's a 
>> hobby. For sure, been there done that. 
>> 
>> But all you have done for the moment is put the snarling dog in a cage where 
>> it can't bite. If you ever run an amp the trouble is likely to return in 
>> some form. You still have the snarling dog. 
>> 
>> And there are unanswered oddities like why the RFI only affected the one 
>> sequence of commands. 
>> 
>> For others reading this thread, the exhortations for VOX or PTT are very 
>> well taken, particularly where deciding on methodology is part of planning. 
>> 
>> Having a PTT and not-PTT signal available to the station *system* can be 
>> very useful for such things as shutting off remote RX amps during transmit. 
>> Many PC station programs like N1MM+ can add transfer delays only where they 
>> apply, as do WinKey equipped devices which can apply CW key speed related 
>> "word space" intervals. 
>> 
>> Not-PTT drives a simple circuit to supply a keyed 12 VDC supply that is only 
>> on when it's safe from TX induced voltages, and can drive relays to detune 
>> towers and de-resonate wires when RX. 
>> 
>> Given that the K3S board has both a USB/serial chip and a sound card on it, 
>> no workable scheme proven robust for the K3 has to be discarded for the K3S. 
>> 
>> All that aside, glad you you managed to cage the snarling dog, by whatever 
>> means.  :>)
>> 
>> 73, Guy K2AV 
>> 
>> On Thursday, January 12, 2017, John Stengrevics > > wrote:
>> Three turns of the USB cable through a #43 ferrite and I am good to go at 
>> full power (95 watts).
>> 
>> John
>> WA1EAZ
>> 
>>> On Jan 12, 2017, at 2:40 PM, Edward R Cole > wrote:
>>> 
>>> Now that the thread has morphed to RFI:

__
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

Re: [Elecraft] WSJT-X Problem with K3S

2017-01-17 Thread John Stengrevics 
Many thanks to all who provided their suggestions.

I decided to try Joe's (W4TV) suggestion and elect RTS.  That appears to have 
solved the problem of the transmit staying on.

My only remaining problem is a 100 to 200 millisecond spillover into the next 
sequence.  I have synched my Mac to time.nist.gov  and 
the time.is  site shows that I am dead on.  If anyone has any 
suggestions, they would be much appreciated.

73,

John
WA1EAZ

> On Jan 13, 2017, at 1:53 PM, Guy Olinger K2AV  wrote:
> 
> Can't argue entirely with success, but often folks just want to put the 
> trouble In a cage so they can get on with having fun. I get that, it's a 
> hobby. For sure, been there done that. 
> 
> But all you have done for the moment is put the snarling dog in a cage where 
> it can't bite. If you ever run an amp the trouble is likely to return in some 
> form. You still have the snarling dog. 
> 
> And there are unanswered oddities like why the RFI only affected the one 
> sequence of commands. 
> 
> For others reading this thread, the exhortations for VOX or PTT are very well 
> taken, particularly where deciding on methodology is part of planning. 
> 
> Having a PTT and not-PTT signal available to the station *system* can be very 
> useful for such things as shutting off remote RX amps during transmit. Many 
> PC station programs like N1MM+ can add transfer delays only where they apply, 
> as do WinKey equipped devices which can apply CW key speed related "word 
> space" intervals. 
> 
> Not-PTT drives a simple circuit to supply a keyed 12 VDC supply that is only 
> on when it's safe from TX induced voltages, and can drive relays to detune 
> towers and de-resonate wires when RX. 
>  
> Given that the K3S board has both a USB/serial chip and a sound card on it, 
> no workable scheme proven robust for the K3 has to be discarded for the K3S. 
> 
> All that aside, glad you you managed to cage the snarling dog, by whatever 
> means.  :>)
> 
> 73, Guy K2AV 
> 
> On Thursday, January 12, 2017, John Stengrevics  > wrote:
> Three turns of the USB cable through a #43 ferrite and I am good to go at 
> full power (95 watts).
> 
> John
> WA1EAZ
> 
> > On Jan 12, 2017, at 2:40 PM, Edward R Cole > wrote:
> >
> > Now that the thread has morphed to RFI:
> >
> > I was getting complaints from my wife that my transmissions were getting 
> > into the home theater audio when she was watching TV.  Specifically, it was 
> > getting into the new powered woofer.  I determined this was only happening 
> > on 6m and at 1000w.
> >
> > So I had an extra ferrite donut from building the 50v switching PS and 
> > wrapped the coaxial audio line thru it a few times, then added a clamp on 
> > ferrite to the ac cord feeding the woofer.  That fixed it!
> >
> > picture of these applied to the 50v swps:
> > http://www.kl7uw.com/6m_control_panel_back_3.jpg 
> > 
> >
> > 73, Ed - KL7UW
> >  http://www.kl7uw.com 
> > Dubus-NA Business mail:
> >  dubus...@gmail.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 jstengrev...@comcast.net <>
> 
> __
> 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  <>k2av@gmail.com 
> 
> 
> -- 
> Sent via Gmail Mobile on my iPhone

__
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

Re: [Elecraft] WSJT-X Problem with K3S

2017-01-13 Thread Guy Olinger K2AV 
Can't argue entirely with success, but often folks just want to put the
trouble In a cage so they can get on with having fun. I get that, it's a
hobby. For sure, been there done that.

But all you have done for the moment is put the snarling dog in a cage
where it can't bite. If you ever run an amp the trouble is likely to return
in some form. You still have the snarling dog.

And there are unanswered oddities like why the RFI only affected the one
sequence of commands.

For others reading this thread, the exhortations for VOX or PTT are
very well taken, particularly where deciding on methodology is part of
planning.

Having a PTT and not-PTT signal available to the station *system* can be
very useful for such things as shutting off remote RX amps during transmit.
Many PC station programs like N1MM+ can add transfer delays only where they
apply, as do WinKey equipped devices which can apply CW key speed related
"word space" intervals.

Not-PTT drives a simple circuit to supply a keyed 12 VDC supply that is
only on when it's safe from TX induced voltages, and can drive relays
to detune towers and de-resonate wires when RX.

Given that the K3S board has both a USB/serial chip and a sound card on it,
no workable scheme proven robust for the K3 has to be discarded for the
K3S.

All that aside, glad you you managed to cage the snarling dog, by whatever
means.  :>)

73, Guy K2AV

On Thursday, January 12, 2017, John Stengrevics 
wrote:

> Three turns of the USB cable through a #43 ferrite and I am good to go at
> full power (95 watts).
>
> John
> WA1EAZ
>
> > On Jan 12, 2017, at 2:40 PM, Edward R Cole  > wrote:
> >
> > Now that the thread has morphed to RFI:
> >
> > I was getting complaints from my wife that my transmissions were getting
> into the home theater audio when she was watching TV.  Specifically, it was
> getting into the new powered woofer.  I determined this was only happening
> on 6m and at 1000w.
> >
> > So I had an extra ferrite donut from building the 50v switching PS and
> wrapped the coaxial audio line thru it a few times, then added a clamp on
> ferrite to the ac cord feeding the woofer.  That fixed it!
> >
> > picture of these applied to the 50v swps:
> > http://www.kl7uw.com/6m_control_panel_back_3.jpg
> >
> > 73, Ed - KL7UW
> >  http://www.kl7uw.com
> > Dubus-NA Business mail:
> >  dubus...@gmail.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 jstengrev...@comcast.net 
>
> __
> 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 k2av@gmail.com 
>


-- 
Sent via Gmail Mobile on my iPhone
__
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

Re: [Elecraft] WSJT-X Problem with K3S

2017-01-13 Thread Dave B via Elecraft 
On 13/01/17 02:06, elecraft-requ...@mailman.qth.net wrote:
> The physical RTS line is moved from the computer to the output of
> the USB UART (in the K3).  However, there is still a physical RTS
> line.  The set RTS/DTR/Break and clear RTS/DTR/Break commands are
> much more robust than sending serial data via USB.

To do that, you are still sending data over the USB link.  Not the same
data, but data none the less.

So, any RF ingress into the USB systems (at either end of the cable!)
Can still cause trouble.

Note, clip-on ferrite cores have very little effect at MF/HF
frequencies, unless you can wrap several turns of the USB cable through
them.  And even then, it depends on what the exact problem is where and
how the RF get's in.

I often wonder why we don't use fibre optic links for rig control and
audio.  TosLink cable and devices are available for the audio, and it's
relatively trivial to send (RS232 like) data down a fibre too.

I'll get my coat...

73.

Dave G0WBX.

__
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

Re: [Elecraft] WSJT-X Problem with K3S

2017-01-12 Thread Wes Stewart 
No slight to Joe, who knows what he's talking about, but why not use Jim's 
suggestion.


I don't use any of the imaginary modes, but I do use VOX exclusively on RTTY and 
PSK.  I do wish VOX gain was remembered by mode, however.  Request #39.


N7WS

On 1/12/2017 11:55 AM, John Stengrevics wrote:

Thanks all.  I’ll try Joe’s suggestion, but have to research it first.

John
WA1EAZ




__
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

Re: [Elecraft] WSJT-X Problem with K3S

2017-01-12 Thread John Stengrevics 
Three turns of the USB cable through a #43 ferrite and I am good to go at full 
power (95 watts).

John
WA1EAZ

> On Jan 12, 2017, at 2:40 PM, Edward R Cole  wrote:
> 
> Now that the thread has morphed to RFI:
> 
> I was getting complaints from my wife that my transmissions were getting into 
> the home theater audio when she was watching TV.  Specifically, it was 
> getting into the new powered woofer.  I determined this was only happening on 
> 6m and at 1000w.
> 
> So I had an extra ferrite donut from building the 50v switching PS and 
> wrapped the coaxial audio line thru it a few times, then added a clamp on 
> ferrite to the ac cord feeding the woofer.  That fixed it!
> 
> picture of these applied to the 50v swps:
> http://www.kl7uw.com/6m_control_panel_back_3.jpg
> 
> 73, Ed - KL7UW
>  http://www.kl7uw.com
> Dubus-NA Business mail:
>  dubus...@gmail.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 jstengrev...@comcast.net

__
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

Re: [Elecraft] WSJT-X Problem with K3S

2017-01-12 Thread Edward R Cole 

Now that the thread has morphed to RFI:

I was getting complaints from my wife that my transmissions were 
getting into the home theater audio when she was watching 
TV.  Specifically, it was getting into the new powered woofer.  I 
determined this was only happening on 6m and at 1000w.


So I had an extra ferrite donut from building the 50v switching PS 
and wrapped the coaxial audio line thru it a few times, then added a 
clamp on ferrite to the ac cord feeding the woofer.  That fixed it!


picture of these applied to the 50v swps:
http://www.kl7uw.com/6m_control_panel_back_3.jpg

73, Ed - KL7UW
  http://www.kl7uw.com
Dubus-NA Business mail:
  dubus...@gmail.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

Re: [Elecraft] WSJT-X Problem with K3S

2017-01-12 Thread Nicklas Johnson 
In that case it's probably statistically slightly more likely that a CAT
command (seems like about 5 bytes) would get garbled going across the USB
than whatever bit stream went across the USB to turn RTS off.  One would be
an op-code (probably 8 bits) plus 5 more bytes, versus the other being just
an op code.  So it's odds of garbling 1 or more bits out of 8 versus 1 or
more bits out of ~48.  Probably mitigates the problem somewhat, but mostly
likely won't make it completely go away.

The best thing still will be attenuating the common mode noise on the USB
cable, IMO... keep it out of there in the first place.

   Nick


On 12 January 2017 at 10:41, Don Wilhelm  wrote:

> Nick,
>
> Yes, the K3S connects directly to USB, but inside the K3S is an FTDI USB
> to serial converter.  It has the RTS and DTR signals and they are properly
> routed to the K3S.  The RS-232 circuits in the K3S are retained just like
> as they were with the K3.
>
> 73,
> Don W3FPR
>
> On 1/12/2017 1:15 PM, Nicklas Johnson wrote:
>
>> Unless I'm mistaken, doesn't the K3S connect directly via USB though?  If
>> the problem is happening because of common mode on the USB cable, there is
>> no physical RTS line involved like there would be in an old-style
>> COM/RS232
>> device
>>
>


-- 
*N6OL*
Saying something doesn't make it true.  Belief in something doesn't make it
real. And if you have to lie to support a position, that position is not
worth supporting.
__
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

Re: [Elecraft] WSJT-X Problem with K3S

2017-01-12 Thread Nr4c 
The USB port on K3S also has the DTR and RTS information available. 

Sent from my iPhone
...nr4c. bill


> On Jan 12, 2017, at 1:15 PM, Nicklas Johnson  wrote:
> 
> Unless I'm mistaken, doesn't the K3S connect directly via USB though?  If
> the problem is happening because of common mode on the USB cable, there is
> no physical RTS line involved like there would be in an old-style COM/RS232
> device- there is only serial data going across a USB cable to a logical COM
> device inside the K3S.  It most likely wouldn't change anything in this
> case.
> 
>   Nick
> 
>> On 12 January 2017 at 10:08, Joe Subich, W4TV  wrote:
>> 
>> 
>>> On 1/12/2017 11:05 AM, John Stengrevics wrote:
>>> What’s the solution, ferrites on the USB cable?
>> 
>> Stop using CAT Commands for PTT!  Instead set CONFIG:PTT-Key to
>> RTS-OFF and use RTS.  WSJT-X supports PTT Method = RTS by setting
>> the PTT Port the same as the CAT Port.
>> 
>> 73,
>> 
>>   ... Joe, W4TV
>> 
>> 
>> 
>> __
>> 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...@n6ol.us
>> 
> 
> 
> 
> -- 
> *N6OL*
> Saying something doesn't make it true.  Belief in something doesn't make it
> real. And if you have to lie to support a position, that position is not
> worth supporting.
> __
> 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...@widomaker.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

Re: [Elecraft] WSJT-X Problem with K3S

2017-01-12 Thread John Stengrevics 
Thanks all.  I’ll try Joe’s suggestion, but have to research it first.

John
WA1EAZ

> On Jan 12, 2017, at 1:50 PM, Nr4c  wrote:
> 
> Could you have multiple PTTs active. Like PTT and VOX, or two PTTs refed in 
> software?
> 
> Sent from my iPhone
> ...nr4c. bill
> 
> 
>> On Jan 12, 2017, at 10:03 AM, stengrevics  wrote:
>> 
>> When I transmit (using MSK144), the transmit stays on after the transmission
>> is complete causing spillover into the next sequence.  This happens
>> randomly.
>> 
>> Anybody have any suggestions as to how to fix this?
>> 
>> Thanks,
>> 
>> John
>> WA1EAZ
>> 
>> 
>> 
>> --
>> View this message in context: 
>> http://elecraft.365791.n2.nabble.com/WSJT-X-Problem-with-K3S-tp7625670.html
>> Sent from the Elecraft mailing list archive at 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...@widomaker.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

Re: [Elecraft] WSJT-X Problem with K3S

2017-01-12 Thread Nr4c 
Could you have multiple PTTs active. Like PTT and VOX, or two PTTs refed in 
software?

Sent from my iPhone
...nr4c. bill


> On Jan 12, 2017, at 10:03 AM, stengrevics  wrote:
> 
> When I transmit (using MSK144), the transmit stays on after the transmission
> is complete causing spillover into the next sequence.  This happens
> randomly.
> 
> Anybody have any suggestions as to how to fix this?
> 
> Thanks,
> 
> John
> WA1EAZ
> 
> 
> 
> --
> View this message in context: 
> http://elecraft.365791.n2.nabble.com/WSJT-X-Problem-with-K3S-tp7625670.html
> Sent from the Elecraft mailing list archive at 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...@widomaker.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

Re: [Elecraft] WSJT-X Problem with K3S

2017-01-12 Thread Don Wilhelm 

Nick,

Yes, the K3S connects directly to USB, but inside the K3S is an FTDI USB 
to serial converter.  It has the RTS and DTR signals and they are 
properly routed to the K3S.  The RS-232 circuits in the K3S are retained 
just like as they were with the K3.


73,
Don W3FPR

On 1/12/2017 1:15 PM, Nicklas Johnson wrote:

Unless I'm mistaken, doesn't the K3S connect directly via USB though?  If
the problem is happening because of common mode on the USB cable, there is
no physical RTS line involved like there would be in an old-style COM/RS232
device

__
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

Re: [Elecraft] WSJT-X Problem with K3S

2017-01-12 Thread Guy Olinger K2AV 
You should really do what Joe suggested. It is highly unlikely that RFI
would ONLY affect the one CAT command. It more likely is some kind of
timing entanglement which will be difficult to diagnose.

DO try what Joe said:

On Thu, Jan 12, 2017 at 1:08 PM, Joe Subich, W4TV  wrote:

> Stop using CAT Commands for PTT!  Instead set CONFIG:PTT-Key to
> RTS-OFF and use RTS.  WSJT-X supports PTT Method = RTS by setting
> the PTT Port the same as the CAT Port.
>

No kidding, try it!

73, Guy K2AV
__
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

Re: [Elecraft] WSJT-X Problem with K3S

2017-01-12 Thread Joe Subich, W4TV 





there is no physical RTS line involved like there would be in an
old-style COM/RS232 device- there is only serial data going across a
USB cable to a logical COM device inside the K3S. It most likely
wouldn't change anything in this case.


The physical RTS line is moved from the computer to the output of
the USB UART (in the K3).  However, there is still a physical RTS
line.  The set RTS/DTR/Break and clear RTS/DTR/Break commands are
much more robust than sending serial data via USB.

Using RTS is *always* more robust (and less susceptible to RFI)
that using CAT commands for TS?RX switching.

73,

   ... Joe, W4TV


On 1/12/2017 1:15 PM, Nicklas Johnson wrote:

Unless I'm mistaken, doesn't the K3S connect directly via USB though?  If
the problem is happening because of common mode on the USB cable, there is
no physical RTS line involved like there would be in an old-style COM/RS232
device- there is only serial data going across a USB cable to a logical COM
device inside the K3S.  It most likely wouldn't change anything in this
case.

   Nick

On 12 January 2017 at 10:08, Joe Subich, W4TV  wrote:



On 1/12/2017 11:05 AM, John Stengrevics wrote:

What’s the solution, ferrites on the USB cable?


Stop using CAT Commands for PTT!  Instead set CONFIG:PTT-Key to
RTS-OFF and use RTS.  WSJT-X supports PTT Method = RTS by setting
the PTT Port the same as the CAT Port.

73,

   ... Joe, W4TV



__
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...@n6ol.us






__
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

Re: [Elecraft] WSJT-X Problem with K3S

2017-01-12 Thread John Stengrevics 
Correct.  The K3S is connected directly to my Mac via a USB cable.

John
WA1EAZ

> On Jan 12, 2017, at 1:15 PM, Nicklas Johnson  wrote:
> 
> Unless I'm mistaken, doesn't the K3S connect directly via USB though?  If
> the problem is happening because of common mode on the USB cable, there is
> no physical RTS line involved like there would be in an old-style COM/RS232
> device- there is only serial data going across a USB cable to a logical COM
> device inside the K3S.  It most likely wouldn't change anything in this
> case.
> 
>   Nick
> 
> On 12 January 2017 at 10:08, Joe Subich, W4TV  > wrote:
> 
>> 
>> On 1/12/2017 11:05 AM, John Stengrevics wrote:
>>> What’s the solution, ferrites on the USB cable?
>> 
>> Stop using CAT Commands for PTT!  Instead set CONFIG:PTT-Key to
>> RTS-OFF and use RTS.  WSJT-X supports PTT Method = RTS by setting
>> the PTT Port the same as the CAT Port.
>> 
>> 73,
>> 
>>   ... Joe, W4TV
>> 
>> 
>> 
>> __
>> 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...@n6ol.us 
>> 
> 
> 
> 
> -- 
> *N6OL*
> Saying something doesn't make it true.  Belief in something doesn't make it
> real. And if you have to lie to support a position, that position is not
> worth supporting.
> __
> 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 jstengrev...@comcast.net 
> 
__
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

Re: [Elecraft] WSJT-X Problem with K3S

2017-01-12 Thread Nicklas Johnson 
Unless I'm mistaken, doesn't the K3S connect directly via USB though?  If
the problem is happening because of common mode on the USB cable, there is
no physical RTS line involved like there would be in an old-style COM/RS232
device- there is only serial data going across a USB cable to a logical COM
device inside the K3S.  It most likely wouldn't change anything in this
case.

   Nick

On 12 January 2017 at 10:08, Joe Subich, W4TV  wrote:

>
> On 1/12/2017 11:05 AM, John Stengrevics wrote:
> > What’s the solution, ferrites on the USB cable?
>
> Stop using CAT Commands for PTT!  Instead set CONFIG:PTT-Key to
> RTS-OFF and use RTS.  WSJT-X supports PTT Method = RTS by setting
> the PTT Port the same as the CAT Port.
>
> 73,
>
>... Joe, W4TV
>
>
>
> __
> 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...@n6ol.us
>



-- 
*N6OL*
Saying something doesn't make it true.  Belief in something doesn't make it
real. And if you have to lie to support a position, that position is not
worth supporting.
__
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

Re: [Elecraft] WSJT-X Problem with K3S

2017-01-12 Thread Joe Subich, W4TV 


On 1/12/2017 11:05 AM, John Stengrevics wrote:
> What’s the solution, ferrites on the USB cable?

Stop using CAT Commands for PTT!  Instead set CONFIG:PTT-Key to
RTS-OFF and use RTS.  WSJT-X supports PTT Method = RTS by setting
the PTT Port the same as the CAT Port.

73,

   ... Joe, W4TV


__
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

Re: [Elecraft] WSJT-X Problem with K3S

2017-01-12 Thread Nicklas Johnson 
The other thing, too, is if your antenna is just relatively close in
proximity to your shack, it won't matter how well balanced your feedline
is; you may still end up with cables inside your house that are resonant at
or near the frequency where you're transmitting, or at least near enough to
cause problems, with an intentional radiator (your antenna) nearby.  For
whatever reason, this always seems to be worse on 20 meters than other
bands with home electronics.  Then I don't know of an option for offending
equipment other than a few turns through some hefty ferrite on the resonant
cable(s).

(As I'm sure you know, a lot of home electronics are poorly executed with
respect to keeping out common mode currents... Jim Brown K9YC has published
a lot of really great information about this state of affairs.  Sometimes
the entry point for common mode noise isn't what you would expect, too.)

If you're like me, and you have a dipole antenna mounted on your roof,
getting it up a little higher may help some too...or just learning to live
with lower power output.  My threshold at home with digital modes on 20m is
about 27 watts... below that, everything is fine.  Above that, everything
is terrible.  Fortunately, most of the time I don't even need that much to
make a successful contact, and even with modes like WinLink, 15 watts is
plenty.

   Nick


On 12 January 2017 at 08:21, John Stengrevics 
wrote:

> Thanks Don.  I already have ferrites all over my coax cables, Anderson
> power cables, literally all over the house.
>
> Will try on the USB cable as well.
>
> John
> WA1EAZ
>
> > On Jan 12, 2017, at 11:17 AM, Don Wilhelm 
> wrote:
> >
> > John,
> >
> > The first step to solving RF-in-the-shack problems is to work on your
> antenna system.  Better common mode chokes on your feedline(s).
> > See the information by Jim Brown K9YC at http://audiosystemsgroup.com/
> RFI-Ham.pdf.
> >
> > If you still have problems after taking those measures, then use ferites
> on cables as a last resort solution.
> >
> > The reason I say this is because if you have RF interfering with the
> wiring in your station, you likely have similar interference on all wires
> in your station - you can fix one or two, but another similar problem will
> rear its ugly head later on.
> > If you fix the problem at its source, you will fix a lot of "strange
> behaviors".
> >
> > 73,
> > Don W3FPR
> >
> > On 1/12/2017 11:05 AM, John Stengrevics wrote:
> >> Hi Nick,
> >>
> >> Thanks for the suggestion!  I turned the power down to 2 watts and the
> problem went away.
> >>
> >> What’s the solution, ferrites on the USB cable?
> >>
>
>


-- 
*N6OL*
Saying something doesn't make it true.  Belief in something doesn't make it
real. And if you have to lie to support a position, that position is not
worth supporting.
__
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

Re: [Elecraft] WSJT-X Problem with K3S

2017-01-12 Thread Don Wilhelm 

John,

The first step to solving RF-in-the-shack problems is to work on your 
antenna system.  Better common mode chokes on your feedline(s).
See the information by Jim Brown K9YC at 
http://audiosystemsgroup.com/RFI-Ham.pdf.


If you still have problems after taking those measures, then use ferites 
on cables as a last resort solution.


The reason I say this is because if you have RF interfering with the 
wiring in your station, you likely have similar interference on all 
wires in your station - you can fix one or two, but another similar 
problem will rear its ugly head later on.
If you fix the problem at its source, you will fix a lot of "strange 
behaviors".


73,
Don W3FPR

On 1/12/2017 11:05 AM, John Stengrevics wrote:

Hi Nick,

Thanks for the suggestion!  I turned the power down to 2 watts and the problem 
went away.

What’s the solution, ferrites on the USB cable?


__
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

Re: [Elecraft] WSJT-X Problem with K3S

2017-01-12 Thread John Stengrevics 
Thanks Don.  I already have ferrites all over my coax cables, Anderson power 
cables, literally all over the house.

Will try on the USB cable as well.

John
WA1EAZ

> On Jan 12, 2017, at 11:17 AM, Don Wilhelm  wrote:
> 
> John,
> 
> The first step to solving RF-in-the-shack problems is to work on your antenna 
> system.  Better common mode chokes on your feedline(s).
> See the information by Jim Brown K9YC at 
> http://audiosystemsgroup.com/RFI-Ham.pdf.
> 
> If you still have problems after taking those measures, then use ferites on 
> cables as a last resort solution.
> 
> The reason I say this is because if you have RF interfering with the wiring 
> in your station, you likely have similar interference on all wires in your 
> station - you can fix one or two, but another similar problem will rear its 
> ugly head later on.
> If you fix the problem at its source, you will fix a lot of "strange 
> behaviors".
> 
> 73,
> Don W3FPR
> 
> On 1/12/2017 11:05 AM, John Stengrevics wrote:
>> Hi Nick,
>> 
>> Thanks for the suggestion!  I turned the power down to 2 watts and the 
>> problem went away.
>> 
>> What’s the solution, ferrites on the USB cable?
>> 

__
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

Re: [Elecraft] WSJT-X Problem with K3S

2017-01-12 Thread Nicklas Johnson 
Two things: one is to go through the usual steps around keeping RF out of
the shack.  There are a lot of resources around this online regarding
baluns, "ugly baluns" and so-on.

The other thing I've done is exactly as you've said: several turns of
computer cables through ferrite.  Watch your cable bend radius.

   Nick

On 12 January 2017 at 08:05, John Stengrevics 
wrote:

> Hi Nick,
>
> Thanks for the suggestion!  I turned the power down to 2 watts and the
> problem went away.
>
> What’s the solution, ferrites on the USB cable?
>
> John
> WA1EAZ
>
> On Jan 12, 2017, at 10:28 AM, Nicklas Johnson  wrote:
>
> When I've had this happen with other rigs in the past, it's been because
> of RF leaking back into the shack and causing CAT commands to fail (because
> of common mode current on the serial line).
>
> If you reduce power to something quite small, like 1-2 W, does it stop
> happening?
>
>Nick
>
> On 12 January 2017 at 07:03, stengrevics  wrote:
>
>> When I transmit (using MSK144), the transmit stays on after the
>> transmission
>> is complete causing spillover into the next sequence.  This happens
>> randomly.
>>
>> Anybody have any suggestions as to how to fix this?
>>
>> Thanks,
>>
>> John
>> WA1EAZ
>>
>>
>>
>> --
>> View this message in context: http://elecraft.365791.n2.nabb
>> le.com/WSJT-X-Problem-with-K3S-tp7625670.html
>> Sent from the Elecraft mailing list archive at 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...@n6ol.us
>>
>
>
>
> --
> *N6OL*
> Saying something doesn't make it true.  Belief in something doesn't make
> it real. And if you have to lie to support a position, that position is not
> worth supporting.
>
>
>


-- 
*N6OL*
Saying something doesn't make it true.  Belief in something doesn't make it
real. And if you have to lie to support a position, that position is not
worth supporting.
__
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

Re: [Elecraft] WSJT-X Problem with K3S

2017-01-12 Thread John Stengrevics 
Hi Nick,

Thanks for the suggestion!  I turned the power down to 2 watts and the problem 
went away.

What’s the solution, ferrites on the USB cable?

John
WA1EAZ

> On Jan 12, 2017, at 10:28 AM, Nicklas Johnson  wrote:
> 
> When I've had this happen with other rigs in the past, it's been because of 
> RF leaking back into the shack and causing CAT commands to fail (because of 
> common mode current on the serial line).
> 
> If you reduce power to something quite small, like 1-2 W, does it stop 
> happening?
> 
>Nick
> 
> On 12 January 2017 at 07:03, stengrevics  > wrote:
> When I transmit (using MSK144), the transmit stays on after the transmission
> is complete causing spillover into the next sequence.  This happens
> randomly.
> 
> Anybody have any suggestions as to how to fix this?
> 
> Thanks,
> 
> John
> WA1EAZ
> 
> 
> 
> --
> View this message in context: 
> http://elecraft.365791.n2.nabble.com/WSJT-X-Problem-with-K3S-tp7625670.html 
> 
> Sent from the Elecraft mailing list archive at 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...@n6ol.us 
> 
> 
> 
> -- 
> N6OL
> Saying something doesn't make it true.  Belief in something doesn't make it 
> real. And if you have to lie to support a position, that position is not 
> worth supporting.

__
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

[Elecraft] WSJT-X Problem with K3S

2017-01-12 Thread stengrevics 
When I transmit (using MSK144), the transmit stays on after the transmission
is complete causing spillover into the next sequence.  This happens
randomly.

Anybody have any suggestions as to how to fix this?

Thanks,

John
WA1EAZ



--
View this message in context: 
http://elecraft.365791.n2.nabble.com/WSJT-X-Problem-with-K3S-tp7625670.html
Sent from the Elecraft mailing list archive at 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 arch...@mail-archive.com