+- Swisslog's Forum (https://www.swisslogforwindows.com/forum)
+-- Forum: Swisslog version 5.x (https://www.swisslogforwindows.com/forum/forumdisplay.php?fid=3)
+--- Forum: General discussion (https://www.swisslogforwindows.com/forum/forumdisplay.php?fid=4)
+--- Thread: Logging from WSJT-X etc. and Realtime QSO entry (/showthread.php?tid=1251)
Logging from WSJT-X etc. and Realtime QSO entry - g0syp - 21-03-2025
I am often using digital modes like FT8 and CW/SSB at the same time.
When I log a contact from WSJT-X or similar programs, it unchecks the "Realtime QSO entry" option for the entry window.
Now if I want to log a "normal" contact afterwards I regularly forget to tick the setting again and can forget to set the correct time (mostly) or sometimes frequency of the QSO.
I seem to remember that this used to work at some point but can't say when or in which version if ever.
Is there a setting somewhere to automatically set it back?
Thanks, 73
Carsten G0SYP
RE: Logging from WSJT-X etc. and Realtime QSO entry - EA3GCV - 21-03-2025
Hi Carnsten,
When Swislsog is linked via UDP with WSJT-X or similar programs the Realtime Entry is unchecked automatically when a QSO is saved because date/time is set from WSJT-X. The same happens with the "Do not set mode from TX" option. this option is automatically checked when UDP linked to allow setting the QSO mode from WSJT-X in case CAT control is on. When UDP linked is off Swisslog restore these settings to the previous state.
In order to know the previous state, Swisslog reads these options when the QSO Entry window is opened. So, with UDP link off (UDP button red), set these options as you like for normal operations: normally the Do not set mode from TX is unchecked and realtime entry is checked. Then close and open the QSO Entry window. This way Swisslog will "know" your initial state fro these options. It's very important the Options / Save desktop at exit option is checked otherwise Swisslog will ignore all changes in the session.
Now you know how this works. Sometimes may happen that these settings are not set back properly. Although it's coded properly but after a crash or other scenarios may happen that Swisslog is not able to restore them properly. In such case, perform the above operation.
Best 73