[Dx4win] More LOTW info

2004-05-26 Thread Cal Kutemeier
I am having the same problem.  I did searches on the help file and user
guide and could not find out how to increase the field  # by 1 as suggested
below within the DX4WIN program. Can this be done within the DX4WIN program,
or is this suggestion related a manual edit of the resultant ADIF file?  My
question relates to past QSOs and QSOs to be logged in the future.

Thanks
Cal
N9KO



- Original Message - 
From: Jim Reisert AD1C [EMAIL PROTECTED]
To: [EMAIL PROTECTED]; Dx4win@mailman.qth.net
Sent: Tuesday, September 23, 2003 8:51 PM
Subject: RE: [Dx4win] More LOTW info


 At 06:23 PM 9/23/2003, Jay Hainline wrote:

 Thanks Jim. I am also receiving errors for 222 MHz band contacts. I am
using
 DX4WIN 5.03 which creates the band 1.2m in the adif file. I think it is
 suppose to be 1.25m but now I get an error message that says invalid band
 (1.25). It cut off the letter m it seems!

 The field has a :# - you have to increase the # by one - that's the width
 of the field.

 I.e. BAND:41.2m should change to BAND:51.25m

 73 - Jim AD1C

 ___
 Dx4win mailing list
 Dx4win@mailman.qth.net
 http://mailman.qth.net/mailman/listinfo/dx4win


[Dx4win] More LOTW info

2003-09-24 Thread Jay Hainline
I am learning more about adif formatting than I ever thought I should know!
I finally figured out why the TQSL program was giving me errors for my 222
MHz  contacts. Proper adif format shows the band to be 1.25m. DX4WIN ver.
5.03 exports it as 1.2m. So the proper adif format should be:

band:51.25m

After making this change, deleting out my satellite qso's, and customizing
the TQSL program to accept PSK3 for mode PSK31, it went with no hitches!

Jay Hainline  KA9CFD  EN40om
Colchester, IL
[EMAIL PROTECTED]
http://www.qsl.net/learc 




[Dx4win] More LOTW info

2003-09-23 Thread Barry
I am in the process of using TQSL to convert the logs for upload for 
LOTW. TQSL also includes a date range filter, so you can exclude QSOs 
from before and after specified dates from the ADIF or Cabrillo file, 
if you didn't do it in your export from DX4WIN.

Another note - warning of sorts: TQSL is VERY slow. My machine is a 
Dell P4 2.2 Ghz and it's converting at about 20 QSOs/second. The 
current selection I'm converting contains 82K QSOs, so it's going to 
be a while. If you have a big log and/or a slow computer, you may 
want to run it overnight.
73,
Barry--
Barry Kutner, W2UP  Internet: [EMAIL PROTECTED]
Newtown, PA Frankford Radio Club
 




[Dx4win] More LOTW info

2003-09-23 Thread Mel
Frankly, the only thing Lotw is going to be good for is WAS...

It's so damn complicated for non-US stations to register I suspect it
will be a domestic database...

We are expected to send personal documents in the mail... Sacrifice
personal security in favour of Lotw security...

I think not!

Cheers...

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On Behalf Of Rick Murphy
 Sent: September 22, 2003 22:59
 To: dx4win@mailman.qth.net
 Subject: RE: [Dx4win] More LOTW info
 
 
 At 08:39 PM 9/22/2003, Mike Mellinger WA0SXV wrote:
 Second, there is a new version of Trusted QSL -- v1.07.  If you're
 going to
 request additional certificates you'll need it.
 
 Mike,
 Thanks for saving me from wasting my time by requesting a new 
 certificate.
 
 I've been trying to submit certificate requests for my old 
 callsign but 
 was getting my password rejected while trying to sign the certificate 
 requests - I figured I fat-fingered the password but 1.07 fixed the 
 problem.
 
 If you're going to ask for certs for old callsigns or for portable 
 operations, get the new software!
  -Rick/K1MU
 
 ___
 Dx4win mailing list
 Dx4win@mailman.qth.net http://mailman.qth.net/mailman/listinfo/dx4win
 



[Dx4win] More LOTW info

2003-09-23 Thread Pete Smith
At 11:25 PM 9/22/03 -0400, Mel wrote:
Frankly, the only thing Lotw is going to be good for is WAS...

It's so damn complicated for non-US stations to register I suspect it
will be a domestic database...

We are expected to send personal documents in the mail... Sacrifice
personal security in favour of Lotw security...

I think not!

Cheers...


Isn't that a bit overdrawn, Mel?  Other than DXpeditions, the only 
requirement for non-US stations is pretty straightforward --

Every non-USA station requesting a certificate for Logbook of the World 
must supply a copy of his or her Amateur Radio license in addition to a 
copy of one other government-issued document indicating his/her identity. 
Such an additional document might be a driver's license, for example.

How many personal documents of that minor level of importance do you send 
every month to someplace or another by mail?  Sure, it's a bit annoying to 
have to wait for mail notification of your initial certificate password, 
but the ultimate payoff would seem to be well worth it, for US and non-US 
stations alike.  If I were LotW's authors, I'd be very concerned that one 
successful fraud could undermine the entire enterprise.

73, Pete N4ZR
The World HF Contest Station Database was updated August 30.
129 stations were added or updated.
Are you current? www.pvrc.org/wcsd/wcsdsearch.htm





[Dx4win] More LOTW info

2003-09-23 Thread Jay Hainline
I received my certificate today and am in the process of converting the =
adif
exported log from DX4WIN into the format for uploading to the LOTW. I am
receiving error messages on my contacts that I have made using the
satellites. Apparently Sat is not a recognized band in the adif =
format?
Is there a work around for this? Maybe I just have to wait before I can
upload these contacts to the LOTW. I may have to create a new adif file =
that
excludes satellite contacts. I am not sure how to do this but will try.

73 Jay

Jay Hainline  KA9CFD  EN40om
Colchester, IL
[EMAIL PROTECTED]
http://www.qsl.net/learc=20




[Dx4win] More LOTW info

2003-09-23 Thread Jim Reisert AD1C
--- Jay Hainline [EMAIL PROTECTED] wrote:

 I received my certificate today and am in the process of converting the adif
 exported log from DX4WIN into the format for uploading to the LOTW. I am
 receiving error messages on my contacts that I have made using the
 satellites. Apparently Sat is not a recognized band in the adif format?
 Is there a work around for this? Maybe I just have to wait before I can
 upload these contacts to the LOTW. I may have to create a new adif file that
 excludes satellite contacts. I am not sure how to do this but will try.

Jay, I got the same errors.  I just allowed TQSL to proceed and uploaded the
log anyway.

When you want to export your SAT QSOs, just do a F8 search for SAT band, then
export the ADIF log using the current filter.

73 - Jim AD1C


=
Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863
USA +978-251-9933, [EMAIL PROTECTED], http://www.ad1c.com
PGP Fingerprint: D8E2 3D78 339F A7F1 8C13  1193 B5D1 4FB6 79D1 70DC


[Dx4win] More LOTW info

2003-09-23 Thread Jay Hainline
Thanks Jim. I am also receiving errors for 222 MHz band contacts. I am =
using
DX4WIN 5.03 which creates the band 1.2m in the adif file. I think it =
is
suppose to be 1.25m but now I get an error message that says invalid =
band
(1.25). It cut off the letter m it seems!=20

73 Jay

Jay Hainline  KA9CFD  EN40om
Colchester, IL
[EMAIL PROTECTED]
http://www.qsl.net/learc=20

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] =
On
Behalf Of Jim Reisert AD1C
Sent: Tuesday, September 23, 2003 21:59
To: [EMAIL PROTECTED]; Dx4win@mailman.qth.net
Subject: RE: [Dx4win] More LOTW info


--- Jay Hainline [EMAIL PROTECTED] wrote:

 I received my certificate today and am in the process of converting=20
 the adif exported log from DX4WIN into the format for uploading to the =

 LOTW. I am receiving error messages on my contacts that I have made=20
 using the satellites. Apparently Sat is not a recognized band in=20
 the adif format? Is there a work around for this? Maybe I just have to =

 wait before I can upload these contacts to the LOTW. I may have to=20
 create a new adif file that excludes satellite contacts. I am not sure =

 how to do this but will try.

Jay, I got the same errors.  I just allowed TQSL to proceed and uploaded =
the
log anyway.

When you want to export your SAT QSOs, just do a F8 search for SAT band,
then export the ADIF log using the current filter.

73 - Jim AD1C


=3D=3D=3D=3D=3D
Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863 USA
+978-251-9933, [EMAIL PROTECTED], http://www.ad1c.com PGP
Fingerprint: D8E2 3D78 339F A7F1 8C13  1193 B5D1 4FB6 79D1 70DC
___
Dx4win mailing list
Dx4win@mailman.qth.net http://mailman.qth.net/mailman/listinfo/dx4win




[Dx4win] More LOTW info

2003-09-23 Thread Barry
There are also errors generated by PSK and PSK3 mode QSOs.
Barry--
Barry Kutner, W2UP  Internet: [EMAIL PROTECTED]
Newtown, PA Frankford Radio Club
 




[Dx4win] More LOTW info

2003-09-23 Thread Michael McCarty
To convert my log from DX4Win to the ADIF needed by LOTW, I exported from 
DX4Win with filters for the various modes.  I have always placed the actual 
mode for the various soundcard (PSK) modes in the QSO Notes field so it was 
easy to filter them out.

When done with the exports I was left with a bunch of files with mode 
extensions.  I used filenames like: k6mmc_ssb.adif, k6mmc_cw.adic, 
k6mmc_psk31.adif, k6mmc_hell.adif, etc.

Within TQSL before signing each file I made the propper mapping from 
PSK-MT63, PSK-HELL, etc.  This required me to change the TQSL ADIF 
mappings between all the different modes I had recorded as PSK within DX4Win.

On the LOTW site it was a simple process to upload the files, one at a time.

73,
Michael




[Dx4win] More LOTW info

2003-09-23 Thread WA9ALS - John
 After making this change,  and customizing
 the TQSL program to accept PSK3 for mode PSK31, it went with no hitches!

So how do you do that?



[Dx4win] More LOTW info

2003-09-23 Thread WC7N
Boy I must have really screwed up... I just submitted about 12 years of logs
which included PSk31 etc and they went through perfect Makes me worry
now.

Rod Wc7N

- Original Message - 
From: Michael McCarty [EMAIL PROTECTED]
To: dx4win@mailman.qth.net
Sent: Tuesday, September 23, 2003 4:43 PM
Subject: RE: [Dx4win] More LOTW info


 To convert my log from DX4Win to the ADIF needed by LOTW, I exported from
 DX4Win with filters for the various modes.  I have always placed the
actual
 mode for the various soundcard (PSK) modes in the QSO Notes field so it
was
 easy to filter them out.

 When done with the exports I was left with a bunch of files with mode
 extensions.  I used filenames like: k6mmc_ssb.adif, k6mmc_cw.adic,
 k6mmc_psk31.adif, k6mmc_hell.adif, etc.

 Within TQSL before signing each file I made the propper mapping from
 PSK-MT63, PSK-HELL, etc.  This required me to change the TQSL ADIF
 mappings between all the different modes I had recorded as PSK within
DX4Win.

 On the LOTW site it was a simple process to upload the files, one at a
time.

 73,
 Michael


 ___
 Dx4win mailing list
 Dx4win@mailman.qth.net
 http://mailman.qth.net/mailman/listinfo/dx4win



[Dx4win] More LOTW info

2003-09-23 Thread Jim Reisert AD1C
At 06:23 PM 9/23/2003, Jay Hainline wrote:

Thanks Jim. I am also receiving errors for 222 MHz band contacts. I am using
DX4WIN 5.03 which creates the band 1.2m in the adif file. I think it is
suppose to be 1.25m but now I get an error message that says invalid band
(1.25). It cut off the letter m it seems!

The field has a :# - you have to increase the # by one - that's the width 
of the field.

I.e. BAND:41.2m should change to BAND:51.25m

73 - Jim AD1C



[Dx4win] More LOTW info

2003-09-23 Thread Jim Reisert AD1C
At 07:30 PM 9/23/2003, Jay Hainline wrote:

DX4WIN ver. 5.03 exports it as 1.2m. So the proper adif format should be:

band:51.25m

DX4WIN 6.02 has the same problem!

73 - Jim AD1C



[Dx4win] More LOTW info

2003-09-23 Thread David Tilley
WC7N wrote:

Boy I must have really screwed up... I just submitted about 12 years of logs
which included PSk31 etc and they went through perfect Makes me worry
now.

 

Kinda makes you wonder what ya missed, don't it?  ;-)   

Isn't that one of Murphy's Laws?

- David, W4HPW

-- 
Flying is of the Spirit.  The Spirit wants to fly!
  - Amazon jungle pilot

They shall mount up with wings, as eagles  Isaiah 40:31

Out of the night, into the morn, drawing us gently through the eye of the 
storm.
 Out of the sorrow, into the joy, where we'll dwell in the Highlands with Him 
evermore.

  from the CD Journey Into The Morn
  Journey Into The Morn
   Iona
  
 





[Dx4win] More LOTW info

2003-09-23 Thread Dean Norris
At  17:52 9/23/2003, WC7N wrote:
Boy I must have really screwed up... I just submitted about 12 years of logs
which included PSk31 etc and they went through perfect Makes me worry
now.

Rod Wc7N


I really don't want to be around then Murphy catches up with you.  You have 
my sincere sympathy!

Be afraid...be very afraid!

Dean




[Dx4win] More LOTW info

2003-09-22 Thread Mike Mellinger WA0SXV
Yes, TQSL is slow.

Couple of things.

First, the site is having problems with large uploads.  Plus although there
aren't that many records coming in it seems slow.  Unless you're into
watching your results immediately you can save some aggravation by emailing
the files.

Second, there is a new version of Trusted QSL -- v1.07.  If you're going to
request additional certificates you'll need it.

I've upload 28k+ records and already have a bunch of QSL's.  Seems to be
working great.

73,
Mike WA0SXV


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Barry 
Sent: Monday, September 22, 2003 19:28
To: dx4win@mailman.qth.net
Subject: [Dx4win] More LOTW info

I am in the process of using TQSL to convert the logs for upload for 
LOTW. TQSL also includes a date range filter, so you can exclude QSOs 
from before and after specified dates from the ADIF or Cabrillo file, 
if you didn't do it in your export from DX4WIN.

Another note - warning of sorts: TQSL is VERY slow. My machine is a 
Dell P4 2.2 Ghz and it's converting at about 20 QSOs/second. The 
current selection I'm converting contains 82K QSOs, so it's going to 
be a while. If you have a big log and/or a slow computer, you may 
want to run it overnight.
73,
Barry--
Barry Kutner, W2UP  Internet: [EMAIL PROTECTED]
Newtown, PA Frankford Radio Club




[Dx4win] More LOTW info

2003-09-22 Thread Mike Mellinger WA0SXV
Obviously Barry managed to upload his logs.  My QSL total just jumped from
about 60 to 90 -- all W2UP.

73,
Mike WA0SXV


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Barry 
Sent: Monday, September 22, 2003 19:28
To: dx4win@mailman.qth.net
Subject: [Dx4win] More LOTW info

I am in the process of using TQSL to convert the logs for upload for 
LOTW. TQSL also includes a date range filter, so you can exclude QSOs 
from before and after specified dates from the ADIF or Cabrillo file, 
if you didn't do it in your export from DX4WIN.

Another note - warning of sorts: TQSL is VERY slow. My machine is a 
Dell P4 2.2 Ghz and it's converting at about 20 QSOs/second. The 
current selection I'm converting contains 82K QSOs, so it's going to 
be a while. If you have a big log and/or a slow computer, you may 
want to run it overnight.
73,
Barry--
Barry Kutner, W2UP  Internet: [EMAIL PROTECTED]
Newtown, PA Frankford Radio Club
 




[Dx4win] More LOTW info

2003-09-22 Thread Rick Murphy
At 08:39 PM 9/22/2003, Mike Mellinger WA0SXV wrote:
Second, there is a new version of Trusted QSL -- v1.07.  If you're 
going to
request additional certificates you'll need it.

Mike,
Thanks for saving me from wasting my time by requesting a new certificate.

I've been trying to submit certificate requests for my old callsign but 
was getting my password rejected while trying to sign the certificate 
requests - I figured I fat-fingered the password but 1.07 fixed the 
problem.

If you're going to ask for certs for old callsigns or for portable 
operations, get the new software!
 -Rick/K1MU