Regarding comments suggesting that a band plan can be implemented and enforced
in software, I don’t think that will work. It would rely on properly engaged
and functional CAT control by the Fox. Given that several stations have already
“jumped the gun” and are using the mode in its incomplete form, I don’t hold
out a lot of hope there.
K1HTV and N0AN have made well-reasoned and prudent suggestions. It is likely
true that whatever the dev team bakes into the software will become the de
facto standard. It is also likely that whatever they choose will torque
somebody off.
Perhaps a compromise (that, of course will not please everyone) could be:
Frequency (Hz) above current FT8 lower “channel edge” --
0000 - 2000 FT8 operation
2001 - 4000 JT65, JT9 primary, and FT8 shared
4001 - 6000 FT8 DXpedition mode or extreme weak signal efforts for JT9 or JT65.
Granted, this accounts for just one Dxpedition at a time. Given the nature of
the project, I would doubt there will be an effective way of preventing
determined users from bypassing any software lockouts, etc., preventing DXp
mode use. Education will be necessary, and, as many of our colleagues suggest,
a healthy dose of “Ham Spirit.” Perhaps the software can feature a pop-up box
(like the beta versions do) upon entering DXp mode, that requires
acknowledgment, beyond just hitting enter, that the operator is running a
recognized DXPedition? Won’t stop anyone who really wants to use it, but might
give pause to the unknowing.
George J Molnar
Washington, DC, 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
