Almost no delay. In fact, I went in and set the WSJT-X delay back to it's
default of 0.2s.
> I was experiencing the same issue and never found resolution; I ended up
going back to using WSJT-> X to control the 7300 directly. Since that
worked okay and I had no other rig to test with Commander, I > assumed it
was a DXLab issue. Can you share what (approximate) delays you are seeing
now with ?>your settings changes?
On Tue, Sep 19, 2017 at 1:01 PM <[email protected]>
wrote:
> Send wsjt-devel mailing list submissions to
> [email protected]
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> or, via email, send a message with subject or body 'help' to
> [email protected]
>
> You can reach the person managing the list at
> [email protected]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of wsjt-devel digest..."
> Today's Topics:
>
> 1. WSJT-X and DXLab Commander TX Delay (Jon Anhold)
> 2. Re: WSJT-X and DXLab Commander TX Delay (Morgen Benner)
> 3. Re: FT8 is forcing the discipline of split ... (Rich - K1HTV)
> 4. A suggested FT8 split option (Rich - K1HTV)
>
>
>
> ---------- Forwarded message ----------
> From: Jon Anhold <[email protected]>
> To: [email protected]
> Cc:
> Bcc:
> Date: Tue, 19 Sep 2017 15:41:29 +0000
> Subject: [wsjt-devel] WSJT-X and DXLab Commander TX Delay
> Apologies if this has been posted previously, but I'm hoping it will help
> out the next 7300 FT8 user!
>
> I recently just replaced my FT-897D + Signalink USB with an Icom IC-7300.
> Wow, what a cool rig!
>
> I like to use Commander to control the rig as much as possible, and use
> the various integrations to it for rig control, etc -- including in WSJT-X.
>
> When switching from the Signalink to the 7300, as I got everything set up,
> I noticed there was an ~2sec delay from when the TX window would start in
> WSJT-X for FT8 and when the radio would actually key up and start
> transmitting.
>
> Since timing is crucial on modes like FT8, obviously this wasn't ideal.
>
> I think I have finally figured out a combination of settings that
> minimizes the TX delay:
>
> - Set the TX delay in WSJT-X to 0.0s (careful if you have a PA)
> - Set Rig to DX Lab Commander, PTT CAT, Mode none, Split rig.
> - Configure the 7300 to use RTS or DTR for PTT
> - Set Commander to use RTS or DTR for TX as appropriate
> - Check the "Suppress CAT" box in the PTT section in Commander
>
> This last one was key, as it minimizes the back and forth CAT commands to
> the radio for TX/RX.
>
> I'm really enjoying the FT8/JT modes. Thanks to all for such a cool
> program, and as always, DXLab has been fantastic - been using it since
> 2003! Thanks Dave!
>
> 73 de KM8V (formerly N8USK)
>
>
>
> ---------- Forwarded message ----------
> From: Morgen Benner <[email protected]>
> To: WSJT software development <[email protected]>
> Cc:
> Bcc:
> Date: Tue, 19 Sep 2017 11:57:50 -0400
> Subject: Re: [wsjt-devel] WSJT-X and DXLab Commander TX Delay
> I was experiencing the same issue and never found resolution; I ended up
> going back to using WSJT-X to control the 7300 directly. Since that worked
> okay and I had no other rig to test with Commander, I assumed it was a
> DXLab issue. Can you share what (approximate) delays you are seeing now
> with your settings changes?
>
> 73,
> KC9SWV - Morgen
> President, TARA
>
> On Tue, Sep 19, 2017 at 11:41 AM, Jon Anhold <[email protected]> wrote:
>
>> Apologies if this has been posted previously, but I'm hoping it will help
>> out the next 7300 FT8 user!
>>
>> I recently just replaced my FT-897D + Signalink USB with an Icom IC-7300.
>> Wow, what a cool rig!
>>
>> I like to use Commander to control the rig as much as possible, and use
>> the various integrations to it for rig control, etc -- including in WSJT-X.
>>
>> When switching from the Signalink to the 7300, as I got everything set
>> up, I noticed there was an ~2sec delay from when the TX window would start
>> in WSJT-X for FT8 and when the radio would actually key up and start
>> transmitting.
>>
>> Since timing is crucial on modes like FT8, obviously this wasn't ideal.
>>
>> I think I have finally figured out a combination of settings that
>> minimizes the TX delay:
>>
>> - Set the TX delay in WSJT-X to 0.0s (careful if you have a PA)
>> - Set Rig to DX Lab Commander, PTT CAT, Mode none, Split rig.
>> - Configure the 7300 to use RTS or DTR for PTT
>> - Set Commander to use RTS or DTR for TX as appropriate
>> - Check the "Suppress CAT" box in the PTT section in Commander
>>
>> This last one was key, as it minimizes the back and forth CAT commands to
>> the radio for TX/RX.
>>
>> I'm really enjoying the FT8/JT modes. Thanks to all for such a cool
>> program, and as always, DXLab has been fantastic - been using it since
>> 2003! Thanks Dave!
>>
>> 73 de KM8V (formerly N8USK)
>>
>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> wsjt-devel mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>>
>>
>
>
>
> ---------- Forwarded message ----------
> From: Rich - K1HTV <[email protected]>
> To: [email protected], WSJT <[email protected]>
> Cc:
> Bcc:
> Date: Tue, 19 Sep 2017 12:29:35 -0400 (EDT)
> Subject: Re: [wsjt-devel] FT8 is forcing the discipline of split ...
>
> Sig,
>
> The only way I can find a way to go split after clicking on his call
> inJTAlert is to hold the shift key down, move the pointer to a clear
> frequency and left click the mouse. If you are fast enough you may be able
> to be decoded the first try.
>
>
> I find it much easier to first find a quiet frequency and shift left-click
> on it to set your TX frequency. Then when you see a station in the Band
> Activity list, hold the ALT key while double clicking on the line
> containing the station that you want to work. This procedure has worked
> very well for me in chasing and working DX. Make sure that
> SFile/Settings/General/Display/"Blank line between decoding periods" is
> checked. It makes it much easier if 15 second periods are separated by
> dashes. And as a bonus, you get to know what country the CQer is in.
>
>
> 73,
>
> Rich - K1HTV
>
> Now over 5,000 FT8 Q's in 139 DXCC countries (116 confirmed) with 50-75W
>
>
> = = =
>
> Message: 2
> Date: Mon, 18 Sep 2017 11:30:57 -0500
> From: Joe <[email protected]>
> To: WSJT software development <[email protected]>, Gary
> McDuffie <[email protected]>
> Subject: Re: [wsjt-devel] FT8 is forcing the discipline of split ...
>
>
> I just WSJT-X and JT-Alert can figure out how to run split together.
>
> I love how JT-Alert works, and does, but any clicking in JT-Alert puts
> both REC and TX on the same freq no matter what you have checked in WSJT-X
>
> Joe WB9SBD
> Sig
>
>
>
> ---------- Forwarded message ----------
> From: Rich - K1HTV <[email protected]>
> To: WSJT <[email protected]>, [email protected]
> Cc:
> Bcc:
> Date: Tue, 19 Sep 2017 13:00:42 -0400 (EDT)
> Subject: [wsjt-devel] A suggested FT8 split option
>
> Gary,
>
> Operating split on FT8 should be the rule and not the exception. Why
> would any want to call on the same frequency and a CQer? Your chances of
> working a station are so much better when you are calling on a clearer
> frequency.
>
>
> I use VNC Viewer with my Android smartphone to view the 3 shack monitors
> and control WSJT-X while working around the house or when in town. Setting
> up a split is much more difficult with a smart phone with no ALT key. It
> becomes a multi-step process which usually takes so much time that one
> calling period is wasted in setting up the split.
>
>
> Joe & the WSJT-X Team:
>
> I wonder if there could be an option which, if checked, would allow the
> user's TX frequency to remain as selected. If this could be done, when you
> double click on a station's call (without the ALT key) in the Band
> Activity column, only the green RX indicator would move and the red TX
> indicator would stay where it was set. . Implementing this option would
> result in much more split operating and a better frequency distribution of
> multiple callers. Fewer multi-station pileups would result in faster QSOs
> because of less single frequency QRM. Why not make this the default?
> Operating simplex would require a CTRL-left mouse click on that station
> callsign.
>
>
> 73,
>
> Rich - K1HTV
> ----------------------------------------------------------------------
>
> Date: Mon, 18 Sep 2017 08:18:43 -0600
> From: Gary McDuffie <[email protected]>
> To: WSJT software development <[email protected]>
> Subject: Re: [wsjt-devel] FT8 is forcing the discipline of split ...
>
> Funny. Same guy finally forced me to go split this morning on 80m. Took
> about 4 tries and some moving around, but I finally got him. I?ve been
> seeing him pretty much daily on 80m in the morning, so some of you might
> want to snag this one.
>
> Gary - AG0N
>
> -------------------------
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> wsjt-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
