Swisslog's Forum

Full Version: QTH-Locator in CallBook wrong - hanging of SwissLog
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
I have running swisslog with WSJT-X.

Sometimes a QSO canĀ“t be stored. Reason is, that the CallSign has an incorrect QTH-Locator is stored (think in HamQTH), and Swisslog fill the field with those wrong information - just giving an error that those is wrong.
Sometimes it is enough to press the "OK" buttom - but sometimes directly the wrong information is set again.

In the FT8-Dialogue the CallSign is send with correct 4-digit locator information.
Example 2E0ERL

Could it be possible maybe with an option simple to ignore QTH-Locator information with syntax issues ?

73 Roland

Attached an example. But was also happened with a view other Callsign
Hello Roland,

You have really found a very strange case! It's obvious this colleague has set wrongly his QTH locator in his HAMQTH profile. I have never found myself a case like this and I guess you won't find a case like this often. However I have added a QTH locator check when reading from callbook databases and in case it's wrong, it won't be copied and no warning message will be released. I have uploaded a beta here implementing this correction:

www.swisslogforwindows.com/Beta/SwisslV5.exe

Simply download and replace this file in the Swisslog folder.

Best 73
Hi Jordi
thanks. Sorry, have seen this information yet.
Shall I try this version, or is it already included in version 5.100c which came out later on?

73 Roland, DK4RH
Hi Roland,

If you read the release notes you will see that this fix is included in 5.100c.

Best 73
Thanks. Can write was not happened after update to 5.100c.
Hi Roland,

Are you having any issues after updating to 5.100c?

Best 73
No, is running very well!
Thanks!

73 Roland, DK4RH