For some reason I loaded the new version and now and this comes up on the screen error :0 : then it want me to select a new data base.
Have I broken it or is it the new software?
Rob
VK3EY
New Version 6.1.1
New Version 6.1.1
Hi Rob
This shouldn't be a problem with the new version, but again this may depend on what version you have updated from?
If you select your log? database and then LOAD button, you should be away, but I am guessing without further info.
If you can email me direct with a screen shot attachment when error message(s) occur, I may be able to figure it.
Or please post here EXACT error message(s) and sequence, plus the version you updated from and windows system you are using.
73 Colin
G0CUZ
This shouldn't be a problem with the new version, but again this may depend on what version you have updated from?
If you select your log? database and then LOAD button, you should be away, but I am guessing without further info.
If you can email me direct with a screen shot attachment when error message(s) occur, I may be able to figure it.
Or please post here EXACT error message(s) and sequence, plus the version you updated from and windows system you are using.
73 Colin
G0CUZ
New Version 6.1.1
Thanks for the reply Colin
Will send a email now.
73
Rob
Will send a email now.
73
Rob
New Version 6.1.1
Hi guys,
anyone noted that when you upload log on LoTW freq. information is missing ? Never had any issue with that before. I am using old LoTW TQSL V1.3 and latest public version of winlog32, all done manualy, no automatic mode.
It's BUG or feature?
example:
EXPORTED ADIF LOG FOR LoTW on 2014-01-07 13:57:42
<PROGRAMID:8>WINLOG32
<PROGRAMVERSION:5>6.1.1
WINLOG32 (G0CUZ) c 1999 - 2014 version 6.1.1
File: C:\Program Files\Winlog32\Logs\9A5CW.LOG
LogName: 9a5cw
RECORDS: 1
CALL 9A5CW
<EOH>
<CALL:4>9A3K <QSO_DATE:8>20140107 <TIME_ON:4>1251 <BAND:4>160m <MODE:2>CW <RST_SENT:3>599 <EOR>
http://www.9a1p.com/9a5cw/9a5cw_lotw.jpg
73, Patrik 9A5CW
anyone noted that when you upload log on LoTW freq. information is missing ? Never had any issue with that before. I am using old LoTW TQSL V1.3 and latest public version of winlog32, all done manualy, no automatic mode.
It's BUG or feature?
example:
EXPORTED ADIF LOG FOR LoTW on 2014-01-07 13:57:42
<PROGRAMID:8>WINLOG32
<PROGRAMVERSION:5>6.1.1
WINLOG32 (G0CUZ) c 1999 - 2014 version 6.1.1
File: C:\Program Files\Winlog32\Logs\9A5CW.LOG
LogName: 9a5cw
RECORDS: 1
CALL 9A5CW
<EOH>
<CALL:4>9A3K <QSO_DATE:8>20140107 <TIME_ON:4>1251 <BAND:4>160m <MODE:2>CW <RST_SENT:3>599 <EOR>
http://www.9a1p.com/9a5cw/9a5cw_lotw.jpg
73, Patrik 9A5CW
New Version 6.1.1
Hi Patrik
I just looked and I have the same problem with no frequency entered for QSO's.
I am using a registered version with LOTW TQSL 2.0
Just reloaded the QSO's with exporting ADIF Full into the TQSL 2.0 and the frequencies are there now.[:)]
73
Rob
VK3EY
I just looked and I have the same problem with no frequency entered for QSO's.
I am using a registered version with LOTW TQSL 2.0
Just reloaded the QSO's with exporting ADIF Full into the TQSL 2.0 and the frequencies are there now.[:)]
73
Rob
VK3EY
New Version 6.1.1
The lack of frequency in the LoTW export is deliberate.
A bug in TQSL v2.0 beta which some guys have started to use, throw out QSO's that are logged out of band, like this can happen with 18MHz (bottom edge is 18.1) but band may usually be logged as 18MHZ and no exact frequency entered.
This was a problem with TQSL - they have fixed it with subsequent versions of v2, but as the original beta may still be use I have no option but to exclude the frequency for now.
LoTW does NOT use the frequency, so it is not of any importance for QSO matching. Winlog32 exports the "Band" for LoTW which is required.
Hope this explains, I may revert to exporting the frequency in the future, but for now, I can do without the agro of your QSOs being rejected.
73 Colin
G0CUZ
A bug in TQSL v2.0 beta which some guys have started to use, throw out QSO's that are logged out of band, like this can happen with 18MHz (bottom edge is 18.1) but band may usually be logged as 18MHZ and no exact frequency entered.
This was a problem with TQSL - they have fixed it with subsequent versions of v2, but as the original beta may still be use I have no option but to exclude the frequency for now.
LoTW does NOT use the frequency, so it is not of any importance for QSO matching. Winlog32 exports the "Band" for LoTW which is required.
Hope this explains, I may revert to exporting the frequency in the future, but for now, I can do without the agro of your QSOs being rejected.
73 Colin
G0CUZ
New Version 6.1.1
Hi Colin.
LOTW is tricky to deal with and it is appreciated for the explanation.
Cheers
Rob
VK3EY
LOTW is tricky to deal with and it is appreciated for the explanation.
Cheers
Rob
VK3EY
New Version 6.1.1
I am currently using 5.9.3 and when trying to install I get an error message that the files are corrupted to download again and did but get the same.
New Version 6.1.1
Never mind - probably my Internet. I kept trying and after a bit I seemed to have gotten a complete download. thanks
Gary, N5PHT
quote:Originally posted by N5PHT
I am currently using 5.9.3 and when trying to install I get an error message that the files are corrupted to download again and did but get the same.
Gary, N5PHT
quote:Originally posted by N5PHT
I am currently using 5.9.3 and when trying to install I get an error message that the files are corrupted to download again and did but get the same.
New Version 6.1.1
I have this problem when using automate LoTW upload (see picture here attached). Anybody can help?
