> On Dec 15, 2018, at 11:11 AM, Ton PA0TBR <[email protected]> wrote: > > I am trying to work out why some callsigns are shown as <...> in WSJT-X > Sometimes <...> is reflected in JTAlert as ... other times it is not shown > in JTAlert. > > For example: > 103615 -12 1.8 1590 ~ <...> LZ1PPZ > 103645 -2 1.8 1590 ~ <...> LZ1PPZ R-18 > 103715 -5 1.9 1589 ~ <...> LZ1PPZ R-20 > 103745 -8 1.8 1588 ~ OG55W <LZ1PPZ> 73 > > Looks like LZ1PPZ worked OG55W, but why was the call of OG55W not shown in > the initial messages? > And why is LZ1PPZ enclosed by <> in the last message?
For the first three messages, the full callsign OG55W had not yet been received and entered into the hashtable. Therefore, the hash number that was received in place of OG55W could not be associated with the callsign OG55W. On the other hand, the full call of LZ1PPZ was received in each of the first three messages, and each time that it was received it was entered into the hashtable. So when the hash of LZ1PPZ was received in the 4’th message, the callsign could be looked up in the hashtable and printed between angle brackets <LZ1PPZ>. > > Other examples: > 112030 -12 0.3 915 ~ G3PLP <...> -16 > 112100 -14 0.3 915 ~ <G3PLP> ZS9YOTA RR73 > Why was ZS9YOTA substituted by <...> ? Same as above. > > 111800 -17 0.1 650 ~ CQ SD4C JP80 Sweden > 111830 -14 0.1 650 ~ <…> > What happened here? Don’t know. > > I use WSJT-X v2.0.0.0 in FT8 mode > > 73, > Ton pa0tbr Steve k9an _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
