Re: Bandmap callsigns on WSJT-X not transferring to L32 Input Window
toggle quoted messageShow quoted text
From: firstname.lastname@example.org <email@example.com> On Behalf Of Fabio IZ8MBW via groups.io
Sent: 25 March 2021 09:50
Subject: Re: [hamlogger] Bandmap callsigns on WSJT-X not transferring to L32 Input Window
another behavior when Loggre32 clear the selected callsign from the Logbook Entry Window is in this case:
- DX Station call CQ.
- I select that DX Station so I will go to call him (now Logger32 correctly put the DX Station callsign into Logbook Entry Window and QRZ lookup start)
- The DX Station did not reply to me but replied to another station.
Well, in this case, when the DX Station did not reply to me but replied to another station, Loggre32 clear the selected callsign from the Logbook Entry Window.
If after I recall that DX station (doble click again on the DX Station), Loggre32 put again the DX station callsign into Logbook Entry Window and QRZ lookup start once again.
This is the example on WSJT-X:
This happens with WSJT-X and not with JTDX (probably because JTDX did not send via UDP the message to immediately "clear" the Callsign).
Well, I think make more sense to leave the DX Station callsign into Logbook Entry Window until I will choose another DX Station to call or I click on a DX Spot of another station. I mean, do not clear the callsign into Logbook Entry Window if I did not decide it.
On Wednesday, March 24, 2021, 06:01:01 AM GMT+1, Gary Hinson <gary@...> wrote:
We are currently beta testing a change that stops Logger32 erasing callsigns from the log entry pane when the UDP BandMap is open … since we normally operate split in FT8, and splits above 1 kHz were tripping the “Clear callsign on QSY > 1kHz setting” for those using it.
There are other changes & bug-fixes in the works, so it may take a wee while to complete the testing and release the next version.
I just hope it will cure your issue.
From: firstname.lastname@example.org <email@example.com> On Behalf Of Jerry Spring
[Edited Message Follows]
I just upgraded from V3.5 to V4.0 and everything seemed to go perfectly. Except that I can no longer double click on a callsign in the WSJT-X bandmap window and have it transferred to the Input "Call" field in L32. The only field that does transfer is the Grid square. So the UDP link is working. I have the UDP server set to 127.0.0.1 in WSJT-X with port 2238. These are the same settings I see at the bottom of L32, when I hover over UDP. What am I missing? I also tried setting the port on both to 2237, with identical results.