<![CDATA[Swisslog's Forum - Error reports]]> https://www.swisslogforwindows.com/forum/ Sat, 06 Jun 2026 03:21:51 +0000 MyBB <![CDATA[Problems with 1 June Beta]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1358 Mon, 01 Jun 2026 14:03:06 +0000 EI4KF]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1358
If I click a callsign in JTDX, in this version the call comes to the Statistic Overview window but then disappears and reappears, which has always happened before quite quickly but now is with a delay. If I click on a callsign in a DX Messages window, there is a delay before the call comes to Statistic Overview. 

The launching of Swisslog in this version takes longer than normal.

Register of QSL Cards: the window opens but is not immediately populated.

Prior to posting this report I had rebooted the computer and compacted my database to rule out extraneous factors. I also reverted to the 29 May beta and do not see this issue in that version.

I have attached a zipped video that may help visualise some of the problem.

Erik.


.zip   SwisslV5_dDQmRbcLNh.zip (Size: 3,77 MB / Downloads: 1) ]]>
If I click a callsign in JTDX, in this version the call comes to the Statistic Overview window but then disappears and reappears, which has always happened before quite quickly but now is with a delay. If I click on a callsign in a DX Messages window, there is a delay before the call comes to Statistic Overview. 

The launching of Swisslog in this version takes longer than normal.

Register of QSL Cards: the window opens but is not immediately populated.

Prior to posting this report I had rebooted the computer and compacted my database to rule out extraneous factors. I also reverted to the 29 May beta and do not see this issue in that version.

I have attached a zipped video that may help visualise some of the problem.

Erik.


.zip   SwisslV5_dDQmRbcLNh.zip (Size: 3,77 MB / Downloads: 1) ]]> <![CDATA[Display Errors]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1356 Sat, 30 May 2026 09:25:20 +0000 dl6lbi]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1356 In the latest beta version, there are several bugs regarding the statistics display and in the "Remarks" window.

The statistics display changes when switching from the "Input" window, (Picture left) to the "Logbook" (Picture right) Please see the attached images: Fail.jpg (incorrect display) vs. the "Input" window (which is correct). This message appears only when some statistics fields are populated.

In the "Remarks" window, the font is too small and cannot be changed.

It would be nice if the date were fully displayed in the input window; currently, a digit is always missing.

73 de Ingo

.jpg   ok.jpg (Size: 288,63 KB / Downloads: 9)

.jpg   Fail.jpg (Size: 234,02 KB / Downloads: 6) ]]> In the latest beta version, there are several bugs regarding the statistics display and in the "Remarks" window.

The statistics display changes when switching from the "Input" window, (Picture left) to the "Logbook" (Picture right) Please see the attached images: Fail.jpg (incorrect display) vs. the "Input" window (which is correct). This message appears only when some statistics fields are populated.

In the "Remarks" window, the font is too small and cannot be changed.

It would be nice if the date were fully displayed in the input window; currently, a digit is always missing.

73 de Ingo

.jpg   ok.jpg (Size: 288,63 KB / Downloads: 9)

.jpg   Fail.jpg (Size: 234,02 KB / Downloads: 6) ]]> <![CDATA[Field Note in QSO window]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1350 Thu, 07 May 2026 11:37:09 +0000 OK1FBE]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1350 I have started to use the version 5.116 and have the following issue: When I try to edit the recorded QSO, the field Note is not copied int QSO entry window (Note is empty) and new text of note overwrites the old note after Save of record. In Logbook window is not possible to set Middleeuropean font (For Note field itwas possible in all previous  versions, only neccessary to set after each start of Swl). After installing the Beta this issue stays the same. I believe this was not an issue in version 5.115 and I will try to return to 5.115 version from backup, hopefully.
Best regards
Vaclav
OK1FBE]]> I have started to use the version 5.116 and have the following issue: When I try to edit the recorded QSO, the field Note is not copied int QSO entry window (Note is empty) and new text of note overwrites the old note after Save of record. In Logbook window is not possible to set Middleeuropean font (For Note field itwas possible in all previous  versions, only neccessary to set after each start of Swl). After installing the Beta this issue stays the same. I believe this was not an issue in version 5.115 and I will try to return to 5.115 version from backup, hopefully.
Best regards
Vaclav
OK1FBE]]> <![CDATA[Weird behaviour in QSO-Entry Field]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1349 Tue, 28 Apr 2026 07:13:11 +0000 oe3kab]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1349 I Type "Jordi" and in the field I read "idroJ".
It happens since I updaded to Vers. 5.116
HW?]]> I Type "Jordi" and in the field I read "idroJ".
It happens since I updaded to Vers. 5.116
HW?]]> <![CDATA[operator field]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1347 Fri, 17 Apr 2026 20:13:58 +0000 dk3uw]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1347
Any ideas ?

Martin 
DK3UW]]>
Any ideas ?

Martin 
DK3UW]]> <![CDATA[missing FT2]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1346 Fri, 17 Apr 2026 13:27:12 +0000 DL1IP]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1346
FYI, I've noticed these two things.

1. Export log to WSJT-X JTDX , Mode selection missing FT2
End 2.  Entry of QSOs      Membership Panel Rhein Ruhr DX Association
The problem always occurs on restart.

Otherwise, everything's great and thanks.
VY 73 DL1IP]]>
FYI, I've noticed these two things.

1. Export log to WSJT-X JTDX , Mode selection missing FT2
End 2.  Entry of QSOs      Membership Panel Rhein Ruhr DX Association
The problem always occurs on restart.

Otherwise, everything's great and thanks.
VY 73 DL1IP]]> <![CDATA[Feld Operator]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1345 Fri, 17 Apr 2026 09:47:37 +0000 dl6lbi]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1345
After the last update, the following error occurs: when entering text in the "Operator" field, the cursor always moves back one step to the beginning. This results in the name being written backwards in capital letters.
This is annoying because it requires a mouse click after the entered letters for the text to continue in the correct sequence in lowercase.

vy 73 de Ingo]]>
After the last update, the following error occurs: when entering text in the "Operator" field, the cursor always moves back one step to the beginning. This results in the name being written backwards in capital letters.
This is annoying because it requires a mouse click after the entered letters for the text to continue in the correct sequence in lowercase.

vy 73 de Ingo]]> <![CDATA[Export data selection with filter]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1342 Sat, 21 Mar 2026 22:19:24 +0000 CT1AXS]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1342
Here what i have found.

1. On a logbook window, chose a filter on callsign, i.e. cy0s (yes not capital letters);
2. The filter will show you all records with this callsign;
3. Now use the Export data button and data on the window is clear and the file (ADIF for example) will be empty;
4. Repeat process but now on the filter selection chose CY0S with all capital letters and all is correct.

This means that we have to chose always all capiltal letters. Another example is, a CY0s will not find the call on the DB. 
Can you change to any type format on it?

73]]>
Here what i have found.

1. On a logbook window, chose a filter on callsign, i.e. cy0s (yes not capital letters);
2. The filter will show you all records with this callsign;
3. Now use the Export data button and data on the window is clear and the file (ADIF for example) will be empty;
4. Repeat process but now on the filter selection chose CY0S with all capital letters and all is correct.

This means that we have to chose always all capiltal letters. Another example is, a CY0s will not find the call on the DB. 
Can you change to any type format on it?

73]]> <![CDATA[Submenues cannot be clicked on]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1341 Tue, 17 Mar 2026 22:58:42 +0000 dl1daw]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1341 This error happens only in SWL not in other installed programmes/apps.
What is the reason for this error and how to correct it?
Shall I rollback to SWL version 5.114 or lower? How to rollback? What is the rollbackprocess?
I highly appreciate any support and assistance to eliminate this error.
Kind regards
Achim, DL1DAW]]> This error happens only in SWL not in other installed programmes/apps.
What is the reason for this error and how to correct it?
Shall I rollback to SWL version 5.114 or lower? How to rollback? What is the rollbackprocess?
I highly appreciate any support and assistance to eliminate this error.
Kind regards
Achim, DL1DAW]]> <![CDATA[update eqsl not working good]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1338 Fri, 06 Mar 2026 19:15:48 +0000 ON7VZ]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1338 I think I may have  a problem with the eQSL upload status in Swisslog.
In my case, Swisslog seems to download and mark received eQSLs correctly, but it no longer marks the QSO as eQSL sent at the moment of upload.
Before, if I remember correctly, Swisslog automatically set the eQSL_Send flag to  1 (or updated the sent status) when the QSO was uploaded to eQSL.
Now, this does not seem to happen anymore.
What I see is this:
  • the upload process starts,
  • received eQSLs are marked correctly,
  • but the eQSL_Send / eQSL_Status / eQSL_Send_date fields are not updated after upload,
  • and the QSO only appears as sent when there is also a received eQSL.
So it looks as if the “sent” flag is now only updated when a received confirmation exists, instead of being written immediately after a successful upload.
I do not understand this, because I am quite sure it worked correctly some time ago.
My login and password are correct, I only have one nickname/QTH, and I am using the latest Swisslog version.
Could this be a bug in the upload routine, or in the way Swisslog parses the eQSL server reply and updates the local fields?
Thank you for your help.
Best 73's
Daniel]]> I think I may have  a problem with the eQSL upload status in Swisslog.
In my case, Swisslog seems to download and mark received eQSLs correctly, but it no longer marks the QSO as eQSL sent at the moment of upload.
Before, if I remember correctly, Swisslog automatically set the eQSL_Send flag to  1 (or updated the sent status) when the QSO was uploaded to eQSL.
Now, this does not seem to happen anymore.
What I see is this:
  • the upload process starts,
  • received eQSLs are marked correctly,
  • but the eQSL_Send / eQSL_Status / eQSL_Send_date fields are not updated after upload,
  • and the QSO only appears as sent when there is also a received eQSL.
So it looks as if the “sent” flag is now only updated when a received confirmation exists, instead of being written immediately after a successful upload.
I do not understand this, because I am quite sure it worked correctly some time ago.
My login and password are correct, I only have one nickname/QTH, and I am using the latest Swisslog version.
Could this be a bug in the upload routine, or in the way Swisslog parses the eQSL server reply and updates the local fields?
Thank you for your help.
Best 73's
Daniel]]> <![CDATA[FTX-1 not reading mode]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1337 Thu, 05 Mar 2026 12:35:43 +0000 OK2KG]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1337
first of all, many thanks for your excellent support for Swisslog.

I have finally (after 3 months) received back my FTX-1 Optima from warranty repair, and connecetd it to Swisslog, my main log allready more than 30 years.
I receive the frequency from thr TRX without problems, but, when i change mode from CW to SSB or vice versa the mode in Swisslog does not change, as usual with my other radios (FTdx101d, IC9700, FT-891, IC7000).

73! George OK2KG]]>
first of all, many thanks for your excellent support for Swisslog.

I have finally (after 3 months) received back my FTX-1 Optima from warranty repair, and connecetd it to Swisslog, my main log allready more than 30 years.
I receive the frequency from thr TRX without problems, but, when i change mode from CW to SSB or vice versa the mode in Swisslog does not change, as usual with my other radios (FTdx101d, IC9700, FT-891, IC7000).

73! George OK2KG]]> <![CDATA[udp Error]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1336 Wed, 04 Mar 2026 15:40:34 +0000 dl4fcj]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1336
.jpg   UDP1.JPG (Size: 19,01 KB / Downloads: 6)

.jpg   UDPJTDX.JPG (Size: 117,46 KB / Downloads: 6) ]]>
.jpg   UDP1.JPG (Size: 19,01 KB / Downloads: 6)

.jpg   UDPJTDX.JPG (Size: 117,46 KB / Downloads: 6) ]]> <![CDATA[access violation error]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1332 Sat, 14 Feb 2026 13:00:09 +0000 on4bam]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1332
After using a TS-480SAT for a very long time the TRX died on me a few weeks ago.
I got an IC-7300MK2 since yesterday and it seems that Swisslog doesn't like this trx much  Huh
On starting Swisslog (5.115) it shows 2 errors.



.jpg   swisslog20260214_error1.jpg (Size: 12,04 KB / Downloads: 3)

.jpg   swisslog20260214_error2.jpg (Size: 13,18 KB / Downloads: 1)  

After clicking OK it seems SL works as expected.

At first I thought it had to do with WSJT-X starting up with SL but unselecting autostart makes no difference.

Swisslog uses omnirig to connect to the IC7300.

Any ideas?
Thanks.]]>
After using a TS-480SAT for a very long time the TRX died on me a few weeks ago.
I got an IC-7300MK2 since yesterday and it seems that Swisslog doesn't like this trx much  Huh
On starting Swisslog (5.115) it shows 2 errors.



.jpg   swisslog20260214_error1.jpg (Size: 12,04 KB / Downloads: 3)

.jpg   swisslog20260214_error2.jpg (Size: 13,18 KB / Downloads: 1)  

After clicking OK it seems SL works as expected.

At first I thought it had to do with WSJT-X starting up with SL but unselecting autostart makes no difference.

Swisslog uses omnirig to connect to the IC7300.

Any ideas?
Thanks.]]> <![CDATA[QSO INFOs via UDP]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1331 Mon, 09 Feb 2026 14:12:40 +0000 SV1FTY]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1331
I send contact infos via UDP to swisslog (from my selfmade logbook in python) all are ok but the UTC qso-time , although I send it in UTC, once SWL receives the contact infos turns the time in local (of course in qso option "Store UTC in log" is ticked - the realtime qso entry no matter - ticked or not)
Any suggestion please ?

P.S.
The forwarding contact infos format are the same as the incoming ones ( in XML format ?)

73 de SV1FTY Sotiris]]>
I send contact infos via UDP to swisslog (from my selfmade logbook in python) all are ok but the UTC qso-time , although I send it in UTC, once SWL receives the contact infos turns the time in local (of course in qso option "Store UTC in log" is ticked - the realtime qso entry no matter - ticked or not)
Any suggestion please ?

P.S.
The forwarding contact infos format are the same as the incoming ones ( in XML format ?)

73 de SV1FTY Sotiris]]> <![CDATA[DX Messages not displayed]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1323 Mon, 12 Jan 2026 14:06:37 +0000 OK1FBE]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1323 for some time (I do not know exactly how long yet) I do not see any DX messages. In Telnet settings the cluster and incoming messages are visible, but no transfer into DX Messages window. Internet is "Con" in this window and also the updates to databases (awards) can be downloaded. Data from QRZ about corresponding station come automatically, so hopefully no problem from firewall (Using Eset Cyber Security). 
I am using version 5.115 (the same when return to 5.114), Windows10 via Parallels 26 on Mac with latest OS. 

I wish you prospectfull year 2026 with full health.

Best Regards

Vaclav
OK1FBE]]> for some time (I do not know exactly how long yet) I do not see any DX messages. In Telnet settings the cluster and incoming messages are visible, but no transfer into DX Messages window. Internet is "Con" in this window and also the updates to databases (awards) can be downloaded. Data from QRZ about corresponding station come automatically, so hopefully no problem from firewall (Using Eset Cyber Security). 
I am using version 5.115 (the same when return to 5.114), Windows10 via Parallels 26 on Mac with latest OS. 

I wish you prospectfull year 2026 with full health.

Best Regards

Vaclav
OK1FBE]]>