connection to jAlert lost

[EA3GCV]

Hello Erik,

Seems the UDP connection is unstable in such case. But I'm unabled to reproduce this issue here. I use JTDX everyday with no problems. The only issue I experience from very time to time is the UDP link broken suddenly and I need to restart Swisslog. But when this happen there is no communication at all, is not as you related which seems a partial link failure. 

This is how the WSJT-X works:

- When the QSO Entry window is started (either at Swisslog atartup or when closing and open the QSO Entry window again) I need to read the following settings (user parameters) :
- Realtime entry
- Do not set transceiver mode

After linking to WSJT-X and receiving a callsign clicked in WSJT-X (that is, DX Call filled out) Swisslog enables the "Do not set transceiver mode" automatically (if not checked). This is mandatory if using transceiver control to set the current WSJT-X mode. Callsing and Locator is set in the QSO entry as well. If you are reading the locator from callbook databases and maidenhead matches from the one read from WSJT-X, Swisslog will set the 6 digits locator. If maidenhead doesn't match then the locator from WSJT-X is set.

When Log QSO button is pressed in WSJT-X or QSO is saved automatically in JTDX, Swisslog sets the Realtime entry off to allow set date/time from WSJT-X. Then all other fields are filled out then QSO is saved. After QSO has been saved, Swisslog restores the "user parameters" read when the QSO Entry is started (see my first explanation). This way Swisslog is set again with the initial user parameters even if the UDP link is active. That's why the mode field reads the transceiver mode again (if user have the Do not set mode from transceiver unchecked normally) and in your case shows RTTY because it should be the radio mode.if RTTY is not your radio mode, make sure you don't have checked the "Set mode according QRG Otherwise it will read mode according to band plan! 

It hay happen sometimes that these settings remain enabled (specially the Do not set mode from transceiver) in the next Swisslog session. The solution is, simple: uncheck this option, close and open, again the QSo entry window. This is the way to tell Swisslog: this is, my default setting to restore it when the UDP link if deactivated or after saving a QSO from WSJT-X. 

During status changes of WSJT- Swisslog reads Callsing, mode and locator from WSJT-X. When logging QSO Swisslog always read callsign,mode, date, time, QRG, Mode, RSTS, RSTR, Comments from WSJT-X then saves the QSO. This is all what happens if the UDP communication is right. That's why is very very important to add exceptions to Swisslog and WSJT-X (or JTDX) in your antivirus, firewall and similar programs. This is the only way to ensure these programs are not supervising and interfering the normal functioning of these programs and their communications. Otherwise there will be unexpected results.

Now I want to explain how the logging process works in Swisslog when saving a QSO, either when user press the Save QSO button or when it receives this order from external programs:

Swisslog starts all saving procedures but before finishing the save procedure, needs to process the realtime saving to the selected online services. At this point, I use multi-threading to speed up this process: Swisslog runs a separate thread for every online service enabled by the user. This means that even if you save in realtime in all online services supported by Swisslog, these operations are performed at once, because every online services uses a different thread. 
But before finishing the logging procedure, Swisslog needs to received the reply for every enabled online service to set the appropiated fields. If internet connection is slow or not consistent, the timeout defined on every online service comes into scene! If an error occurs or timeout is expired then Swisslog won't set the appropiated fields informing the QSO has not been saved in the affected online service. So if your internet connection is not stable or fast, I suggest to:

- Always disable error messages from all online services. This is a must when working linked to externañ programs such WSJT-X, to avoid dialogs which will interfere the logging process. I'm planning to display these error messages (if any) in a separate window instead a dialog window. This will show error messages without inteefering the logging process.
 - Set a, low, timeout value on the enabled online services. 15 seconds is the default value. 
- Disable realtime logging and upload your QSOs at the end of your session. This will speed up the saving procedure and maybe is the best way to know whether this is causing this issue or not. 

Excuse me for the long message but I wanted to explain how all processes work internally. Maybe this will help you to find out the source of this issue. Unfortunately I haven't received reports like this from other users and myself I use Swisslog with JTDX with no issues. If I can't reproduce here the reported issues, it's very difficult to me  to solve them. That's why I have explained you how the whole thing works. Maybe it will help. 

Some things are out of my control (such adding exceptions in antivirus) and must be performed manually by the user to ensure none of these programs are interfering the normal functioning of Swisslog and all programs linked with it. 

73