overloading CALLSIGN field with old entry

V2 error reports
Post Reply
dk1ws
Novice Class
Posts: 18
Joined: 22 Nov 2019, 08:39

overloading CALLSIGN field with old entry

Post by dk1ws »

My problem:

Configuration: LOG4OM, WIN4Icom,WSJT-X, activated in setup but not started: FLdigi

After program start the CALLSIGN field is automatic filled with an old call sign.
After deleting the entry in main window- it comes back as active if adjusting anything on the radio (udp).
Load new entry from cluster- radio gets correct CI-V commands, then reloads the old call sign.

Stop WSJT-X application- all works fine...

73!
Wolfgang
User avatar
KI5IO
Moderator
Posts: 1948
Joined: 16 Aug 2015, 16:30
Location: Plano, TX

Re: overloading CALLSIGN field with old entry

Post by KI5IO »

Wolfgang,

That is picking up the ADIF feed from WSJT-x and filling in the last QSO you had via that APP.
73 - Nolan Kienitz - KI5IO
Plano, TX
dk1ws
Novice Class
Posts: 18
Joined: 22 Nov 2019, 08:39

Re: overloading CALLSIGN field with old entry

Post by dk1ws »

Hi, Nolan,

thank you for the input, I think, I found now a workaround.

All works correct if the last FT*-qso was successful finished in WSJT-X with a log entry.
In other case active call sign will been stored in the WSJT-X.ini file and then it is the default value until manual deleting the entry or run a qso with a log entry...

73!
Wolfgang
Post Reply