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 <n...@widomaker.com> 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 <jstengrev...@comcast.net> >> 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 <k2av....@gmail.com> 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 <jstengrev...@comcast.net >>> <mailto:jstengrev...@comcast.net>> 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 <kl...@acsalaska.net <>> 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: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
