Date   

LOTW ADIF Sync problem

Anthony Buscaglia
 

Hi All
I am a newbie to L32.
I transferred 200k+ Qs from my old logging program (home brew FileMaker 6)
I am working on reconciling my DXCC and Challenge data.
Two problems:
1. When I try to sync with LOTW ADI file I get this error:



2. When I manually update my DXCC challenge by band, the Challenge table is right but when I view the DXCC table it does not reflect the entries updated in the Challenge table.

I also noticed incidents when updating the credits by clicking on the table entries and going to the log and updating that in some cases the updates did not apply.

I realize I am at the bottom of the learning curve, so I appreciate any help!

Best 73
Tony
K2NV


Re: HFAUTO Program To Logger

Terry Glagowski / W1TR / AFA1DI
 

Bob,
Can you give me some more details about this UDP broadcast.
I am the author / developer of the HFAUTO software, and would like to make the HFAUTO interoperable with Logger32.
The HFAUTO software gets CAT information from UDP broadcasts...
Currently N1MM, DXLAB, and FLDIGI+ FLDIGI_UDP (an extension to FLDIGI that I developed) are supported.
Others have figured out how to use DDUTIL to accomplish this.
Since the logic for N1MM is different than DXLAB and FLDIGI, the UDP needs to have at least some difference from the N1MM UDP for me to process it.
Please give me details or reference to LOGGER32 DOCs.
Terry / W1TR


Re: QSO TIME

Vilhjalmur Sigurjonsson
 

DR Paul,
According to your question I do assume that you key in the call sign and then hit ENTER.
If you want to log anything other than the call and 599 this is not the proper way to go.
You can decide number of fields to be filled automatially in the proper manner, e.g. the band, frequency and mode and you can have several other fields automatically filled in, either with fixed text, from the callbook (CD or Telnet) or/and from previous entries in the log. It is all up to you and you will have to set up the entry form for your preferences.
Some fields require your keying in and will not be automatically populated.
What you must do is to hit the TAB key to jump from one field to another. You can even decide the Tab jump order as you like. When you have filled in all you need, then and only then you should hit the ENTER key to log the QSO.
73 Villi
TF3VS

-----Original Message-----
From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Paul F6EXV
Sent: sunnudagur, 5. janúar 2020 11:34
To: hamlogger@groups.io
Subject: Re: [hamlogger] QSO TIME

Hi
In other words, I need to log a QSO, then edit it and modify whatever I need/want to change ?
Can I edit all the fields BEFORE logging ?
Thanks + 73
Paul F6EXV

Le 05/01/2020 à 11:30, Bob a écrit :
Like this?



When you type <ENTER> this is what is entered into the Logbook. /ti
change/set the QSO Start time type CTRL+S. The help file is more than
400 pages, I recommend you read it. SeventyThree(s).

PS. To download the current Help File, Google GITHUB LOGGER32.

On January 5, 2020 at 5:17 AM Paul F6EXV < @F6EXV
<mailto:@F6EXV>> wrote:


Hi all
I am trying to see if it is possible to modify any field of the
logging windows BEFORE the QSO is actually logged ?
For example, how to I add an IOTA reference, how do I modify the
time, how do I add/modify a QSL manager, again, BEFORE the QSO is
actually logged.
If I have to log it first, and then edit the QSO to modify field(s),
it will have already be uploaded to ClubLog and/or LoTW. This is what
I do not want to happen.

Thanks for help
73
Paul F6EXV


Re: Poblem on Clublog

Bob
 

If you had imported 2000 QSOs with "Invalid Country", you would click SETUP | UPDATES | VALIDATE YOUR LOGBOOK DXCC COUNTRY CODES FROMCLUB LOG. And Club Log will make the necessary corrections for you. This feature is described in the Help File. SeventyThree(s).

On January 5, 2020 at 7:19 AM Paul F6EXV <@F6EXV> wrote:


France

I have manuall corrected the 13 calls that showed "inavlid country"
after import. I would noyt want to do that if I imported 2000 QSOs....
What did I do wrong ?

73
Paul F6EXV

Le 05/01/2020 à 13:14, Bob a écrit :
If you type F6EXV into Logbook Entry Window, What Country is Logger32
telling you?



Does the ADIF file from DXLog include The DXCC number somewhere?

Importing ADIF files into Logger32 gives you a number of options. One
option is to Flag QSOs with no DXCC as "Invalid for DXCC". How did you
set this option?

SeventyThree(s).
On January 5, 2020 at 6:45 AM Paul F6EXV < @F6EXV
<mailto:@F6EXV>> wrote:


Hi all
I am sending this email to the 3 forums, as I am very unsure which
program is "responsible" of the following.
I logged a few QSO in CW on DXLog (CW, DXpedition mode). I exported that
log to an adif file, and imported that file into Logger32. Logger32 then
automatically uploaded these QSO onto Clublog.
The upload went fine, BUT the country is indicated as "invalid".

Any idea which program is responsible, and how to solve that ?
Thanks + 73
Paul F6EXV



Re: Poblem on Clublog

Bob
 

It's all in the Help File. SeventyThree(s).

On January 5, 2020 at 7:34 AM Paul F6EXV <@F6EXV> wrote:


The ADIF file created by DXLog does not contain a DXCC field.
Yes, I had that option ticked.

I imagine the solution it to NOT tick that option, and L32 will
automatically fill in the DXCC field, so the upload to ClubLog will be
correct.

If this is correct, sorry for the bandwidth
73
Paul F6EXV

Le 05/01/2020 à 13:26, Bob a écrit :
You did no answer two more questions ...

a) Does the ADIF file from DX Log include a DXCC field for each QSO?
b) When you imported the ADIF file into Logger32 did you have the option to mark QSOs with no DXCC as "Invalid for DXCC"?

SeventyThree(s).

On January 5, 2020 at 7:19 AM Paul F6EXV <@F6EXV> wrote:


France

I have manuall corrected the 13 calls that showed "inavlid country"
after import. I would noyt want to do that if I imported 2000 QSOs....
What did I do wrong ?

73
Paul F6EXV

Le 05/01/2020 à 13:14, Bob a écrit :
If you type F6EXV into Logbook Entry Window, What Country is Logger32
telling you?



Does the ADIF file from DXLog include The DXCC number somewhere?

Importing ADIF files into Logger32 gives you a number of options. One
option is to Flag QSOs with no DXCC as "Invalid for DXCC". How did you
set this option?

SeventyThree(s).
On January 5, 2020 at 6:45 AM Paul F6EXV < @F6EXV
<mailto:@F6EXV>> wrote:


Hi all
I am sending this email to the 3 forums, as I am very unsure which
program is "responsible" of the following.
I logged a few QSO in CW on DXLog (CW, DXpedition mode). I exported that
log to an adif file, and imported that file into Logger32. Logger32 then
automatically uploaded these QSO onto Clublog.
The upload went fine, BUT the country is indicated as "invalid".

Any idea which program is responsible, and how to solve that ?
Thanks + 73
Paul F6EXV


.



Re: Poblem on Clublog

Paul F6EXV
 

The ADIF file created by DXLog does not contain a DXCC field.
Yes, I had that option ticked.

I imagine the solution it to NOT tick that option, and L32 will
automatically fill in the DXCC field, so the upload to ClubLog will be
correct.

If this is correct, sorry for the bandwidth
73
Paul F6EXV

Le 05/01/2020 à 13:26, Bob a écrit :
You did no answer two more questions ...

a) Does the ADIF file from DX Log include a DXCC field for each QSO?
b) When you imported the ADIF file into Logger32 did you have the option to mark QSOs with no DXCC as "Invalid for DXCC"?

SeventyThree(s).

On January 5, 2020 at 7:19 AM Paul F6EXV <@F6EXV> wrote:


France

I have manuall corrected the 13 calls that showed "inavlid country"
after import. I would noyt want to do that if I imported 2000 QSOs....
What did I do wrong ?

73
Paul F6EXV

Le 05/01/2020 à 13:14, Bob a écrit :
If you type F6EXV into Logbook Entry Window, What Country is Logger32
telling you?



Does the ADIF file from DXLog include The DXCC number somewhere?

Importing ADIF files into Logger32 gives you a number of options. One
option is to Flag QSOs with no DXCC as "Invalid for DXCC". How did you
set this option?

SeventyThree(s).
On January 5, 2020 at 6:45 AM Paul F6EXV < @F6EXV
<mailto:@F6EXV>> wrote:


Hi all
I am sending this email to the 3 forums, as I am very unsure which
program is "responsible" of the following.
I logged a few QSO in CW on DXLog (CW, DXpedition mode). I exported that
log to an adif file, and imported that file into Logger32. Logger32 then
automatically uploaded these QSO onto Clublog.
The upload went fine, BUT the country is indicated as "invalid".

Any idea which program is responsible, and how to solve that ?
Thanks + 73
Paul F6EXV


.


Re: Poblem on Clublog

Bob
 

You did no answer two more questions ...

a) Does the ADIF file from DX Log include a DXCC field for each QSO?
b) When you imported the ADIF file into Logger32 did you have the option to mark QSOs with no DXCC as "Invalid for DXCC"?

SeventyThree(s).

On January 5, 2020 at 7:19 AM Paul F6EXV <@F6EXV> wrote:


France

I have manuall corrected the 13 calls that showed "inavlid country"
after import. I would noyt want to do that if I imported 2000 QSOs....
What did I do wrong ?

73
Paul F6EXV

Le 05/01/2020 à 13:14, Bob a écrit :
If you type F6EXV into Logbook Entry Window, What Country is Logger32
telling you?



Does the ADIF file from DXLog include The DXCC number somewhere?

Importing ADIF files into Logger32 gives you a number of options. One
option is to Flag QSOs with no DXCC as "Invalid for DXCC". How did you
set this option?

SeventyThree(s).
On January 5, 2020 at 6:45 AM Paul F6EXV < @F6EXV
<mailto:@F6EXV>> wrote:


Hi all
I am sending this email to the 3 forums, as I am very unsure which
program is "responsible" of the following.
I logged a few QSO in CW on DXLog (CW, DXpedition mode). I exported that
log to an adif file, and imported that file into Logger32. Logger32 then
automatically uploaded these QSO onto Clublog.
The upload went fine, BUT the country is indicated as "invalid".

Any idea which program is responsible, and how to solve that ?
Thanks + 73
Paul F6EXV



Re: Poblem on Clublog

Paul F6EXV
 

France

I have manuall corrected the 13 calls that showed "inavlid country"
after import. I would noyt want to do that if I imported 2000 QSOs....
What did I do wrong ?

73
Paul F6EXV

Le 05/01/2020 à 13:14, Bob a écrit :
If you type F6EXV into Logbook Entry Window, What Country is Logger32
telling you?



Does the ADIF file from DXLog include The DXCC number somewhere?

Importing ADIF files into Logger32 gives you a number of options. One
option is to Flag QSOs with no DXCC as "Invalid for DXCC". How did you
set this option?

SeventyThree(s).
On January 5, 2020 at 6:45 AM Paul F6EXV < @F6EXV
<mailto:@F6EXV>> wrote:


Hi all
I am sending this email to the 3 forums, as I am very unsure which
program is "responsible" of the following.
I logged a few QSO in CW on DXLog (CW, DXpedition mode). I exported that
log to an adif file, and imported that file into Logger32. Logger32 then
automatically uploaded these QSO onto Clublog.
The upload went fine, BUT the country is indicated as "invalid".

Any idea which program is responsible, and how to solve that ?
Thanks + 73
Paul F6EXV


Re: Poblem on Clublog

Bob
 

If you type F6EXV into Logbook Entry Window, What Country is Logger32 telling you?



Does the ADIF file from DXLog include The DXCC number somewhere?

Importing ADIF files into Logger32 gives you a number of options. One option is to Flag QSOs with no DXCC as "Invalid for DXCC". How did you set this option?

SeventyThree(s).

On January 5, 2020 at 6:45 AM Paul F6EXV < f6exv@...> wrote:


Hi all
I am sending this email to the 3 forums, as I am very unsure which
program is "responsible" of the following.
I logged a few QSO in CW on DXLog (CW, DXpedition mode). I exported that
log to an adif file, and imported that file into Logger32. Logger32 then
automatically uploaded these QSO onto Clublog.
The upload went fine, BUT the country is indicated as "invalid".

Any idea which program is responsible, and how to solve that ?
Thanks + 73
Paul F6EXV


Re: Poblem on Clublog

Paul F6EXV
 

It says "Not accepted for DXCC".
This happened to all the QSO I imported (mostly JAs, but not only)

Le 05/01/2020 à 13:01, Bob a écrit :
Merde! If you look at the QSO in the Logbook Entry, What is the DXCC for the QSO? I suspect the problem is none of the three programs. It is probably the operator. SeventyThree(s).

On January 5, 2020 at 6:45 AM Paul F6EXV <@F6EXV> wrote:


Hi all
I am sending this email to the 3 forums, as I am very unsure which
program is "responsible" of the following.
I logged a few QSO in CW on DXLog (CW, DXpedition mode). I exported that
log to an adif file, and imported that file into Logger32. Logger32 then
automatically uploaded these QSO onto Clublog.
The upload went fine, BUT the country is indicated as "invalid".

Any idea which program is responsible, and how to solve that ?
Thanks + 73
Paul F6EXV



.


Re: Poblem on Clublog

Bob
 

Merde! If you look at the QSO in the Logbook Entry, What is the DXCC for the QSO? I suspect the problem is none of the three programs. It is probably the operator. SeventyThree(s).

On January 5, 2020 at 6:45 AM Paul F6EXV <@F6EXV> wrote:


Hi all
I am sending this email to the 3 forums, as I am very unsure which
program is "responsible" of the following.
I logged a few QSO in CW on DXLog (CW, DXpedition mode). I exported that
log to an adif file, and imported that file into Logger32. Logger32 then
automatically uploaded these QSO onto Clublog.
The upload went fine, BUT the country is indicated as "invalid".

Any idea which program is responsible, and how to solve that ?
Thanks + 73
Paul F6EXV



Re: QSO TIME

Charles
 

Paul,
         You can also set up the other user fields in the Log Entry Window and edit those during the Qso (or before the Qso has ended) which is very useful too.

73

Charles

Charles Wilmott (MØOXO)
60 Church Hill, 
Royston, Barnsley,
South Yorkshire, S71 4NG
England, 
United Kingdom

Tel ; (+44) 7900 500775


The information in this internet email is copyright of Charles Wilmott, confidential and is intended solely for the addressee(s). Any views expressed in this e-mail are those of Charles Wilmott only, except where the sender specifically states these to be his own views. Access, copying, dissemination to or re-use of information in it to or by anyone else is unauthorised.


On Sun, 5 Jan 2020, 11:56 Bob, <k4cy@...> wrote:
No, you can edit the Logbook Entry Window as much as you like BEFORE you add the QSO to the logbook. If your QTH is Marseilles, then I can change your name to AbdulRahman, or AbuBooBoo, or whatever they call themselves down there under the palm trees. I can even change the name to Paul before I log the QSO. SeventyThree(s).

> On January 5, 2020 at 6:34 AM Paul F6EXV <f6exv@...> wrote:
>
>
> Hi
> In other words, I need to log a QSO, then edit it and modify whatever I
> need/want to change ?
> Can I edit all the fields BEFORE logging ?
> Thanks + 73
> Paul F6EXV
>
> Le 05/01/2020 à 11:30, Bob a écrit :
> > Like this?
> >
> >
> >
> > When you type <ENTER> this is what is entered into the Logbook. /ti
> > change/set the QSO Start time type CTRL+S. The help file is more than
> > 400 pages, I recommend you read it. SeventyThree(s).
> >
> > PS. To download the current Help File, Google GITHUB LOGGER32.
> >
> >> On January 5, 2020 at 5:17 AM Paul F6EXV < f6exv@...
> >> <mailto:f6exv@...>> wrote:
> >>
> >>
> >> Hi all
> >> I am trying to see if it is possible to modify any field of the logging
> >> windows BEFORE the QSO is actually logged ?
> >> For example, how to I add an IOTA reference, how do I modify the time,
> >> how do I add/modify a QSL manager, again, BEFORE the QSO is actually
> >> logged.
> >> If I have to log it first, and then edit the QSO to modify field(s), it
> >> will have already be uploaded to ClubLog and/or LoTW. This is what I do
> >> not want to happen.
> >>
> >> Thanks for help
> >> 73
> >> Paul F6EXV
> >>
> >
>
>
>
>




Re: QSO TIME

Bob
 

No, you can edit the Logbook Entry Window as much as you like BEFORE you add the QSO to the logbook. If your QTH is Marseilles, then I can change your name to AbdulRahman, or AbuBooBoo, or whatever they call themselves down there under the palm trees. I can even change the name to Paul before I log the QSO. SeventyThree(s).

On January 5, 2020 at 6:34 AM Paul F6EXV <@F6EXV> wrote:


Hi
In other words, I need to log a QSO, then edit it and modify whatever I
need/want to change ?
Can I edit all the fields BEFORE logging ?
Thanks + 73
Paul F6EXV

Le 05/01/2020 à 11:30, Bob a écrit :
Like this?



When you type <ENTER> this is what is entered into the Logbook. /ti
change/set the QSO Start time type CTRL+S. The help file is more than
400 pages, I recommend you read it. SeventyThree(s).

PS. To download the current Help File, Google GITHUB LOGGER32.

On January 5, 2020 at 5:17 AM Paul F6EXV < @F6EXV
<mailto:@F6EXV>> wrote:


Hi all
I am trying to see if it is possible to modify any field of the logging
windows BEFORE the QSO is actually logged ?
For example, how to I add an IOTA reference, how do I modify the time,
how do I add/modify a QSL manager, again, BEFORE the QSO is actually
logged.
If I have to log it first, and then edit the QSO to modify field(s), it
will have already be uploaded to ClubLog and/or LoTW. This is what I do
not want to happen.

Thanks for help
73
Paul F6EXV



Re: QSO TIME

ja1nlx
 

Paul

Before logging QSO (I mean before you hit Enter-key) you can change everything

you see in Logbook entry window.

After logging QSO you can change everything you see in Logbook page window.

73

On 2020/01/05 20:34, Paul F6EXV wrote:
Hi
In other words, I need to log a QSO, then edit it and modify whatever I
need/want to change ?
Can I edit all the fields BEFORE logging ?
Thanks + 73
Paul F6EXV

Le 05/01/2020 à 11:30, Bob a écrit :
Like this?



When you type <ENTER> this is what is entered into the Logbook. /ti
change/set the QSO Start time type CTRL+S. The help file is more than
400 pages, I recommend you read it. SeventyThree(s).

PS. To download the current Help File, Google GITHUB LOGGER32.

On January 5, 2020 at 5:17 AM Paul F6EXV < @F6EXV
<mailto:@F6EXV>> wrote:


Hi all
I am trying to see if it is possible to modify any field of the logging
windows BEFORE the QSO is actually logged ?
For example, how to I add an IOTA reference, how do I modify the time,
how do I add/modify a QSL manager, again, BEFORE the QSO is actually
logged.
If I have to log it first, and then edit the QSO to modify field(s), it
will have already be uploaded to ClubLog and/or LoTW. This is what I do
not want to happen.

Thanks for help
73
Paul F6EXV
--
73 de aki
JA1NLX


Poblem on Clublog

Paul F6EXV
 

Hi all
I am sending this email to the 3 forums, as I am very unsure which
program is "responsible" of the following.
I logged a few QSO in CW on DXLog (CW, DXpedition mode). I exported that
log to an adif file, and imported that file into Logger32. Logger32 then
automatically uploaded these QSO onto Clublog.
The upload went fine, BUT the country is indicated as "invalid".

Any idea which program is responsible, and how to solve that ?
Thanks + 73
Paul F6EXV


Re: QSO TIME

Paul F6EXV
 

Hi
In other words, I need to log a QSO, then edit it and modify whatever I
need/want to change ?
Can I edit all the fields BEFORE logging ?
Thanks + 73
Paul F6EXV

Le 05/01/2020 à 11:30, Bob a écrit :
Like this?



When you type <ENTER> this is what is entered into the Logbook. /ti
change/set the QSO Start time type CTRL+S. The help file is more than
400 pages, I recommend you read it. SeventyThree(s).

PS. To download the current Help File, Google GITHUB LOGGER32.

On January 5, 2020 at 5:17 AM Paul F6EXV < @F6EXV
<mailto:@F6EXV>> wrote:


Hi all
I am trying to see if it is possible to modify any field of the logging
windows BEFORE the QSO is actually logged ?
For example, how to I add an IOTA reference, how do I modify the time,
how do I add/modify a QSL manager, again, BEFORE the QSO is actually
logged.
If I have to log it first, and then edit the QSO to modify field(s), it
will have already be uploaded to ClubLog and/or LoTW. This is what I do
not want to happen.

Thanks for help
73
Paul F6EXV


Re: Logger32 RadioInfo UDP Broadcasts

Bob
 

... and I don't have a radio with CAT control, but I simulated a VFO frequency change to 14001.234 kHz. This is broadcast:

<?xml version="1.0"?>
<RadioInfo>
<Freq>1400123.4</Freq>
</RadioInfo>

Simulated a frequency change to 14123 kHz. This is broadcast:

<?xml version="1.0"?>
<RadioInfo>
<Freq>1412300</Freq>
</RadioInfo>

SeventyThree(s)/



On January 5, 2020 at 5:48 AM Bob <k4cy@...> wrote:

... to setup/enable UDP Broadcast of frequency in Logger32, click SETUP | FREQUENCY and check the UDP Broadcast option. Period. That's it. No port setup, no nothing, just turn it on. SeventyThree(s).
On January 4, 2020 at 9:34 PM Bob <k4cy@...> wrote:

There's a section UDP Broadcast of DX Spots in the Logger32 Help file. SeventyThree(s).
On January 4, 2020 at 9:18 PM Terry Glagowski / W1TR / AFA1DI <W1TR@...> wrote:

Does anyone have info about UDP broadcasts from Logger32 to other APPs?

Just a topic name or location in the documentation would help.

 

Terry G. Glagowski / W1TR
HAM: W1TR / USAF MARS: AFA1DI / GRID: FN31vw / ELEV: 950 MSL / 41.924750 N, 72.190320 W.


25 Hnath Road, Ashford, CT 06278 .
(860) 429-9444 (Landline) .
(860) 617-1969 (Cell) .

(EMail) W1TR@... .
(Web)  http://www.Glagowski.org/Radio .

 


 

 

 


Re: Logger32 RadioInfo UDP Broadcasts

Bob
 

... to setup/enable UDP Broadcast of frequency in Logger32, click SETUP | FREQUENCY and check the UDP Broadcast option. Period. That's it. No port setup, no nothing, just turn it on. SeventyThree(s).

On January 4, 2020 at 9:34 PM Bob <k4cy@...> wrote:

There's a section UDP Broadcast of DX Spots in the Logger32 Help file. SeventyThree(s).
On January 4, 2020 at 9:18 PM Terry Glagowski / W1TR / AFA1DI <W1TR@...> wrote:

Does anyone have info about UDP broadcasts from Logger32 to other APPs?

Just a topic name or location in the documentation would help.

 

Terry G. Glagowski / W1TR
HAM: W1TR / USAF MARS: AFA1DI / GRID: FN31vw / ELEV: 950 MSL / 41.924750 N, 72.190320 W.


25 Hnath Road, Ashford, CT 06278 .
(860) 429-9444 (Landline) .
(860) 617-1969 (Cell) .

(EMail) W1TR@... .
(Web)  http://www.Glagowski.org/Radio .

 


 

 


Re: QSO TIME

Bob
 

Like this?



When you type <ENTER> this is what is entered into the Logbook. /ti change/set the QSO Start time type CTRL+S. The help file is more than 400 pages, I recommend you read it. SeventyThree(s).

PS. To download the current Help File, Google GITHUB LOGGER32.

On January 5, 2020 at 5:17 AM Paul F6EXV < f6exv@...> wrote:


Hi all
I am trying to see if it is possible to modify any field of the logging
windows BEFORE the QSO is actually logged ?
For example, how to I add an IOTA reference, how do I modify the time,
how do I add/modify a QSL manager, again, BEFORE the QSO is actually logged.
If I have to log it first, and then edit the QSO to modify field(s), it
will have already be uploaded to ClubLog and/or LoTW. This is what I do
not want to happen.

Thanks for help
73
Paul F6EXV


QSO TIME

Paul F6EXV
 

Hi all
I am trying to see if it is possible to modify any field of the logging
windows BEFORE the QSO is actually logged ?
For example, how to I add an IOTA reference, how do I modify the time,
how do I add/modify a QSL manager, again, BEFORE the QSO is actually logged.
If I have to log it first, and then edit the QSO to modify field(s), it
will have already be uploaded to ClubLog and/or LoTW. This is what I do
not want to happen.

Thanks for help
73
Paul F6EXV