HamApps Support (VK3AMA)
On 10/09/2019 12:32 am, Frode Igland wrote:
I was asked yesterday by a friend to help him get the decoded callsigns to show in JTAlert again, like they have been since he started to use JTAlert a long while ago until a couple of days ago. He is running WSJT-X 2.1.0 and JTAlert 2.14.3 and HRD 184.108.40.206. Logging from WSJT-X to HRD Logbook ran smoothly, so obviously WSJT-X broadcast were working as it should. As no call signs appeared in JTAlert, we thought the port numbers in WSJT-X and JTAlert might not comply, but they were all correct. We made a fresh install of JTAlert, to no avail. We kept trying other approaches, but made no progress. After all of this, we noticed that a vertical roller field had appeared to the left of the JTAlert call sign fields. We clicked the arrow on top of the roller field, but still no call signs to see. We then changed the number of call sign display lines from 3 to 2 lines, and suddenly the decoded call signs appeared, with everything working as normal. The roller field disappeared, not to be seen again. From WSJT-X we saw that there were certainly enough stations decoded that they would fill more than one or two lines.
Like you, I have no idea why changing the number of display lines appeared to correct the non-display of callsigns. I am unable to reproduce that effect here in testing. I typically run with 2 callsign lines and have never seen this effect.
While you were testing, did you also play with the JTAlert Alert Filter settings? The only way I can reproduce the non-display of Callsigns is to set one of the QSL Filters (eQSL, LoTW) and not have the HamApps Callsign database installed. It is that database that provides JTAlert with the QSL membership status of each decoded callsign and without the data JTAlert treats each callsign has having no QSL service membership causing the callsign to not pass an active LoTW or eQSL filter.
de Laurie VK3AMA