kd0zv wrote: ↑

22 Feb 2020, 18:52

That is interesting.

So in the other thread where I was talking about having to check USB, LSB and SSB in filtering to get all phone contacts must be causing issues here as well.

Rich

It is the same problem

Please email me an ADIF file of the QSO

User guide updated and ready for download by users

Integration of latest JTDX checked and found to work 100%

I am using V2 but want to keep another copy of my log in DXlabs DXkeeper. When exporting a single qso from V2 to DXkeeper I get an error message "imported frequency 0 doesn't match imported band 17M". The QSO is then imported showing just 17M but no frequency. Have a missed a setting somewhere? Jim...

Did you...……

1. Complete the Settings/Program Configuration/info providers tab
2. Complete the Settings/Program Configuration/Configuration tab
3. Restart the program

Hello In such a configuration as in the pictures, everything works without any problems so far. QSO login and clearing the callsign window after logging in. https://obrazki.elektroda.pl/9951350500_1582363130_thumb.jpg https://obrazki.elektroda.pl/5766201900_1582363213_thumb.jpg https://obrazki.elek...

kd0zv wrote: ↑

21 Feb 2020, 18:08

THANK YOU Terry.

I have also thought that CTY was just short for country file. My mistake.

I now see that falls under external databases and country file falls under data that Log4OM provides.

See https://www.country-files.com/

Terry, That is interesting. Here is my setup 2020-02-21_11-46-28.gif If I use Mikes VP8PJ as an example it shows up as Falkland Islands in the Country File. But if you look them up on QRZ.com they show up as South Orkney. So just trying to under how the logic works. Why would it choose the 3rd choi...

Cluster checks prefix against country file but inserting call in input field does a deep search of all lookup facilities including QRZ, Clublog etc so it gets a better match.

Means you dont have the COUNTRY confirmed ELECTRONICALLY (EQSL or LOTW) on that BAND