Date   
Re: All KG4 calls assigned to Guantanamo on import

Joe Subich, W4TV
 

I don't know that I would call it a defect in N1MM+ since ADIF does
not require a specific minimum complement of tags. However, failing
to export something as basic as "country" or exporting enumerated data
(country, zone, etc.) using application specific (e.g., APP_N1MM_)
tags is sloppy programming.

73,

... Joe, W4TV

On 2020-01-19 5:32 PM, Gilbert Baron W0MN wrote:
So the defect is actually in N1MM then ?
Outlook Laptop Gil W0MN
Hierro candente, batir de repente
44.08226N 92.51265W EN34rb
-----Original Message-----
From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Joe Subich, W4TV
Sent: Sunday, January 19, 2020 16:07
To: DXLab@groups.io
Subject: Re: [DXLab] All KG4 calls assigned to Guantanamo on import
On 2020-01-19 3:01 PM, Tom LeClerc wrote:
I had 4 KG4xxx calls and all were K in N1MM and imported as
Guantanamo.
Unfortunately, N1MM+ does not export the ADIF number (DXCC entity Code), e.g., KG4 = <COUNTRY:3> 105, K = <COUNTRY:3> 291, etc. even though N1MM+ knows the correct information internally.
73,
... Joe, W4TV

Re: Private: Re: [DXLab] monitor 60M for new DXCC

Joe Subich, W4TV
 

On 2020-01-19 6:14 PM, N2TK, Tony via Groups.Io wrote:
To get through my thick head, please clarify a point for me - Is
there any frequency I can operate FT8 on 60M? If I am on 5.357 in
data mode with my K3, do I have to operate exactly on 5.358.5? Or am
I reading this wrong and I should not operate FT8 on 60M?
To follow the rules as *written*, if you are operating on the channel
with a center frequency of 5358.5 KHz, you must operate on a carrier
frequency of 5337.0 KHz with an audio offset of 1500 Hz. In other
words, the FT8 (or FT4, or JT65, or JT9) "base" tone must be on
exactly 5358.5 KHz.

Admittedly, the FCC's own procedure will not result in transmitted
FT4, FT8, JT9 and/or JT65 signals being *exactly centered* in the
2.7 KHz "channel" since the 1500 Hz "offset" represents the lowest
tone and additional tones move up in frequency by the keying rate.
This means FT4 (4 tones spaced 20.833 Hz) is 1500 - 1583.3 Hz, FT8
(8 tones spaced 6.25 Hz) is 1500-1550 Hz, JT9A (4 tones spaced 1.736
Hz) is 1500 - 1515.6 Hz and JT65A (65 tones spaced 2.692 Hz) is
1500-1677.6 Hz. The asymmetry is small but is it certainly not
equivalent to multiple stations operating with audio offsets from
200 - 2700 Hz.

73,

... Joe, W4TV


On 2020-01-19 6:14 PM, N2TK, Tony via Groups.Io wrote:
To get through my thick head, please clarify a point for me - Is there any frequency I can operate FT8 on 60M? If I am on 5.357 in data mode with my K3, do I have to operate exactly on 5.358.5? Or am I reading this wrong and I should not operate FT8 on 60M?
There are sure lots of US stations on FT8 on 60M. Are we all wrong and should not be on 60M with FT8?
N2TK, Tony
-----Original Message-----
From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Joe Subich, W4TV
Sent: Thursday, January 16, 2020 6:03 PM
To: DXLab@groups.io
Subject: Re: Private: Re: [DXLab] monitor 60M for new DXCC
On 2020-01-16 3:50 PM, ve3ki wrote:
> Why not just quote the FCC rules?

> Part 97.303(h),

(h) 60 m band: (1) In the 5330.5-5406.4 kHz band (60 m band), amateur
stations may transmit only on the five center frequencies specified in
the table below. In order to meet this requirement, control operators
of stations transmitting phone, data, and RTTY emissions (emission
designators 2K80J3E, 2K80J2D, and 60H0J2B, respectively) may set the
carrier frequency 1.5 kHz below the center frequency as specified in
the table below. For CW emissions (emission designator 150HA1A), the
carrier frequency is set to the center frequency.
Amateur operators shall ensure that their emissions do not occupy more
than 2.8 kHz centered on each of these center frequencies.
>
60 M Band Frequencies (kHz)
Carrier Center
5330.5 5332.0
5346.5 5348.0
5357.0 5358.5
5371.5 5373.0
5403.5 5405.0
> Part 97.303(h)(2),

(2) Amateur stations transmitting on the 60 m band must not cause
harmful interference to, and must accept interference from, stations
authorized by:

(i) The United States (NTIA and FCC) and other nations in the fixed
service; and

(ii) Other nations in the mobile except aeronautical mobile service.
> part 97.221(c)

(c) Except for channels specified in §97.303(h), a station may be
automatically controlled while transmitting a RTTY or data emission on
any other frequency authorized for such emission types provided
that:
Again, ARRL have *on multiple occasions* reported communications from FCC Enforcement staff (and NTIA who are responsible for the "60 M
band") reminding US licensed amateurs that 97.303(h) requires using
*identical* audio frequency and carrier offsets so that the transmitted signal is centered exactly on the middle of the assigned "Channel" - not generating a random offset within a 2.7 KHz "band".
73,
... Joe, W4TV
On 2020-01-16 3:50 PM, ve3ki wrote:
Why not just quote the FCC rules?

Part 97.303(h), first sentence, and part 97.221(c), first sentence.

73,
Rich VE3KI

On Thu, Jan 16, 2020 at 02:51 PM, Joe Subich, W4TV wrote:



Is this word for word from a rule or interpretive guideline (please
cite the reference), or your interpretation of something else? >
<Begin quote>:
The use of any of the 60 meter "channels" as a 3 KHz wide CW/digital
band or for ACDS (automatically controlled digital operations) is
*ILLEGAL* for *ANY* amateur station licensed by the United States.
<End quote>
The statement was my paraphrase of what ARRL have posted both on-line
at ARRL.org and printed in QST on multiple occasions. If you have a
disagreement, take it up with them.


Suffice it to say, while I personally follow the 1500 Hz approach,
and as a very active 60m FT8 operator with hundreds of qsos, 99% of
the USA stations I work are not transmitting on 1500 Hz exclusively,
nor am I aware of any enforcement actions taken against them.
I expect to see active enforcement of this rule (among others) as the
new Amateur Auxiliary (replacement for the old Official Observer
program but with designated enforcement authority from the FCC and
headed by Rudy Hollingsworth) gets up and running.

73,

... Joe, W4TV

Re: Spot Collector No Sun Spot date appearing

wb6bee
 

I know my skimmer doesn't.   Don't know about the other one,   What can I use to get the information Dave

Don

Re: Private: Re: [DXLab] monitor 60M for new DXCC

N2TK, Tony
 

To get through my thick head, please clarify a point for me - Is there any frequency I can operate FT8 on 60M? If I am on 5.357 in data mode with my K3, do I have to operate exactly on 5.358.5? Or am I reading this wrong and I should not operate FT8 on 60M?
There are sure lots of US stations on FT8 on 60M. Are we all wrong and should not be on 60M with FT8?
N2TK, Tony

-----Original Message-----
From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Joe Subich, W4TV
Sent: Thursday, January 16, 2020 6:03 PM
To: DXLab@groups.io
Subject: Re: Private: Re: [DXLab] monitor 60M for new DXCC



On 2020-01-16 3:50 PM, ve3ki wrote:
> Why not just quote the FCC rules?

> Part 97.303(h),

(h) 60 m band: (1) In the 5330.5-5406.4 kHz band (60 m band), amateur
stations may transmit only on the five center frequencies specified in
the table below. In order to meet this requirement, control operators
of stations transmitting phone, data, and RTTY emissions (emission
designators 2K80J3E, 2K80J2D, and 60H0J2B, respectively) may set the
carrier frequency 1.5 kHz below the center frequency as specified in
the table below. For CW emissions (emission designator 150HA1A), the
carrier frequency is set to the center frequency.
Amateur operators shall ensure that their emissions do not occupy more
than 2.8 kHz centered on each of these center frequencies.
>
60 M Band Frequencies (kHz)
Carrier Center
5330.5 5332.0
5346.5 5348.0
5357.0 5358.5
5371.5 5373.0
5403.5 5405.0
> Part 97.303(h)(2),

(2) Amateur stations transmitting on the 60 m band must not cause
harmful interference to, and must accept interference from, stations
authorized by:

(i) The United States (NTIA and FCC) and other nations in the fixed
service; and

(ii) Other nations in the mobile except aeronautical mobile service.
> part 97.221(c)

(c) Except for channels specified in §97.303(h), a station may be
automatically controlled while transmitting a RTTY or data emission on
any other frequency authorized for such emission types provided
that:
Again, ARRL have *on multiple occasions* reported communications from FCC Enforcement staff (and NTIA who are responsible for the "60 M
band") reminding US licensed amateurs that 97.303(h) requires using
*identical* audio frequency and carrier offsets so that the transmitted signal is centered exactly on the middle of the assigned "Channel" - not generating a random offset within a 2.7 KHz "band".

73,

... Joe, W4TV


On 2020-01-16 3:50 PM, ve3ki wrote:
Why not just quote the FCC rules?

Part 97.303(h), first sentence, and part 97.221(c), first sentence.

73,
Rich VE3KI

On Thu, Jan 16, 2020 at 02:51 PM, Joe Subich, W4TV wrote:



Is this word for word from a rule or interpretive guideline (please
cite the reference), or your interpretation of something else? >
<Begin quote>:
The use of any of the 60 meter "channels" as a 3 KHz wide CW/digital
band or for ACDS (automatically controlled digital operations) is
*ILLEGAL* for *ANY* amateur station licensed by the United States.
<End quote>
The statement was my paraphrase of what ARRL have posted both on-line
at ARRL.org and printed in QST on multiple occasions. If you have a
disagreement, take it up with them.


Suffice it to say, while I personally follow the 1500 Hz approach,
and as a very active 60m FT8 operator with hundreds of qsos, 99% of
the USA stations I work are not transmitting on 1500 Hz exclusively,
nor am I aware of any enforcement actions taken against them.
I expect to see active enforcement of this rule (among others) as the
new Amateur Auxiliary (replacement for the old Official Observer
program but with designated enforcement authority from the FCC and
headed by Rudy Hollingsworth) gets up and running.

73,

... Joe, W4TV

Re: All KG4 calls assigned to Guantanamo on import

Gilbert Baron W0MN
 

So the defect is actually in N1MM then ?

Outlook Laptop Gil W0MN
Hierro candente, batir de repente
44.08226N 92.51265W EN34rb

-----Original Message-----
From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Joe Subich, W4TV
Sent: Sunday, January 19, 2020 16:07
To: DXLab@groups.io
Subject: Re: [DXLab] All KG4 calls assigned to Guantanamo on import

On 2020-01-19 3:01 PM, Tom LeClerc wrote:
I had 4 KG4xxx calls and all were K in N1MM and imported as
Guantanamo.
Unfortunately, N1MM+ does not export the ADIF number (DXCC entity Code), e.g., KG4 = <COUNTRY:3> 105, K = <COUNTRY:3> 291, etc. even though N1MM+ knows the correct information internally.

73,

... Joe, W4TV


On 2020-01-19 3:01 PM, Tom LeClerc wrote:
I had 4 KG4xxx calls and all were K in N1MM and imported as Guantanamo.
Good thing Clublog sent me an email response saying it had them as US.

On Sun, Jan 19, 2020 at 2:31 PM Jim McPhee <jmcphee@...> wrote:

[Edited Message Follows]
That happened to me as well when I imported the N1MM+ ADIF file from
the NAQP-SSB. I only had one:

KG4IGC
Summerville, SC 29483

but it was assigned to Guantanamo Bay.

--
Jim McPhee
Placitas, NM
W5ABA







--
W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente

HP Laptop

Re: DX Keeper question

Ron KU7Y
 

Thanks Dave,

That was what I needed. It looks like I need to have DXV running with
DXKeeper for that to work but I can live with that!

My biggest problem is that I can almost never seem to find what I'm looking
for in the help wiki!

Thanks again,

OK, back in my hole,

Ron, KU7Y
Mountain Home, ID DN23dc
CW Ops #1211
SKCC #4904
QRP ARCI #8829
SOC #2
Idaho DX Association
Ron@...

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Dave AA6YQ
Sent: Sunday, January 19, 2020 2:42 PM
To: DXLab@groups.io
Subject: Re: [DXLab] DX Keeper question

+ AA6YQ comments below

I have a file I use in Spot Collector to show me the Clubs a station is
a member of. I would like to show these memberships in DX
Keeper. The files are in the following format:

CALL,CLUB-Number (Example - VE5SDH,BUG-001

Is there any way this file could be used with DX Keeper to show the
Club-Number?

+ Yes: the Configuration section in

<https://www.dxlabsuite.com/dxlabwiki/IdentifyLogClubMembers>

+ explains how to append the club number to the QSO's Comment item.

73,

Dave, AA6YQ





--
This email has been checked for viruses by AVG.
https://www.avg.com

Re: All KG4 calls assigned to Guantanamo on import

Joe Subich, W4TV
 

On 2020-01-19 3:01 PM, Tom LeClerc wrote:
I had 4 KG4xxx calls and all were K in N1MM and imported as
Guantanamo.
Unfortunately, N1MM+ does not export the ADIF number (DXCC
entity Code), e.g., KG4 = <COUNTRY:3> 105, K = <COUNTRY:3>
291, etc. even though N1MM+ knows the correct information
internally.

73,

... Joe, W4TV


On 2020-01-19 3:01 PM, Tom LeClerc wrote:
I had 4 KG4xxx calls and all were K in N1MM and imported as Guantanamo.
Good thing Clublog sent me an email response saying it had them as US.
On Sun, Jan 19, 2020 at 2:31 PM Jim McPhee <jmcphee@...> wrote:

[Edited Message Follows]
That happened to me as well when I imported the N1MM+ ADIF file from the
NAQP-SSB. I only had one:

KG4IGC
Summerville, SC 29483

but it was assigned to Guantanamo Bay.

--
Jim McPhee
Placitas, NM
W5ABA


Re: Best Spot Sources for use

ghassan chammas
 

Hny to you all

Hi dave

I only have 4 clusters only  in green ie connected from the default clusters within sc.
What clusters do you suggest we use in this part of the world?

Regards
Ghassan
Od5ya



Sent from Samsung tablet.


-------- Original message --------
From: Dave AA6YQ <aa6yq@...>
Date: 16/01/2020 00:55 (GMT+02:00)
To: DXLab@groups.io
Subject: Re: [DXLab] Best Spot Sources for use

+ AA6YQ comments below

I am in MN

Many spot sources I had been using in SC just do not connect. They time out.

IRC does work.


On FT8 I usually use only WSJTX as I am looking for states and if WSJTX does not see them well not going to either with CQ only..

Looking for recommended sources when on HF, SSB or CW THAT ARE RELIABLE, AND FIT FOR THIS Ara.

+ In addition to DX Summit (via IRC) and WSJT-X, I suggest a nearby cluster, a cluster on the North American west coast, a cluster
in Japan, and a cluster in Europe.

+ I'm using N6WS, JH1RFM, and EI7MRE, all of which have been reliable. I also use K1TTT, but you should choose a cluster closer to
your station.

         73,

                 Dave, AA6YQ




Re: DXKeeper Recorded Wrong Freq for FT8 Split Operation

Dave AA6YQ
 

+ AA6YQ comments below

This morning I worked several JA stations on 160m FT8. I was working split, transmitting on 1840 and listening on 1908. I was using JTAlert to send the QSO information to DXkeeper.

When I look at DXKeeper, I see that my TX and RX Frequnecies have been logged as 1.909. This is OK for my RX Freq but my actual TX Freq was 1840.

I had Commander running but I think think the FT8 logging info comes via JTAlert

+ DXKeeper logs the information contained in the ADIF record it receives from JTAlert, which specifies the QSO frequency or frequencies; DXKeeper does not consult Commander to obtain your transceiver frequencies, as those are not the QSO frequencies when operating FT8.

73,

Dave, AA6YQ

Re: DX Keeper question

Dave AA6YQ
 

+ AA6YQ comments below

I have a file I use in Spot Collector to show me the Clubs a station is a member of. I would like to show these memberships in DX
Keeper. The files are in the following format:

CALL,CLUB-Number (Example - VE5SDH,BUG-001

Is there any way this file could be used with DX Keeper to show the Club-Number?

+ Yes: the Configuration section in

<https://www.dxlabsuite.com/dxlabwiki/IdentifyLogClubMembers>

+ explains how to append the club number to the QSO's Comment item.

73,

Dave, AA6YQ

Re: All KG4 calls assigned to Guantanamo on import

Dave AA6YQ
 

+ AA6YQ comments below

Here is one from yesterday's NAQP.

<CALL:6>KG4IGC <QSO_DATE:8>20200119 <TIME_ON:6>035916 <TIME_OFF:6>035916 <STATE:2>SC <BAND:3>80M <STATION_CALLSIGN:4>ND9G <FREQ:7>3.71469 <CONTEST_ID:8>NAQP-SSB <FREQ_RX:7>3.71469 <MODE:3>SSB <NAME:5>FRANK <RST_RCVD:2>59 <RST_SENT:2>59 <TX_PWR:3>100 <OPERATOR:4>ND9G <CQZ:1>5 <STX:3>476 <APP_N1MM_POINTS:1>1 <APP_N1MM_RADIO_NR:1>1 <APP_N1MM_CONTINENT:2>NA <APP_N1MM_RUN1RUN2:1>1 <APP_N1MM_RADIOINTERFACED:1>1 <APP_N1MM_ISORIGINAL:4>True <APP_N1MM_NETBIOSNAME:15>DESKTOP-V25NV5K <APP_N1MM_ISRUNQSO:1>0 <EOR>

+ That's the result of a defect inadvertently introduced in DXKeeper 14.8.3, which was released on 2019-01-24. The defect is triggered by importing an ADIF record that specifies a KG4 callsign but does not specify a DXCC entity.

+ I have corrected this defect in the next version of DXKeeper, but that next version of DXKeeper includes the ability to replace PSK with another digital mode family for realtime DXCC award tracking. See

<https://www.dxlabsuite.com/dxlabwiki/DXCCUserSelectedDigitalMode>

+ Versions of DXKeeper, DXView and SpotCollector that support this new capability are being tested as we speak, but more testing is required before making public releases.

+ To correct KG4 callsigns imported from N1MM with incorrect DXCC entities,


1. backup your log


2. filter your Log Page Display with the expression

<(len(call)<>5) and (mid$(call,1,3)='KG4') and (QSO_Begin > #2019-01-24#)


3. review the QSOs shown in the Log Page Display to confirm that each is actually in the continental United States.


4. in the "Advanced Sorts, Filters, and Modifiers" window's "Modify QSOs" panel,

4a. set the "Item name" selector to

DXCCPrefix

4b. set the "Item new value" selector to K

K

4c. click the Mod button


5. To correct each QSO's logged CQ zone and ITU zone, if you have DXKeeper configured to use a Callbook ("QRZ.com via Pathfinder" is free), depress the CTRL and ALT keys while clicking the CBA button above the Log Page Display. Otherwise, lookup each logged QSO's callsign in DXView to determine its CQ zone and ITU zone, and update the logged QSO accordingly.

73,

Dave, AA6YQ

DXKeeper Recorded Wrong Freq for FT8 Split Operation

Mark Robinson
 

This morning I worked several JA stations on 160m FT8.   I was working split, transmitting on 1840 and listening on 1908.   I was using JTAlert to send the QSO information to DXkeeper.

When I look at DXKeeper,  I see that my TX and RX Frequnecies have been logged  as 1.909.  This is OK for my RX Freq but my actual TX Freq was 1840.

I had Commander running but I think think the FT8 logging info comes via JTAlert


73 Mark N1UK

Re: All KG4 calls assigned to Guantanamo on import

Gary K9GS
 

Same here. That's how I found out.



73,

Gary K9GS


-------- Original message --------
From: Tom LeClerc <w1tjl@...>
Date: 1/19/20 2:01 PM (GMT-06:00)
To: DXLab@groups.io
Subject: Re: [DXLab] All KG4 calls assigned to Guantanamo on import

I had 4 KG4xxx calls and all were K in N1MM and imported as Guantanamo.  Good thing Clublog sent me an email response saying it had them as US.

On Sun, Jan 19, 2020 at 2:31 PM Jim McPhee <jmcphee@...> wrote:

[Edited Message Follows]

That happened to me as well when I imported the N1MM+ ADIF file from the NAQP-SSB. I only had one:

KG4IGC 
Summerville, SC 29483

but it was assigned to Guantanamo Bay.

--
Jim McPhee
Placitas, NM
W5ABA



--
Tom LeClerc, Amateur Radio Station W1TJL
 (past calls WB1CBY, /VE8,XL8,CI8,VO2)

               LeClerc Consulting
              email: w1tjl@...
            PC/Network Consulting

Re: All KG4 calls assigned to Guantanamo on import

Tom LeClerc
 

I had 4 KG4xxx calls and all were K in N1MM and imported as Guantanamo.  Good thing Clublog sent me an email response saying it had them as US.


On Sun, Jan 19, 2020 at 2:31 PM Jim McPhee <jmcphee@...> wrote:

[Edited Message Follows]

That happened to me as well when I imported the N1MM+ ADIF file from the NAQP-SSB. I only had one:

KG4IGC 
Summerville, SC 29483

but it was assigned to Guantanamo Bay.

--
Jim McPhee
Placitas, NM
W5ABA



--
Tom LeClerc, Amateur Radio Station W1TJL
 (past calls WB1CBY, /VE8,XL8,CI8,VO2)

               LeClerc Consulting
              email: w1tjl@...
            PC/Network Consulting

Re: All KG4 calls assigned to Guantanamo on import

Jim McPhee
 
Edited

That happened to me as well when I imported the N1MM+ ADIF file from the NAQP-SSB. I only had one:

KG4IGC 
Summerville, SC 29483

but it was assigned to Guantanamo Bay.

--
Jim McPhee
Placitas, NM
W5ABA

Re: Spot Collector No Sun Spot date appearing

Dave AA6YQ
 

+ AA6YQ comments below

What am I missing. Two Telnet connections, one my own skimmer, one DJ1YFK

+ Do either of those convey WWV "spots"?

73,

Dave, AA6YQ

DX Keeper question

Ron KU7Y
 

Hi Dave,

I have a file I use in Spot Collector to show me the Clubs a station is a
member of. I would like to show these memberships in DX Keeper. The files
are in the following format:

CALL,CLUB-Number (Example - VE5SDH,BUG-001

Is there any way this file could be used with DX Keeper to show the
Club-Number?

Thanks,

OK, back in my hole,

Ron, KU7Y
Mountain Home, ID DN23dc
CW Ops #1211
SKCC #4904
QRP ARCI #8829
SOC #2
Idaho DX Association
Ron@...

Re: crashed HD

Richard Clare
 

Thanks for all the replies back. Dave, thanks for the advice. I will be doing all of the things you suggested to prevent this from happening again


On Sun, Jan 19, 2020, 8:50 AM Bart AA7VA <bartvanallen@...> wrote:
I had a major HD crash a couple months ago (and then the motherboard died on abt 10 year old I3 that ran very hot because I was pushing it too hard) - but I had backup on both a thumb drive and online (cloud storage).  DXlabs is setup to do the former, cloud software to backup the latter along with some other folders of importance, and also an occasional full disk backup.  When my hard drive fried, I lost some setup info, but reconstructed it with some troubles where DXlabs Wiki was immensely appreciated.  Had to reload almost everything with the new computer, and backups of data for various programs made life much easier to get running correctly.
If you do not have any log backups, you can go to various online logs you are using (eQSL, LotW, QRZ, etc), export as ADIF log and then import into DXlabs log, allowing for some loss of data.  I note that my various online logs do not have the same number of entries, so maybe importing a variety and dupe checking can help recover most of them.

Re: crashed HD

Bart AA7VA
 

I had a major HD crash a couple months ago (and then the motherboard died on abt 10 year old I3 that ran very hot because I was pushing it too hard) - but I had backup on both a thumb drive and online (cloud storage).  DXlabs is setup to do the former, cloud software to backup the latter along with some other folders of importance, and also an occasional full disk backup.  When my hard drive fried, I lost some setup info, but reconstructed it with some troubles where DXlabs Wiki was immensely appreciated.  Had to reload almost everything with the new computer, and backups of data for various programs made life much easier to get running correctly.
If you do not have any log backups, you can go to various online logs you are using (eQSL, LotW, QRZ, etc), export as ADIF log and then import into DXlabs log, allowing for some loss of data.  I note that my various online logs do not have the same number of entries, so maybe importing a variety and dupe checking can help recover most of them.

Re: All KG4 calls assigned to Guantanamo on import

ve3ki
 

This also happens with 2x1 call signs like KG4Q.

73,
Rich VE3KI


On Sun, Jan 19, 2020 at 10:57 AM, ND9G Mike wrote:
Here is one from yesterday's NAQP.
 

 <CALL:6>KG4IGC <QSO_DATE:8>20200119 <TIME_ON:6>035916 <TIME_OFF:6>035916 <STATE:2>SC <BAND:3>80M <STATION_CALLSIGN:4>ND9G <FREQ:7>3.71469 <CONTEST_ID:8>NAQP-SSB <FREQ_RX:7>3.71469 <MODE:3>SSB <NAME:5>FRANK <RST_RCVD:2>59 <RST_SENT:2>59 <TX_PWR:3>100 <OPERATOR:4>ND9G <CQZ:1>5 <STX:3>476 <APP_N1MM_POINTS:1>1 <APP_N1MM_RADIO_NR:1>1 <APP_N1MM_CONTINENT:2>NA <APP_N1MM_RUN1RUN2:1>1 <APP_N1MM_RADIOINTERFACED:1>1 <APP_N1MM_ISORIGINAL:4>True <APP_N1MM_NETBIOSNAME:15>DESKTOP-V25NV5K <APP_N1MM_ISRUNQSO:1>0 <EOR>
 
73,
Mike ND9G

On Sun, Jan 19, 2020 at 9:47 AM Joe Subich, W4TV <lists@...> wrote:

On 2020-01-19 9:52 AM, ND9G Mike wrote:
> When I import an ADIF file from my contest log, every station I work
> with a KG4 prefix is assigned to Guantanamo Bay, even when the call
> is a 2x3 call, which are US based calls.
Please provide an example of the ADIF entry (import file) for a call
that imports incorrectly.

73,

    ... Joe, W4TV


On 2020-01-19 9:52 AM, ND9G Mike wrote:
> When I import an ADIF file from my contest log, every station I work with a
> KG4 prefix is assigned to Guantanamo Bay, even when the call is a 2x3 call,
> which are US based calls.
>
> I notice when I enter any of these calls into the capture window, or direct
> logging of a new QSO, it correctly identifies them as United States, not
> Guantanamo Bay.
>
> Is there something I can do to have these identified correctly on import,
> so I don't have to go back and find them and fix them?
>
> 73,
> Mike ND9G
>