ADIF import does not happen

18 posts / 0 new
Last post
sm6vja
ADIF import does not happen

Hi!

I´m a new Linux user and have just got started with Xubuntu 9.10.
The CQRLOG seem to work fine, I can log QSOs and other features also seem to work. BUT when I tried to import an ADIF-log created by DXLAB/DX-keeper nothing happens. Zero imported QSOs and no content in the folder where the qsos should be stored. The message I get is that ADIF import was successful!

The log file works fine when uploaded to LOTW. I have added the libraries as suggested in other threads here on this forum.

What could be wrong here? Please give some advise, as I intend to drop Bill G at the next station.

Best regards,

zl3aau
ADIF Import

Hi I,m having the same problem with Ubuntu 9.10.I can set up dummy QSO's export them,delete the QSO's in the log and import them OK but when I try to import my old WL32 ADIF log I get the same result as you.I have examined the files and find the sequence of the ADIF files is different in CQRlog than WL32.As I understand this should not make a difference, can anyone confirm this.
73 John

john-zl3aau

ok1rr
ok1rr's picture
Re: ADIF Import

ADIF should be a standard but definitely is NOT, at least as interpreted by some software authors. There are minor differences, both visible and invisible, which is real problem. I can recall a software which produced ADIF with some non-printable (thus non visible) ASCII characters inside the output.

Provide us with the ADIF file which you can't import, please. We will analyse it, correct the problem and an advice will appear here.

73 Martin, OK1RR

sm6vja
ADIF import

Great Martin!

I will e-mail my log-file to you. What you say is what I also thought, the standard is not followed...

BR/
Mikael SM6VJA

Mikael SM6VJA

ok1rr
ok1rr's picture
Re: ADIF Import

Hi Mikael,

of course, the ADIF file does contain A LOT of non-standard fields but I don't think this is a real problem. The real problem is the non standard header and the dummy records 0 at the file begin. The is also a lot of redundant data building a lot of balast.

With apologies, DXKeeper provides a junk output. The correct ADIF header is

2.2.1
ADIF export from CQRLOG for Linux version 0.9.2
Copyright (C) 2009 by Petr, OK2CQR and Martin, OK1RR

Internet: http://www.cqrlog.com

----
but your file has

ADIF file
created by DXKeeper 8.5.6 on 2010-04-22 19:49:46 UTC
DXKeeper

----

You see that the header is incomplete. CQRLOG has no chance to resolve/confirm that the file really IS in ADIF format. Of course, CQRLOG can be more forgiving but we need the ADIF version number 2.2.1 - this will ensure that in the future the older files can be imported correctly regardless of future changes of ADIF specification.

Anyway, allow me some time to analyse your file to learn which component of the file is the culprit.

73 Martin, OK1RR

sm6vja
ADIF import

OK! Yes, I discovered the dummy records in the beginning. When converting the ADIF to LoTW-format, I get warnings about these dummies but they are automatically removed before conversion.
Thank's a lot and I would be glad if your analyze just could tell med how to modify the header, if thats the problem. I will try to modify as described in a copy of the file.

/Mikael SM6VJA

Mikael SM6VJA

sm6vja
ADIF import

Hi! It seem to work fine when I add "2.2.1" in the header and remove the dummy rows in the beginning. Thanks, now I can continue my conversion into Linux.

/Mikael SM6VJA

Mikael SM6VJA

N6YBG
ADIF Import

Martin, the ADIF header generated by DXKeeper that you show above is perfectly valid. Read the ADIF specification.

All changes to ADIF since 1.0 have been upward compatible. Thus it is not necessary to know the ADIF version associated with a particular ADIF file in order to correctly parse that file. If you need help understanding this, let me know and I will explain it to you.

If you carefully read the specification, you will also discover that the fields used in DXKeeper are in conformance with the ADIF specification. DXKeeper does not produce "junk output" as you claim above. If you don't know how to parse an ADIF file, ask for help; blaming your troubles on other logging applications will only damage your credibility.

73,

Dave, AA6YQ

sm6vja
ADIF import

Hi John!

I have not examined my files as since they seem to work in other programs.
Maybe a lot of log-programs do not follow some ADIF-standard too strictly?
Maybe CQRLOG should be made more flexible to small differences? Seems like
it does not accept any deviation, which other programs seem to handle.

Hope to get in touch with the CQRLOG-team soon. I'm not in a big hurry, but I
plan to "convert" to Linux as much as possible during this year. At the moment I'm
busy typing my paper logs into digital format...

BR
/Mikael SM6VJA

Mikael SM6VJA

zl3aau
ADIF

Hi,The ADIF spec can be found at www.adif.org

73 John

john-zl3aau

la9nka
Re: ADIF import failure

I had similar problems trying to import my logbook from my Windows XP based Logger32 installation. The import function seemed to "scan" the file, and not showing any error messages, not even in the logs. But nothing was actually imported.

It seems that the Logger32 adif export routine is not following the adif definition 100%. The problem on my part was that all the frequencies was exported with a comma "," (ascii 44) as the decimal point, which is the correct symbol for my national settings. The adif definition however states that the decimal point for "number" fields should be the punctuation "." (ascii 46).

Fortunately my logbook wasn't more than a couple hundred QSOs, so it was fairly easy changing the incorrect symbols using "search & replace" in a text editor. After correcting, the import into CQRLOG worked fine.

The CQRLOG seems to be a very well made logging software. All that remains now is to get my station up and running and start logging ;-)

Keep up the good work folks.

...Anders, LA9NKA

AC6SL
missing ADIF header causes 100% CPU hang

A few of my ADIF files were missing the header line. This caused IMPORT to hang with CPU usage 100%. Adding a header line to the top of these files fixed the problem, but it would be nice if cqrlog would emit an error message, instead of hang.

I had entered data from my old paper logs in a very minimal format, e.g. "19960317 20 CW 2232 WA0BZD", and then I wrote an awk script to convert them to ADIF, so that they could be submitted to LOTW. There have been other format conversion problems, especially "\r\n" versus "\n".

W6RBA
ops wrong thread...

seems to be that it is important what is in the ADIF header. see http://www.cqrlog.com/?q=node/284

I have been using the same file going from DXkeeper to Ham Radio Deluxe and other windows based logging softwares with no issues though so I think it would be good to know how it has to look.

EDIT: this was supposed to have gone to a "bug" I filed :) but I seem to have posted it in wrong thread.
Anyways...I have tried to export my log from both HamRadioDelux as well as from DX Keeper and Import is not successful to CQRLOG. I'll wait until this is fixed for my next CQRLOG try (no time).

ok2cqr
ok2cqr's picture
Re: missing ADIF header causes 100% CPU hang

Hello,

just modified. Now CQRLOG ignores ADIF header. But I thing ADIF file without proper header is not an ADIF file.

73 Petr, OK2CQR

2E0WHN
another .adi question

Started to use CQRLOG with Linux. Had to download an old program and get the new one to work from that. So that is one problem solved.

The problem now is the .adif file I get from EQSL. It says it is either dumping as a .txt file and not loading it up, or I get the adif file and it refuses to add my logbook to the QSO log. I feel as though I have jumped three places and gone down the snake.

Any idea what may be going wrong?

ok2cqr
ok2cqr's picture
Re: another .adi question

Please look into the txt file. Maybe there is an error message and not QSO in adif format. I also use eQSL and it works without any problem.

73 Petr, OK2CQR

k8wdx
k8wdx's picture
Try to load the log into

Try to load the log into HamQTH, then go to your Profile "my profile" then see if all your "Q's" are there, if they are then go to the log upload page again and re download it on to your pc and load that into CQRlog, and see if that works Tom K8WDX

Tom K8WDX

2E0WHN
Solved.

Solved.

The log window it opened was minimised on the screen. When I maximised it it showed the procedure for entering the .adi file. Now the logbook is on the screen and can be worked.

Maybe a tweak on the log file window to show file only so when minimised it can be added with out maximising and input the log directly.