I’d suggest the last one past the pole (last decoded) wins. Could do it where 
it looks at dB value and pick the weaker (or stronger), or just have it do 
nothing. But, I suspect those solutions get more complicated. I’m probably 
overthinking it...



George J Molnar
Nevada, USA
KF2T  @GJMolnar





> On Jul 9, 2017, at 10:00 AM, Eric Gruff <egr...@cox.net> wrote:
> 
> I thought about that, but how will it deal with two or more stations calling 
> right around the CQ DF?
>  
> From: George J Molnar [mailto:geo...@molnar.com <mailto:geo...@molnar.com>] 
> Sent: Sunday, July 9, 2017 9:29 AM
> To: WSJT software development <wsjt-devel@lists.sourceforge.net 
> <mailto:wsjt-devel@lists.sourceforge.net>>
> Subject: Re: [wsjt-devel] FT8 Issue
>  
> Maybe a similar idea, but in reverse - when TX6 is selected and Enable TX is 
> True (you are calling CQ), any valid MYCALL HISCALL HISGRID response within a 
> certain DF range will get an auto response with TX2?
>  
> George J Molnar
> Nevada, USA
> KF2T  @GJMolnar
>  
>  
>  
> 
> 
> 
>> On Jul 9, 2017, at 9:16 AM, Eric Gruff <egr...@cox.net 
>> <mailto:egr...@cox.net>> wrote:
>>  
>> My suggestion was to enable a check box that auto sequences a call (HISCALL 
>> MYCALL MYGRID) on the cursor frequency only if a CQ (TX6) is selected. That 
>> way, you can park on his DF, and when he sends CQ, you will automatically 
>> call him. I suppose we can get fancy and allow selection of any CQ 
>> (including CQ DX) or just the standard one. It would also be nice to have a 
>> check box that only calls another station after he sends 73- this would be 
>> for when you want to work someone that is already in a QSO. If set up this 
>> way, you won't QRM an ongoing QSO.
>> 
>> 
> 
>  
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org <http://slashdot.org/>! 
> http://sdm.link/slashdot_______________________________________________ 
> <http://sdm.link/slashdot_______________________________________________>
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net>
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel 
> <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

Reply via email to