I will try to make this into a wsjt-devel topic. I have experienced the
same "CQ right on top of me" many times. Mostly it is because a station
just worked me and switched to CQ after the contact is complete. When
people work spit (Hold Tx frequency, no problem. But if I am calling CQ
and running stations, and the a station with Tx on Rx strategy it can be a
problem for the next station not working split.
But there another case that we should think about. Too often a station
starts calling CQ on top of a Dx station I'm trying to work, and the the
frequency is too close to be a coincidence. There are 2500 frequencies so
it is very unlikely that a station will start up within 2 Hz of another
station by chance.
What I think is happening is that people click on signals so they can see
them in the Rx Frequency window. They have not checked the Hold Tx
Frequency and so the transmitter frequency is automatically following the
Rx frequency. I used to click on an Rx signal in JT65 because it improved
the decode or duplicated the decode. I don't think that has any benefit in
FT8 mode. I have no idea why someone would want to click on a frequency to
the "set the receiver" but maybe some do it.
If this is correct, then I would suggest some ideas, some of these may be
terrible, please criticize and discuss...
- Change the operation of FT8 to not let the transmit frequency follow
receive oriented clicks
- Even if not operating Split, don't let the Tx follow the Rx
- Consider deleting the Rx frequency selection function, what is the
benefit?
- Set the default to split operation (check Hold Tx Frequency)
- Consider renaming "Hold Tx Frequency" to "Split Operation" or "Optimum
Tx Select"...People still don't have a good model for operation that allows
Tx anywhere and Rx everywhere
- Have a lot more discussion and training on strategies for setting Tx
frequency
- Tx frequency selection is too important to leave to accidents, side
effects, and misunderstandings
Thanks for starting this thread, it a good excuse to discuss some things
that have been bugging me.
thoughts?
jeff, wa1hco
On Thu, Apr 18, 2019 at 4:41 PM James Shaver <[email protected]> wrote:
> And speaking of S/N, I just realized this is the “devel” reflector and not
> the generic WSJT Group reflector. This really isn’t a topic suitable for
> the development side, to be honest...
>
> 73,
>
> Jim S.
> N2ADV (ex KD2BIP)
>
> > On Apr 18, 2019, at 4:34 PM, James Shaver <[email protected]> wrote:
> >
> > It never ceases to amaze me how so many hams instantly jump to the
> conclusion that what they witness on the air is automatically attributed to
> intentional “rudeness” or ill intent.
> >
> > His s/n is not really relevant - it’s very possible that even if
> propagation was, to coin a phrase, putting this person in your lap, that
> does not mean you’re even a weak trace on his/her end. That person may have
> a very high local noise floor due to an indoor antenna or a lot of noisy
> consumer electronics around them or it could even be as simple as plain old
> propagation differences or it could be someone who has just jumped into
> digital modes for the very first time and is not yet familiar with the
> interface.
> >
> > If it bothers you that much, look up their email on QRZ and send them a
> screen shot and *politely* ask if they even heard/saw you. If they didn’t,
> offer to help them track down local noise generators or help them optimize
> their receive setup.
> >
> > It pays to give people the benefit of the doubt. If they turn out to be
> a jerk, then you can at least walk away with the satisfaction that you
> tried your best to be an “Elmer” and are, at the end of the day, the better
> person.
> >
> > And relax. It’s just ham radio. Nobody died on the table. This is
> supposed to be fun.
> >
> > Jim S.
> > N2ADV
> >
> > _______________________________________________
> > wsjt-devel mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
> _______________________________________________
> wsjt-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
