Date   
Re: RTTY (AFSK) in WinWarbler problems with setup

Dave AA6YQ
 

Those screenshots looks fine. Try running the MMTTY.exe in your WinWarbler folder. Does it generate RTTY AFSK?

73,

Dave, AA6YQ

Re: RTTY (AFSK) in WinWarbler problems with setup

Dave AA6YQ
 

+ AA6YQ comments below

Yes. It is set to sound, and the other two options (Sound +COM and COM-TXD) are both greyed out an unavailable.
On the SoundCArd tab, the two appropriate RX and TX sound cards are (and have been) selected.

Are there any other items in MMTTY that need to be set up, and if so, what are the starting points?

+ No. Most MMTTY settings are configured by WinWarbler.

Earlier this evening, working in conjuction with Barry, K3NDM, I was able to configure both FLDIGI and N1MM Logger Plus successfully for AFSK RTTY, and we were able to have a QSO, so we've now ruled out the K3s itself. It's able to send and receive AFSK properly. Barry is running into the exactly the same issues with WW that I am.

+ The next time I borrow a K3, I'll check it out. For now, you can use FLDigi with DXLab via this bridge:

<http://www.n2amg.com/software/fldigi-dxlabs-gateway/>

+ If anyone who previously had WinWarbler configured to run RTTY AFSK with their K3 finds that this no longer works, please let me know.

73,

Dave, AA6YQ

Re: RTTY (AFSK) in WinWarbler problems with setup

Peter Dougherty
 

Here are the three MMTTY setup screencaps:
TX Tab
MISC tab
SoundCard tab

Re: RTTY (AFSK) in WinWarbler problems with setup

Peter Dougherty
 

Yes. It is set to sound, and the other two options (Sound +COM and COM-TXD) are both greyed out an unavailable. 
On the SoundCArd tab, the two appropriate RX and TX sound cards are (and have been) selected.

Are there any other items in MMTTY that need to be set up, and if so, what are the starting points?

Earlier this evening, working in conjuction with Barry, K3NDM, I was able to configure both FLDIGI and N1MM Logger Plus successfully for AFSK RTTY, and we were able to have a QSO, so we've now ruled out the K3s itself. It's able to send and receive AFSK properly. Barry is running into the exactly the same issues with WW that I am.

 

Re: RTTY (AFSK) in WinWarbler problems with setup

Dave AA6YQ
 

+ AA6YQ comments below

Is this what you're referring to?
RTTY Tab of WW config <https://www.facebook.com/photo.php?fbid=10156460898593650&set=p.10156460898593650&type=3&theater>

+ Yes, that now looks correct.

+ On the RTTY tab of WinWarbler's Configuration window, click the "MMTTY Setup" button in the upper right corner. In the "Setup" window that appears, select the Misc tab; is the "TX Port" panel set to "sound"?

73,

Dave, AA6YQ

Re: RTTY (AFSK) in WinWarbler problems with setup

Peter Dougherty
 

Is this what you're referring to? 
RTTY Tab of WW config

Re: RTTY (AFSK) in WinWarbler problems with setup

Dave AA6YQ
 

+ AA6YQ comments below

On Wed, Mar 20, 2019 at 08:04 PM, Peter Dougherty wrote:

There are two sets of screen shots in there. One was the initial post from early yesterday. I posted the current ones about an hour ago. That setting has been set to RTTY since late last night. Here's the link to the one I believe you're referring to.

Operating Mode Selection, General Tab

+ No, that's not the the panel to which I'm referring.

+ The "Operating Mode Selection" panel governs how WinWarbler reacts when you change the transceiver's mode. It does not specify how WinWarbler knows what transceiver mode to send to Commander when WinWarbler's "Operating Mode" is set to RTTY.

+ As Joe W4TV has posted and Rich VE3KI states his article, the relevant selector is named "Xcvr Mode" and lives in the "Modulation and transceiver mode" panel on the RTTY tab of WinWarbler's Configuration window. It should be set to RTTY, not LSB (in the screen shot of the "Modulation and transceiver mode" panel that you posted on Facebook earlier today, it is incorrectly set to LSB).

         73,

                Dave, AA6YQ

Re: RTTY (AFSK) in WinWarbler problems with setup

Peter Dougherty
 

There are two sets of screen shots in there. One was the initial post from early yesterday. I posted the current ones about an hour ago. That setting has been set to RTTY since late last night. Here's the link to the one I believe you're referring to.

Operating Mode Selection, General Tab

Re: RTTY (AFSK) in WinWarbler problems with setup

Dave AA6YQ
 

In a message posted earlier in this thread, Joe W4TV posted

"In WinWarbler -> Config -> RTTY there is a select (drop down) box to the right of the LSB radio button in the "Modulation and transceiver mode" field. To what is XCVR Mode set? With the K3/K3S it should be set to *RTTY* (not *LSB*) for AFSK LSB."

Rick VE3KI's "RTTY AFSK" instructions also state that the "Xcvr Mode" selector shoud be set to RTTY.

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

In the screenshot you posted to Facebook earlier today, the "XCVR Mode" selector was incorrectly set to LSB.

     73,

           Dave, AA6YQ

Re: RTTY (AFSK) in WinWarbler problems with setup

Peter Dougherty
 

Hi Jamie, it's an Elecraft K3s, using the USB codec exclusively, (not RTS/DTR). 

CW, SSB, and PSK-31 are fine; the radio works as intended, and the desired information is able to be transmitted. RTTY is failing. I can't get WW to invoke the correct mode on the radio (it's forcing it into LSB), and the radio isn't going into transmit when commanded to by WinWarbler--but it IS able to T/R switch and command AFSK-A on the K3s via Commander.

I posit there's something amiss between Commander and WW.

Re: RTTY (AFSK) in WinWarbler problems with setup

Peter Dougherty
 

That link is about setting levels when one is able to transmit tones. I haven't even gotten to the point where WW is able to set the radio into the correct RTTY mode yet. 
Commander is working as it should, but there's a mis-communication somewhere between Commander and WinWarbler. 

At this point, I wonder if it's possible to delete all existing settings from WinWarbler, delete the program and reinstall it fresh? I have a nagging feeling there a config file or something of that nature that's gone bad. 

As for sound cards, one thing to note is that when I go into transmit using PSK-31 I'm hearing the tones and they appear to be sent over the air. 

As an experiment, in the Soundcard tab of WinWarbler's config panel I changed the PSK & RTTY Transmission to the local speakers. Using Commander I put the radio into RTTY mode and put the transceiver in transmit. As soon as I hit any macro or free keyboard text I expected to hear tones, but none were generated. 

Before I kick this into Elecraft's lap (I seriously doubt they'll know what to do either--I have this issue open on their email reflector too) I really want to find out why WW can't tell Commander to apply the RTTY mode when I press the RTTY button on WinWarbler's main interface. And likewise, when I press the Start (F2) button in WinWarbler, why is it not able to get Commander to invoke that command (assuming that's the way it works). It really sound to me like WW's configuration is screwed up somehow, which bring me back to the question of removing WW and reinstalling it from scratch.

Re: RTTY (AFSK) in WinWarbler problems with setup

Jamie WW3S
 

I'm late to the party....whats the radio type? 


------ Original Message ------
From: "Peter Dougherty" <lists@...>
Sent: 3/20/2019 9:02:13 PM
Subject: Re: [DXLab] RTTY (AFSK) in WinWarbler problems with setup

On Wed, Mar 20, 2019 at 05:02 PM, Joe Subich, W4TV wrote:
(1) selecting RTTY in WW results in the radio erroneously going in to
LSB instead of DATA-A mode on the radio,
I have seen two different replies here, and I have tried both. One was RTTY, the other was DATA-L. Neither works for me.

In WinWarbler -> Config -> RTTY there is a select (drop down) box to
the right of the LSB radio button in the "Modulation and transceiver
mode" field. To what is XCVR Mode set? With the K3/K3S it should be
set to *RTTY* (not *LSB*) for AFSK LSB.

Selecting *LSB* will cause WinWarbler to direct Commander to select LSB
instead of AFSK.
XCVR MODE is currently set to RTTY, the LSB radio button is checked under the AFSK panel 
> (2) inability to switch into transmit.

In WinWarbler -> Config -> PTT what is selected in the *MODE* box?
If you are using Commander to control the rig and provide PTT,
the MODE box must be set to "Xcvr Ctrl App".
It has been set to XCVR CTRL APP since the beginning.

Re: RTTY (AFSK) in WinWarbler problems with setup

Dave AA6YQ
 

+ AA6YQ comments below

I've been in contact with Rich via email, sending him current screenshots and he says everything is set as it should be. Those screenshots are a day or two old.
I don't recall why commander wasn't switching TX/RX but that issue was definitely solved at some point.

To be clear, my current setting in Modulation and Transceiver Mode is RTTY from the dropdown box, in the AFSK/LSB section.
While I don't want to split this thread into 2 places and waste bandwidth, I have just posted 4 screenshots to the existing Facebook DXLS thread that I started yesterday. This should clear up what my current settings are and prevent even more wasted bandwidth here. If I could post screengrabs here directly I would.

+ You began this thread on Facebook, and then ask that it be moved here. Here it will stay.

+ Did you follow the instructions in

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

?

+ If you've done so but still can't generate an AFSK output with the radio having switched from RX to TX, then you'll have to contact Elecraft Support, as I know of no way to monitor the output of the K3's virtual soundcard. Alternatively, you could use a "real" soundcard and connect that to your K3's audio input and output; then you'd be able to directly monitor the soundcard output with a powered speaker or an oscilloscope.

73,

Dave, AA6YQ

Re: RTTY (AFSK) in WinWarbler problems with setup

Peter Dougherty
 

I've been in contact with Rich via email, sending him current screenshots and he says everything is set as it should be. Those screenshots are a day or two old.
I don't recall why commander wasn't switching TX/RX but that issue was definitely solved at some point.

To be clear, my current setting in Modulation and Transceiver Mode is RTTY from the dropdown box, in the AFSK/LSB section. 
While I don't want to split this thread into 2 places and waste bandwidth, I have just posted 4 screenshots to the existing Facebook DXLS thread that I started yesterday. This should clear up what my current settings are and prevent even more wasted bandwidth here. If I could post screengrabs here directly I would.

Re: RTTY (AFSK) in WinWarbler problems with setup

Dave AA6YQ
 

* more AA6YQ comments below

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Peter Dougherty
Sent: Wednesday, March 20, 2019 9:09 PM
To: DXLab@groups.io
Subject: Re: [DXLab] RTTY (AFSK) in WinWarbler problems with setup

On Wed, Mar 20, 2019 at 05:09 PM, Dave AA6YQ wrote:


+ AA6YQ comments below

+ Can you change your K3's frequency and mode using Commander's Main window?

Yes. Commander is working 100% reliably now, and has been since I found that P3 cable connection two days ago.

* Just this morning, you posted that clicking the TX button in Commander's PTT panel did not switch your K3 from TX to TX.

If I press the RTTY button on Commander's main screen the radio correctly drops to AFSK-A mode, and I am able to cleanly decode RTTY transmissions. If I press the TX and RX buttons in Commander I am able two switch the radio between transmit and receive. Commander is doing exactly what it's supposed to. The Start/Stop/Abort buttons in WinWarbler are not functional at this time.

Unfortunately groups.io won't allow me to paste screen captures in these messages, but would sending them via email help, or reposting them to the DX Labs Facebook Group assist?

* No, I don't need to look at screen shots of your configuration. You need to carefully review the documentation and set your configuration accordingly:

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

* Be sure to follow all of the cited links.

73,

Dave, AA6YQ






________________________________

AVG logo <https://www.avg.com/internet-security> This email has been checked for viruses by AVG antivirus software.
www.avg.com <https://www.avg.com/internet-security>

Re: Logging FT8 - something's changed

Dave AA6YQ
 

+ AA6YQ comments below

I jump into this thread to get an information: I've read the "Getting started" about interoperation between DXLab and WSJT-X and
I've read the limitation that only the TX frequency is logged. Being JT-Alert capable to log both TX and RX frequencies, could this
mechanism be implemented in a future release?

+ WSJT-X only reports a single frequency. From what I can tell, JT-Alert logs that frequency as both the TX frequency and the RX
frequency.

+ Most FT8 QSOs are made with different RX and TX frequencies.

+ If WSJT-X is extended to report both TX and RX frequencies when a QSO is logged, I will extend DXLab to log both frequencies.

73,

Dave, AA6YQ

Re: RTTY (AFSK) in WinWarbler problems with setup

Dave AA6YQ
 

* AA6YQ comments below

On Wed, Mar 20, 2019 at 06:10 PM, Peter Dougherty wrote:

On Wed, Mar 20, 2019 at 05:11 PM, Dave AA6YQ wrote:

+ Until we determine why Commander is unable to switch your K3 between RX and TX by sending it a CAT command, there's no point in pursuing any other misbehavior.

As stated in a previous reply, Commander is functioning perfectly right now. The problems I experienced two days ago are gone and it's behaving exactly as it should.

* As of yesterday, you reported that clicking the TX button in Commander's PTT panel did not switch your K3 from TX to TX. That's why I asked if the "Suppress CAT" box was checked.

* If Commander is now correctly controlling your radio, then I suggest that you carefully step through Rich VE3KI's instructions in

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

* keeping in mind that you're using RTTY AFSK, not RTTY FSK.

* Be sure to specify the "Mark Offset" in WinWarbler's "Modulation and Transceiver Mode" panel (Configuration window, RTTY tab); it was blank in the screenshot you posted on Facebook.

* Note that Rich's article points you Joe W4TV's "Setting the AFSK Audio Output Level for RTTY and Phone Operation on Vista, Windows 7, Windows 8, and Windows 10" article in 

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

        73,

               Dave, AA6YQ

 

 

 

 

 

Re: RTTY (AFSK) in WinWarbler problems with setup

Peter Dougherty
 

On Wed, Mar 20, 2019 at 05:11 PM, Dave AA6YQ wrote:

+ Until we determine why Commander is unable to switch your K3 between RX and TX by sending it a CAT command, there's no point in pursuing any other misbehavior.

As stated in a previous reply, Commander is functioning perfectly right now. The problems I experienced two days ago are gone and it's behaving exactly as it should.

Re: RTTY (AFSK) in WinWarbler problems with setup

Peter Dougherty
 

On Wed, Mar 20, 2019 at 05:09 PM, Dave AA6YQ wrote:

+ AA6YQ comments below

+ Can you change your K3's frequency and mode using Commander's Main window?

Yes. Commander is working 100% reliably now, and has been since I found that P3 cable connection two days ago. If I press the RTTY button on Commander's main screen the radio correctly drops to AFSK-A mode, and I am able to cleanly decode RTTY transmissions. If I press the TX and RX buttons in Commander I am able two switch the radio between transmit and receive. Commander is doing exactly what it's supposed to. The Start/Stop/Abort buttons in WinWarbler are not functional at this time.

Unfortunately groups.io won't allow me to paste screen captures in these messages, but would sending them via email help, or reposting them to the DX Labs Facebook Group assist?

 

Re: RTTY (AFSK) in WinWarbler problems with setup

Peter Dougherty
 

On Wed, Mar 20, 2019 at 05:02 PM, Joe Subich, W4TV wrote:
(1) selecting RTTY in WW results in the radio erroneously going in to
LSB instead of DATA-A mode on the radio,
I have seen two different replies here, and I have tried both. One was RTTY, the other was DATA-L. Neither works for me.

In WinWarbler -> Config -> RTTY there is a select (drop down) box to
the right of the LSB radio button in the "Modulation and transceiver
mode" field. To what is XCVR Mode set? With the K3/K3S it should be
set to *RTTY* (not *LSB*) for AFSK LSB.

Selecting *LSB* will cause WinWarbler to direct Commander to select LSB
instead of AFSK.
XCVR MODE is currently set to RTTY, the LSB radio button is checked under the AFSK panel 
> (2) inability to switch into transmit.

In WinWarbler -> Config -> PTT what is selected in the *MODE* box?
If you are using Commander to control the rig and provide PTT,
the MODE box must be set to "Xcvr Ctrl App".
It has been set to XCVR CTRL APP since the beginning.