Date   

Re: CQ WW RTTY Contest ADIF Logs

Ed Muns, W0YK
 

Yep, we discovered that case a today and are arranging a fix.  Thanks for the sleuthing and feedback! 

73,
Ed W0YK


-------- Original message --------
From: "Phil Cooper via groups.io" <pcooper@...>
Date: 9/29/20 10:01 (GMT-08:00)
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MM+] CQ WW RTTY Contest ADIF Logs

Hi Ed,

 

After running through the process, and getting to the bit where it produces the Cabrillo file, I noted that DX (ie non-US/VE stations) were correctly identified as DX, but it also put DX against all my US/VE contacts too.

 

From what I could see, it asks for a sample of the CQ Zone, and a sample of the "Received Location", but the choices available don't seem to cater for what N1MM produces in the ADIF file, which is (for example) <STATE:2>MA.

 

If I choose the default of AUTO:DX it places DX against all US/VE calls, rather than the State, as per the instructions. However, I note that it says " Select ADIF field that contains received State/Province", but I can't seem to navigate to anything other than the first contact in the ADIF file.

 

73 de Phil GU0SUP

 

 

 

-----Original Message-----
From: "Ed Muns, W0YK" <ed@...>
Sent: Tuesday, 29 September, 2020 13:10
To: N1MMLoggerPlus@groups.io
Subject: [N1MM+] CQ WW RTTY Contest ADIF Logs

We’ve added an ADIF Converter webpage to the CQ WW RTTY Contest website and would like to test it with some N1MM+ Logger ADIF logs.  Please export an ADIF of your log from last weekend and email it to me.  Or, if you’d like, try the converter yourself.

 

                https://www.cqwwrtty.com/adif/

 

One concern is whether the QTH exchange field is provided (US state, VE area or ‘DX’).

 

73,

Ed W0YK

 


Re: CQ WW RTTY Contest ADIF Logs

Phil Cooper
 

Hi Ed,

 

After running through the process, and getting to the bit where it produces the Cabrillo file, I noted that DX (ie non-US/VE stations) were correctly identified as DX, but it also put DX against all my US/VE contacts too.

 

From what I could see, it asks for a sample of the CQ Zone, and a sample of the "Received Location", but the choices available don't seem to cater for what N1MM produces in the ADIF file, which is (for example) <STATE:2>MA.

 

If I choose the default of AUTO:DX it places DX against all US/VE calls, rather than the State, as per the instructions. However, I note that it says " Select ADIF field that contains received State/Province", but I can't seem to navigate to anything other than the first contact in the ADIF file.

 

73 de Phil GU0SUP

 

 

 

-----Original Message-----
From: "Ed Muns, W0YK" <ed@...>
Sent: Tuesday, 29 September, 2020 13:10
To: N1MMLoggerPlus@groups.io
Subject: [N1MM+] CQ WW RTTY Contest ADIF Logs

We’ve added an ADIF Converter webpage to the CQ WW RTTY Contest website and would like to test it with some N1MM+ Logger ADIF logs.  Please export an ADIF of your log from last weekend and email it to me.  Or, if you’d like, try the converter yourself.

 

                https://www.cqwwrtty.com/adif/

 

One concern is whether the QTH exchange field is provided (US state, VE area or ‘DX’).

 

73,

Ed W0YK

 


Re: CQ WW RTTY Contest ADIF Logs

ve3ki
 

Tim,

If you use the "Export ADIF to file by date to from ALL contests" option to export an ADIF file, you can almost count on having problems with the contest exchange and CONTEST_ID fields. The "export from all contests" routine does not look at each QSO to determine which contest it was logged in and decide what ADIF tags are needed for contest-specific items in the database. If you want the contest-related data (such as the exchange) to be handled correctly, you should export each contest log individually. Perhaps this is an explanation for the defective ADIF files Ed reported, i.e. perhaps people were using the "export from all contests" option instead of the basic "export the current contest" option.

73,
Rich VE3KI


On Tue, Sep 29, 2020 at 11:48 AM, Tim Shoppa wrote:
Just to show how complicated it can be, I switched from my WW RTTY log to my General-purpose DX N1MM log, then did an ADIF export of all contests starting with 0000Z Friday night.  The CONTEST_ID comes out as CQ-WW-RTTY. The state comes out, but in ARRL_SECT, not in STATE.
 
Then I switched to a CWT log and did an ADIF export of all contests again starting with 0000Z Friday night. The CONTEST_ID comes out as CQ-WW-RTTY. The state doesn't appear anywhere at all in this ADIF.
 
I'm not saying any of the N1MM behavior is wrong, I'm just saying ADIF export depends on the context of the current contest (not the context of a past contest) even though CONTEST_ID is there and correct for the past contest being exported.
 
I use N1MM more than anyone else in the world (except AA3B) so I kind of understand it's internal model and why it does it does, but it might surprise other less regular contesters (which is everybody in the world except for AA3B and me) to see it work this way.
 
Tim N3QE

On Tue, Sep 29, 2020 at 11:15 AM ve3ki <ve3iay@...> wrote:
Yes. You can check for this in the ADIF file by looking at the CONTEST_ID field.

73,
Rich VE3KI


On Tue, Sep 29, 2020 at 11:08 AM, Tim Shoppa wrote:
There is also a very good chance someone tried to use CQ WW CW logger or some zone-but-no-state RTTY logger to log the WW RTTY contest and that's why there's no states recorded anywhere in the ADIF.
 
I can tell you (as a club secretary) that a couple percent of hams start the contest with the wrong log and need help fixing everything up. Very common is for someone to start CQ WW SSB with CQ WPX SSB and they don't know until they are hundreds of QSO's in that they have been typing in zone numbers into the serial number box.
 
Tim N3QE

On Tue, Sep 29, 2020 at 10:11 AM ve3ki <ve3iay@...> wrote:
N1MM Logger has exported the state/province part of the CQ WW RTTY exchange to ADIF using the STATE tag since 2014 or before (I just tested it with N1MM Logger Classic version 14.9.0). In fact, it looks to me from the revision history as though this change to do this was made in 2003 (version 3.0.97). I doubt whether anyone is using a version that old, but you never know...

73,
Rich VE3KI

On Tue, Sep 29, 2020 at 09:53 AM, Tim Shoppa wrote:
Ed, I’m guessing an older version of N1MM? There have been several recent (last year or so) improvements in N1MM ADIF exports in an attempt to somehow encode all parts of the exchange (including location I recall)  in a more useful way for general purpose logger import.
 
Tim N3QE

On Sep 29, 2020, at 9:36 AM, Ed Muns, W0YK <ed@...> wrote:

Thanks much Tim.  We got some ADIF logs from N1MM Logger that didn't have the QTH field.  How could that happen?
 
73,
Ed W0YK
 
 
-------- Original message --------
From: Tim Shoppa <tshoppa@...>
Date: 9/29/20 05:54 (GMT-08:00)
Subject: Re: [N1MM+] CQ WW RTTY Contest ADIF Logs
 
Ed, I did a "diff" between N1MM's native Cabrillo export, and the N1MM's ADIF run through the Cabrillo converter.
 
The only differences in the QSO: lines were superficial, like whether there's a leading zero on the zone, or how frequencies are rounded off.
 
For example N1MM will round off frequencies to the nearest kHz, and the ADIF converter always rounds down ("floor"). e.g. 14.08573 shows up as "14086" in N1MM Cabrillo, and as "14085" in ADIF->Cabrillo conversion. I don't think the Cabrillo spec says which way we are supposed to round anyway.
 
The pulldowns, based on the users actual ADIF, to let the user decide which ADIF fields have state and zone, that actually seems pretty nifty and is an inspired solution to a hairy problem. They defaulted to the correct fields for my ADIF which started with a USA call. If the pulldown was based on the first US/VE QSO that might be marginally better than letting it use the very first ADIF QSO which might not be US/VE.
 
This converter seems like it'll be more broadly useful for WW Digi than for WW RTTY. But maybe there's more loggers out there today than a decade ago, that only do ADIF exports.
 
Tim N3QE

On Tue, Sep 29, 2020 at 8:10 AM Ed Muns, W0YK <ed@...> wrote:

We’ve added an ADIF Converter webpage to the CQ WW RTTY Contest website and would like to test it with some N1MM+ Logger ADIF logs.  Please export an ADIF of your log from last weekend and email it to me.  Or, if you’d like, try the converter yourself.

 

                https://www.cqwwrtty.com/adif/

 

One concern is whether the QTH exchange field is provided (US state, VE area or ‘DX’).

 

73,

Ed W0YK

 

 

 

 

 

 

 


(offlist) CQ contest names

Tim Shoppa
 

It doesn't help that all 10 of the CQ contest names formally start with "CQ World-Wide (whatever)."

A lot of us say WPX not CQ WW WPX but we are being slackers and not saying the full contest name.

If the contest name was just "WPX" or "WW" it would help a little.


On Tue, Sep 29, 2020 at 11:50 AM Ed Muns, W0YK <ed@...> wrote:
Oh, yes, I'm well aware of these and many other anomalies.  I've cleaned up thousands of mangled logs over my contest admin tenure!

73,
Ed W0YK


-------- Original message --------
From: Tim Shoppa <tshoppa@...>
Date: 9/29/20 08:07 (GMT-08:00)
Subject: Re: [N1MM+] CQ WW RTTY Contest ADIF Logs

There is also a very good chance someone tried to use CQ WW CW logger or some zone-but-no-state RTTY logger to log the WW RTTY contest and that's why there's no states recorded anywhere in the ADIF.

I can tell you (as a club secretary) that a couple percent of hams start the contest with the wrong log and need help fixing everything up. Very common is for someone to start CQ WW SSB with CQ WPX SSB and they don't know until they are hundreds of QSO's in that they have been typing in zone numbers into the serial number box.

Tim N3QE

On Tue, Sep 29, 2020 at 10:11 AM ve3ki <ve3iay@...> wrote:
N1MM Logger has exported the state/province part of the CQ WW RTTY exchange to ADIF using the STATE tag since 2014 or before (I just tested it with N1MM Logger Classic version 14.9.0). In fact, it looks to me from the revision history as though this change to do this was made in 2003 (version 3.0.97). I doubt whether anyone is using a version that old, but you never know...

73,
Rich VE3KI

On Tue, Sep 29, 2020 at 09:53 AM, Tim Shoppa wrote:
Ed, I’m guessing an older version of N1MM? There have been several recent (last year or so) improvements in N1MM ADIF exports in an attempt to somehow encode all parts of the exchange (including location I recall)  in a more useful way for general purpose logger import.
 
Tim N3QE

On Sep 29, 2020, at 9:36 AM, Ed Muns, W0YK <ed@...> wrote:

Thanks much Tim.  We got some ADIF logs from N1MM Logger that didn't have the QTH field.  How could that happen?
 
73,
Ed W0YK
 
 
-------- Original message --------
From: Tim Shoppa <tshoppa@...>
Date: 9/29/20 05:54 (GMT-08:00)
Subject: Re: [N1MM+] CQ WW RTTY Contest ADIF Logs
 
Ed, I did a "diff" between N1MM's native Cabrillo export, and the N1MM's ADIF run through the Cabrillo converter.
 
The only differences in the QSO: lines were superficial, like whether there's a leading zero on the zone, or how frequencies are rounded off.
 
For example N1MM will round off frequencies to the nearest kHz, and the ADIF converter always rounds down ("floor"). e.g. 14.08573 shows up as "14086" in N1MM Cabrillo, and as "14085" in ADIF->Cabrillo conversion. I don't think the Cabrillo spec says which way we are supposed to round anyway.
 
The pulldowns, based on the users actual ADIF, to let the user decide which ADIF fields have state and zone, that actually seems pretty nifty and is an inspired solution to a hairy problem. They defaulted to the correct fields for my ADIF which started with a USA call. If the pulldown was based on the first US/VE QSO that might be marginally better than letting it use the very first ADIF QSO which might not be US/VE.
 
This converter seems like it'll be more broadly useful for WW Digi than for WW RTTY. But maybe there's more loggers out there today than a decade ago, that only do ADIF exports.
 
Tim N3QE

On Tue, Sep 29, 2020 at 8:10 AM Ed Muns, W0YK <ed@...> wrote:

We’ve added an ADIF Converter webpage to the CQ WW RTTY Contest website and would like to test it with some N1MM+ Logger ADIF logs.  Please export an ADIF of your log from last weekend and email it to me.  Or, if you’d like, try the converter yourself.

 

                https://www.cqwwrtty.com/adif/

 

One concern is whether the QTH exchange field is provided (US state, VE area or ‘DX’).

 

73,

Ed W0YK

 

 

 


Re: CQ WW RTTY Contest ADIF Logs

Ed Muns, W0YK
 

Oh, yes, I'm well aware of these and many other anomalies.  I've cleaned up thousands of mangled logs over my contest admin tenure!

73,
Ed W0YK


-------- Original message --------
From: Tim Shoppa <tshoppa@...>
Date: 9/29/20 08:07 (GMT-08:00)
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MM+] CQ WW RTTY Contest ADIF Logs

There is also a very good chance someone tried to use CQ WW CW logger or some zone-but-no-state RTTY logger to log the WW RTTY contest and that's why there's no states recorded anywhere in the ADIF.

I can tell you (as a club secretary) that a couple percent of hams start the contest with the wrong log and need help fixing everything up. Very common is for someone to start CQ WW SSB with CQ WPX SSB and they don't know until they are hundreds of QSO's in that they have been typing in zone numbers into the serial number box.

Tim N3QE

On Tue, Sep 29, 2020 at 10:11 AM ve3ki <ve3iay@...> wrote:
N1MM Logger has exported the state/province part of the CQ WW RTTY exchange to ADIF using the STATE tag since 2014 or before (I just tested it with N1MM Logger Classic version 14.9.0). In fact, it looks to me from the revision history as though this change to do this was made in 2003 (version 3.0.97). I doubt whether anyone is using a version that old, but you never know...

73,
Rich VE3KI

On Tue, Sep 29, 2020 at 09:53 AM, Tim Shoppa wrote:
Ed, I’m guessing an older version of N1MM? There have been several recent (last year or so) improvements in N1MM ADIF exports in an attempt to somehow encode all parts of the exchange (including location I recall)  in a more useful way for general purpose logger import.
 
Tim N3QE

On Sep 29, 2020, at 9:36 AM, Ed Muns, W0YK <ed@...> wrote:

Thanks much Tim.  We got some ADIF logs from N1MM Logger that didn't have the QTH field.  How could that happen?
 
73,
Ed W0YK
 
 
-------- Original message --------
From: Tim Shoppa <tshoppa@...>
Date: 9/29/20 05:54 (GMT-08:00)
Subject: Re: [N1MM+] CQ WW RTTY Contest ADIF Logs
 
Ed, I did a "diff" between N1MM's native Cabrillo export, and the N1MM's ADIF run through the Cabrillo converter.
 
The only differences in the QSO: lines were superficial, like whether there's a leading zero on the zone, or how frequencies are rounded off.
 
For example N1MM will round off frequencies to the nearest kHz, and the ADIF converter always rounds down ("floor"). e.g. 14.08573 shows up as "14086" in N1MM Cabrillo, and as "14085" in ADIF->Cabrillo conversion. I don't think the Cabrillo spec says which way we are supposed to round anyway.
 
The pulldowns, based on the users actual ADIF, to let the user decide which ADIF fields have state and zone, that actually seems pretty nifty and is an inspired solution to a hairy problem. They defaulted to the correct fields for my ADIF which started with a USA call. If the pulldown was based on the first US/VE QSO that might be marginally better than letting it use the very first ADIF QSO which might not be US/VE.
 
This converter seems like it'll be more broadly useful for WW Digi than for WW RTTY. But maybe there's more loggers out there today than a decade ago, that only do ADIF exports.
 
Tim N3QE

On Tue, Sep 29, 2020 at 8:10 AM Ed Muns, W0YK <ed@...> wrote:

We’ve added an ADIF Converter webpage to the CQ WW RTTY Contest website and would like to test it with some N1MM+ Logger ADIF logs.  Please export an ADIF of your log from last weekend and email it to me.  Or, if you’d like, try the converter yourself.

 

                https://www.cqwwrtty.com/adif/

 

One concern is whether the QTH exchange field is provided (US state, VE area or ‘DX’).

 

73,

Ed W0YK

 

 

 


Re: CQ WW RTTY Contest ADIF Logs

Tim Shoppa
 

Just to show how complicated it can be, I switched from my WW RTTY log to my General-purpose DX N1MM log, then did an ADIF export of all contests starting with 0000Z Friday night.  The CONTEST_ID comes out as CQ-WW-RTTY. The state comes out, but in ARRL_SECT, not in STATE.

Then I switched to a CWT log and did an ADIF export of all contests again starting with 0000Z Friday night. The CONTEST_ID comes out as CQ-WW-RTTY. The state doesn't appear anywhere at all in this ADIF.

I'm not saying any of the N1MM behavior is wrong, I'm just saying ADIF export depends on the context of the current contest (not the context of a past contest) even though CONTEST_ID is there and correct for the past contest being exported.

I use N1MM more than anyone else in the world (except AA3B) so I kind of understand it's internal model and why it does it does, but it might surprise other less regular contesters (which is everybody in the world except for AA3B and me) to see it work this way.

Tim N3QE


On Tue, Sep 29, 2020 at 11:15 AM ve3ki <ve3iay@...> wrote:
Yes. You can check for this in the ADIF file by looking at the CONTEST_ID field.

73,
Rich VE3KI


On Tue, Sep 29, 2020 at 11:08 AM, Tim Shoppa wrote:
There is also a very good chance someone tried to use CQ WW CW logger or some zone-but-no-state RTTY logger to log the WW RTTY contest and that's why there's no states recorded anywhere in the ADIF.
 
I can tell you (as a club secretary) that a couple percent of hams start the contest with the wrong log and need help fixing everything up. Very common is for someone to start CQ WW SSB with CQ WPX SSB and they don't know until they are hundreds of QSO's in that they have been typing in zone numbers into the serial number box.
 
Tim N3QE

On Tue, Sep 29, 2020 at 10:11 AM ve3ki <ve3iay@...> wrote:
N1MM Logger has exported the state/province part of the CQ WW RTTY exchange to ADIF using the STATE tag since 2014 or before (I just tested it with N1MM Logger Classic version 14.9.0). In fact, it looks to me from the revision history as though this change to do this was made in 2003 (version 3.0.97). I doubt whether anyone is using a version that old, but you never know...

73,
Rich VE3KI

On Tue, Sep 29, 2020 at 09:53 AM, Tim Shoppa wrote:
Ed, I’m guessing an older version of N1MM? There have been several recent (last year or so) improvements in N1MM ADIF exports in an attempt to somehow encode all parts of the exchange (including location I recall)  in a more useful way for general purpose logger import.
 
Tim N3QE

On Sep 29, 2020, at 9:36 AM, Ed Muns, W0YK <ed@...> wrote:

Thanks much Tim.  We got some ADIF logs from N1MM Logger that didn't have the QTH field.  How could that happen?
 
73,
Ed W0YK
 
 
-------- Original message --------
From: Tim Shoppa <tshoppa@...>
Date: 9/29/20 05:54 (GMT-08:00)
Subject: Re: [N1MM+] CQ WW RTTY Contest ADIF Logs
 
Ed, I did a "diff" between N1MM's native Cabrillo export, and the N1MM's ADIF run through the Cabrillo converter.
 
The only differences in the QSO: lines were superficial, like whether there's a leading zero on the zone, or how frequencies are rounded off.
 
For example N1MM will round off frequencies to the nearest kHz, and the ADIF converter always rounds down ("floor"). e.g. 14.08573 shows up as "14086" in N1MM Cabrillo, and as "14085" in ADIF->Cabrillo conversion. I don't think the Cabrillo spec says which way we are supposed to round anyway.
 
The pulldowns, based on the users actual ADIF, to let the user decide which ADIF fields have state and zone, that actually seems pretty nifty and is an inspired solution to a hairy problem. They defaulted to the correct fields for my ADIF which started with a USA call. If the pulldown was based on the first US/VE QSO that might be marginally better than letting it use the very first ADIF QSO which might not be US/VE.
 
This converter seems like it'll be more broadly useful for WW Digi than for WW RTTY. But maybe there's more loggers out there today than a decade ago, that only do ADIF exports.
 
Tim N3QE

On Tue, Sep 29, 2020 at 8:10 AM Ed Muns, W0YK <ed@...> wrote:

We’ve added an ADIF Converter webpage to the CQ WW RTTY Contest website and would like to test it with some N1MM+ Logger ADIF logs.  Please export an ADIF of your log from last weekend and email it to me.  Or, if you’d like, try the converter yourself.

 

                https://www.cqwwrtty.com/adif/

 

One concern is whether the QTH exchange field is provided (US state, VE area or ‘DX’).

 

73,

Ed W0YK

 

 

 

 

 


Re: Crash during WW RTTY contest #n1mm

Jim Denneny
 

I had same lockup until I realized N1MM RTTY MMTTY was decoding LOTONES and K3  FSK D setting was forHITONES.  Changed K3s to LOTONES and all was well

73, Jim K7EG


Re: CQ WW RTTY Contest ADIF Logs

ve3ki
 

Yes. You can check for this in the ADIF file by looking at the CONTEST_ID field.

73,
Rich VE3KI


On Tue, Sep 29, 2020 at 11:08 AM, Tim Shoppa wrote:
There is also a very good chance someone tried to use CQ WW CW logger or some zone-but-no-state RTTY logger to log the WW RTTY contest and that's why there's no states recorded anywhere in the ADIF.
 
I can tell you (as a club secretary) that a couple percent of hams start the contest with the wrong log and need help fixing everything up. Very common is for someone to start CQ WW SSB with CQ WPX SSB and they don't know until they are hundreds of QSO's in that they have been typing in zone numbers into the serial number box.
 
Tim N3QE

On Tue, Sep 29, 2020 at 10:11 AM ve3ki <ve3iay@...> wrote:
N1MM Logger has exported the state/province part of the CQ WW RTTY exchange to ADIF using the STATE tag since 2014 or before (I just tested it with N1MM Logger Classic version 14.9.0). In fact, it looks to me from the revision history as though this change to do this was made in 2003 (version 3.0.97). I doubt whether anyone is using a version that old, but you never know...

73,
Rich VE3KI

On Tue, Sep 29, 2020 at 09:53 AM, Tim Shoppa wrote:
Ed, I’m guessing an older version of N1MM? There have been several recent (last year or so) improvements in N1MM ADIF exports in an attempt to somehow encode all parts of the exchange (including location I recall)  in a more useful way for general purpose logger import.
 
Tim N3QE

On Sep 29, 2020, at 9:36 AM, Ed Muns, W0YK <ed@...> wrote:

Thanks much Tim.  We got some ADIF logs from N1MM Logger that didn't have the QTH field.  How could that happen?
 
73,
Ed W0YK
 
 
-------- Original message --------
From: Tim Shoppa <tshoppa@...>
Date: 9/29/20 05:54 (GMT-08:00)
Subject: Re: [N1MM+] CQ WW RTTY Contest ADIF Logs
 
Ed, I did a "diff" between N1MM's native Cabrillo export, and the N1MM's ADIF run through the Cabrillo converter.
 
The only differences in the QSO: lines were superficial, like whether there's a leading zero on the zone, or how frequencies are rounded off.
 
For example N1MM will round off frequencies to the nearest kHz, and the ADIF converter always rounds down ("floor"). e.g. 14.08573 shows up as "14086" in N1MM Cabrillo, and as "14085" in ADIF->Cabrillo conversion. I don't think the Cabrillo spec says which way we are supposed to round anyway.
 
The pulldowns, based on the users actual ADIF, to let the user decide which ADIF fields have state and zone, that actually seems pretty nifty and is an inspired solution to a hairy problem. They defaulted to the correct fields for my ADIF which started with a USA call. If the pulldown was based on the first US/VE QSO that might be marginally better than letting it use the very first ADIF QSO which might not be US/VE.
 
This converter seems like it'll be more broadly useful for WW Digi than for WW RTTY. But maybe there's more loggers out there today than a decade ago, that only do ADIF exports.
 
Tim N3QE

On Tue, Sep 29, 2020 at 8:10 AM Ed Muns, W0YK <ed@...> wrote:

We’ve added an ADIF Converter webpage to the CQ WW RTTY Contest website and would like to test it with some N1MM+ Logger ADIF logs.  Please export an ADIF of your log from last weekend and email it to me.  Or, if you’d like, try the converter yourself.

 

                https://www.cqwwrtty.com/adif/

 

One concern is whether the QTH exchange field is provided (US state, VE area or ‘DX’).

 

73,

Ed W0YK

 

 

 

 

 


Re: CQ WW RTTY Contest ADIF Logs

Tim Shoppa
 

There is also a very good chance someone tried to use CQ WW CW logger or some zone-but-no-state RTTY logger to log the WW RTTY contest and that's why there's no states recorded anywhere in the ADIF.

I can tell you (as a club secretary) that a couple percent of hams start the contest with the wrong log and need help fixing everything up. Very common is for someone to start CQ WW SSB with CQ WPX SSB and they don't know until they are hundreds of QSO's in that they have been typing in zone numbers into the serial number box.

Tim N3QE

On Tue, Sep 29, 2020 at 10:11 AM ve3ki <ve3iay@...> wrote:
N1MM Logger has exported the state/province part of the CQ WW RTTY exchange to ADIF using the STATE tag since 2014 or before (I just tested it with N1MM Logger Classic version 14.9.0). In fact, it looks to me from the revision history as though this change to do this was made in 2003 (version 3.0.97). I doubt whether anyone is using a version that old, but you never know...

73,
Rich VE3KI

On Tue, Sep 29, 2020 at 09:53 AM, Tim Shoppa wrote:
Ed, I’m guessing an older version of N1MM? There have been several recent (last year or so) improvements in N1MM ADIF exports in an attempt to somehow encode all parts of the exchange (including location I recall)  in a more useful way for general purpose logger import.
 
Tim N3QE

On Sep 29, 2020, at 9:36 AM, Ed Muns, W0YK <ed@...> wrote:

Thanks much Tim.  We got some ADIF logs from N1MM Logger that didn't have the QTH field.  How could that happen?
 
73,
Ed W0YK
 
 
-------- Original message --------
From: Tim Shoppa <tshoppa@...>
Date: 9/29/20 05:54 (GMT-08:00)
Subject: Re: [N1MM+] CQ WW RTTY Contest ADIF Logs
 
Ed, I did a "diff" between N1MM's native Cabrillo export, and the N1MM's ADIF run through the Cabrillo converter.
 
The only differences in the QSO: lines were superficial, like whether there's a leading zero on the zone, or how frequencies are rounded off.
 
For example N1MM will round off frequencies to the nearest kHz, and the ADIF converter always rounds down ("floor"). e.g. 14.08573 shows up as "14086" in N1MM Cabrillo, and as "14085" in ADIF->Cabrillo conversion. I don't think the Cabrillo spec says which way we are supposed to round anyway.
 
The pulldowns, based on the users actual ADIF, to let the user decide which ADIF fields have state and zone, that actually seems pretty nifty and is an inspired solution to a hairy problem. They defaulted to the correct fields for my ADIF which started with a USA call. If the pulldown was based on the first US/VE QSO that might be marginally better than letting it use the very first ADIF QSO which might not be US/VE.
 
This converter seems like it'll be more broadly useful for WW Digi than for WW RTTY. But maybe there's more loggers out there today than a decade ago, that only do ADIF exports.
 
Tim N3QE

On Tue, Sep 29, 2020 at 8:10 AM Ed Muns, W0YK <ed@...> wrote:

We’ve added an ADIF Converter webpage to the CQ WW RTTY Contest website and would like to test it with some N1MM+ Logger ADIF logs.  Please export an ADIF of your log from last weekend and email it to me.  Or, if you’d like, try the converter yourself.

 

                https://www.cqwwrtty.com/adif/

 

One concern is whether the QTH exchange field is provided (US state, VE area or ‘DX’).

 

73,

Ed W0YK

 

 

 


Re: CQ WW RTTY Contest ADIF Logs

ve3ki
 

N1MM Logger has exported the state/province part of the CQ WW RTTY exchange to ADIF using the STATE tag since 2014 or before (I just tested it with N1MM Logger Classic version 14.9.0). In fact, it looks to me from the revision history as though this change to do this was made in 2003 (version 3.0.97). I doubt whether anyone is using a version that old, but you never know...

73,
Rich VE3KI


On Tue, Sep 29, 2020 at 09:53 AM, Tim Shoppa wrote:
Ed, I’m guessing an older version of N1MM? There have been several recent (last year or so) improvements in N1MM ADIF exports in an attempt to somehow encode all parts of the exchange (including location I recall)  in a more useful way for general purpose logger import.
 
Tim N3QE

On Sep 29, 2020, at 9:36 AM, Ed Muns, W0YK <ed@...> wrote:

Thanks much Tim.  We got some ADIF logs from N1MM Logger that didn't have the QTH field.  How could that happen?
 
73,
Ed W0YK
 
 
-------- Original message --------
From: Tim Shoppa <tshoppa@...>
Date: 9/29/20 05:54 (GMT-08:00)
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MM+] CQ WW RTTY Contest ADIF Logs
 
Ed, I did a "diff" between N1MM's native Cabrillo export, and the N1MM's ADIF run through the Cabrillo converter.
 
The only differences in the QSO: lines were superficial, like whether there's a leading zero on the zone, or how frequencies are rounded off.
 
For example N1MM will round off frequencies to the nearest kHz, and the ADIF converter always rounds down ("floor"). e.g. 14.08573 shows up as "14086" in N1MM Cabrillo, and as "14085" in ADIF->Cabrillo conversion. I don't think the Cabrillo spec says which way we are supposed to round anyway.
 
The pulldowns, based on the users actual ADIF, to let the user decide which ADIF fields have state and zone, that actually seems pretty nifty and is an inspired solution to a hairy problem. They defaulted to the correct fields for my ADIF which started with a USA call. If the pulldown was based on the first US/VE QSO that might be marginally better than letting it use the very first ADIF QSO which might not be US/VE.
 
This converter seems like it'll be more broadly useful for WW Digi than for WW RTTY. But maybe there's more loggers out there today than a decade ago, that only do ADIF exports.
 
Tim N3QE

On Tue, Sep 29, 2020 at 8:10 AM Ed Muns, W0YK <ed@...> wrote:

We’ve added an ADIF Converter webpage to the CQ WW RTTY Contest website and would like to test it with some N1MM+ Logger ADIF logs.  Please export an ADIF of your log from last weekend and email it to me.  Or, if you’d like, try the converter yourself.

 

                https://www.cqwwrtty.com/adif/

 

One concern is whether the QTH exchange field is provided (US state, VE area or ‘DX’).

 

73,

Ed W0YK

 

 

 


Re: CQ WW RTTY Contest ADIF Logs

Tim Shoppa
 

Ed, I’m guessing an older version of N1MM? There have been several recent (last year or so) improvements in N1MM ADIF exports in an attempt to somehow encode all parts of the exchange (including location I recall)  in a more useful way for general purpose logger import.

Tim N3QE

On Sep 29, 2020, at 9:36 AM, Ed Muns, W0YK <ed@...> wrote:


Thanks much Tim.  We got some ADIF logs from N1MM Logger that didn't have the QTH field.  How could that happen?

73,
Ed W0YK


-------- Original message --------
From: Tim Shoppa <tshoppa@...>
Date: 9/29/20 05:54 (GMT-08:00)
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MM+] CQ WW RTTY Contest ADIF Logs

Ed, I did a "diff" between N1MM's native Cabrillo export, and the N1MM's ADIF run through the Cabrillo converter.

The only differences in the QSO: lines were superficial, like whether there's a leading zero on the zone, or how frequencies are rounded off.

For example N1MM will round off frequencies to the nearest kHz, and the ADIF converter always rounds down ("floor"). e.g. 14.08573 shows up as "14086" in N1MM Cabrillo, and as "14085" in ADIF->Cabrillo conversion. I don't think the Cabrillo spec says which way we are supposed to round anyway.

The pulldowns, based on the users actual ADIF, to let the user decide which ADIF fields have state and zone, that actually seems pretty nifty and is an inspired solution to a hairy problem. They defaulted to the correct fields for my ADIF which started with a USA call. If the pulldown was based on the first US/VE QSO that might be marginally better than letting it use the very first ADIF QSO which might not be US/VE.

This converter seems like it'll be more broadly useful for WW Digi than for WW RTTY. But maybe there's more loggers out there today than a decade ago, that only do ADIF exports.

Tim N3QE

On Tue, Sep 29, 2020 at 8:10 AM Ed Muns, W0YK <ed@...> wrote:

We’ve added an ADIF Converter webpage to the CQ WW RTTY Contest website and would like to test it with some N1MM+ Logger ADIF logs.  Please export an ADIF of your log from last weekend and email it to me.  Or, if you’d like, try the converter yourself.

 

                https://www.cqwwrtty.com/adif/

 

One concern is whether the QTH exchange field is provided (US state, VE area or ‘DX’).

 

73,

Ed W0YK

 


Re: CQ WW RTTY Contest ADIF Logs

Ed Muns, W0YK
 

Thanks much Tim.  We got some ADIF logs from N1MM Logger that didn't have the QTH field.  How could that happen?

73,
Ed W0YK


-------- Original message --------
From: Tim Shoppa <tshoppa@...>
Date: 9/29/20 05:54 (GMT-08:00)
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MM+] CQ WW RTTY Contest ADIF Logs

Ed, I did a "diff" between N1MM's native Cabrillo export, and the N1MM's ADIF run through the Cabrillo converter.

The only differences in the QSO: lines were superficial, like whether there's a leading zero on the zone, or how frequencies are rounded off.

For example N1MM will round off frequencies to the nearest kHz, and the ADIF converter always rounds down ("floor"). e.g. 14.08573 shows up as "14086" in N1MM Cabrillo, and as "14085" in ADIF->Cabrillo conversion. I don't think the Cabrillo spec says which way we are supposed to round anyway.

The pulldowns, based on the users actual ADIF, to let the user decide which ADIF fields have state and zone, that actually seems pretty nifty and is an inspired solution to a hairy problem. They defaulted to the correct fields for my ADIF which started with a USA call. If the pulldown was based on the first US/VE QSO that might be marginally better than letting it use the very first ADIF QSO which might not be US/VE.

This converter seems like it'll be more broadly useful for WW Digi than for WW RTTY. But maybe there's more loggers out there today than a decade ago, that only do ADIF exports.

Tim N3QE

On Tue, Sep 29, 2020 at 8:10 AM Ed Muns, W0YK <ed@...> wrote:

We’ve added an ADIF Converter webpage to the CQ WW RTTY Contest website and would like to test it with some N1MM+ Logger ADIF logs.  Please export an ADIF of your log from last weekend and email it to me.  Or, if you’d like, try the converter yourself.

 

                https://www.cqwwrtty.com/adif/

 

One concern is whether the QTH exchange field is provided (US state, VE area or ‘DX’).

 

73,

Ed W0YK

 


Re: CQ WW RTTY Contest ADIF Logs

Tim Shoppa
 

Ed, I did a "diff" between N1MM's native Cabrillo export, and the N1MM's ADIF run through the Cabrillo converter.

The only differences in the QSO: lines were superficial, like whether there's a leading zero on the zone, or how frequencies are rounded off.

For example N1MM will round off frequencies to the nearest kHz, and the ADIF converter always rounds down ("floor"). e.g. 14.08573 shows up as "14086" in N1MM Cabrillo, and as "14085" in ADIF->Cabrillo conversion. I don't think the Cabrillo spec says which way we are supposed to round anyway.

The pulldowns, based on the users actual ADIF, to let the user decide which ADIF fields have state and zone, that actually seems pretty nifty and is an inspired solution to a hairy problem. They defaulted to the correct fields for my ADIF which started with a USA call. If the pulldown was based on the first US/VE QSO that might be marginally better than letting it use the very first ADIF QSO which might not be US/VE.

This converter seems like it'll be more broadly useful for WW Digi than for WW RTTY. But maybe there's more loggers out there today than a decade ago, that only do ADIF exports.

Tim N3QE

On Tue, Sep 29, 2020 at 8:10 AM Ed Muns, W0YK <ed@...> wrote:

We’ve added an ADIF Converter webpage to the CQ WW RTTY Contest website and would like to test it with some N1MM+ Logger ADIF logs.  Please export an ADIF of your log from last weekend and email it to me.  Or, if you’d like, try the converter yourself.

 

                https://www.cqwwrtty.com/adif/

 

One concern is whether the QTH exchange field is provided (US state, VE area or ‘DX’).

 

73,

Ed W0YK

 


Re: No RTTY

ve3ki
 

Pete,

If the MK's FSK LED is flashing but the radio is transmitting a single tone, that suggests that the problem is between the MK and the radio. I would suggest that you check the FSK keying connection from the MK to the K3's FSK keying input (pin 1 on the K3's ACC connector).

73,
Rich VE3KI


On Tue, Sep 29, 2020 at 08:18 AM, Pete W1RM wrote:

COM11 is a virtual port created by microHAM MicroKeyer for the sole purpose of FSK.  In the MicroHAM setup, COM11 is set for FSK with PTT selected.  WinKey is COM12.  I have a second CAT on COM17 for WSJT-X.  The N1MM Rotor is on COM7.

 

I removed COM11 from configurer and N1MM no longer complains.  However that did not fix the no RTTY TX issue.  When I transmit RTTY I only get a single tone.

 

Happily WSJT works OK.  But when I transmit RTTY, the microKeyerII shows pulsing for RTTY but the monitor in the K3S is just a single tone.

 

 

Pete, W1RM

W1RM@...

 

From: N1MMLoggerPlus@groups.io <N1MMLoggerPlus@groups.io> On Behalf Of ve3ki
Sent: Monday, September 28, 2020 7:27 PM
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MM+] No RTTY

 

Are you using COM11 only for FSK keying from a digital software engine such as MMTTY? If so, remove COM11 completely from the N1MM+ Configurer - there should be no mention of it there at all. If there is no need for N1MM+ itself to use it, then the only place it should be configured is in MMTTY (or, if MMTTY is using EXTFSK, in EXTFSK).

If you are time-sharing the port between CW in N1MM+ and FSK keying in MMTTY, then if you don't want to set up two separate configurations, you need to check the Digital check box for COM11 in the Configurer, and you probably will have to shut down the Digital Interface window first every time before closing down N1MM+, and start it up again only after the main N1MM+ program has started up and finished initialization. Otherwise, there is a chance that MMTTY or EXTFSK will open COM11 before N1MM+ gets that far along in its initialization, which will cause the error message. Opening N1MM+ first allows it to open the port, then close it again when you open the DI window so that MMTTY or EXTFSK can open it.

If you are using COM11 with a TinyFSK or Winkeyer 3.1, then I believe you might need to check the Digital check box beside COM11 in the Configurer.

One other thing - sometimes the Configurer emits that error message when it closes down even though you just removed the port from the configuration. Just ignore the message, close down N1MM+ and restart it to see if that clears things up.

73,
Rich VE3KI


On Mon, Sep 28, 2020 at 05:42 PM, Pete W1RM wrote:

I know I’ve done something to break this but I can’t seem to figure out why I don’t get any RTTY transmit.  When I go to save configure I get this message:

 

---------------------------

N1MMLogger.net

---------------------------

COM11 is in use by another program, but the port is also configured in N1MM Logger.

 

The COM port will not work in N1MM Logger until this is corrected.

---------------------------

OK  

 

Com11 is set to be digi with no radio selected.  I am set for so1v I am also set for digital Interface 1 soundcard interface 2 is none.  In the n1mm.ini file Digital 1 and Digital 2 ports are both set to com11.  I tried deleting digital 2 port but it came back.

 

I’m stumped and have no rtty transmit.

 

 

Pete, W1RM

W1RM@...

 

 


Re: Working Dupes without ESM

ve3ki
 

John,

I just tested this with all 8 possible combinations of CW vs RTTY, ESM vs non-ESM and "Work dupes" checked vs unchecked.

In RTTY with ESM turned off, the ; and Insert keys did not send the exchange, as Lee has reported. With ESM turned on, the exchange was sent. The "Work dupes" setting did not make any difference. 

In CW, regardless of whether ESM was on or off and regardless of the "Work dupes" setting, the ; and Insert keys always sent the exchange.

So, the issue is specific to digital modes with ESM off. With that one particular combination of choices, the ; and Insert keys do not send the exchange to a dupe.

73,
Rich VE3KI


On Tue, Sep 29, 2020 at 07:43 AM, John Bednar wrote:

Lee,

 

I just tested this using SO1V mode with the CQWW CW and PA QSO Party contests, ESM off, RUN mode, logging CW contacts.

 

The ; and ‘ keys allow me to work a dupe station.

 

John, K3CT

 

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of KY7M Lee
Sent: Monday, September 28, 2020 11:23 PM
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MM+] Working Dupes without ESM

 

I think I have figured out the issue.  I have the box checked in Configurer for Function Keys “Work dupes when running”.  I use the semicolon hot key to send the exchange when running and it normally send F5+F2.  The semicolon key does NOT work for me when working a  dupe while running.  If I press the F5 and F2 keys directly it DOES send for a dupe while running.  Something missing in the program??? 

 

The source of my confusion was that when you hover over that “Work dupes” check box you see the message “If this box is checked, ESM mode will let you work duplicate contacts when running” – thus my conclusion that it was only intended for ESM users.

 

Please excuse my confusion, but there is an issue using the semicolon hotkey when running and trying to work a dupe.

 

 

 

 


Re: CQ WW RTTY Contest ADIF Logs

John Eigenbrode
 

Ed,
Uploaded file appears to be a success.
73,
John W3SA


Re: No RTTY

Pete W1RM
 

COM11 is a virtual port created by microHAM MicroKeyer for the sole purpose of FSK.  In the MicroHAM setup, COM11 is set for FSK with PTT selected.  WinKey is COM12.  I have a second CAT on COM17 for WSJT-X.  The N1MM Rotor is on COM7.

 

I removed COM11 from configurer and N1MM no longer complains.  However that did not fix the no RTTY TX issue.  When I transmit RTTY I only get a single tone.

 

Happily WSJT works OK.  But when I transmit RTTY, the microKeyerII shows pulsing for RTTY but the monitor in the K3S is just a single tone.

 

 

Pete, W1RM

W1RM@...

 

From: N1MMLoggerPlus@groups.io <N1MMLoggerPlus@groups.io> On Behalf Of ve3ki
Sent: Monday, September 28, 2020 7:27 PM
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MM+] No RTTY

 

Are you using COM11 only for FSK keying from a digital software engine such as MMTTY? If so, remove COM11 completely from the N1MM+ Configurer - there should be no mention of it there at all. If there is no need for N1MM+ itself to use it, then the only place it should be configured is in MMTTY (or, if MMTTY is using EXTFSK, in EXTFSK).

If you are time-sharing the port between CW in N1MM+ and FSK keying in MMTTY, then if you don't want to set up two separate configurations, you need to check the Digital check box for COM11 in the Configurer, and you probably will have to shut down the Digital Interface window first every time before closing down N1MM+, and start it up again only after the main N1MM+ program has started up and finished initialization. Otherwise, there is a chance that MMTTY or EXTFSK will open COM11 before N1MM+ gets that far along in its initialization, which will cause the error message. Opening N1MM+ first allows it to open the port, then close it again when you open the DI window so that MMTTY or EXTFSK can open it.

If you are using COM11 with a TinyFSK or Winkeyer 3.1, then I believe you might need to check the Digital check box beside COM11 in the Configurer.

One other thing - sometimes the Configurer emits that error message when it closes down even though you just removed the port from the configuration. Just ignore the message, close down N1MM+ and restart it to see if that clears things up.

73,
Rich VE3KI


On Mon, Sep 28, 2020 at 05:42 PM, Pete W1RM wrote:

I know I’ve done something to break this but I can’t seem to figure out why I don’t get any RTTY transmit.  When I go to save configure I get this message:

 

---------------------------

N1MMLogger.net

---------------------------

COM11 is in use by another program, but the port is also configured in N1MM Logger.

 

The COM port will not work in N1MM Logger until this is corrected.

---------------------------

OK  

 

Com11 is set to be digi with no radio selected.  I am set for so1v I am also set for digital Interface 1 soundcard interface 2 is none.  In the n1mm.ini file Digital 1 and Digital 2 ports are both set to com11.  I tried deleting digital 2 port but it came back.

 

I’m stumped and have no rtty transmit.

 

 

Pete, W1RM

W1RM@...

 


CQ WW RTTY Contest ADIF Logs

Ed Muns, W0YK
 

We’ve added an ADIF Converter webpage to the CQ WW RTTY Contest website and would like to test it with some N1MM+ Logger ADIF logs.  Please export an ADIF of your log from last weekend and email it to me.  Or, if you’d like, try the converter yourself.

 

                https://www.cqwwrtty.com/adif/

 

One concern is whether the QTH exchange field is provided (US state, VE area or ‘DX’).

 

73,

Ed W0YK

 


locked Re: New Version

Tom - N1MM
 

Version 1.0.8672 (September 29, 2020)
  1. Corrects an issue that stopped the WSJT CAT from working with the --language setting being set. (Coded by N2AMG)
  2. ME QSO Party: Would not accept state as valid exch when generating Cabrillo (AC3LZ) (Coded by N1MM)
  3. Spectrum window: Fix "Warning Out of Range" message with SDRPlay SDRs (N6GP)


Re: Working Dupes without ESM

John Bednar
 

Lee,

 

I just tested this using SO1V mode with the CQWW CW and PA QSO Party contests, ESM off, RUN mode, logging CW contacts.

 

The ; and ‘ keys allow me to work a dupe station.

 

John, K3CT

 

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of KY7M Lee
Sent: Monday, September 28, 2020 11:23 PM
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MM+] Working Dupes without ESM

 

I think I have figured out the issue.  I have the box checked in Configurer for Function Keys “Work dupes when running”.  I use the semicolon hot key to send the exchange when running and it normally send F5+F2.  The semicolon key does NOT work for me when working a  dupe while running.  If I press the F5 and F2 keys directly it DOES send for a dupe while running.  Something missing in the program??? 

 

The source of my confusion was that when you hover over that “Work dupes” check box you see the message “If this box is checked, ESM mode will let you work duplicate contacts when running” – thus my conclusion that it was only intended for ESM users.

 

Please excuse my confusion, but there is an issue using the semicolon hotkey when running and trying to work a dupe.