It has been said that the current dust-up over the use of the DXP mode is the
result, in part, of use of the program before its official release. How is
making the release of the feature official going to change anything? If making
the release official is a matter of tidying up a few last minute bugs, making
some last minute decisions about recommended frequencies, then we can expect
the same troubles when the official release is made. DXP leaders may make poor
choices for FT8 DXP mode and cause QRM.
It seems to me that the FT8 DXPedition mode QRM problem is equivalent to a
DXPedition opening QSOs in sideband mode on a regional net frequency. There’s
no way you will stop the eager DXers from tromping on the net frequency, so the
solution has to start with the DXPedition leaders.
The program is being misused. Short of retracting the feature, how do we
police its use? What is the plan?
Dave / NX6D
________________________________
From: Neil Zampella <ne...@techie.com>
Sent: Thursday, March 29, 2018 1:45:47 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Premature use of FT8 DXpedition Mode
The problem is Serge, that they picked frequencies that are normally in
use by other modes, thus causing more problems then Fox & Hounds solves,
as they did not consider the consequences of those actions.
Neil, KN3ILZ
On 3/29/2018 3:45 PM, F6BHK wrote:
> And about the expedition using DXp without the authorization of the
> development team (and who did not read the readme file either):
>
> I find, for one, that they are doing a very good job. They found how
> to publicize their expedition (freq and time),
>
> and, with the number of bugs in the app, they manage to give a
> significant number of ham reports.
>
> look to me people you should ask how they did it! Just in case you are
> walking down an improvement process.
>
> Cheers
>
> Serge
>
>
>
> On 29/03/2018 21:15, Joe Taylor wrote:
>> Everyone paying attention should already know what's contained in
>> this message -- but it's clear that some do not.
>>
>> The current General Availability (GA) release of WSJT-X is v1.8.0.
>> That program version does not include FT8 DXpedition Mode.
>>
>> We have made beta-level "release candidates" available for the
>> explicit purpose of testing FT8 DXpedition Mode. The release
>> candidates have included cautionary warnings to the effect that in
>> its present form, DXpedition Mode should be used only for controlled
>> testing.
>>
>> A few operators or groups have ignored our warnings and tried to use
>> FT8 DXpedition Mode in true pileup situations. The consequences are
>> predictably bad -- especially when the offending operator(s) have
>> chosen their frequencies badly and other operators are using a mix of
>> program versions including v1.8.0, v1.9.0-rc2, v1.9.0-rc3, some
>> version of JTDX.
>>
>> FT8 DXpedition Mode is not yet ready for “production” use. Until
>> WSJT-X v1.9.0 is fully released -- not a beta-level "release
>> candidate", but a full General Availability release -- DXpedition
>> Mode should be used only in controlled test situations.
>>
>> The next public test of FT8 DXpedition Mode conducted by the WSJT
>> Development Group will be conducted on April 7, a little over a week
>> from now. You are cordially invited to join us for this test. See
>> the announcement posted here yesterday (Subject: WSJT-X v1.9.0-rc3:
>> Testing of FT8 DXpedition Mode) for details.
>>
>> -- 73, Joe, K1JT
>>
>> ------------------------------------------------------------------------------
>>
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org!
>> https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fsdm.link%2Fslashdot&data=02%7C01%7C%7C6119466bf3c04b7b235a08d595b82919%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636579540553825520&sdata=9FR979Cdd%2BrxXy%2FbEjiArOWaeWEGR39rnOir4bwz14Q%3D&reserved=0
>> _______________________________________________
>> wsjt-devel mailing list
>> wsjt-devel@lists.sourceforge.net
>> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fwsjt-devel&data=02%7C01%7C%7C6119466bf3c04b7b235a08d595b82919%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636579540553825520&sdata=lBYUGahIdCIvBMKgGmnoQ0Zr8PjPUo15mybYg9XIIaY%3D&reserved=0
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org!
https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fsdm.link%2Fslashdot&data=02%7C01%7C%7C6119466bf3c04b7b235a08d595b82919%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636579540553825520&sdata=9FR979Cdd%2BrxXy%2FbEjiArOWaeWEGR39rnOir4bwz14Q%3D&reserved=0
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fwsjt-devel&data=02%7C01%7C%7C6119466bf3c04b7b235a08d595b82919%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636579540553825520&sdata=lBYUGahIdCIvBMKgGmnoQ0Zr8PjPUo15mybYg9XIIaY%3D&reserved=0
------------------------------------------------------------------------------
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
