The problem with using it with DX friendly propagation is the antipode
being used for R <grid> . Yes people should know better but many don’t.
In fact there is guidance that it should be turned off when propagation
favors DX.
Ria
N2RJ
On Mon, Jul 23, 2018 at 8:33 PM W0MU Mike Fatchett <w...@w0mu.com> wrote:
> This had nothing to do with DX. The exchange was the grid DX or not.
>
> The issue is that you cannot work people if they are in contest mode and
> you are not.
>
> W0MU
>
>
> On 7/23/2018 6:22 PM, rjai...@gmail.com wrote:
> > NA VHF Contest mode should not be used in a DX contest, or at least
> > one with significant potential for DX.
> >
> > It was frustrating for me too, mostly because of the inconsistency.
> >
> > 73
> > Ria, N2RJ
> > On Mon, Jul 23, 2018 at 8:15 PM David Fisher <dsfis...@outlook.com>
> wrote:
> >> Sometimes stations would call “CQ WW xxxx yyyy”. In that case, it was
> easy to select contest mode and return the call. But in many other cases,
> the other station would give no hint he was in contest mode until his
> mangled grid square was received. In those cases I got the pop up that
> prompted me to turn on contest mode. I did so, but all of that takes time,
> coordination and practice to make work smoothly.
> >>
> >>
> >>
> >> I one case that I ran as an experiment, I called CQ in contest mode,
> got a reply, then got a message through JTAlertX asking what I was doing
> and why my grid square didn’t make sense. Etc. etc. etc.
> >>
> >>
> >>
> >> Bottom line – I wasn’t in the contest, but I made a mess of a number of
> other station’s contest mode QSOs, which defeated the intent of contest
> mode.
> >>
> >>
> >>
> >> Dave / NX6D
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> ________________________________
> >> From: W0MU Mike Fatchett <w...@w0mu.com>
> >> Sent: Monday, July 23, 2018 4:37:07 PM
> >> To: wsjt-devel@lists.sourceforge.net
> >> Subject: [wsjt-devel] Contest mode CQVHF
> >>
> >> First of all I want to thank everyone for this great advancement in the
> >> hobby!
> >>
> >>
> >> The CQ WW VHF was my first exposure to contest mode and it was a very
> >> frustrating 27 hours.
> >>
> >> If I am in contest mode and I call CQ and get an answer from someone who
> >> is not, there is essentially no way to complete a qso unless one side
> >> changes into or out of contest mode. What happened to me is I would
> >> switch and then the other side would switch and we would be opposite.
> >> Frustrating!
> >>
> >> The main issue is that we cannot expect those not in the contest to have
> >> to switch into a specific mode to work us. This does not happen in any
> >> other contest. We cannot expect this from casual ops. I am glad they
> >> want to work me. Being able to work them should be painless too!
> >>
> >> Why is contest mode needed? If a qso is good in contest mode with less
> >> sequences I suggest that all FT8 exchanges be the same. Is there a
> >> specific reason two have multiple sets of exchanges for in a contest and
> >> not in a contest? I don't think so.
> >>
> >> I understand that this was an issue for the June VHF contest too.
> >>
> >> If you guys can move my xmit around in fox/hound mode, which worked out
> >> really well, there has to be a solution for this. I believe that the
> >> fox was still able to work people not running hound? We need the same
> >> ability in contest mode.
> >>
> >> I believe that this is already being examined but I thought I would give
> >> my feedback. I would be happy to provide more information if desired.
> >>
> >> Thanks again for all the hard work in bringing us FT8!
> >>
> >> W0MU
> >>
> >>
> >>
> ------------------------------------------------------------------------------
> >> Check out the vibrant tech community on one of the world's most
> >> engaging tech sites, Slashdot.org!
> https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fsdm.link%2Fslashdot&data=02%7C01%7C%7Cbe807b8121b94f841e5808d5f0f86e14%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636679872141956608&sdata=4ngp%2FoSOWuPUakyW3qTn6b49JD01iE6jHJc%2BQlc6qbM%3D&reserved=0
> >> _______________________________________________
> >> wsjt-devel mailing list
> >> wsjt-devel@lists.sourceforge.net
> >>
> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fwsjt-devel&data=02%7C01%7C%7Cbe807b8121b94f841e5808d5f0f86e14%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636679872141956608&sdata=AiDSOG94NAAree6BMP1FFzeJk%2B6exoF2EylLUp9fu08%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
> >
> ------------------------------------------------------------------------------
> > 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
