Date   

Re: K3s second VFO RTTY

Dave AA6YQ
 

+ AA6YQ comments below
I can't find any way to receive on VFO-B to listen to the pileup. I am using a USB connection between the radio and the PC and I don't know if there's any way to tap into the second VFO using that method.
Sub RX Audio is on the *RIGHT* channel of USB Audio CODEC
*IF AND ONLY IF* SUB is ON. The Windows "Default Format" for the
USB Audio CODEC (Recording) *MUST* be a two channel format - it *may*
default to a single channel format depending on the (Windows) INF
file for the particular VID/PID of the chip.

I used to be able to bring up a second instance of MMTTY in the old days, but even that is no longer possible if WW is running,
You *MUST* use the "-Z" switch on the command line (or Shortcut "Target"
used to launch the second instance of MMTTY as by default it will only
launch a single instance. *READ* the MMTTY documentation!

*ALL* of this has been documented in this list as well as the Elecraft
and RTTY lists on *MULTIPLE OCCASIONS*. I'm sure a simple search of
the list archives will discover it.

+ This article explains how to simultaneously decode a RTTY station and its pileup when using an Icom IC-78XX or IC-7610 using CI-V commands in WinWarbler macros:

https://www.dxlabsuite.com/dxlabwiki/RTTY_SplitDecode

+ The "RTTY Configuration and Operations" section of this article explains how to simultaneously decode a RTTY station and its pileup when using a Flex Signature transceiver using Flex API commands in WinWarbler macros:

https://www.dxlabsuite.com/dxlabwiki/FlexSignature

+ The techniques described in the above articles - switching receiver outputs or switching soundcard sections - should be applicable to any transceiver with a subreceiver and a competent set of CAT instructions. If you successfully accomplish this, please send me your notes, and I'll incorporate them into a similar article for your transceiver model. Thanks!

      73,

             Dave, AA6YQ

 


Re: WinWarbler behavior on FSK

Joe Subich, W4TV
 

Jeff,

Look at the information on using the SCU-17
<http://www.dxlabsuite.com/dxlabwiki/YaesuSCU-17>

The FTdx101 is another of those transceivers with the SCU-17
functionality built in like FTd3000, FT-991 (and others).

In the case of the FTdx101 there does not appear to be a "PC Keying"
or "Data In" selection in the menu structure. However, you will want
to set all of the "RPTT SELECT" (MODE PSK/DATA, MODE RTTY, MODE SSB,
MODE AM, MODE FM) to RTS. You will need to experiment with EXTFSK
to see if TxD or DTR will provide the FSK signal (there is no menu
setting in the FTdx101) and set EXTFSK to use RTS for PTT.

I can not tell if the FTdx101 can use USB for FSK as there is no
information on FSK via USB in the operating Manual and I have no
access to an FTdx101 for testing.

73,

... Joe, W4TV

On 2021-10-11 2:38 PM, Jeff, K6JW wrote:
Yes, I have followed all instructions as outlined by you, including trying inverting FSK. The functioning Commander link is on COM 14 via the RS-232 port.The radio responds by going into transmit via its USB port on COM 10, the standard port loaded by the Silicon Labs driver from Yaesu. The enhanced port from that driver is on COM 12, also via the USB port, and unless I misunderstand how things are working, data should be transferred via that port but attempts to get Commander to link the radio via the USB port on COM 12 and with the RS-232 port disconnected are met by a port error message.
So, the current status is that I can get the radio to go into transmit using WinWarbler, but it appears that data (or, at least, meaningful data) is not getting from the computer into the radio. Finally, I mention again that I can run FSK using MMTTY freestanding with no problems.
--Jeff, K6JW


Re: K3s second VFO RTTY

Joe Subich, W4TV
 

I can't find any way to receive on VFO-B to listen to the pileup. I am using a USB connection between the radio and the PC and I don't know if there's any way to tap into the second VFO using that method.
Sub RX Audio is on the *RIGHT* channel of USB Audio CODEC
*IF AND ONLY IF* SUB is ON. The Windows "Default Format" for the
USB Audio CODEC (Recording) *MUST* be a two channel format - it *may*
default to a single channel format depending on the (Windows) INF
file for the particular VID/PID of the chip.

I used to be able to bring up a second instance of MMTTY in the old days, but even that is no longer possible if WW is running,
You *MUST* use the "-Z" switch on the command line (or Shortcut "Target"
used to launch the second instance of MMTTY as by default it will only
launch a single instance. *READ* the MMTTY documentation!

*ALL* of this has been documented in this list as well as the Elecraft
and RTTY lists on *MULTIPLE OCCASIONS*. I'm sure a simple search of
the list archives will discover it.

73,

... Joe, W4TV


On 2021-10-11 3:08 PM, Peter Dougherty wrote:
Still having the same problems I had years ago with RTTY. I have WW set up fine for simplex operation, and I can receive OK and it seems to be sending out a signal as well (no luck working the station I'm calling yet), but I can't find any way to receive on VFO-B to listen to the pileup. I am using a USB connection between the radio and the PC and I don't know if there's any way to tap into the second VFO using that method. I used to be able to bring up a second instance of MMTTY in the old days, but even that is no longer possible if WW is running, and 2-Tone will also receive VFO-A regardless of whether Left or Right is selected.
Any ideas? I'm fresh out after three hours of trying every trick in the book.


Re: WinWarbler problems with RTTY LOW tones (915Hz)

Gordon LaPoint
 

On 10/11/2021 15:09 PM, Joe Subich, W4TV wrote:

Thanks, with the Horz zoom set to 4 and the Horiz pan in the center the waterfall is off the display to the right,
Do you have your MARK OFFSET = -915?  The - is important.

the pan all the way to the right I can get the waterfall on the
display, but 4 is too big to be useful to me.
"4" sets the waterfall width to just over 1 KHz (~1200 Hz).  Can't
see much outside that with a 500 Hz filter anyway.

With Horiz zoom = 4 and Horiz pos fully left one click on the right
arrow for Horiz pos buts 915 Hz (mark) almost dead center of the
waterfall.  With Horiz Zoom at 2, the waterfall is ~2020 Hz wide
(100 - 2120 Hz) with 1100 Hz in the center with Horiz pos fully to
the left - but with a Horiz Zoom = 2 there is no ability to move
the center frequency below 1200 Hz (with Horiz Zoom = 1, Horiz pos
is grayed out since the entire 4 KHz audio passband is displayed).

73,

   ... Joe, W4TV
Joe,

   Thanks for the info, my MARK offset = -915, still not working the way you describe.  I will re-do all the settings and try again.

Just worked S9OK on 20Mtr rtty, split of course, and it worked fine, just used 2tone to monitor the tuning instead mmtty.

Gordon - N1MGO


Re: WinWarbler problems with RTTY LOW tones (915Hz)

Joe Subich, W4TV
 

Thanks, with the Horz zoom set to 4 and the Horiz pan in the center the waterfall is off the display to the right,
Do you have your MARK OFFSET = -915? The - is important.

the pan all the way to the right I can get the waterfall on the
display, but 4 is too big to be useful to me.
"4" sets the waterfall width to just over 1 KHz (~1200 Hz). Can't
see much outside that with a 500 Hz filter anyway.

With Horiz zoom = 4 and Horiz pos fully left one click on the right
arrow for Horiz pos buts 915 Hz (mark) almost dead center of the
waterfall. With Horiz Zoom at 2, the waterfall is ~2020 Hz wide
(100 - 2120 Hz) with 1100 Hz in the center with Horiz pos fully to
the left - but with a Horiz Zoom = 2 there is no ability to move
the center frequency below 1200 Hz (with Horiz Zoom = 1, Horiz pos
is grayed out since the entire 4 KHz audio passband is displayed).

73,

... Joe, W4TV


On 2021-10-11 2:43 PM, Gordon LaPoint wrote:
On 10/11/2021 14:10 PM, Joe Subich, W4TV wrote:

Gordon,

Try grabbing the "Horiz Pos" slider (lower right just above the right
end of the "waterfall") and sliding left/right to center 1000 Hz (or
"mark + 85 Hz") in the display.  If "Horiz zoom" is "1" the 915/1085
Hz tones will be shifted to the left as the display is actually
*AUDIO FREQUENCY* from 0 - 4000 Hz.

For RTTY, I generally leave "Horiz Zoom" = 4 with "Horiz Pos" set to
center the two tones (915/1085 in your case) in the display.

73,

   ... Joe, W4TV

Joe,
   Thanks, with the Horz zoom set to 4 and the Horiz pan in the center the waterfall is off the display to the right, the pan all the way to the right I can get the waterfall on the display, but 4 is too big to be useful to me. With High tones (2125Hz) the display was centered with zoom=2 and pan centered.  I expected the same with everything set to low tones (915)  .
With zoom set to 1 the display is still shifted to the right, but is on the screen of WinWarbler.
I'm using FSK set for LSB
Thanks,
Gordon - N1MGO


K3s second VFO RTTY

Peter Dougherty
 
Edited

Still having the same problems I had years ago with RTTY. I have WW set up fine for simplex operation, and I can receive OK and it seems to be sending out a signal as well, but I can't find any way to receive on VFO-B to listen to the pileup. I am using a USB connection between the radio and the PC and I don't know if there's any way to tap into the second VFO using that method. I used to be able to bring up a second instance of MMTTY in the old days, but even that is no longer possible if WW is running, and 2-Tone will also receive VFO-A regardless of whether Left or Right is selected.

Any ideas? I'm fresh out after three hours of trying every trick in the book. 

 

 


Re: WinWarbler behavior on FSK

Dave AA6YQ
 

+ AA6YQ comments below
Yes, I have followed all instructions as outlined by you, including trying inverting FSK. The functioning Commander link is on COM 14 via the RS-232 port.The radio responds by going into transmit via its USB port on COM 10, the standard port loaded by the Silicon Labs driver from Yaesu.
+ What does "The radio responds by going into transmit via its USB port on COM 10" mean?

The enhanced port from that driver is on COM 12, also via the USB port, and unless I misunderstand how things are working, data should be transferred via that port but attempts to get Commander to link the radio via the USB port on COM 12 and with the RS-232 port disconnected are met by a port error message.
+ If you have Commander configured to control the radio via the RS-232 port (COM 14), then you should not disconnect this port! If you disconnect it, Commander will not be able to switch your transceiver between RX and TX at WinWarbler's request.
So, the current status is that I can get the radio to go into transmit using WinWarbler, but it appears that data (or, at least, meaningful data) is not getting from the computer into the radio. Finally, I mention again that I can run FSK using MMTTY freestanding with no problems/

+ Since WinWarbler uses MMTTY for RTTY transmission, it too will work correctly when properly configured. When you run MMTTY standalone, what port and modem control signal do you have EXTFSK configured to utilize?

    73,

          Dave, AA6YQ

 

 

 


Re: WinWarbler problems with RTTY LOW tones (915Hz)

Gordon LaPoint
 

On 10/11/2021 14:10 PM, Joe Subich, W4TV wrote:

Gordon,

Try grabbing the "Horiz Pos" slider (lower right just above the right
end of the "waterfall") and sliding left/right to center 1000 Hz (or
"mark + 85 Hz") in the display.  If "Horiz zoom" is "1" the 915/1085
Hz tones will be shifted to the left as the display is actually
*AUDIO FREQUENCY* from 0 - 4000 Hz.

For RTTY, I generally leave "Horiz Zoom" = 4 with "Horiz Pos" set to
center the two tones (915/1085 in your case) in the display.

73,

   ... Joe, W4TV

Joe,

   Thanks, with the Horz zoom set to 4 and the Horiz pan in the center the waterfall is off the display to the right, the pan all the way to the right I can get the waterfall on the display, but 4 is too big to be useful to me. With High tones (2125Hz) the display was centered with zoom=2 and pan centered.  I expected the same with everything set to low tones (915)  .

With zoom set to 1 the display is still shifted to the right, but is on the screen of WinWarbler.

I'm using FSK set for LSB

Thanks,

Gordon - N1MGO


Re: WinWarbler behavior on FSK

Jeff, K6JW
 

Yes, I have followed all instructions as outlined by you, including trying inverting FSK. The functioning Commander link is on COM 14 via the RS-232 port.The radio responds by going into transmit via its USB port on COM 10, the standard port loaded by the Silicon Labs driver from Yaesu. The enhanced port from that driver is on COM 12, also via the USB port, and unless I misunderstand how things are working, data should be transferred via that port but attempts to get Commander to link the radio via the USB port on COM 12 and with the RS-232 port disconnected are met by a port error message.
So, the current status is that I can get the radio to go into transmit using WinWarbler, but it appears that data (or, at least, meaningful data) is not getting from the computer into the radio. Finally, I mention again that I can run FSK using MMTTY freestanding with no problems.
--Jeff, K6JW


Re: WinWarbler problems with RTTY LOW tones (915Hz)

Joe Subich, W4TV
 

Gordon,

Try grabbing the "Horiz Pos" slider (lower right just above the right
end of the "waterfall") and sliding left/right to center 1000 Hz (or
"mark + 85 Hz") in the display. If "Horiz zoom" is "1" the 915/1085
Hz tones will be shifted to the left as the display is actually
*AUDIO FREQUENCY* from 0 - 4000 Hz.

For RTTY, I generally leave "Horiz Zoom" = 4 with "Horiz Pos" set to
center the two tones (915/1085 in your case) in the display.

73,

... Joe, W4TV

On 2021-10-11 10:17 AM, Gordon LaPoint wrote:
Joe,
    FSK, and yes I set the Optimal Offset to 1000
The FSK worked fine with WriteLog using 2tone and MMTTY, but that is a different display than WinWarbler.
Thanks,
Gordon - N1MGO
On 10/11/2021 9:29 AM, Joe Subich, W4TV wrote:

AFSK or FSK?

Did you set "Optimal Offset" in WinWarbler -> Config -> RTTY to 1000?


73,

   ... Joe, W4TV


On 2021-10-11 9:07 AM, Gordon LaPoint wrote:
I have a new Elecraft K4 that I just used with WriteLog to do the Makrothen RTTY contest this last weekend. It worked fine, but I have to use LOW tones (915Hz) because of a bug in firmware with HIGH tones (2125Hz).  When I setup WinWarbler this morning to use the K4 with LOW tones it appears to work correctly, but the waterfall at the bottom of the WinWarbler screen is set off to the right of the screen, on the edge.  I did change all of the MMTTY settings to the LOW tones, including the defaults in the userpara.ini.   Is there some other place I forgot to change the tone frequency?  2Tone was also set for low tones and displays correctly.

Thanks,

Gordon - N1MGO


Re: support for rigctl

Dave AA6YQ
 

+ AA6YQ comments below

no one is asking you to do that, OTOH the Hamlib team might appreciate feedback on a utility they provide for exactly the purpose the OP was seeking.

+ Any transceiver control problem report involving Hamlib will produce the response "connect your transceiver directly to Commander".

73,

Dave, AA6YQ


Re: support for rigctl

g4wjs
 

On 11/10/2021 18:42, Dave AA6YQ wrote:
+ AA6YQ comments below

surely that depends only on the quality of emulation of the TS-2000 by the rigctlcom application?

+ There's no justification for time spent debugging that emulation for one transceiver, much less for many transceivers.

73,

Dave, AA6YQ
Dave,

no one is asking you to do that, OTOH the Hamlib team might appreciate feedback on a utility they provide for exactly the purpose the OP was seeking.



--
73

Bill

G4WJS.


Re: support for rigctl

Dave AA6YQ
 

+ AA6YQ comments below

surely that depends only on the quality of emulation of the TS-2000 by the rigctlcom application?

+ There's no justification for time spent debugging that emulation for one transceiver, much less for many transceivers.

73,

Dave, AA6YQ


Re: support for rigctl

g4wjs
 

On 11/10/2021 18:31, Dave AA6YQ wrote:
+ AA6YQ comments below

I think that may be possible by using a Hamlib utility called rigctlcom, it can connect to a Hamlib rigctld server and also emulates basic TS-2000 rig. You would connect to it using a virtual serial loopback service like com0com (or socat on *nix style systems). It is also a full Hamlib rigctl client so can connect directly to any Hamlib supported rig, thereby converting the CAT interface to a basic TS-2000 emulation.

Having said that, I just tried it to interface with my Icom IC-756 starting it on a serial port loopback pair COM18 - COM19 like this:

rigctlcom -m 3026 -r COM5 -s 19200 -p COM5 -P RTS -R COM18 -S 19200

then tried to connect to as if a Kenwood rig on COM19 19200 baud 8N1 from Commander. It didn't work quite as it should but it was trying to work. YMMV with the rig(s) you are using.

+ That's not a supported configuration.

         73,

             Dave, AA6YQ

Dave,

surely that depends only on the quality of emulation of the TS-2000 by the rigctlcom application? If it were a perfect TS-2000 emulation (not that I am saying it is) then it would be indistinguishable from a real TS-2000!

I would suggest that users that really need to control a rig served by Hamlib from Commander that they try this application and if it doesn't work then report the issues to the Hamlib team (https://lists.sourceforge.net/lists/listinfo/hamlib-developer) so they can fix the problem(s).


--
73

Bill

G4WJS.


Re: support for rigctl

Dave AA6YQ
 

+ AA6YQ comments below

I think that may be possible by using a Hamlib utility called rigctlcom, it can connect to a Hamlib rigctld server and also emulates basic TS-2000 rig. You would connect to it using a virtual serial loopback service like com0com (or socat on *nix style systems). It is also a full Hamlib rigctl client so can connect directly to any Hamlib supported rig, thereby converting the CAT interface to a basic TS-2000 emulation.

Having said that, I just tried it to interface with my Icom IC-756 starting it on a serial port loopback pair COM18 - COM19 like this:

rigctlcom -m 3026 -r COM5 -s 19200 -p COM5 -P RTS -R COM18 -S 19200

then tried to connect to as if a Kenwood rig on COM19 19200 baud 8N1 from Commander. It didn't work quite as it should but it was trying to work. YMMV with the rig(s) you are using.

+ That's not a supported configuration.

         73,

             Dave, AA6YQ


Re: support for rigctl

Dave AA6YQ
 

+ AA6YQ comments below:
i have 2 transceivers on 2 seperate com ports controlled by hamlib rigctl
is there any support to connect to the hamlib interface on a port instead of connecting the rig thru a serial port?

+ No. If you want Commander to control a transceiver connected to COM port X, first direct hamlib to close COM port X. 

       73,

              Dave, AA6YQ


Re: WinWarbler logging problems

Dave AA6YQ
 

+ AA6YQ comments below
When I log a contact from WinWarbler, psk31, DXKeeper does not send the contact to LOTW, EQSL, or Club Log.  In the WinWarbler Config, Log tab I do have the three "upload to" boxes checked.

What else have I forgot?  Its been a while since I used WinWarbler (Version 9.3.7).  All of my DXLabs suite software is uptodate on versions.
+ Please do the following:

1. on the General tab of DXKeeper's Configuration window, check the "Log debugging info" box

2. terminate DXKeeper

3. start DXKeeper

4. log a QSO from WinWarbler

5. on the General tab of DXKeeper's Configuration window, uncheck the "Log debugging info" box

6. attach the errorlog.txt file from your DXKeeper folder to an email message, and send that message to me via

aa6yq (at) ambersoft.com

        73,

               Dave, AA6YQ


Re: WinWarbler problems with RTTY LOW tones (915Hz)

Dave AA6YQ
 

+ AA6YQ comments below
I also have "WinWarbler MultiRadio" setup and have the K4 radio position (radio 4) set to Mark Offset of -915 and Optimal Offset set to 1000.
+ When configuring DXLab to support a new transceiver, it is best to ignore MultiRadio support in Commander and WinWarbler until you have all functionality with the radio working correctly when it's directly selected Commander.

       73,

              Dave, AA6YQ


Re: WinWarbler problems with RTTY LOW tones (915Hz)

Dave AA6YQ
 

+ AA6YQ comments below
I have a new Elecraft K4 that I just used with WriteLog to do the Makrothen RTTY contest this last weekend. It worked fine, but I have to use LOW tones (915Hz) because of a bug in firmware with HIGH tones (2125Hz).  When I setup WinWarbler this morning to use the K4 with LOW tones it appears to work correctly, but the waterfall at the bottom of the WinWarbler screen is set off to the right of the screen, on the edge.  I did change all of the MMTTY settings to the LOW tones, including the defaults in the userpara.ini.   Is there some other place I forgot to change the tone frequency?  2Tone was also set for low tones and displays correctly.
+ So that I can see what's going on, please make a screen shot of WinWarbler's Main window with the "Operating Mode" set to RTTY, and a screen shot showing the RTTY tab of WinWarbler's Configuration window. Attach both screen shots to an email message, and send the message to me via

aa6yq (at) ambersoft.com

      73,

             Dave, AA6YQ


Re: support for rigctl

g4wjs
 

On 11/10/2021 17:40, KF7NN wrote:
i have 2 transceivers on 2 seperate com ports controlled by hamlib rigctl
is there any support to connect to the hamlib interface on a port instead of connecting the rig thru a serial port?

thanks

Hi George,

I think that may be possible by using a Hamlib utility called rigctlcom, it can connect to a Hamlib rigctld server and also emulates basic TS-2000 rig. You would connect to it using a virtual serial loopback service like com0com (or socat on *nix style systems). It is also a full Hamlib rigctl client so can connect directly to any Hamlib supported rig, thereby converting the CAT interface to a basic TS-2000 emulation.

Having said that, I just tried it to interface with my Icom IC-756 starting it on a serial port loopback pair COM18 - COM19 like this:

rigctlcom -m 3026 -r COM5 -s 19200 -p COM5 -P RTS -R COM18 -S 19200

then tried to connect to as if a Kenwood rig on COM19 19200 baud 8N1 from Commander. It didn't work quite as it should but it was trying to work. YMMV with the rig(s) you are using.


--
73

Bill

G4WJS.

5821 - 5840 of 209605