Tnx for that. I had a brief look, but I don't know how accurate or complete is the JA data. I have always been under the impression that JA Hams outnumber other countries including the US in terms of

#Beta

I found this: Has some other useful links too… But I think there maybe something more official… I’ll have to look but most likely its in Japanese, which I don’t speak, read, or write. http://motobayas

#Beta

If there is an accurate and maintained list of JA Callsigns and their Prefectures or some reasonably accurate way to programmatically determine the Prefecture perhaps from an official Callsigns databa

#Beta

If there is a link to a Callsign+RDA list please let me know and I will download and investigate its suitability. de Laurie VK3AMA

#Beta

I guess it would be too slow for Japan too? Tracking Prefectures? It would be almost the same as the US callsigns and states. Mike K7QDX

#Beta

+ AA6YQ comments below I fully understand Dave. I just don't get it. Resources are about money....I guess, I get it.. But what is the cost. I know folks willing to help with this (since it is outside

#Beta

I fully understand Dave. I just don't get it. Resources are about money....I guess, I get it.. But what is the cost. I know folks willing to help with this (since it is outside my skillset).... Just n

#Beta

Thanks you and understood. This list of Russian Calls AND their associated RDA numbers/locations is 100% available AND well maintained by ES1TU. I will ask he reach out to you. Thank you, Jose N4BAA

#Beta

I replied to your previous message regarding this. See https://hamapps.groups.io/g/Support/message/36449 Unless there is a published list of Callsigns and their current RDA then it wont be possible to

#Beta

I have been attempting to get LoTW onboard with supporting RDA districts as part of Russian LoTW certificates which is technical easy to do, but man are they resistant. I just don't understand enough

#Beta

Laurie, Hello. Hope you are well. I have been attempting to get LoTW onboard with supporting RDA districts as part of Russian LoTW certificates which is technical easy to do, but man are they resistan

#Beta

Ah, Laurie! Must be Aussie Hacker humor to point out settings and info based on code released just hours before, ha! Thought I was bad when running the code distributions for Fido and Opus, et al. <lo

#Beta

Why bother with the UDP forwarding? That is no longer needed now that JTAlert supports UDP mulitcasting. You just need to set both WSJT-X and Grid Tracker to use the same multicast IP address (in the

#Beta

Glad you noted the multicast test-build issue, Laurie. I, too, lost my GridTracker input feed when I upgraded it at the same time I upgraded JT. Thought it was GT. Now looks like it may be due to the

#Beta

Bill, I just checked the code, that option was being ignored in the latest build (left over testing code that should have been removed) so it would not have made a difference. de Laurie VK3AMA

#Beta

Laurie, It was a cursory observation. I didn't see the pink B4s and maybe some other colors initially and not sure if JTA was displaying all of the callsigns either. So there appeared to be some effec

#Beta

Bill, Failing to uncheck that resend option should have no ill effects. Did you see otherwise? That resend option was being used by GridTracker prior to multicast, but with changing GT to using a mult

#Beta

Decided to try UDP Multicast with Grid Tracker and immediately saw positive benefits. Callsign lookups have more info and my QSLs are showing up according to the legend colors. Still getting feet wet.

#Beta

Hi Laurie, Thanks for the response. Right. I’d been using GT with JTA that way until now and wanted to explicitly mention they can be used independently now and that is working perfectly. JTA is never

#Beta

Russ, Tnx for the positive report. The point that many people are missing about multicast is that it allows multiple WSJT-X cooperating applications like JTAlert, DX Aggregator & Grid Tracker to be ru

#Beta