Hi Dennis,
in my last importing file, this morning, I had an experience as follows:

The Logic version is .29.
Imported adi file with NA, SA, JA, UA stations for a total of 48 qso make this night. The import aws been right!
Updated all the qsos with Callbook batch updated
Updated the qsos with QSL.cc and LOTW.
Updated QSL_SENT and RIG fields with MASSE CHANGE in Advance Database Command.
I ran fixstuff program to fill in the rest of fields and fix the wpx.
The CNTY field into USA qso was been empty.
Some JA qsos have had an update with CNTY value wich seems to be as JCC value.
The reason is fix stuff or LOTW wrong operation?
I sent You the adi file and an screenshot for information.
73's de IKØCHU Mauro
***

Hello Dennis and all

I am one of the miserable ones who have not "subscribed". I've been a user of LOGic since Version 4 and have paid for numerous "updates" until the subscription system was introduced. At that time I "choked".

Part of the reason at the time was the problems I was having with my Elecraft K3 and LOGic not happy with each other and all efforts Dennis made to resolve this being unsuccessful. My use of LOGic is now limited due to its inability to have a Webcluster connected via Telnet without continually crashing. So the facility to "click" on a needed contact is no longer available to me and missed badly.

So, ignore my comments if I don't count!

I regularly use other logging software, particularly N1NM+ for contesting and WSJT-X for some of the digital modes, especially FT8 of late. However, I use LOGic as my "base" logging software for maintaining my data for DXCC and other awards. For this reason I am regularly importing .ADI files.

For some time now I have had two problems arise after import. These are either:
1. JA's with a number inserted into the US County field, or
2. North American stations with rejected Zone numbers (can be either CQZ or ITUZ).

So after each import I have to edit to correct this. I don't understand the JA entries into the County field, but the North American Zone entries appear to be caused by the inclusion of a leading Zero in the imported zone number. I have read that there are variations in the interpretation of what is considered "correct" in .ADI files and suspect a clash due to that sort of thing.

I could send Dennis a copy of my log for his analysis but the files has become quite large with 40 years of DX-ing recorded. I know it is not large compared with many of my keen DX-ing friends but there are over 55,000 contacts included.

I see reference to linking WSJT-X importation to LOGic. If both that and the Webcluster/Telnet issues were properly operational, I might be convinced to become a "subscriber", rather than exploring other options.

73, Cliff ZL4AS

Thanks for that information Kyle.

The Webcluster/Telnet problem just drove me crazy at the time and no amount of playing with polling etc. lead to any resolution, so reluctantly, I switched it all off. I guess had I coughed up for the "support" the problem would have been resolved for me and I would not have denied myself the use of this handy feature meantime. At the time, my patience just ran out on me...

And thanks for the tip on dealing with imported log data. I shall investigate that and maybe give it a try. However, it would be much better if we did not have to do that either.

That only leaves the automation of importation of WSJT-X data which would be an extremely handy and time saving feature. Most of the local ZL hams keen on DX-ing use Logger 32 software which I believe has had this feature available for some time.

73, Cliff ZL4AS

The K3 is solid now, and Telnet also. We totally redid Telnet. What version are you actually running? (Help/about).



That has been fixed in the .30 update. The ARRL changed some stuff on their end.


It will be done soon. We're close.

Tnx & 73,

Dennis WN4AZY

Thanks for responding Dennis

I am on Version 9.1.1

With K3/Webcluster/Telnet fixed I am encouraged to come on board again! All of that will make life much more relaxed for me.

And the importation of WSJT-X data will be a further simplification once it's operational. I worked over 100 entities on FT-8 up until Dec 31, then restarted my count and am in the 90's already since Jan 1 this year!!

Just 10 days ago ZL's were given limited privileges on the 60M band too, so I have been giving that a bash too.

73, Cliff ZL4AS