Date   

Re: Auxiliary 'station call' flashing

Tim N3XX
 

Go to DXKeeper Config, Defaults tab. You can enter the station callsign there.

73,
Tim - N3XX

On 2020-09-05 2:45 PM, Max Cotton wrote:
In Dx keeper the blue station call is flashing, no matter what I do I cannot enter my callsign into the auxiliary boxes. TZ4AM was the call entered.
Help,
73 Max M0GHQ


Auxiliary 'station call' flashing

Max Cotton
 

In Dx keeper the blue station call is flashing, no matter what I do I cannot enter my callsign into the auxiliary boxes. TZ4AM was the call entered. 
Help,
73 Max M0GHQ


Re: WW and MMTTY RX Issue

Joe Subich, W4TV
 

Without knowing which setting had been changed, it is hard to say
what caused the problem. However, The MMTTY MARK frequency is
stored in MMTTY.INI - you have at least three copies (in N1MM+,
in the stand alone MMTTY directory, and in your WinWarbler directory) -
*and* in the Windows Registry entries for WinWarbler (plus your
"workspace" if you use that feature as recommended). If the issue
existed for all three applications, I would say the K3 pitch had
been changed.

The K3/K3S DATA/PITCH setting is not changed in the CONFIG menu -
it is changed using the "Pitch" key (SPOT/Hold) and VFO A while
the K3 is in DATA/DATA_A or DATA/FSK_D mode.

73,

... Joe, W4TV

On 2020-09-05 12:14 PM, Jim Denneny wrote:
Appreciate the analysis Joe.  I guess tone mismatch remains a mystery if root cause is not Win 10 upgrade. I have used these apps for years and never experienced high-low tone mismatch.  Also, it has been over a year since I was in the K3S CONFIG menu. You can be sure I will remain vigilant to this event. Thanks again to all who responded.
73, Jim K7EG


Re: WW and MMTTY RX Issue

Jim Denneny
 

Appreciate the analysis Joe.  I guess tone mismatch remains a mystery if root cause is not Win 10 upgrade. I have used these apps for years and never experienced high-low tone mismatch.  Also, it has been over a year since I was in the K3S CONFIG menu. You can be sure I will remain vigilant to this event. Thanks again to all who responded.

73, Jim K7EG


Re: WW and MMTTY RX Issue

Adrian Fewster <vk4tux@...>
 

Thanks Joe, I appreciate the reply and clarification.

On 5/9/20 10:25 pm, Joe Subich, W4TV wrote:

No, in this case it means that MMTTY was set for 2295/2125 (MMTTY
default) and the rig set for 1445/1275 (menu option).

73,

   ... Joe, W4TV


Re: Importing Log into DXKeeper

Joe Subich, W4TV
 

+ are invalid. As shown in the ADIF specification

<http://adif.org.uk/310/ADIF_310.htm#QSLSent_Enumeration>
Although not applicable in this discussion, ADIF 3.1.1 has
approved and released on 2 September:
<https://adif.org/311/ADIF_311_annotated.htm>

These changes from the previous version may necessitate application code or data changes:
Addition of the FST4 submode to the MFSK mode in the Mode and Submode Enumerations.
Addition of the 5m and 8m bands to the Band Enumeration.
Addition of ARRL-10-GHZ and WW-DIGI to the Contest-ID Enumeration.

73,

... Joe, W4TV


On 2020-09-05 1:03 AM, Dave AA6YQ wrote:
+ AA6YQ comments below
I'm having a hard time importing my old log into DXKeeper. Tried many times without success. Finally reworked the Excel and
converted to ADI. It would not accept.
+ Is your "old log" in Excel or in ADIF format?
Then attempted to upload the same file as a tab delimited *.txt file. Got the following error message:
"Illegal - too many fields in record:"
These are the fields in my log that I am trying to upload. What am I doing wrong?
Here is a sample record from the log.
<QSO_date:8>20000909 <Time_On:4>0154 <Time_Off:4>0156 <Freq:6>21.195 <Band:2>15 <Mode:3>SSB <Tx_Pwr:2>50
<Call:6>JG1PED <RST_sent:2>59 <RST_rcvd:2>59 <Name:4>TONY <QTH:8>YOKOHAMA <State:2>11 <Cnty:4>1101
<Comment:0> <QSL_sent:1>X <QSL_rcvd:1>- <Station_Callsign:6>VU2ABE <eor>
+ When I direct DXKeeper to import that record, the result is
"Illegal - imported frequency 21.195 doesn't match imported band 15"
+ That's because <Band:2>15 is not a valid ADIF field. The QSO is imported into DXKeeper, but with its "tx band" item empty, and
the "tx band" label flashing in red font (meaning "either select a valid band, or delete this QSO).
As you can see from the "Band enumeration" in the ADIF specification
<http://adif.org.uk/310/ADIF_310.htm#Band_Enumeration>
+ the correct specification for 15 meters is
<Band:3>15m
+ Correcting the band field enables DXKeeper to import the record without error. However,
<QSL_sent:1>X
+ and
<QSL_rcvd:1>-
+ are invalid. As shown in the ADIF specification
<http://adif.org.uk/310/ADIF_310.htm#QSLSent_Enumeration>
X is not a valid choice for QSL_sent, and hyphen is not a valid choice for QSL_rcvd. Unlike Band, which DXKeeper considers critical,
neither QSL_sent nor QSL_rcvd are considered critical, so they are simply ignored. Typically, one corrects problems like this in the
ADIF file "en masse" with a text editor (after making a backup copy of your original file). For example, you would change all
instances of
<QSL_sent:1>X
+ to whichever of the valid QSL_sent choices describe what "X" meant in your previous logging application:
<http://adif.org.uk/310/ADIF_310.htm#QSLSent_Enumeration>
+ Similarly, you'd change all instances of
<QSL_rcvd:1>-
+ to the appropriate choice from among these candidates:
<http://adif.org.uk/310/ADIF_310.htm#QSLRcvd_Enumeration>
+ For context, I suggest that you review these two articles:
<https://www.dxlabsuite.com/dxlabwiki/QSOImport>
<https://www.dxlabsuite.com/dxlabwiki/SwitchingToDXKeeper>
73,
Dave, AA6YQ


Re: WW and MMTTY RX Issue

Joe Subich, W4TV
 

No, in this case it means that MMTTY was set for 2295/2125 (MMTTY
default) and the rig set for 1445/1275 (menu option).

73,

... Joe, W4TV

On 2020-09-05 7:25 AM, Adrian Fewster wrote:
Does this mean that the mark/space afsk generated tones were reverse to the ssb choice used on the radio ?
On 5/9/20 12:13 pm, Adrian Fewster via groups.io wrote:

Jim, Can you let us know the actual setting parameter descriptions please in regard to below ?


On 5/9/20 11:53 am, Jim Denneny wrote:
Found root cause with the help of friend Bob Wilson N6TV
As reported earlier I could not understand why MMTTY, N1MM, and DXL WW could TX rtty but could not RX rtty. Radio was set for low tones & MMTTY was set for high tones. This disparity has never occurred before.
I suspect recent Win 10 August upgrade caused this event but impossible to prove

Jim Denneny K7EG


Re: LoTW upload not working

Phil Cooper
 

Dave,

 

I only twigged as when I rebooted, I had an error message  in the POST that said there was an overcurrent issue with USB, and it would shut down in 15s, which it did.

 

I was aware that one port was having a problem, as when plugging something in, it would only work intermittently.

 

73 de Phil GU0SUP

 

 

-----Original Message-----
From: "Dave AA6YQ" <aa6yq@...>
Sent: Saturday, 5 September, 2020 10:01
To: DXLab@groups.io
Subject: Re: [DXLab] LoTW upload not working

+ AA6YQ comments below

Thanks for the reply.

I did reboot Windows, and found that a USB port was causing a problem. I disabled the port (unplugged the feed from the motherboard), and that appears to have cured the issue.

+ "It's always something!"

73,

Dave, AA6YQ






Re: WW and MMTTY RX Issue

Jamie WW3S
 

no, not reversed.....different audio tones selected.....high tones are centered at 2125 hz, low tones at 1275 (or others)...much easier on the ears.....but the radio and software both need to be configured the same, so the audio stays within the passband,.....

------ Original Message ------
From: "Adrian Fewster" <vk4tux@...>
To: DXLab@groups.io
Sent: 9/5/2020 7:25:36 AM
Subject: Re: [DXLab] WW and MMTTY RX Issue

Does this mean that the mark/space afsk generated tones were reverse to the ssb choice used on the radio ?


On 5/9/20 12:13 pm, Adrian Fewster via groups.io wrote:

Jim, Can you let us know the actual setting parameter descriptions please in regard to below ?


On 5/9/20 11:53 am, Jim Denneny wrote:
Found root cause with the help of friend Bob Wilson N6TV
As reported earlier I could not understand why MMTTY, N1MM, and DXL WW could TX rtty but could not RX rtty. Radio was set for low tones & MMTTY was set for high tones. This disparity has never occurred before.
I suspect recent Win 10 August upgrade caused this event but impossible to prove

Jim Denneny K7EG


Re: WW and MMTTY RX Issue

Adrian Fewster <vk4tux@...>
 

Does this mean that the mark/space afsk generated tones were reverse to the ssb choice used on the radio ?

On 5/9/20 12:13 pm, Adrian Fewster via groups.io wrote:

Jim, Can you let us know the actual setting parameter descriptions please in regard to below ?


On 5/9/20 11:53 am, Jim Denneny wrote:
Found root cause with the help of friend Bob Wilson N6TV
As reported earlier I could not understand why MMTTY, N1MM, and DXL WW could TX rtty but could not RX rtty. Radio was set for low tones & MMTTY was set for high tones. This disparity has never occurred before.
I suspect recent Win 10 August upgrade caused this event but impossible to prove

Jim Denneny K7EG


DXKeeper is the best!

Abie Alexander
 

Hi Dave,

 

You deserve a Nobel Prize of for creating the best amateur radio logging program there is – DXKeeper.

 

After working for over a month on converting a self-made Paradox database created over 30 years ago to ADIF format for import into DXKeeper, I needed some help to get across the finish line. And Dave did not disappoint.

 

Was able to finally import the log going back 33 years ago into DXKeeper a short while ago and I am still marveling at the versatility of the program. In addition to DXCC, US, and Canadian reports, I was also able to run JCC, JCG, KDN, Russian, and other reports in a matter of minutes.

 

Absolutely delighted. And grateful. Many thanks, Dave!

 

73,

 

Abie/AB1F – VU2ABE

 


Re: LoTW upload not working

Dave AA6YQ
 

+ AA6YQ comments below

Thanks for the reply.

I did reboot Windows, and found that a USB port was causing a problem. I disabled the port (unplugged the feed from the motherboard), and that appears to have cured the issue.

+ "It's always something!"

73,

Dave, AA6YQ


Re: LoTW upload not working

Phil Cooper
 

Dave,

 

Thanks for the reply.

I did reboot Windows, and found that a USB port was causing a problem. I disabled the port (unplugged the feed from the motherboard), and that appears to have cured the issue.

Time to get that new PC out of the box I think!

 

73 de Phil GU0SUP

 

 

-----Original Message-----
From: "Dave AA6YQ" <aa6yq@...>
Sent: Friday, 4 September, 2020 22:18
To: DXLab@groups.io
Subject: Re: [DXLab] LoTW upload not working

+ AA6YQ comments below

Today, after making some contacts, I added the new QSO's using the ADD REQUESTED function, and directed DXK to "Upload to LoTW", and I noticed that the banner just showed "waiting for TQSL to complete processing", which has sat there for some time now.
Normally, when doing this, I briefly see a small window that shows C:\ and then the contacts are uploaded. I didn't see that this time.

I checked my config, and the correct path is shown to TQSL, and using the "run" button, it brings up TQSL as expected. The username and password are correct, so I wonder what is going on.
Looking at ARRL.org and the LoTW site shows no issues reported today.

What else can I check to see what is wrong?

+ Please reboot Windows into "Safe mode with network"; then start DXKeeper and invoke the "Add Requested" operation. Any change in behavior?

73,

Dave, AA6YQ






Re: Importing Log into DXKeeper

Dave AA6YQ
 

* more AA6YQ comments below

Thanks a million, Dave!

* Are you now able to import your ADIF file?

* Incidentally, the "Illegal - too many fields in record" error message is only displayed when DXKeeper is importing a tab-delimited
file, not an ADIF file.

73,

Dave, AA6YQ


Re: Importing Log into DXKeeper

Abie Alexander
 

Thanks a million, Dave!

73,

Abie/AB1F - VU2ABE

-----Original Message-----
From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Dave AA6YQ
Sent: Saturday, September 5, 2020 10:34
To: DXLab@groups.io
Subject: Re: [DXLab] Importing Log into DXKeeper

+ AA6YQ comments below

I'm having a hard time importing my old log into DXKeeper. Tried many times without success. Finally reworked the Excel and converted to ADI. It would not accept.

+ Is your "old log" in Excel or in ADIF format?

Then attempted to upload the same file as a tab delimited *.txt file. Got the following error message:

"Illegal - too many fields in record:"

These are the fields in my log that I am trying to upload. What am I doing wrong?

Here is a sample record from the log.

<QSO_date:8>20000909 <Time_On:4>0154 <Time_Off:4>0156 <Freq:6>21.195 <Band:2>15 <Mode:3>SSB <Tx_Pwr:2>50
<Call:6>JG1PED <RST_sent:2>59 <RST_rcvd:2>59 <Name:4>TONY <QTH:8>YOKOHAMA <State:2>11 <Cnty:4>1101
<Comment:0> <QSL_sent:1>X <QSL_rcvd:1>- <Station_Callsign:6>VU2ABE <eor>

+ When I direct DXKeeper to import that record, the result is

"Illegal - imported frequency 21.195 doesn't match imported band 15"

+ That's because <Band:2>15 is not a valid ADIF field. The QSO is
+ imported into DXKeeper, but with its "tx band" item empty, and
the "tx band" label flashing in red font (meaning "either select a valid band, or delete this QSO).

As you can see from the "Band enumeration" in the ADIF specification

<https://eur04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fadif.org.uk%2F310%2FADIF_310.htm%23Band_Enumeration&;data=02%7C01%7C%7Ce94135d10e9448578f6608d851592341%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637348790565553927&amp;sdata=Up6o0MOSUyA%2BT6l2bMnfLZ3wlVQJawFVF8gXZy3o6cU%3D&amp;reserved=0>

+ the correct specification for 15 meters is

<Band:3>15m

+ Correcting the band field enables DXKeeper to import the record
+ without error. However,

<QSL_sent:1>X

+ and

<QSL_rcvd:1>-

+ are invalid. As shown in the ADIF specification

<https://eur04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fadif.org.uk%2F310%2FADIF_310.htm%23QSLSent_Enumeration&;data=02%7C01%7C%7Ce94135d10e9448578f6608d851592341%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637348790565553927&amp;sdata=Fzzq%2B4kOjjP7xjiUl8WByd6zuyRa8fFMgP0Yb6PXhz4%3D&amp;reserved=0>

X is not a valid choice for QSL_sent, and hyphen is not a valid choice for QSL_rcvd. Unlike Band, which DXKeeper considers critical, neither QSL_sent nor QSL_rcvd are considered critical, so they are simply ignored. Typically, one corrects problems like this in the ADIF file "en masse" with a text editor (after making a backup copy of your original file). For example, you would change all instances of

<QSL_sent:1>X

+ to whichever of the valid QSL_sent choices describe what "X" meant in your previous logging application:

<https://eur04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fadif.org.uk%2F310%2FADIF_310.htm%23QSLSent_Enumeration&;data=02%7C01%7C%7Ce94135d10e9448578f6608d851592341%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637348790565553927&amp;sdata=Fzzq%2B4kOjjP7xjiUl8WByd6zuyRa8fFMgP0Yb6PXhz4%3D&amp;reserved=0>

+ Similarly, you'd change all instances of

<QSL_rcvd:1>-

+ to the appropriate choice from among these candidates:

<https://eur04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fadif.org.uk%2F310%2FADIF_310.htm%23QSLRcvd_Enumeration&;data=02%7C01%7C%7Ce94135d10e9448578f6608d851592341%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637348790565553927&amp;sdata=ttdSuN6z9J1T3XuwDu93JuHqA8fYT%2FENPY9XbMM0d74%3D&amp;reserved=0>

+ For context, I suggest that you review these two articles:

<https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.dxlabsuite.com%2Fdxlabwiki%2FQSOImport&;data=02%7C01%7C%7Ce94135d10e9448578f6608d851592341%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637348790565553927&amp;sdata=8E6CRSIZ%2Fy1IjABiZqKQI1a8yPoyTCkvHZRY%2Fa7E0q0%3D&amp;reserved=0>

<https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.dxlabsuite.com%2Fdxlabwiki%2FSwitchingToDXKeeper&;data=02%7C01%7C%7Ce94135d10e9448578f6608d851592341%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637348790565553927&amp;sdata=64RcF7qaGdR1AA3ZpQKBG%2BArYyppsTMClcTLrBI2L70%3D&amp;reserved=0>

73,

Dave, AA6YQ


Re: Importing Log into DXKeeper

Dave AA6YQ
 

+ AA6YQ comments below

I'm having a hard time importing my old log into DXKeeper. Tried many times without success. Finally reworked the Excel and
converted to ADI. It would not accept.

+ Is your "old log" in Excel or in ADIF format?

Then attempted to upload the same file as a tab delimited *.txt file. Got the following error message:

"Illegal - too many fields in record:"

These are the fields in my log that I am trying to upload. What am I doing wrong?

Here is a sample record from the log.

<QSO_date:8>20000909 <Time_On:4>0154 <Time_Off:4>0156 <Freq:6>21.195 <Band:2>15 <Mode:3>SSB <Tx_Pwr:2>50
<Call:6>JG1PED <RST_sent:2>59 <RST_rcvd:2>59 <Name:4>TONY <QTH:8>YOKOHAMA <State:2>11 <Cnty:4>1101
<Comment:0> <QSL_sent:1>X <QSL_rcvd:1>- <Station_Callsign:6>VU2ABE <eor>

+ When I direct DXKeeper to import that record, the result is

"Illegal - imported frequency 21.195 doesn't match imported band 15"

+ That's because <Band:2>15 is not a valid ADIF field. The QSO is imported into DXKeeper, but with its "tx band" item empty, and
the "tx band" label flashing in red font (meaning "either select a valid band, or delete this QSO).

As you can see from the "Band enumeration" in the ADIF specification

<http://adif.org.uk/310/ADIF_310.htm#Band_Enumeration>

+ the correct specification for 15 meters is

<Band:3>15m

+ Correcting the band field enables DXKeeper to import the record without error. However,

<QSL_sent:1>X

+ and

<QSL_rcvd:1>-

+ are invalid. As shown in the ADIF specification

<http://adif.org.uk/310/ADIF_310.htm#QSLSent_Enumeration>

X is not a valid choice for QSL_sent, and hyphen is not a valid choice for QSL_rcvd. Unlike Band, which DXKeeper considers critical,
neither QSL_sent nor QSL_rcvd are considered critical, so they are simply ignored. Typically, one corrects problems like this in the
ADIF file "en masse" with a text editor (after making a backup copy of your original file). For example, you would change all
instances of

<QSL_sent:1>X

+ to whichever of the valid QSL_sent choices describe what "X" meant in your previous logging application:

<http://adif.org.uk/310/ADIF_310.htm#QSLSent_Enumeration>

+ Similarly, you'd change all instances of

<QSL_rcvd:1>-

+ to the appropriate choice from among these candidates:

<http://adif.org.uk/310/ADIF_310.htm#QSLRcvd_Enumeration>

+ For context, I suggest that you review these two articles:

<https://www.dxlabsuite.com/dxlabwiki/QSOImport>

<https://www.dxlabsuite.com/dxlabwiki/SwitchingToDXKeeper>

73,

Dave, AA6YQ


DXKeeper - Importing Log - “Illegal - too many fields in record:"

Abie Alexander
 

Resubmitted as the graphic did not carry in the earlier email.

 

Hi,

 

I’m having a hard time importing my old log into DXKeeper. Tried many times without success. Finally reworked the Excel and converted to ADI. It would not accept.

 

Then attempted to upload the same file as a tab delimited *.txt file. Got the following error message:

 

Illegal - too many fields in record:"

 

These are the fields in my log that I am trying to upload. What am I doing wrong?

 

          QSO_date

      Time_On

      Time_Off

      Freq

      Band

      Mode

      Tx_Pwr

      Call

      RST_sent

      RST_rcvd

      Name

      QTH

      State

      Cnty

      Comment

      QSL_sent

      QSL_rcvd

      Station_Callsign

 

 

Here is a sample record from the log.

 

<QSO_date:8>20000909    <Time_On:4>0154   <Time_Off:4>0156      <Freq:6>21.195    <Band:2>15  <Mode:3>SSB <Tx_Pwr:2>50      <Call:6>JG1PED    <RST_sent:2>59    <RST_rcvd:2>59      <Name:4>TONY      <QTH:8>YOKOHAMA   <State:2>11 <Cnty:4>1101      <Comment:0> <QSL_sent:1>X     <QSL_rcvd:1>-      <Station_Callsign:6>VU2ABE    <eor>

 

There are 15,513 entries. So manual entry is out of the question. I am re-starting the hobby after a 16-year gap and would like to begin with DXKeeper in place.

 

Any help would be greatly appreciated! Thanks!

 

73,

 

Abie/AB1F – VU2ABE

 

 

 

 

 

 

73,

 

Abie/AB1F – VU2ABE

 

Mr. Abie Alexander

7919 Mandan Rd #103

Greenbelt, MD 20770-2828

USA

 


Importing Log into DXKeeper

Abie Alexander
 

Hi,

 

I’m having a hard time importing my old log into DXKeeper. Tried many times without success. Finally reworked the Excel and converted to ADI. It would not accept.

 

Then attempted to upload the same file as a tab delimited *.txt file. Got the following error message:

 

Illegal - too many fields in record:"

 

These are the fields in my log that I am trying to upload. What am I doing wrong?

 

 

 

Here is a sample record from the log.

 

<QSO_date:8>20000909    <Time_On:4>0154   <Time_Off:4>0156      <Freq:6>21.195    <Band:2>15  <Mode:3>SSB <Tx_Pwr:2>50      <Call:6>JG1PED    <RST_sent:2>59    <RST_rcvd:2>59      <Name:4>TONY      <QTH:8>YOKOHAMA   <State:2>11 <Cnty:4>1101      <Comment:0> <QSL_sent:1>X     <QSL_rcvd:1>-      <Station_Callsign:6>VU2ABE    <eor>

 

There are 15,513 entries. So manual entry is out of the question. I am re-starting the hobby after a 16-year gap and want to begin with DXKeeper in place.

 

Any help would be greatly appreciated! Thanks!

 

73,

 

Abie/AB1F – VU2ABE

 


Re: WW and MMTTY RX Issue

Joe Subich, W4TV
 

I suspect recent Win 10 August upgrade caused this event but
impossible to prove
Not likely as Windows would need to either modify a key in MMTTY.INI
in a specific way *or* would need to change the K3 "PITCH" setting
while in DATA mode!

73,

... Joe, W4TV


On 2020-09-04 9:53 PM, Jim Denneny wrote:
Found root cause with the help of friend Bob Wilson N6TV
As reported earlier I could not understand why MMTTY, N1MM, and DXL WW could TX rtty but could not RX rtty. Radio was set for low tones & MMTTY was set for high tones. This disparity has never occurred before.
I suspect recent Win 10 August upgrade caused this event but impossible to prove
Jim Denneny K7EG


Re: WW and MMTTY RX Issue

Adrian Fewster <vk4tux@...>
 

Jim, Can you let us know the actual setting parameter descriptions please in regard to below ?


On 5/9/20 11:53 am, Jim Denneny wrote:
Found root cause with the help of friend Bob Wilson N6TV
As reported earlier I could not understand why MMTTY, N1MM, and DXL WW could TX rtty but could not RX rtty. Radio was set for low tones & MMTTY was set for high tones. This disparity has never occurred before.
I suspect recent Win 10 August upgrade caused this event but impossible to prove

Jim Denneny K7EG
_._,_._,_


14281 - 14300 of 210356