www.dl2rum.de

Screen Shot 2021-07-23 at 2.20.31 PM.png Here you can see the same call (W4C) being displayed in the dxspots window as EL95 and the Network window showing Rumlog telling WSJT-X to start calling EL95(second from bottom line). WSJTX correctly called W4C and when I halted transmission, you can see ...

Screen Shot 2021-07-23 at 1.13.09 PM.png This behavior seems to be occurring with 1x1 callsigns. Here in this screenshot you can see the callsign is W4C, but Rumlog is displaying data for EL95. The second line shows another call that is parsed correctly, so I think this might be related to shorter ...

In the attached screenshot you can see the WSJTX import for 2 CQ calls
K2J and K2M (see note section for the actual call)
However the DX Call column is showing the locator (FM06 and EN90)

WSJTX version 2.4.0 (running on ubuntu)
RumlogNG version 5.6 (489)

Confirmed this issue is resolved in the latest release.
Thanks for fixing this!

Awesomesauce!

Thanks for the update.

I misread the field, my apologies.

Guess I shouldn't stay up so late and try to computer.
Thanks for your patience.

Upon further inspection, I have no idea how the country field is being populated in the log. I have manually entered logs where the qrz/hamQTH lookup was used and there is no country information in the country field. I also seem to have some automated WSJt-x entries where the country field has been ...

The third option works fine for States, as I can look them up and enter them manually after the log is saved. However for DX, the is no apparent way for me to update or even manually enter the country. The log shows country as a field, and calls created manually (SSB/Phone) have the country field ...

I had to turn on "Prompt me to log QSO" in WSJT-X to get this to work. Meaning I have to click OK in WSJT-X to log the QSO then switch over to RumLogNG and manually save the QSO (after it prompted me). This seems like an extra step, and no longer color codes the RumLogNG entry as per the settings ...

So I grabbed a screen recording from both machines of the behavior I'm seeing.
Main window is OSX running RumLogNG, and inset window (purple outline is my linux box running wsjt-x.
https://youtu.be/mElzl7FAx-M: