have been using FT8 today on 20m 18 qso in log 14dxcc eqsl will not exept
mode ?
like mode very quick no faults exept eqsl
On 30 June 2017 at 18:55, Dan Malcolm <dan.malcol...@gmail.com> wrote:
> FYI. I just tried the “split” mode in WSJT-X for an FT8 QSO. My Apache
> 100D seems to like it just fine.
>
>
>
> *From:* Black Michael via wsjt-devel [mailto:wsjt-devel@lists.
> sourceforge.net]
> *Sent:* Friday, June 30, 2017 12:04 PM
> *To:* WSJT software development <wsjt-devel@lists.sourceforge.net>
> *Cc:* Black Michael <mdblac...@yahoo.com>
>
> *Subject:* Re: [wsjt-devel] FT8 - build 7752 and rig control
>
>
>
> What if we just named that box "Audio Split Operation" and improve the
> tooltips?
>
>
>
> Tooltip on groupbox: Special split ops for cleaner audio -- see help file
>
> Tooltip on None: No split
>
> Tooltip on Rig: Use rig split capability
>
> Tooltip on FakeIt:Split occurs on VFOA during transmit
>
>
>
> Might have to improve the help a bit to explain these things better.
>
>
>
> de Mike W9MDB
>
>
> ------------------------------
>
> *From:* George J Molnar <geo...@molnar.com>
> *To:* WSJT software development <wsjt-devel@lists.sourceforge.net>
> *Sent:* Friday, June 30, 2017 11:40 AM
> *Subject:* Re: [wsjt-devel] FT8 - build 7752 and rig control
>
>
>
> (Sorry Joe - posted this to you instead of the group - apologies for the
> double message)
>
>
>
> Hi Joe,
>
>
>
> I was just about to send an “amen” to Mike’s comments - he hit it on the
> head.
>
>
>
> The nut here seems to be with the use of the term “split.” It implies two
> different frequencies are being used for the contact. This threw me, and
> probably some others.
>
>
>
> We also use the “split” terminology to describe MSK144’s use of "CQ nnn”
> to indicate a true split between calling and operating frequency. That
> makes plenty of sense, but isn’t what we’re doing for FT8, for example.
>
>
>
> As for “needing” a “solution.” it’s really neither a need, nor a solution.
> I don’t want to see my dial frequency move without explicit command by me.
> Personal preference, really. It’s not wrong either way, so technically
> doesn’t need a solution. Just a preference that I suspect others may share.
> Having CAT enabled for PTT and proper logging is very desirable, though, so
> I don’t want to disable it.
>
>
>
> BTW, the manual is an excellent guide. I fear that most don’t read it line
> by line, or even at all. We can’t count on the very clear text (and it is)
> making it to all users before they get frustrated or vent their feelings
> on-line. The more we can make intuitive and transparent, the better for
> everyone.
>
>
>
> /opinion
>
>
>
> *George J Molnar*
>
> Nevada, USA
> KF2T @GJMolnar
>
>
>
>
>
>
>
> ------------------------------------------------------------
> ------------------
> 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
> wsjt-devel@lists.sourceforge.net
> 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
> wsjt-devel@lists.sourceforge.net
> 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
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
