Just another view on this - last night there was a UK contest - despite it being a ‘Normal’ mode contest a pile of people were using ‘EU Contest mode’. What was noticeable, yes WSJT switched modes to follow but in many cases while switching you ‘lost’ the report.
While the system went on to sent RR73 etc. and log the contact - it was not complete - so stations had to call again. If there was yet another option to remember to switch off/on and both ends needing to recognise the need if one was ‘hidden’ Nope sorry leave it up to the operator. Tom P.S. I could see on a QUIET band there would be benefit of suppressing the odd local - glance at screen if activity cool band opening work the band - the local 5 miles away (running in robot mode) makes it not that easy. Thankfully JTAlert can limit by distance but that is Windows only. You would need to make sure the entries fully supported ‘wildcards’. -- 73’s Tom GM8MJV (IO85) On 4 Dec 2019, at 05:37, Black Michael via wsjt-devel <wsjt-devel@lists.sourceforge.net> wrote: > It's not a lockout file. > > The idea is very simple. > > Right now call first always picks the 1st decode...ergo the problem.... > > So the idea is that once a call is worked it gets put in a list (doesn't > matter whether or not you log it). The call first logic checks the list and > ignores anybody in it. > If call first does not trigger then the 1st entry that was detected would be > used. > So it would all be completely transparent, only temporarily blocks calls, and > clears itself. > > If you have 5 people calling you it will go 1,2,3,4,5 and start over again > whereas right now it's 1,1,1,1,1, ad nauseum. > > For the most part nobody would even notice this was happening except the 1st > decode may not be the one chosen. > > de Mike W9MDB > > > > > On Tuesday, December 3, 2019, 11:28:30 PM CST, Jim Brown > <k...@audiosystemsgroup.com> wrote: > > > W9MDB wrote: > > > I'm all ears for opinions from operators who have had a call pileup on them. > > I've been a ham since 1955, General in '56, Extra '59. I've always been > primarily a CW op, mostly contesting and chasing DX. I've been the guy > on the DX end of pileups working CW in a major contest, no split > operation. I also work RTTY contests as part of a club that often wins > them. So far, I've not gotten interested in FT4/FT8 contesting on HF. > > I'm near San Francisco and have a very good station. I use FT8 > extensively on 160M during the winter to work EU, and both FT8 and > MSK144 on 6M chasing grids. I rarely call CQ, mostly tail-ending > stations I want to work, just as Dave does. That's smart operating. > > The craziest I've seen FT8 is when 6M is open to JA, often with > JTAlert's 4x9 display nearly full of decodes. By far the best way to > work it is to call CQ with Call First off, Auto Seq on, Hold TX Freq on, > and pick the station I want to respond to. > > As to this lockout thing -- IMO, the nuisance calls come from new folks > who have little HF experience, have massive receive noise, and never > realize the band is open for DX, only look at JTAlert, and are calling > the only signals strong enough to get through their noise. A library of > lockout calls is quite unlikely to work, because it's different new > folks every time! Indeed, those JA openings are almost the only time I > call CQ, and for that reason! The only folks I want calling me are the > DX I want to work, and I don't want guys who can't hear or don't have a > clue covering them up! > > 73, Jim K9YC > > > > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
