WSJT-X Problem with K3S
Locked
12
12
 
|
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:[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] |
Re: WSJT-X Problem with K3S
|
|
In reply to this post by stengrevics
On 13/01/17 02:06, [hidden email] 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:[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] |
|
|
In reply to this post by stengrevics
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 <[hidden email]> 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 <[hidden email] > <javascript:;>> 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: > > [hidden email] <javascript:;> > > ______________________________________________________________ > > Elecraft mailing list > > Home: http://mailman.qth.net/mailman/listinfo/elecraft > > Help: http://mailman.qth.net/mmfaq.htm > > Post: mailto:[hidden email] <javascript:;> > > > > 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] <javascript:;> > > ______________________________________________________________ > Elecraft mailing list > Home: http://mailman.qth.net/mailman/listinfo/elecraft > Help: http://mailman.qth.net/mmfaq.htm > Post: mailto:[hidden email] <javascript:;> > > 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] <javascript:;> > -- 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:[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] |
|
|
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 <http://time.nist.gov/> and the time.is <http://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 <[hidden email]> 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 <[hidden email] <mailto:[hidden email]>> 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 <[hidden email] <>> 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 <http://www.kl7uw.com/6m_control_panel_back_3.jpg> > > > > 73, Ed - KL7UW > > http://www.kl7uw.com <http://www.kl7uw.com/> > > Dubus-NA Business mail: > > [hidden email] <> > > ______________________________________________________________ > > Elecraft mailing list > > Home: http://mailman.qth.net/mailman/listinfo/elecraft <http://mailman.qth.net/mailman/listinfo/elecraft> > > Help: http://mailman.qth.net/mmfaq.htm <http://mailman.qth.net/mmfaq.htm> > > Post: mailto:[hidden email] <> > > > > This list hosted by: http://www.qsl.net <http://www.qsl.net/> > > Please help support this email list: http://www.qsl.net/donate.html <http://www.qsl.net/donate.html> > > Message delivered to [hidden email] <> > > ______________________________________________________________ > Elecraft mailing list > Home: http://mailman.qth.net/mailman/listinfo/elecraft <http://mailman.qth.net/mailman/listinfo/elecraft> > Help: http://mailman.qth.net/mmfaq.htm <http://mailman.qth.net/mmfaq.htm> > Post: mailto:[hidden email] <> > > This list hosted by: http://www.qsl.net <http://www.qsl.net/> > Please help support this email list: http://www.qsl.net/donate.html <http://www.qsl.net/donate.html> > Message delivered to <>[hidden email] <mailto:[hidden email]> > > > -- > 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:[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] |
|
|
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 <[hidden email]> 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 <http://time.nist.gov/> and the time.is <http://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 <[hidden email]> 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 <[hidden email] <mailto:[hidden email]>> 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 <[hidden email] <>> 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:[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] |
|
|
Bill,
I am on MSK144 and the transmit duration is 15 seconds. John WA1EAZ > On Jan 17, 2017, at 1:02 PM, Nr4c <[hidden email]> 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 <[hidden email]> 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 <http://time.nist.gov/> and the time.is <http://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 <[hidden email]> 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 <[hidden email] <mailto:[hidden email]>> 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 <[hidden email] <>> 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:[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] |
Re: WSJT-X Problem with K3S
|
|
In reply to this post by Nr4c
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 <[hidden email]> 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 <[hidden email]> 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 <http://time.nist.gov/> and the time.is <http://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 <[hidden email]> 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 <[hidden email] <mailto:[hidden email]>> 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 <[hidden email] <>> 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:[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] 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] |
Re: WSJT-X Problem with K3S
|
|
In reply to this post by stengrevics
> On 17 Jan 2017, at 16:48, John Stengrevics <[hidden email]> 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 <http://time.nist.gov/> and the time.is <http://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:[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] |
«
Return to Elecraft
|
1 view|%1 views
| Free forum by Nabble | Edit this page |