Rich,
I agree with you completely, as my experience is the same as yours. No
matter how it is implemented, I'm typically NOT going to call on on the OPS
Tx freq...it is too congested and just adds to the "local" QRM.
It is true that the band fills up with spread out callers using our
approach...but FT8 has no problems with that and there is a lot more room
in the band than on the TX freq fo the originating station.
Calling on the TX frq for a popular station is inefficient, being more
subject to the pileup qrm..but hey, people can do what they want. FT8 gets
decoded wherever it can...and rarely is that on the TX freq of the DX
station.
For casual contacts tx/rx same can work, but if I am actually invested in
working someone, I don't call them on their freq.
73, N0AN
Hasan
On Tue, Sep 26, 2017 at 10:00 AM, Rich - K1HTV <k1...@comcast.net> wrote:
> Ed,
> How does every caller moving to the TX frequency of a CQing station with a
> double click REDUCE QRM? That INCREASES QRM. The station that sent CQ is
> now faced with multiple callers, and as a result often NOTHING is decoded.
> This wastes time. Then when he finally picks out a station, he is faced
> with the QRM from those other on-frequency callers who insist on
> re-enabling their TX to continue calling, causing the receive station even
> more problems decoding the station he is trying to work.
>
> I believe that the way WSJT-X was configured in r8019 and r8021 would
> result in much LESS QRM than the way it was before r8019 and the way it is
> now in r8023. I encouraged Martti, OH2BH, to try FT8 in the very first FT8
> DXpedition, to Market Reef, OJ0. In a post-expition exchanges of emails
> with Martti, he related the great frustration of having to deal with many
> calling on his TX frequency, resulting in a much lower QSO rate. With over
> 5,500 FT8 QSOs in my log, and having to deal with multiple on-freq
> callers,I know of what I speak! Making split the default by leaving your TX
> frequency where you want it and NOT moving it a CQer's frequency is the way
> to reduce QRM.
>
> 73,
> Rich - K1HTV
>
> = = =
>
>
> From: Ed Wilson via wsjt-devel [wsjt-devel@lists.sourceforge.net]
> Sent: Tuesday, September 26, 2017 6:22 AM
> To: wsjt-devel@lists.sourceforge.net
> Cc: Ed Wilson <ed.wil...@ymail.com>
> Subject: [wsjt-devel] r8123 UDP Communication
>
> I built r8123 this morning and was pleased to see that double-clicking on
> a station calling CQ moves both the Tx and Rx frequencies to that of the
> caller. Although I can appreciate the comments of some of my colleagues
> suggesting that only the Rx frequency be moved, I believe that moving both
> is the best approach to reducing QRM.
>
> Now to the subject of this posting: it appears that communication between
> WSJT-X and JTAlert has been lost. I cannot double-click on a caller in
> JTAlert and get any response from WSJT-X. I can, however, double-click on
> the caller in WSJT-X and make a contact as usual.
>
> I am just passing this info along to assist in the development process...I
> can work around the issues as they arise in the testing process.
>
> Ed, K0KC
>
> ------------------------------------------------------------
> ------------------
> 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
