I think the problem here is the error message that is being generated if
call3.txt is considered too short. The required length is not specified but 3
entries is too short. The error message appears to print a random number of
times in each decode period. To avoid this I Googled and found a populated
call3.txt. That stopped the error message, but of course there were then a
couple of 'unexpected' DX spots! (I won't claim the first 2 metre transatlantic
long path contact though!) I was monitoring a beacon with a lot of aircraft
Doppler.
I think the right behaviour is to bring up the "call3.txt is too short "
message just once, but if I was only interested in spotting one beacon who is
to say what is too short?
Bob Thornton
G3WKW
> Date: Tue, 01 Nov 2016 19:05:37 -0400
> From: Joe Taylor <j...@princeton.edu>
> Subject: Re: [wsjt-devel] call3.txt
> To: WSJT software development <wsjt-devel@lists.sourceforge.net>
> Message-ID: <58191fc1.1070...@princeton.edu>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>> On 11/1/2016 6:54 PM, Relu Jianu wrote:
>> Is there a mechanism of updating the call3.txt list?
>>
>> Thanks
>> 73 Relu NJ9R
>
> Everyone's working habits of band, mode, location, etc., are different.
> The callsign database is best maintained by you, yourself, using the
> "Add" button on the WSJT or WSJT-X main window.
>
> -- 73, Joe, K1JT
>
------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
