My .adi file import does not seem to work.
1. I exported nearly 27k qso's from DXLab and put on USB drive. (Cruzer blade 32GB)
2. Imported into CQRLog and ticked "more than 10k qso's"
3. Import says 22439 done (but more than 4k qso's missing).
4. No log update to cqrlog i.e. no qso's showing in log and no errors reported.
For some reason the log file move to Ubuntu seems to convert the file to audio format. When I right click to check the file I get the message "file type aac (audio/aac)is not supported". Is it my USB drive corrupting the file?
I have tried two different usb drives and get the same problem. File opens ok in WIndows Notepad before unplugging from Windows pc and then plug into Linux pc for cqrlog import.
Paul
PS
Today I changed the import log file name with suffix .ADI rather than .adi
It made no difference to import i.e. import shows 22439 qso's imported from 27k in the file but zero show in log.
Hi
Your OS mime-type is set so that it thinks file is audio. If you right click it with file manager you should choose "Open with".
And then search plain text editor from the applications your file manager shows. With the list there is also checkbox "set as default application".
After that it no longer complains about audio file.
When you get your adif file open check that ends properly.
Last line should have <EOR> that ends the last qso record.
You could also try to start cqrlog from console:
cqrlog debug=1
and see what texts you have there during import. Specially at that point when it ends too early.
--
Saku
OH1KH
--
Saku
OH1KH
Saku,
Appreciate the help....I am moving forward a little at a time.
Here is the debug log ending comments
insert into cqrlog_main (qsodate,time_on,time_off,callsign,freq,mode,rst_s,rst_r,name,qth,qsl_s,qsl_r,qsl_via,iota,pwr,itu,waz,loc,my_loc,remarks,county,adif,idcall,award,band,state,cont,profile,lotw_qslsdate,lotw_qsls,lotw_qslrdate,lotw_qslr,qsls_date,qslr_date,eqsl_qslsdate,eqsl_qsl_sent,eqsl_qslrdate,eqsl_qsl_rcvd) values(:qsodate,:time_on,:time_off,:callsign,:freq,:mode,:rst_s,:rst_r,:name,:qth,:qsl_s,:qsl_r,:qsl_via,:iota,:pwr,:itu,:waz,:loc,:my_loc,:remarks,:county,:adif,:idcall,:award,:band,:state,:cont,:profile,:lotw_qslsdate,:lotw_qsls,:lotw_qslrdate,:lotw_qslr,:qsls_date,:qslr_date,:eqsl_qslsdate,:eqsl_qsl_sent,:eqsl_qslrdate,:eqsl_qsl_rcvd)
Import failed! TMySQL57Connection : Error executing query: Data too long for column 'remarks' at row 1
It takes about 0 minutes and 50 seconds 77 milliseconds
Sending: fmv
This seems to be repeated in the console for each qso import until failure.
It seems the remarks column data is too long in row 1. The upload fails at qso 22439. I have looked at this line in the text file but cannot see any remarks there in the data.
Here is a copy of the first few lines copied from the export document...
ADIF file
created by DXKeeper 14.4.8 on 06-Mar-2018 10:10:01 UTC
DXKeeper
14.4.8
20180306 101001
3.0.4
0 4000-01-01 00:00:00
160M G5IV G 223 CW G4AFU Y 19710711 103300 101000 599 599 10.0 EU 27 14 G5 G4AFU G4AFU N R Y R 20161126 Y 2016-11-21 10:59:11 Bedale
Maybe you have ideas on this problem?
Paul G4AFU
Hi !
Just thinking what happens for "remarks" as I did a test export from cqrlog and there is no "remarks" instead there is "comments".
<COMMENT:12>Wkd as OF1KH<ITUZ:2>28<CQZ:2>15
Number in adif tag, here COMMENT:12 means that actual text after > must have 12 characters until <. If it does not there is length failure.
How ever if I were you i would try to change all REMARK to COMMENT and then try adif import. I do not know if it helps, and I'm too lazy now to peek from source code if REMARKS is accepted( and how = converted perhaps).
copy your adi file to /tmp folder with name hi.adi
Open console and go to tmp folder:
cd /tmp
Give command:
cat hi.adi | sed s/REMARKS/COMMENT/g > ha.adi
After that try to import /tmp/ha.adi and see what happens.
That is quite easy and fast to test.
!!NOTE if you have something else in log DO BACKUP FIRST !!!
--
Saku
OH1KH
--
Saku
OH1KH
HI!
Im afraid moving remarks to comments were not solution and not so good idea. (Bad as most of my ideas...;( )
Cqrlog can handle remarks.
It is even selectable at adif export side. I just do not have an idea where the remarks go. I know comment to qso (adif comment) and comment to callsign (adif notes).
I did peek the source. Unfortunately that unit is not commented in English.
I looked also database structure and found:
remarks varchar(200)
So if your remarks are longer than 200 char you may expect problems from database side.
Not so very helpful. Solution is usually very simple (when someone else says it ).
Let's wait a bit.
--
Saku
OH1KH
--
Saku
OH1KH
Btw
Forum can not handle < and > You have to change them to something else like + - or change them to HTML codes.
to get < you have to type: & l t ; but without spaces between. > is & g t ; with no spaces.
Easy to remember: & starts special code ; ends it. LT comes from less (!? not quite) and GT comes from greater (more sense)
Then your adif tags shows as should.
--
Saku
OH1KH
--
Saku
OH1KH
Thanks Saku,
The problem started because I learned to touch type cw in the 70’s. G3IBB keyboard. Now I transcribe into “remarks/details” most of the QSO details during the QSO. Always more than 200 characters because I chat: not hello and goodbye.
I will QRX.
Paul.
HI!
Fine! Reason found!
Can't you export all qsos from another log program with "remarks" unselected ?
If that is not possible I could try to write something that drops "remarks" from ready made adif export file.
--
Saku
OH1KH
--
Saku
OH1KH
Saku,
I used the ClubLog ADIF export which worked fine. 27k QSO's imported with no errors.
As I guessed, this does strip all the junk from the QSO line.
I am doing a dance around the shack!
Appreciate your help and patience.
73
Paul G4AFU
One happy cqrlog user
Fine ! Nice to hear.
73
--
Saku
OH1KH