Date
1 - 10 of 10
WW and MMTTY RX Issue
|
Jim Denneny <57JNDenneny@...>
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 |
|
|
|
Dave AA6YQ
+ AA6YQ comments below
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 + I'm glad that you and Bob were able to get this sorted, Jim. Thanks for reporting your findings here! 73, Dave, AA6YQ |
|
|
|
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 |
|
|
|
Joe Subich, W4TV
I suspect recent Win 10 August upgrade caused this event butNot 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 |
|
|
|
Adrian Fewster <vk4tux@...>
Does this mean that the mark/space afsk generated tones were reverse to the ssb choice used on the radio ?
toggle quoted message
Show quoted text
On 5/9/20 12:13 pm, Adrian Fewster via groups.io wrote:
|
|
|
|
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,.....
toggle quoted message
Show quoted text
------ 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 ? |
|
|
|
Joe Subich, W4TV
No, in this case it means that MMTTY was set for 2295/2125 (MMTTY
toggle quoted message
Show quoted text
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 ? |
|
|
|
Adrian Fewster <vk4tux@...>
Thanks Joe, I appreciate the reply and clarification.
toggle quoted message
Show quoted text
On 5/9/20 10:25 pm, Joe Subich, W4TV wrote:
|
|
|
|
Jim Denneny <57JNDenneny@...>
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 |
|
|
|
Joe Subich, W4TV
Without knowing which setting had been changed, it is hard to say
toggle quoted message
Show quoted text
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. |
|
|