Swisslog's Forum - All Forums

Options not remembered on closing programme and restarting

Wed, 07 Oct 2026 09:59:59 +0000

I do not want to have the “Query LLOTA activators” checked. When unchecking and closing the program, next time I open it, it it still is checked. Occasionally this also happens with “Query US state…”

Is this a bug?

De Tom OH6VDA

Beta released on 16th October 2026

Tue, 06 Oct 2026 09:55:33 +0000

Dear users,

I have released a beta including the following improvements (latest changes highlighted in boldface):

NEW: Band Map - Advanced filtering system:
- Selection criteria — DXCC, Continent and Zone filters — The mode selection dialog now includes three additional filter: DXCC, Continent and Zone. Multiple values are supported in all three checkbox fields. Examples: EA, G, F for DXCC; EU, NA for Continent; 14, 33 for Zone. These filters allow precise control over which spots appear in the window based on the geographic origin of the DX station.
NEW: French Regions: Swisslog will automatically fill out the French Region field in all QSO with French stations (DXCC = F) where user has set the DDFM number (French Departament)
NEW: UDP Realtime saving and receiving UDP/TCP data in ADIF format: added State / Cnty ADIF fields (REGION, SUB-REGION respectively). When saving QSOs with DL stations the UDP packet will include the field DARC_DOK if the DOK field is filled out.
NEW: Support for JTTY: added new mode and adapted ADIF import/export function to fulfill the new requirements in forthcoming ADIF specs 3.1.8
NEW: Support for PAC, PAC2, PAC3 and PAC4: Renamed PACTOR mode to PAC to fulfill ADIF specs. Added new modes PAC2, PAC3 and PAC4
Corrected: QSO Entry > Station tab: Notes field was displayed empty when adding a new QSO with a previously worked station having notes in the C_NOTE field.
Corrected: QSO Entry > Station tab: Note field Unicode characters were displayed as ???.
Corrected: Band Maps: double clicking on a spot, if one of the actions was Log QSO and the spot contained award info such as WFF, SOTA, DME, etc. these fields were not set in the QSO Entry window.
Corrected: Dx Alerts: position and size were not restored after closing Swisslog.
Corrected: Telnet server window: now accented latin characters are displayed properly
Corrected: Routine to process Pendient Log QSO Requests: often one or some QSO were lost during the process of the queue of Pending Log QSO requests. Now the routine has been improved and it checks if the QSO has been really saved before deleting it from the queue. In case it's not saved the routine will process next queued QSO leaving this pending QSO in the queue to be processed later.
Corrected: DEE info table: DME where not imported properly resulting with no leading zero in DME. Example: instead of 01001 was imported as 1001.
Optimized: Transceiver control for TCI and Flex Radio: reduced traffic drastically improving overall performance
Corrected: Logbook view: Manual tab: when selecting a MyQTH the following error message appears: Parameter L_MyQTHID has no default value.
Corrected: Import ADIF QSO: selecting option "QSL action based on QSL Received/sent" fields didn't work and a blank QSL Action was set despite user assigned a value in the QSL-Action field.
Corrected: QSO entry: QTH Locator was not set when reading from Callbook databases under very rare scenarios.
Improved: Transceiver control: improved performance and stability reducing port traffic and internal messages.
Corrected: Band Maps: solved reported filtering issues. If user checked all modes, not all were checked after restarting Swisslog.
Corrected: Query LLOTA Activators option: this option could not be disabled unless user disable the Query POTA Activators option.

QTH locator NOT copied from callbook (QRZ.com)

Tue, 06 Oct 2026 06:01:35 +0000

I am using v. 5.118 BETA. In a few instances the locator is not copied from the callbook (QRZ) view. Pushing the "Copy" or "Copy All" buttons have no effect.
It happens with some, not all calls. See enclosed screenshot (JH0CIX). I tested my own Norwegian call LA6VDA, and that works as it's supposed to do.

Tom

Edit qso-callbook view error.JPG (Size: 92,58 KB / Downloads: 4)

New Country Table

Sun, 04 Oct 2026 11:45:08 +0000

The Swisslog Country Database was updated 4 October 2026.

The following definitions were added:

KH6KI = W USA
E51A = E5N North Cook

DXCC Name Change: C2 Nauru is now Naoero (pronounced Now-ero). See various online confirmations including https://www.independent.co.uk/news/world...32999.html

Swisslog will soon prompt you to update.

Erik EI4KF / G0CGL / "The Magic Rat" (CB!)

JTTS

Wed, 30 Sep 2026 18:06:06 +0000

just made my first QSO in JTTS . It would be nice to have JTTS included in the mode list

73's
Martin
DK3UW

V5 error, entry window frequency change

Thu, 24 Sep 2026 17:20:53 +0000

Hi!

I would like to say thank you to the admin who accepted me to the forum.

I have a few questions about the Swisslog.

1. Every time I run Swisslog, an error shows up: Access violation at address 00B192B1 in module "SwissIV5.exe". Read of address 00000000. Actually the log also opens a WSJT-X.

2. In the entry window of the Swisslog I cannot change the band and mode on the radio, but the radio always changes the band and mode in the entry window. Is this normal?

3. It happens that QSO made in WSJT-X is not properly saved in the log, especially if I use the button Save in the entry window. In this case, in the log is always missing the reports (RST-S and RST-R). When I use the log window in the WSJT-X, there are no problems.

I use IC-7300Mk2 with Omnirig settings.

Any suggestion?

Thanks for all the answers!

73 DE Robi S58Y

QSO-Gruppen exportieren

Thu, 10 Sep 2026 16:54:28 +0000

Ich habe derzeit rund 120 K QSOs in Swisslog gespeichert und habe daraus rund 4 K QSOs als extrahiert, die ich als ADIF-Datei in das DARC DCL Logbuch eintragen möchte.
Meine Fragen:
A) Wie kann ich die extrahierten QSOs sehen? Wenn ich auf den Gruppennamen klicke, erscheinen keinerlei QSO-Einträge
B) Wo wird die ADIF-Datei unter SWISSLOG gespeichert, damit ich sie exportieren kann?

Vielen Dank für jede Hilfe!

vy 73 de Rudolf, DJ3WE

ADIF to QSO group

Thu, 03 Sep 2026 17:11:59 +0000

Is it possible to import an SWL ADIF-file into a QSO group (i.e QSL_label) ? I have an ADIF- file with 200 QSOs of my logbook which I need to import to a QSO group in order to add the QSL action (i.e. via buro). At the end the logbook view should show and tickmarked the QSL-action. Or is there any other alternative? i.e. how to add the QSL action to the ADIF-file? In this caase I could do the normal data import and overwrite the QSOs with the additional QSL-action. Any idea is highly appreciated! Thanks for your time!

New Country Table (WRTC special)

Fri, 28 Aug 2026 17:59:33 +0000

A new Country Database has been released 28 August 2026.

It has one new definition: MB has been added for G England. Swisslog will prompt to update soon.

This prefix was used at WRTC but did not have a DXCC assignment in Swisslog.

This leaves the issue of existing log entries for MB calls that you worked. These, unless you made a manual entry, will not have a DXCC allocated. Some Swisslog users made a large number of MB QSOs and to avoid a lot of manual editing of your logbook, please use a solution below.

Jordi has prepared a SQL script. Download it from www.swisslogforwindows.com/Download/Fix-MB-QSO.zip

Unzip it in the SCRIPTS folder. Open Swisslog and go to Tools>For Experts Only> Execute SQL script and pick your saved file. Swisslog will execute the script and the database will refresh.

Note: Jordi would like to remind everyone that Swisslog implements a very powerful and useful function to Set DXCC from Club Log in the Tools > Club Log menu. Not only will it fix these QSOs but will probably fix many other wrong allocations.

ICOM IC-7300MK2 Hex-Adress

Thu, 20 Aug 2026 16:12:52 +0000

Hello Jordi,

I have no Problems to run the Kenwood TS-990 and the ICOMs IC-705, IC-7300 and IC-9700 with Swisslog 5.118.
But with the ICOM IC-7300MK2 it is not possible to put in the right Hex-Adress B6.

See Picture below:

[attachment=634]

All the other HAM-Radio-Applications, like UCX-Log, WSJT-X, JTDX, etc. run very well with the IC-7300MK2.

Do you have a solution for this error?

Thanks in advance

New Country Table

Fri, 14 Aug 2026 11:22:34 +0000

The Swisslog Country Database was updated 14 August 2026.

Definition updates are as follows:

9M4GKS and 9M4LHD = 9M6 East Malaysia

GB2CG and G5RRR = GM Scotland

G0X = GW Wales

KK7RSM = KH8 American Samoa

KG5NSU = KP2 Virgin Is

K4A, WQ2N and K1PT are KP4 Puerto Rico

VI9POL = VK Australia

VK2LHW = VK9L Lord Howe Is

Swisslog will prompt to update soon.

73 de Erik EI4KF.

ERROR

Sat, 25 Jul 2026 18:40:01 +0000

BUENAS TARDES:
HE CONECTADO LA EMISORA KENWOOD TS-690S AL PROGRAMA SWISSLOG. EN PRINCIPIO TODO FUNCIONA CORRECTAMENTE. DE REPENTE UNAS VECES ANTES Y OTRAS MAS TARDE COMIENZA A PRESENTAR UN CUADRO DE DIALOGO DE ERROR: " ES UN VALOR ENTERO INCORRECTO" Y VA SALIENDO ESTE CUADRO DE DIALOGO UNA VEZ TRAS OTRA BLOQUEANDO CUALQUIER ACTIVIDADA EN EL PROGRAMA TENIENDO QUE ACUDIR AL ADMINISTRADOR DE TAREAS DE WINDOWS PARA PODER CERRAR EL PROGRAMA.
N
Captura de pantalla 2026-07-25 192548.png (Size: 260,05 KB / Downloads: 5)

Printing eQSLs with a Brother HL-L2375DW Laser printer

Sat, 25 Jul 2026 04:31:47 +0000

Hi,

So far, I have been printing my QSL cards on 10 × 15 cm card stock, which fits perfectly in my printer's lower paper tray.

Unfortunately, following our recent TM25TFR operation, I now have to deal with professionally printed standard 9 × 14 cm QSL cards.
With this size, I can only use the manual feed slot, one card at a time! (Brother HL-L2375DW Laser printer)
Does anyone have a Swisslog QSL printing form set up for 9 × 14 cm cards, and if so, what printer/page settings do you use?

add : I think I found one : QSL9x14 A4_EA5VK.rpt prints on my brother from the upper tray, without any mod
......but only prints a SINGLE qso......any idea to print more ...say 4 or 5 ...?
add : found how to group qso's, but only can display 3 the 10x15 format allows me 5 qso's....never mind.....

73 de Guy F6DKQ

What might be happening?

Fri, 24 Jul 2026 15:16:57 +0000

Hello Jordi

Please see video at https://youtu.be/7UjtpWRsfxk

This is not an email for help as its not a Swisslog error I believe. I do wonder though if you have any idea why it happens. Its on every station called / worked on JTDX. The callsign comes to the Entry of QSOs window and then switches in and out. Nothing actually goes wrong, the callsign is logged.

Flex Radio SmartSDR software, due to the company's regressive policy toward its customers that now mean a subscription is required to get latest new features, has come under competition. A superb alternative has emerged called AetherSDR. All software that works with SmartSDR also works with AetherSDR. One of its features is that I can open a second panorama and connect to a KIWI SDR. So I can have Slice 1 locally on 21074 for example and be using JTDX and I have Slice 2 connected to a KIWI and use WSJTx to receive either same band or other band.

Swisslog does not like this! My UDP link is only to JTDX (as far as I know) but somehow the WSJTx instance interferes. As soon as I close WSJTx or the second Slice, the problem stops. The UDP is solid and remains green.

It is not "end of the world" but I wonder if there might be a solution.

73 de Erik EI4KF

NEW version 5.118

Sun, 12 Jul 2026 19:49:49 +0000

Dear users,

I have just released version 5.118 implementing VERY IMPORTANT CORRECTIONS detected in version 5.117.

Please UPGRADE when asked and read the full list of corrections HERE.

IMPORTANT!! All users executing Swisslog as administrator will lose this setting after upgrade. Remember to set it again in the Swisslog icon to avoid undesired issues.

Best 73