Date   
Re: DXCC Challenge summary changed incorrectly

Bob
 

Ken, thanks for the clues. I'll set up a test and see what I can find. QRX. 73.

On December 20, 2019 at 12:18 AM Ken JN7FAH <jn7fah@...> wrote:

Bob,

I studied this problem and found a reason more than probable.
DXCC challenge summary is not changed by importing ADIF files
produced by Logger32, but changed by importing ADIF files 
generated by JTDX or WSJT-X.
  
Almost every morning I import an ADIF file of new QSOs exported 
from Logger32 and sometime I also import wsjt_x_log.adif as well 
when I made new QSOs by JTDX or WSJT-X.
In the later situation, ADIF files includes old QSOs that were 
already imported. If the old QSOs counted as "Granted" in DXCC 
summary table, the DXCC status of these QSO will be changed to 
"Confirmed".

I further studied differences between ADIF file structures
exported from Logger32 and generated by JTDX or WSJT-X.

Finally, I concluded that the status "Granted" in DXCC summary
table of a QSO will be changed to "Confirmed" by importing ADIF
data of the same QSO without the ADIF data field of 
"APP_LOGGER32_CREDIT_GRANTED".  

If it is possible, I hope that the DXCC summary table won't be 
changed by luck of the ADIF data field of 
"APP_LOGGER32_CREDIT_GRANTED", even if dupe QSOs
are imported.

73 Ken JN7FAH

PS,
You can reproduce this phenomena as follow.
1) Export an ADIF file of a granted QSO.
2) Edit the ADIF file to eliminate  the ADIF data field of 
"APP_LOGGER32_CREDIT_GRANTED".
3) Import the ADIF file, then Logger32 alert that
1 QSOs read. 1 records could not be imported. 
4) In the DXCC challenge summary table, the status of the granted QSO 
is changed to "Confirmed".

2019年12月18日(水) 20:55 Ken JN7FAH via Groups.Io <jn7fah= gmail.com@groups.io>:
Bob,

Okey I will send you logbook backup and an ADIF file that cause trouble.
 
Ken JN7FAH

2019年12月18日(水) 20:11 Bob < k4cy@...>:
Ken, I have tested for several hours, and have not been able to duplicate this. Can you please create a sample logbook, and an ADIF file to import that I can use to test/simulate the problem. Thanks, 73.
On December 18, 2019 at 3:09 AM Ken JN7FAH < jn7fah@...> wrote:

Bob,

No, the ADIF file imported includes daily new QSOs only.

Anyway, 
The summary can be recovered by recalculation time to time.
Not matter for small database.
 
Ken

2019年12月18日(水) 16:41 Bob < k4cy@...>:
Ken, apologies for all the questions, but I am looking for clues as to what is the cause of this problem. Did the ADIF file you imported have another QSO with 3B8XF on 160M/FT8? 73.
On December 18, 2019 at 2:32 AM Ken JN7FAH < jn7fah@...> wrote:

Bob,

Yes, I always import new QSOs to logbook by importing an ADIF file.

Ken JN7FAH


2019年12月18日(水) 16:24 Bob < k4cy@...>:
Ken, clarification please. You said:  However, this summary changed when I import an ADIF file for new QSOs as show below ... Did you import new QSOs into your logbook by importing an ADIF file, or did you synchronize your logbook with an ADIF file from LoTW? 73.
On December 18, 2019 at 1:04 AM Ken JN7FAH < jn7fah@...> wrote:

Hello Folks,

I recently applied DXCC challenge endorsement of 62
band points to reach 2,700 through LoTW.
I changed Awards Status of granted QSOs as shown below
for example 3B8XF (160m FT8).
3B8XF.JPG
After all done, I recalculate statistics, then I see DXCC
challenge status achieved 2,700 as seen below.
2700.JPG
However, this summary changed when I import an ADIF file for new QSOs 
as show below.
2678.JPG
Total number of challenge points changes always to 2,678. 
In this window includes three newly granted points those are 3B8/160F,
3D2C/160C and 4O/160F.
I checked all those newly granted QSOs and found all those QSOs turning 
status Granted to Confirmed were granted for DXCC Digital and DXCC Mixed 
as shown in the first picture.
In the same time, other newly granted QSOs for DXCC CW/Phone and Mixed 
were not changed against ADIF importing.

What's wrong?
I appreciate your suggestions.
 
73
Ken JN7FAH

 

 

 


 

 

 


 

 

 

 

 


 

Re: Latest TQSL Update does not allow L32LogSynch to open

Jeff Wilson
 

Thanks Rick and Gary.  Switching back to Run as Admin fixed it up.  And thanks for all you do for the Logger32 devotees out there!
Now back to upgrading shack computer from Win 7 to 10 Pro and getting everything working again.
73
Jeff VE3CV

Re: DXCC Challenge summary changed incorrectly

Ken JN7FAH
 

Bob,

I studied this problem and found a reason more than probable.
DXCC challenge summary is not changed by importing ADIF files
produced by Logger32, but changed by importing ADIF files 
generated by JTDX or WSJT-X.
  
Almost every morning I import an ADIF file of new QSOs exported 
from Logger32 and sometime I also import wsjt_x_log.adif as well 
when I made new QSOs by JTDX or WSJT-X.
In the later situation, ADIF files includes old QSOs that were 
already imported. If the old QSOs counted as "Granted" in DXCC 
summary table, the DXCC status of these QSO will be changed to 
"Confirmed".

I further studied differences between ADIF file structures
exported from Logger32 and generated by JTDX or WSJT-X.

Finally, I concluded that the status "Granted" in DXCC summary
table of a QSO will be changed to "Confirmed" by importing ADIF
data of the same QSO without the ADIF data field of 
"APP_LOGGER32_CREDIT_GRANTED".  

If it is possible, I hope that the DXCC summary table won't be 
changed by luck of the ADIF data field of 
"APP_LOGGER32_CREDIT_GRANTED", even if dupe QSOs
are imported.

73 Ken JN7FAH

PS,
You can reproduce this phenomena as follow.
1) Export an ADIF file of a granted QSO.
2) Edit the ADIF file to eliminate the ADIF data field of 
"APP_LOGGER32_CREDIT_GRANTED".
3) Import the ADIF file, then Logger32 alert that
1 QSOs read. 1 records could not be imported. 
4) In the DXCC challenge summary table, the status of the granted QSO 
is changed to "Confirmed".

2019年12月18日(水) 20:55 Ken JN7FAH via Groups.Io <jn7fah=gmail.com@groups.io>:

Bob,

Okey I will send you logbook backup and an ADIF file that cause trouble.
 
Ken JN7FAH

2019年12月18日(水) 20:11 Bob <k4cy@...>:
Ken, I have tested for several hours, and have not been able to duplicate this. Can you please create a sample logbook, and an ADIF file to import that I can use to test/simulate the problem. Thanks, 73.
On December 18, 2019 at 3:09 AM Ken JN7FAH <jn7fah@...> wrote:

Bob,

No, the ADIF file imported includes daily new QSOs only.

Anyway, 
The summary can be recovered by recalculation time to time.
Not matter for small database.
 
Ken

2019年12月18日(水) 16:41 Bob < k4cy@...>:
Ken, apologies for all the questions, but I am looking for clues as to what is the cause of this problem. Did the ADIF file you imported have another QSO with 3B8XF on 160M/FT8? 73.
On December 18, 2019 at 2:32 AM Ken JN7FAH < jn7fah@...> wrote:

Bob,

Yes, I always import new QSOs to logbook by importing an ADIF file.

Ken JN7FAH


2019年12月18日(水) 16:24 Bob < k4cy@...>:
Ken, clarification please. You said:  However, this summary changed when I import an ADIF file for new QSOs as show below ... Did you import new QSOs into your logbook by importing an ADIF file, or did you synchronize your logbook with an ADIF file from LoTW? 73.
On December 18, 2019 at 1:04 AM Ken JN7FAH < jn7fah@...> wrote:

Hello Folks,

I recently applied DXCC challenge endorsement of 62
band points to reach 2,700 through LoTW.
I changed Awards Status of granted QSOs as shown below
for example 3B8XF (160m FT8).
3B8XF.JPG
After all done, I recalculate statistics, then I see DXCC
challenge status achieved 2,700 as seen below.
2700.JPG
However, this summary changed when I import an ADIF file for new QSOs 
as show below.
2678.JPG
Total number of challenge points changes always to 2,678. 
In this window includes three newly granted points those are 3B8/160F,
3D2C/160C and 4O/160F.
I checked all those newly granted QSOs and found all those QSOs turning 
status Granted to Confirmed were granted for DXCC Digital and DXCC Mixed 
as shown in the first picture.
In the same time, other newly granted QSOs for DXCC CW/Phone and Mixed 
were not changed against ADIF importing.

What's wrong?
I appreciate your suggestions.
 
73
Ken JN7FAH

 

 

 


 

 

 


 

Re: Packet Cluster

Chuck Kraly K0XM
 

Hi John,
I operate K0XM-5 and can help. Team viewer is a real pain anymore. UltraViewer (which drives the same is better and fully free). Email direct if you need my assistance k0xm@...
Chuck K0XM


On Thu, Dec 19, 2019 at 3:52 PM Dave Colliau <n8dc-8@...> wrote:
VE7CC CC user connected to a node and interfaced to logger 32 thru local port 7300 via telnet.
Dave N8DC
On December 19, 2019 at 4:46 PM JohnD <johnab9hh@...> wrote:

Its been several years since I used Logger32. I stopped because the packet cluster stopped working. Any tips for configuring? I do have Team Viewer if someone wants to take a look.

Big Thanks, 73
johnab9hh@...

 

Re: Packet Cluster

Bob
 

First, do you have the latest version of Logger32 installed and running - Version 3.50.403? 
73.

On December 19, 2019 at 4:46 PM JohnD <johnab9hh@...> wrote:

Its been several years since I used Logger32. I stopped because the packet cluster stopped working. Any tips for configuring? I do have Team Viewer if someone wants to take a look.

Big Thanks, 73
johnab9hh@...

 

Re: Packet Cluster

Dave Colliau
 

VE7CC CC user connected to a node and interfaced to logger 32 thru local port 7300 via telnet.
Dave N8DC

On December 19, 2019 at 4:46 PM JohnD <johnab9hh@...> wrote:

Its been several years since I used Logger32. I stopped because the packet cluster stopped working. Any tips for configuring? I do have Team Viewer if someone wants to take a look.

Big Thanks, 73
johnab9hh@...

 

Packet Cluster

JohnD
 

Its been several years since I used Logger32. I stopped because the packet cluster stopped working. Any tips for configuring? I do have Team Viewer if someone wants to take a look.

Big Thanks, 73
johnab9hh@...

Re: new feature

José L. Peña EA4AFP
 

OK Bob, thanks for the prompt response.

73 jose EA4AFP


El jue., 19 dic. 2019 a las 13:50, Bob (<k4cy@...>) escribió:
Jose, I have no interest in adding another UDP BandMap for 'called' stations. If you can hear the called station when he replies to a call he will show on the current UDP BandMap. If you can not hear him, he will appear on the DX Cluster BandMap when someone makes a DX Spot. Aren't there dedicated DX Clusters and tools for collecting FT8/FT4 type DX Spots? This will provide you with the same information you would get from a 'called' UDP BandMap. 73.
On December 19, 2019 at 4:13 AM "José L. Peña EA4AFP" <ea4afp@...> wrote:

Probably of interest only for 6 meters or local propagation conditions...

 

What?

A new “UDP band map” window showing the stations that are called (instead of the stations that are calling). To avoid unnecessary information, only stations that would be colored according to our preferences on the standard “UDP band map” should be shown.

 

Why?

On 6 meters and from EA, most of the time the antenna is beaming to USA/VE/Caribbean, OH/LA/JA or Middle East. Taking into account the lobe size, that covers 99,9% of the stations leaving out only Africa.

The latest season has have very good conditions to AF. But if the antenna is beaming the aforementioned directions, probably the UDP band map will show nothing and the only way to notice that there is a chance to work Africa, is the DX spot window showing a spot colored according to your preferences... if someone spots the DX, and when this happens it is late, lots of people calling.

 

Useful for 6 meters ops? Please comment, there is time enough before next Es season.

 

Thanks Bob & Team

 

Jose EA4AFP


 

Re: new feature

Bob
 

Jose, I have no interest in adding another UDP BandMap for 'called' stations. If you can hear the called station when he replies to a call he will show on the current UDP BandMap. If you can not hear him, he will appear on the DX Cluster BandMap when someone makes a DX Spot. Aren't there dedicated DX Clusters and tools for collecting FT8/FT4 type DX Spots? This will provide you with the same information you would get from a 'called' UDP BandMap. 73.

On December 19, 2019 at 4:13 AM "José L. Peña EA4AFP" <ea4afp@...> wrote:

Probably of interest only for 6 meters or local propagation conditions...

 

What?

A new “UDP band map” window showing the stations that are called (instead of the stations that are calling). To avoid unnecessary information, only stations that would be colored according to our preferences on the standard “UDP band map” should be shown.

 

Why?

On 6 meters and from EA, most of the time the antenna is beaming to USA/VE/Caribbean, OH/LA/JA or Middle East. Taking into account the lobe size, that covers 99,9% of the stations leaving out only Africa.

The latest season has have very good conditions to AF. But if the antenna is beaming the aforementioned directions, probably the UDP band map will show nothing and the only way to notice that there is a chance to work Africa, is the DX spot window showing a spot colored according to your preferences... if someone spots the DX, and when this happens it is late, lots of people calling.

 

Useful for 6 meters ops? Please comment, there is time enough before next Es season.

 

Thanks Bob & Team

 

Jose EA4AFP


 

Re: new feature

ja1nlx
 

Jose

Thanks  I understand.

I do not know whether Bob has interest on this or not....

73

On 2019/12/19 21:07, José L. Peña EA4AFP wrote:
Aki, all,

lets imagine WSJT is decoding this while I am beaming USA/VE:
XT2SE I0AFP JN53
then IZ0AFP appears in the "UDP bandmap" according to my settings. Nice and it works fine.
If I am not reviewing WSJT window, I am missing that there is an opening to AF. On 6 meters, if an Italian station can copy XT, probably I can.
If XT2SE answers, I will not copy her (I'm beaming another direction)  and I will not be aware of the opening if I do not review WSJT screen or someone spots XT2SE.

XT2SE I0AFP JN53
calling: I0AFP
called: XT2SE

Now UDP shows "calling sations", I0AFP in this example. My request is to generate a new "UDP bandmap-called" showing only "called stations", XT2SE in the example. Only stations that should be coloured according to my settings in the standard "UDP bandmap" should be displayed in the new "UDP bandmap-called".

Hope this clarifies, 73

Jose  EA4AFP



El jue., 19 dic. 2019 a las 12:08, ja1nlx (<ayoshida0205@...>) escribió:

Jose

UDP BandMap display all decoded (by jtdx/wsjtx) callsign except blocked callsign (you setup)

What you mean "calling" and "called" ?

73

On 2019/12/19 18:13, José L. Peña EA4AFP wrote:

Probably of interest only for 6 meters or local propagation conditions...

What?

A new “UDP band map” window showing the stations that are called (instead of the stations that are calling). To avoid unnecessary information, only stations that would be colored according to our preferences on the standard “UDP band map” should be shown.

Why?

On 6 meters and from EA, most of the time the antenna is beaming to USA/VE/Caribbean, OH/LA/JA or Middle East. Taking into account the lobe size, that covers 99,9% of the stations leaving out only Africa.

The latest season has have very good conditions to AF. But if the antenna is beaming the aforementioned directions, probably the UDP band map will show nothing and the only way to notice that there is a chance to work Africa, is the DX spot window showing a spot colored according to your preferences... if someone spots the DX, and when this happens it is late, lots of people calling.

Useful for 6 meters ops? Please comment, there is time enough before next Es season.

Thanks Bob & Team

Jose EA4AFP

--
73 de aki
JA1NLX
--
73 de aki
JA1NLX

Re: new feature

José L. Peña EA4AFP
 

Aki, all,

lets imagine WSJT is decoding this while I am beaming USA/VE:
XT2SE I0AFP JN53
then IZ0AFP appears in the "UDP bandmap" according to my settings. Nice and it works fine.
If I am not reviewing WSJT window, I am missing that there is an opening to AF. On 6 meters, if an Italian station can copy XT, probably I can.
If XT2SE answers, I will not copy her (I'm beaming another direction)  and I will not be aware of the opening if I do not review WSJT screen or someone spots XT2SE.

XT2SE I0AFP JN53
calling: I0AFP
called: XT2SE

Now UDP shows "calling sations", I0AFP in this example. My request is to generate a new "UDP bandmap-called" showing only "called stations", XT2SE in the example. Only stations that should be coloured according to my settings in the standard "UDP bandmap" should be displayed in the new "UDP bandmap-called".

Hope this clarifies, 73

Jose  EA4AFP



El jue., 19 dic. 2019 a las 12:08, ja1nlx (<ayoshida0205@...>) escribió:

Jose

UDP BandMap display all decoded (by jtdx/wsjtx) callsign except blocked callsign (you setup)

What you mean "calling" and "called" ?

73

On 2019/12/19 18:13, José L. Peña EA4AFP wrote:

Probably of interest only for 6 meters or local propagation conditions...

What?

A new “UDP band map” window showing the stations that are called (instead of the stations that are calling). To avoid unnecessary information, only stations that would be colored according to our preferences on the standard “UDP band map” should be shown.

Why?

On 6 meters and from EA, most of the time the antenna is beaming to USA/VE/Caribbean, OH/LA/JA or Middle East. Taking into account the lobe size, that covers 99,9% of the stations leaving out only Africa.

The latest season has have very good conditions to AF. But if the antenna is beaming the aforementioned directions, probably the UDP band map will show nothing and the only way to notice that there is a chance to work Africa, is the DX spot window showing a spot colored according to your preferences... if someone spots the DX, and when this happens it is late, lots of people calling.

Useful for 6 meters ops? Please comment, there is time enough before next Es season.

Thanks Bob & Team

Jose EA4AFP

--
73 de aki
JA1NLX

Re: new feature

ja1nlx
 

Jose

UDP BandMap display all decoded (by jtdx/wsjtx) callsign except blocked callsign (you setup)

What you mean "calling" and "called" ?

73

On 2019/12/19 18:13, José L. Peña EA4AFP wrote:

Probably of interest only for 6 meters or local propagation conditions...

What?

A new “UDP band map” window showing the stations that are called (instead of the stations that are calling). To avoid unnecessary information, only stations that would be colored according to our preferences on the standard “UDP band map” should be shown.

Why?

On 6 meters and from EA, most of the time the antenna is beaming to USA/VE/Caribbean, OH/LA/JA or Middle East. Taking into account the lobe size, that covers 99,9% of the stations leaving out only Africa.

The latest season has have very good conditions to AF. But if the antenna is beaming the aforementioned directions, probably the UDP band map will show nothing and the only way to notice that there is a chance to work Africa, is the DX spot window showing a spot colored according to your preferences... if someone spots the DX, and when this happens it is late, lots of people calling.

Useful for 6 meters ops? Please comment, there is time enough before next Es season.

Thanks Bob & Team

Jose EA4AFP

--
73 de aki
JA1NLX

new feature

José L. Peña EA4AFP
 

Probably of interest only for 6 meters or local propagation conditions...

What?

A new “UDP band map” window showing the stations that are called (instead of the stations that are calling). To avoid unnecessary information, only stations that would be colored according to our preferences on the standard “UDP band map” should be shown.

Why?

On 6 meters and from EA, most of the time the antenna is beaming to USA/VE/Caribbean, OH/LA/JA or Middle East. Taking into account the lobe size, that covers 99,9% of the stations leaving out only Africa.

The latest season has have very good conditions to AF. But if the antenna is beaming the aforementioned directions, probably the UDP band map will show nothing and the only way to notice that there is a chance to work Africa, is the DX spot window showing a spot colored according to your preferences... if someone spots the DX, and when this happens it is late, lots of people calling.

Useful for 6 meters ops? Please comment, there is time enough before next Es season.

Thanks Bob & Team

Jose EA4AFP

Re: ERROR 6

David Bonnet
 

Many thanks it’s working fine now. 

73

Le mer. 18 déc. 2019 à 08:52, Bob <k4cy@...> a écrit :
Also, you probably want to UNcheck the RADIO CHANGES FREQUENCY WHEN MODE IS CHANGED option on the Radio configuration Window. I don't think your IC-7300 does that. 73.
On December 18, 2019 at 2:32 AM David Bonnet <f8crs63@...> wrote:

I just change polling interval to 200 and works fine. 
Many thanks guys 

Best regards
73

Le mer. 18 déc. 2019 à 08:21, Bob < k4cy@...> a écrit :
Click the VIEW menu and UNcheck the ENABLE ERROR TRAPPING option. This will remove the pop-up, but will not fix the problem. With the pop-up removed, now you can look for the setup problem. 73.
On December 18, 2019 at 1:11 AM David Bonnet < f8crs63@...> wrote:

Yes I have 9600 on the radio. Cat is working but locked by the pop up. 
I will try by changing polling interval 

Le mer. 18 déc. 2019 à 07:07, ja1nlx < ayoshida0205@...> a écrit :

David

Try larger value of Polling interval, 500, 1000 etc

Is 9600 Baudrate is same as one in ic7300 menu settings ?

73

On 2019/12/18 14:20, David Bonnet wrote:

This appear when I put the 94 icom adress 

Le mer. 18 déc. 2019 à 06:05, David Bonnet via Groups.Io <f8crs63= gmail.com@groups.io> a écrit :
Hello
I use an ic7300. 

Le mar. 17 déc. 2019 à 21:20, Bob < k4cy@...> a écrit :
There is no line 208, maybe line 280?  It looks to me like the overflow is caused by operating on microwave frequencies ... What radio frequency are you operating when you see the error? 73.


On December 17, 2019 at 1:04 PM David Bonnet < f8crs63@...> wrote:

HI
I have this pop-up, anyone can help me please?

error on line 208
error 6 overflow in procedur radio frequency holder_change of form MDIForm1

thanks
73 david F8CRS

 
--
--
--
73 de aki
JA1NLX

 

 

--
 

 

 

 

--
 

 

--

Re: DXCC Challenge summary changed incorrectly

Ken JN7FAH
 

Bob,

Okey I will send you logbook backup and an ADIF file that cause trouble.
 
Ken JN7FAH

2019年12月18日(水) 20:11 Bob <k4cy@...>:

Ken, I have tested for several hours, and have not been able to duplicate this. Can you please create a sample logbook, and an ADIF file to import that I can use to test/simulate the problem. Thanks, 73.
On December 18, 2019 at 3:09 AM Ken JN7FAH <jn7fah@...> wrote:

Bob,

No, the ADIF file imported includes daily new QSOs only.

Anyway, 
The summary can be recovered by recalculation time to time.
Not matter for small database.
 
Ken

2019年12月18日(水) 16:41 Bob < k4cy@...>:
Ken, apologies for all the questions, but I am looking for clues as to what is the cause of this problem. Did the ADIF file you imported have another QSO with 3B8XF on 160M/FT8? 73.
On December 18, 2019 at 2:32 AM Ken JN7FAH < jn7fah@...> wrote:

Bob,

Yes, I always import new QSOs to logbook by importing an ADIF file.

Ken JN7FAH


2019年12月18日(水) 16:24 Bob < k4cy@...>:
Ken, clarification please. You said:  However, this summary changed when I import an ADIF file for new QSOs as show below ... Did you import new QSOs into your logbook by importing an ADIF file, or did you synchronize your logbook with an ADIF file from LoTW? 73.
On December 18, 2019 at 1:04 AM Ken JN7FAH < jn7fah@...> wrote:

Hello Folks,

I recently applied DXCC challenge endorsement of 62
band points to reach 2,700 through LoTW.
I changed Awards Status of granted QSOs as shown below
for example 3B8XF (160m FT8).
3B8XF.JPG
After all done, I recalculate statistics, then I see DXCC
challenge status achieved 2,700 as seen below.
2700.JPG
However, this summary changed when I import an ADIF file for new QSOs 
as show below.
2678.JPG
Total number of challenge points changes always to 2,678. 
In this window includes three newly granted points those are 3B8/160F,
3D2C/160C and 4O/160F.
I checked all those newly granted QSOs and found all those QSOs turning 
status Granted to Confirmed were granted for DXCC Digital and DXCC Mixed 
as shown in the first picture.
In the same time, other newly granted QSOs for DXCC CW/Phone and Mixed 
were not changed against ADIF importing.

What's wrong?
I appreciate your suggestions.
 
73
Ken JN7FAH

 

 

 


 

 

 


 

Re: DXCC Challenge summary changed incorrectly

Bob
 

Ken, I have tested for several hours, and have not been able to duplicate this. Can you please create a sample logbook, and an ADIF file to import that I can use to test/simulate the problem. Thanks, 73.

On December 18, 2019 at 3:09 AM Ken JN7FAH <jn7fah@...> wrote:

Bob,

No, the ADIF file imported includes daily new QSOs only.

Anyway, 
The summary can be recovered by recalculation time to time.
Not matter for small database.
 
Ken

2019年12月18日(水) 16:41 Bob < k4cy@...>:
Ken, apologies for all the questions, but I am looking for clues as to what is the cause of this problem. Did the ADIF file you imported have another QSO with 3B8XF on 160M/FT8? 73.
On December 18, 2019 at 2:32 AM Ken JN7FAH < jn7fah@...> wrote:

Bob,

Yes, I always import new QSOs to logbook by importing an ADIF file.

Ken JN7FAH


2019年12月18日(水) 16:24 Bob < k4cy@...>:
Ken, clarification please. You said:  However, this summary changed when I import an ADIF file for new QSOs as show below ... Did you import new QSOs into your logbook by importing an ADIF file, or did you synchronize your logbook with an ADIF file from LoTW? 73.
On December 18, 2019 at 1:04 AM Ken JN7FAH < jn7fah@...> wrote:

Hello Folks,

I recently applied DXCC challenge endorsement of 62
band points to reach 2,700 through LoTW.
I changed Awards Status of granted QSOs as shown below
for example 3B8XF (160m FT8).
3B8XF.JPG
After all done, I recalculate statistics, then I see DXCC
challenge status achieved 2,700 as seen below.
2700.JPG
However, this summary changed when I import an ADIF file for new QSOs 
as show below.
2678.JPG
Total number of challenge points changes always to 2,678. 
In this window includes three newly granted points those are 3B8/160F,
3D2C/160C and 4O/160F.
I checked all those newly granted QSOs and found all those QSOs turning 
status Granted to Confirmed were granted for DXCC Digital and DXCC Mixed 
as shown in the first picture.
In the same time, other newly granted QSOs for DXCC CW/Phone and Mixed 
were not changed against ADIF importing.

What's wrong?
I appreciate your suggestions.
 
73
Ken JN7FAH

 

 

 


 

 

 


 

Re: DXCC Challenge summary changed incorrectly

Ken JN7FAH
 

Bob,

No, the ADIF file imported includes daily new QSOs only.

Anyway, 
The summary can be recovered by recalculation time to time.
Not matter for small database.
 
Ken

2019年12月18日(水) 16:41 Bob <k4cy@...>:

Ken, apologies for all the questions, but I am looking for clues as to what is the cause of this problem. Did the ADIF file you imported have another QSO with 3B8XF on 160M/FT8? 73.
On December 18, 2019 at 2:32 AM Ken JN7FAH <jn7fah@...> wrote:

Bob,

Yes, I always import new QSOs to logbook by importing an ADIF file.

Ken JN7FAH


2019年12月18日(水) 16:24 Bob < k4cy@...>:
Ken, clarification please. You said:  However, this summary changed when I import an ADIF file for new QSOs as show below ... Did you import new QSOs into your logbook by importing an ADIF file, or did you synchronize your logbook with an ADIF file from LoTW? 73.
On December 18, 2019 at 1:04 AM Ken JN7FAH < jn7fah@...> wrote:

Hello Folks,

I recently applied DXCC challenge endorsement of 62
band points to reach 2,700 through LoTW.
I changed Awards Status of granted QSOs as shown below
for example 3B8XF (160m FT8).
3B8XF.JPG
After all done, I recalculate statistics, then I see DXCC
challenge status achieved 2,700 as seen below.
2700.JPG
However, this summary changed when I import an ADIF file for new QSOs 
as show below.
2678.JPG
Total number of challenge points changes always to 2,678. 
In this window includes three newly granted points those are 3B8/160F,
3D2C/160C and 4O/160F.
I checked all those newly granted QSOs and found all those QSOs turning 
status Granted to Confirmed were granted for DXCC Digital and DXCC Mixed 
as shown in the first picture.
In the same time, other newly granted QSOs for DXCC CW/Phone and Mixed 
were not changed against ADIF importing.

What's wrong?
I appreciate your suggestions.
 
73
Ken JN7FAH

 

 

 


 

Re: ERROR 6

Bob
 

Also, you probably want to UNcheck the RADIO CHANGES FREQUENCY WHEN MODE IS CHANGED option on the Radio configuration Window. I don't think your IC-7300 does that. 73.

On December 18, 2019 at 2:32 AM David Bonnet <f8crs63@...> wrote:

I just change polling interval to 200 and works fine. 
Many thanks guys 

Best regards
73

Le mer. 18 déc. 2019 à 08:21, Bob < k4cy@...> a écrit :
Click the VIEW menu and UNcheck the ENABLE ERROR TRAPPING option. This will remove the pop-up, but will not fix the problem. With the pop-up removed, now you can look for the setup problem. 73.
On December 18, 2019 at 1:11 AM David Bonnet < f8crs63@...> wrote:

Yes I have 9600 on the radio. Cat is working but locked by the pop up. 
I will try by changing polling interval 

Le mer. 18 déc. 2019 à 07:07, ja1nlx < ayoshida0205@...> a écrit :

David

Try larger value of Polling interval, 500, 1000 etc

Is 9600 Baudrate is same as one in ic7300 menu settings ?

73

On 2019/12/18 14:20, David Bonnet wrote:

This appear when I put the 94 icom adress 

Le mer. 18 déc. 2019 à 06:05, David Bonnet via Groups.Io <f8crs63= gmail.com@groups.io> a écrit :
Hello
I use an ic7300. 

Le mar. 17 déc. 2019 à 21:20, Bob < k4cy@...> a écrit :
There is no line 208, maybe line 280?  It looks to me like the overflow is caused by operating on microwave frequencies ... What radio frequency are you operating when you see the error? 73.


On December 17, 2019 at 1:04 PM David Bonnet < f8crs63@...> wrote:

HI
I have this pop-up, anyone can help me please?

error on line 208
error 6 overflow in procedur radio frequency holder_change of form MDIForm1

thanks
73 david F8CRS

 
--
--
--
73 de aki
JA1NLX

 

 

--
 

 

 

 

--
 

 

Re: DXCC Challenge summary changed incorrectly

Bob
 

Ken, apologies for all the questions, but I am looking for clues as to what is the cause of this problem. Did the ADIF file you imported have another QSO with 3B8XF on 160M/FT8? 73.

On December 18, 2019 at 2:32 AM Ken JN7FAH <jn7fah@...> wrote:

Bob,

Yes, I always import new QSOs to logbook by importing an ADIF file.

Ken JN7FAH


2019年12月18日(水) 16:24 Bob < k4cy@...>:
Ken, clarification please. You said:  However, this summary changed when I import an ADIF file for new QSOs as show below ... Did you import new QSOs into your logbook by importing an ADIF file, or did you synchronize your logbook with an ADIF file from LoTW? 73.
On December 18, 2019 at 1:04 AM Ken JN7FAH < jn7fah@...> wrote:

Hello Folks,

I recently applied DXCC challenge endorsement of 62
band points to reach 2,700 through LoTW.
I changed Awards Status of granted QSOs as shown below
for example 3B8XF (160m FT8).
3B8XF.JPG
After all done, I recalculate statistics, then I see DXCC
challenge status achieved 2,700 as seen below.
2700.JPG
However, this summary changed when I import an ADIF file for new QSOs 
as show below.
2678.JPG
Total number of challenge points changes always to 2,678. 
In this window includes three newly granted points those are 3B8/160F,
3D2C/160C and 4O/160F.
I checked all those newly granted QSOs and found all those QSOs turning 
status Granted to Confirmed were granted for DXCC Digital and DXCC Mixed 
as shown in the first picture.
In the same time, other newly granted QSOs for DXCC CW/Phone and Mixed 
were not changed against ADIF importing.

What's wrong?
I appreciate your suggestions.
 
73
Ken JN7FAH

 

 

 


 

Re: DXCC Challenge summary changed incorrectly

Ken JN7FAH
 

Bob,

Yes, I always import new QSOs to logbook by importing an ADIF file.

Ken JN7FAH


2019年12月18日(水) 16:24 Bob <k4cy@...>:

Ken, clarification please. You said:  However, this summary changed when I import an ADIF file for new QSOs as show below ... Did you import new QSOs into your logbook by importing an ADIF file, or did you synchronize your logbook with an ADIF file from LoTW? 73.
On December 18, 2019 at 1:04 AM Ken JN7FAH <jn7fah@...> wrote:

Hello Folks,

I recently applied DXCC challenge endorsement of 62
band points to reach 2,700 through LoTW.
I changed Awards Status of granted QSOs as shown below
for example 3B8XF (160m FT8).
3B8XF.JPG
After all done, I recalculate statistics, then I see DXCC
challenge status achieved 2,700 as seen below.
2700.JPG
However, this summary changed when I import an ADIF file for new QSOs 
as show below.
2678.JPG
Total number of challenge points changes always to 2,678. 
In this window includes three newly granted points those are 3B8/160F,
3D2C/160C and 4O/160F.
I checked all those newly granted QSOs and found all those QSOs turning 
status Granted to Confirmed were granted for DXCC Digital and DXCC Mixed 
as shown in the first picture.
In the same time, other newly granted QSOs for DXCC CW/Phone and Mixed 
were not changed against ADIF importing.

What's wrong?
I appreciate your suggestions.
 
73
Ken JN7FAH