Multicast support to GridTracker

[EI4KF]

My scenario: JTDX and Swisslog on my Windows 11 computer and GridTracker on my networked Raspberry Pi.

What I have been doing: GridTracker will accept Multicast UDP messages from JTDX. I used IP 224.0.0.251 on port 2237 and it works as far as GT is concerned very well.
Unfortunately, only the Primary UDP Server in JTDX can be configured for Multicast. This means that a second and more limited server has to be used in JTDX to send log data to Swisslog. That works but of course I do not get the full features, the loss of which I have tolerated but now my tolerance has expired! 

What would really help, if it could be done, is for Swisslog Main UDP input to forward to GT using the Multicast addressing noted above. I have checked forwarding, entered the 224.0.0.251 on port 2237 but it is not received by GT and in Wireshark I do not see anything leave Swisslog on that port. I suspect therefore that Multicast is not implemented, not surprising really hi. I wonder if it can be?

It is not absolutely critical. All it means at the moment is that GT will not track band changes and I have to manually do that in GT. But it would be nice if I could have all 3 programs working together.

Erik EI4KF

[EA3GCV]

Hello Erik,

If your data flow is:

JTDX > Grid Tracker > Swisslog

Instead of enabling the second UDP server in JTDX to send QSO to Swisslog, in Grid tracker enable Forward UDP messages to another port (i.e. 2238) then use this port as input in Swisslog. Of course under this scenario you will always have to use Grid Tracker to log QSO from JTDX. Which features are you losing in Swisslog using the second UDP server? using the GT's forwarding option should work perfectly as well.

The forwarding option available in Swisslog only works to forward data on an not already used IP/port. Because you are forwarding data on the same IP/Port used by JTDX that's the reason you won't see anything in GT or Wireshark.

I have revised all options in the UDP component used in Swisslog and there is no Multicast option. I'm using the best component available for the Delphi D6 compiler. However, there is an option (already enabled) which allows more than one instance of the component to be active on the same local port. That is, sharing local port with other applications. But this doesn't work for forwarding only to receive data.

73

[EI4KF]

Hello Jordi

Thank you for your answer.

GridTracker on the Raspberry Pi does not forward to Swisslog on my Windows computer. I have no idea why not. I can transfer files across my network from the Pi to the W11 machine and vice versa. But if I enter the IP of the W11 machine in GT forwarding on the port set up in Swisslog to receive it, nothing happens. In Wireshark I see nothing, not even dumped UDP packets. I am not alone in experiencing this issue as there is thread on the GridTrackerApp io group about it. 

I am not using the same port used by JTDX by the way.

The features not seen when only log data is sent to Swisslog is the display of information that Swisslog provides before the QSO is logged. I don't see the Callsign field populated until the actual logging and I don't see the statistical information while the QSO is in progress either. Personally, I think this is one of the many important features of Swisslog that is not available in other logging software. I have been operating without it, having previously had it before changing GT to another computer on the network, but my tolerance for its loss expired.

However, I have solved it (with help from one of the GT group). It is convoluted and not ideal but in the absence of multicast this seems to be the only option. I now have the main primary UDP server in JTDX sending data to Swisslog. The 2nd UDP server feeds a GridTracker application on the Windows machine. This is a 'dummy' application, I do not display it because even with 3 large monitors I do not have screen space (the reason for having GT on a Raspberry Pi in the first place) and it is just running in the background. This GT in Windows will forward to GT on the Raspberry Pi using the Pi's IP address. Why this works whilst nothing works else beats me. It appears that GT will forward to another GT but not to anything else. I must have that wrong but I cannot figure it out. Anyway, now Swisslog gets the full features and GT is working on the Pi. Hooray, success.

If I dispense with Swisslog and use Ham Radio Deluxe instead, I can use multicast transfer from HRD in Windows to GT on the Pi. I don't need the 2nd GT app running in Windows. But no way am I changing from SWL to HRD as you can imagine. 

73 de Erik.

[EA3GCV]

Hello Erik,

Thank your your detailed explanation about the issue and solution!

Excuse me my ignorance, but what's the reason of using GT on a Raspberry Pi? and what are the benefits you get of using GT on a Raspberry Pi instead of using the regular Windows version apart from saving screen space? If I have a clear map of your setup and reason of using GT on a Raspberry Pi maybe I can think on another solution.

73

[EI4KF]

Hello Jordi,

Screen space. You would not believe what I have running here.

I have for Windows 11: 3x 4K monitors, of which 2 are 28 inch and one is 30 inch (forgive my imperial measurements). I don't have room for another large monitor.

Screen 1: entirely SmartSDR SDR panorama and waterfall for my FlexRadio 8400M

Screen 2: 75% is Swisslog a) logbook view b) DX Messages low bands c) DX messages high bands and d) Statistic overview
              25% is CC User for either a DX Cluster view of VE7CC or the ON4KST 50/70 mHz chat and 6m DX path map if 6m is open

Screen 3 (30 inch) is where I used to have GT but now: Swisslog a) DX messages 6m b) DX Messages 60m c) Entry of QSOs
SDC Skimmer A window, SDC Skimmer B window, SDC Shortcut Panel (DX Clusters, Skimmers controls)
JTDX main window and wide graph window
FlexRadio CAT / DAX / Tuner Genius control window / PGXL amplifier control window
FRStack control automation for Flex

and that leaves me with nothing for GT which I like as a utility because as it zooms in I can see great detail of the location of my QSO partner in FT8 but only if its window is large enough to see that detail. So I moved it to a Pi with its own 15 inch monitor.

I could have used another Windows computer I suppose. But I like the Pi because it has a minimal desk footprint as the unit is small as you know and I can also run HamClock on it which I also find useful.

So there you are Jordi, screen space alone is my reason. Someone will say 'but if you've added a monitor for the Pi you could have added it for the Windows machine'. This is true but I already had the Pi for running HamClock.

PS: look out for new country table near end of October - there is very little to add but I will check on CQ WW activities before sending you a new database.

73 de Erik.

[EA3GCV]

Hello Erik,

Thank you again for your detailed response. What a pity that UDP messages from the GT on the PI are not reachable to avoid using the GT on Windows as "gateway". At least you have found out a solution! Why UDP messages from the PI can't be read in Windows? Have you tried to disable Multicast in GT then enable forward from GT to the Windows 11 IP? Maybe you don't need Multicast at all. I remember having issues enabling Multicast in GT in some of my testing.

I'm also thinking that if the 2nd JTDX server feeds properly GT, then you could use this second server perfectly as input in Swisslog (used as main instance to get all the benefits). I will test but second server should send exactly the same UDP messsges as first server.

I will release the new country table as soon as you send it to me. Thank you for your excellent job maintaining the country table!

73

[EI4KF]

Hello Jordi

Could you please test second JTDX server when you have the time? I did not get the full features when I tried it, only the log data. But maybe I did not have correct settings.

There is no rush because I do at least have a solution.

BTW I can get GT on Pi to send or receive UDP to GT on W11 computer just by using each machines IP address (not multicast). But I cannot transfer UDP from Swisslog or JTDX to GT on the Pi by using the Pi IP address. Why it works GT<>GT but not SWL>GT or JTDX>GT without multicast I do not know. Maybe it is something about my network although I can transfer files all over my network i.e to any other computer or to my Synology NAS storage so there is something I do not understand (as usual!)

Anyway, don't worry although I would be interested to know if all the SWL benefits are available from JTDX 2nd server.

73 de Erik.

[EA3GCV]

Hello Erik,

I have tested 2nd JTDX server and I can confirm that it's only sending log data! Works the same as the TCP server.. what a pity!

Have you tried forwarding UDP messages from GT on Pi to W11 IP? In Swisslog you will have to set the W11 IP address not 127.0.0.1. It should work.

73

[EI4KF]

Hello Jordi

Thank you for testing. Yes, a pity.

In GT there is a Forward UDP messages settings box. It will forward to another GT but not to anything else. Unless I use multicast. But that cuts out Swisslog and I'd have to change logbooks to, for example, HRD. No thankyou! Perhaps I have a network issue, I do not know. Anyway, I have a solution and no need to waste more time on it. Thank you for assisting me. 


73 de Erik.