Topics

Sending Real CW

Mark Robinson
 

Hi Dave,

I am running an Icom IC7610 with Win4Icom.  Commander is connected to the Icom through Win4Icom with no issues


I have been trying to get Fldigi and MultiPSK to send real cw with the rig in the CW mode but have had no luck at all

Winwarbler of course transmits perfect cw with the radio in the cw mode.  How is it doing it?  If I understood what was happening maybe it would help me to configure the other two programs.     MultiPSK uses Commander for rig control.


73 Mark N1UK

Andrew OBrien
 

When I send CW via my 7610 and Winwarbler and Commander I am using CAT command.

Andy K3UK

On Dec 23, 2019, at 2:22 PM, Mark Robinson <markrob@...> wrote:

Hi Dave,

I am running an Icom IC7610 with Win4Icom. Commander is connected to the Icom through Win4Icom with no issues


I have been trying to get Fldigi and MultiPSK to send real cw with the rig in the CW mode but have had no luck at all

Winwarbler of course transmits perfect cw with the radio in the cw mode. How is it doing it? If I understood what was happening maybe it would help me to configure the other two programs. MultiPSK uses Commander for rig control.


73 Mark N1UK


Mark Robinson
 

I am not sure what I configured in WW but it certainly works well...it was a painlesss configuration.  I will take a closer look at the my configuration.

73 Mark N1UK

On 23-Dec-19 2:25 PM, Andrew OBrien wrote:
When I send CW via my 7610 and Winwarbler and Commander I am using CAT command.

Andy K3UK


On Dec 23, 2019, at 2:22 PM, Mark Robinson <markrob@...> wrote:

Hi Dave,

I am running an Icom IC7610 with Win4Icom. Commander is connected to the Icom through Win4Icom with no issues


I have been trying to get Fldigi and MultiPSK to send real cw with the rig in the CW mode but have had no luck at all

Winwarbler of course transmits perfect cw with the radio in the cw mode. How is it doing it? If I understood what was happening maybe it would help me to configure the other two programs. MultiPSK uses Commander for rig control.


73 Mark N1UK


Dave AA6YQ
 

+ AA6YQ comments below

I am not sure what I configured in WW but it certainly works well...it was a painlesss configuration. I will take a closer look at the my configuration.

+ See step 1.f in

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

+ Transceivers that can be directed to transmit CW by sending them CAT commands are listed in step 5.b of

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

+ Commander can be directed to transmit text in CW by conveying it to a capable transceiver via CAT commands, but I don't know of any applications other than WinWarbler that are exploiting this capability.

73,

Dave, AA6YQ

Mark Robinson
 

Thank you for the information

Looking at my WW configuration

All I have set in the CW  Keying Section is

PTT port (com8)    DTR


So maybe it is defaulting to CAT control ?   It works well.

My Icom control ports are Com 7 and Com 8



73 Mark N1UK

On 23-Dec-19 2:42 PM, Dave AA6YQ wrote:
+ AA6YQ comments below

I am not sure what I configured in WW but it certainly works well...it was a painlesss configuration. I will take a closer look at the my configuration.

+ See step 1.f in

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

+ Transceivers that can be directed to transmit CW by sending them CAT commands are listed in step 5.b of

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

+ Commander can be directed to transmit text in CW by conveying it to a capable transceiver via CAT commands, but I don't know of any applications other than WinWarbler that are exploiting this capability.

73,

Dave, AA6YQ



Dave AA6YQ
 

+ AA6YQ comments below

Thank you for the information

Looking at my WW configuration

All I have set in the CW' Keying Section is

PTT port (com8): DTR


So maybe it is defaulting to CAT control ?

It works well.

My Icom control ports are Com 7 and Com 8

+ That means WinWarbler is wiggling the DTR signal on COM8 to generate dots and dashes. Assuming you have Commander running, you might try switching that panel to "Xcvr Ctrl App" to see if you like it better.

73,

Dave, AA6YQ

Dave Fugleberg
 

Mark, you mentioned you're using Win4Icom. If that works like Win4K3, that may be your issue.
I used to use DTR keying for CW on my K3, but found that it didn't work through Win4K3. I checked with Tom, VA2FSQ, and he told me that the virtual  radio com ports in Win4K3 do not pass those handshake lines. You might check with him to see if that's true with Win4Icom as well.
I worked around the problem by adding a Winkeyer clone to my station.

On Mon, Dec 23, 2019 at 2:27 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

Thank you for the information

Looking at my WW configuration

All I have set in the CW' Keying Section is

PTT port (com8):  DTR


So maybe it is defaulting to CAT control ?

 It works well.

My Icom control ports are Com 7 and Com 8

+ That means WinWarbler is wiggling the DTR signal on COM8 to generate dots and dashes. Assuming you have Commander running, you might try switching that panel to "Xcvr Ctrl App" to see if you like it better.

         73,

                Dave, AA6YQ




Joe Subich, W4TV
 

Looking at my WW configuration

All I have set in the CW Keying Section is

PTT port (com8) DTR
I do not believe that fldigi and/or MultiPSK are capable of flipping
the DTR line on a serial port for CW as you have configured WW. I
certainly can't find any setting in fldigi that would permit such
operation.

Note - both Winarbler and fldigi do support "real" CW using a Winkey
device.

73,

... Joe, W4TV


On 2019-12-23 2:53 PM, Mark Robinson wrote:
Thank you for the information
Looking at my WW configuration
All I have set in the CW  Keying Section is
PTT port (com8)    DTR
So maybe it is defaulting to CAT control ?   It works well.
My Icom control ports are Com 7 and Com 8
73 Mark N1UK
On 23-Dec-19 2:42 PM, Dave AA6YQ wrote:
+ AA6YQ comments below

I am not sure what I configured in WW but it certainly works well...it was a painlesss configuration.  I will take a closer look at the my configuration.

+ See step 1.f in

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

+ Transceivers that can be directed to transmit CW by sending them CAT commands are listed in step 5.b of

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

+ Commander can be directed to transmit text in CW by conveying it to a capable transceiver via CAT commands, but I don't know of any applications other than WinWarbler that are exploiting this capability.

        73,

                Dave, AA6YQ




Patrick Lindecker
 

 

Hello Mark,

 

By default, Multipsk sends CW in USB (as PSK31), so your XCVR must be in USB (through Commander). All this is true, except if you have chosen to key CW directly through the serial port (click the MODE button for this) and not through Commander.

 

73

Patrick

 

 

*********************************

Sending Real CW
From:
Mark Robinson
Date: Mon, 23 Dec 2019 11:21:55 PST

Hi Dave,

I am running an Icom IC7610 with Win4Icom.
  Commander is connected to the Icom through Win4Icom with no issues


I have been trying to get Fldigi and MultiPSK to send real cw with the rig in the CW mode but have had no luck at all

Winwarbler of course transmits perfect cw with the radio in the cw mode.
  How is it doing it?  If I understood what was happening maybe it would help me to configure the other two programs.     MultiPSK uses Commander for rig control.


73 Mark N1UK

 

Mark Robinson
 

Thanks Dave,

Yes I had set the icom internal menu to

USB  Key CW  DTR


I tried switching WW to "Xcvr Ctrl App" and it sent cw nicely but the CW WPM speed control didn't work.  I could change the wpm  displayed number but the actual cw speed stayed the same.  When I have

PTT port (com8): DTR


Then the cw speed is adjustable without any problems.

73 Mark N1UK

On 23-Dec-19 3:26 PM, Dave AA6YQ wrote:
+ AA6YQ comments below

Thank you for the information

Looking at my WW configuration

All I have set in the CW' Keying Section is

PTT port (com8): DTR


So maybe it is defaulting to CAT control ?

It works well.

My Icom control ports are Com 7 and Com 8

+ That means WinWarbler is wiggling the DTR signal on COM8 to generate dots and dashes. Assuming you have Commander running, you might try switching that panel to "Xcvr Ctrl App" to see if you like it better.

73,

Dave, AA6YQ



Dave AA6YQ
 

+ AA6YQ comments below

Thanks Dave,

Yes I had set the icom internal menu to

USB Key CW DTR

I tried switching WW to "Xcvr Ctrl App" and it sent cw nicely but the CW WPM speed control didn't work. I could change the wpm displayed number but the actual cw speed stayed the same.

+ Are you referring to WinWarbler's "CW WPM" speed control?

+ If so, please do the following:

1. configure WinWarbler for "Xcvr Ctrl App"

2. on the General tab of Commander's Configuration window, check the "log debugging info" box

3. terminate and then restart Commander, and wait for Commander to initialize its Main window

4. direct WinWarbler to send some CW

5. increase WinWarbler's "CW WPM" speed control

6. direct WinWarbler to send some CW

7. decrease WinWarbler's "CW WPM" speed control

8. on the General tab of Commander's Configuration window, uncheck the "log debugging info" box

9. attach the errorlog.txt file from your Commander folder to an email message, and send the email message to me via

aa6yq (at) ambersoft.com

+ Thanks!

73,

Dave, AA6YQ

Andrew OBrien
 

Speed control functions well with my 7610 and Commander , as described by Dave .

Andy

On Dec 23, 2019, at 5:15 PM, Dave AA6YQ <@AA6YQ> wrote:

+ AA6YQ comments below

Thanks Dave,

Yes I had set the icom internal menu to

USB Key CW DTR

I tried switching WW to "Xcvr Ctrl App" and it sent cw nicely but the CW WPM speed control didn't work. I could change the wpm displayed number but the actual cw speed stayed the same.

+ Are you referring to WinWarbler's "CW WPM" speed control?

+ If so, please do the following:

1. configure WinWarbler for "Xcvr Ctrl App"

2. on the General tab of Commander's Configuration window, check the "log debugging info" box

3. terminate and then restart Commander, and wait for Commander to initialize its Main window

4. direct WinWarbler to send some CW

5. increase WinWarbler's "CW WPM" speed control

6. direct WinWarbler to send some CW

7. decrease WinWarbler's "CW WPM" speed control

8. on the General tab of Commander's Configuration window, uncheck the "log debugging info" box

9. attach the errorlog.txt file from your Commander folder to an email message, and send the email message to me via

aa6yq (at) ambersoft.com

+ Thanks!

73,

Dave, AA6YQ



Mark Robinson
 

I sent you the error log

73 Mark N1UK

On 23-Dec-19 5:14 PM, Dave AA6YQ wrote:
+ AA6YQ comments below

Thanks Dave,

Yes I had set the icom internal menu to

USB Key CW DTR

I tried switching WW to "Xcvr Ctrl App" and it sent cw nicely but the CW WPM speed control didn't work. I could change the wpm displayed number but the actual cw speed stayed the same.

+ Are you referring to WinWarbler's "CW WPM" speed control?

+ If so, please do the following:

1. configure WinWarbler for "Xcvr Ctrl App"

2. on the General tab of Commander's Configuration window, check the "log debugging info" box

3. terminate and then restart Commander, and wait for Commander to initialize its Main window

4. direct WinWarbler to send some CW

5. increase WinWarbler's "CW WPM" speed control

6. direct WinWarbler to send some CW

7. decrease WinWarbler's "CW WPM" speed control

8. on the General tab of Commander's Configuration window, uncheck the "log debugging info" box

9. attach the errorlog.txt file from your Commander folder to an email message, and send the email message to me via

aa6yq (at) ambersoft.com

+ Thanks!

73,

Dave, AA6YQ



Dave AA6YQ
 

Thanks, Mark.

The errorlog shows that Commander is not receiving a response to the "change CW speed" CAT commands it is sending to your IC-7700, for example:

2019-12-23 22:26:48.707 > CIVModule.DisplayLine: Port = P, Hex = FE FE 98 E0 14 C 0 67 FD
2019-12-23 22:26:48.707 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 1
2019-12-23 22:26:48.737 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 2
2019-12-23 22:26:48.770 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 3
2019-12-23 22:26:48.800 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 4
2019-12-23 22:26:48.830 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 5
2019-12-23 22:26:48.863 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 6
2019-12-23 22:26:48.895 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 7
2019-12-23 22:26:48.924 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 8
2019-12-23 22:26:48.955 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 9
2019-12-23 22:26:48.988 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 10
2019-12-23 22:26:48.988 > response timeout SetCWSpeed

Your IC-7700 occasionally does not respond to a "read meter" request:

2019-12-23 22:26:47.849 > CIVModule.SendCommand: FE FE 98 E0 15 11 FD
2019-12-23 22:26:47.879 > CIVModule.DisplayLine: Port = P, Hex = FE FE 98 E0 15 11 FD
2019-12-23 22:26:47.879 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 1
2019-12-23 22:26:47.910 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 2
2019-12-23 22:26:47.941 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 3
2019-12-23 22:26:47.974 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 4
2019-12-23 22:26:48.005 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 5
2019-12-23 22:26:48.038 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 6
2019-12-23 22:26:48.065 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 7
2019-12-23 22:26:48.098 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 8
2019-12-23 22:26:48.128 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 9
2019-12-23 22:26:48.159 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 10
2019-12-23 22:26:48.159 > response timeout Request meter

Is your computer connected directly to the radio, or is there an "intermediary"?

73,

Dave, AA6YQ

Mark Robinson
 

I am running through Win4Icom with a Com0Com virtual com port to my IC 7610

Mark N1UK

On 23-Dec-19 6:15 PM, Dave AA6YQ wrote:
Thanks, Mark.

The errorlog shows that Commander is not receiving a response to the "change CW speed" CAT commands it is sending to your IC-7700, for example:

2019-12-23 22:26:48.707 > CIVModule.DisplayLine: Port = P, Hex = FE FE 98 E0 14 C 0 67 FD
2019-12-23 22:26:48.707 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 1
2019-12-23 22:26:48.737 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 2
2019-12-23 22:26:48.770 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 3
2019-12-23 22:26:48.800 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 4
2019-12-23 22:26:48.830 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 5
2019-12-23 22:26:48.863 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 6
2019-12-23 22:26:48.895 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 7
2019-12-23 22:26:48.924 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 8
2019-12-23 22:26:48.955 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 9
2019-12-23 22:26:48.988 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 10
2019-12-23 22:26:48.988 > response timeout SetCWSpeed

Your IC-7700 occasionally does not respond to a "read meter" request:

2019-12-23 22:26:47.849 > CIVModule.SendCommand: FE FE 98 E0 15 11 FD
2019-12-23 22:26:47.879 > CIVModule.DisplayLine: Port = P, Hex = FE FE 98 E0 15 11 FD
2019-12-23 22:26:47.879 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 1
2019-12-23 22:26:47.910 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 2
2019-12-23 22:26:47.941 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 3
2019-12-23 22:26:47.974 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 4
2019-12-23 22:26:48.005 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 5
2019-12-23 22:26:48.038 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 6
2019-12-23 22:26:48.065 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 7
2019-12-23 22:26:48.098 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 8
2019-12-23 22:26:48.128 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 9
2019-12-23 22:26:48.159 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 10
2019-12-23 22:26:48.159 > response timeout Request meter

Is your computer connected directly to the radio, or is there an "intermediary"?

73,

Dave, AA6YQ



Dave AA6YQ
 

+ AA6YQ comments below

I am running through Win4Icom with a Com0Com virtual com port to my IC 7610

+ Win4Icom doesn't convey the "CW Speed" instruction to your radio. I reported this to Tom awhile ago.

73,

Dave, AA6YQ

On 23-Dec-19 6:15 PM, Dave AA6YQ wrote:
Thanks, Mark.

The errorlog shows that Commander is not receiving a response to the "change CW speed" CAT commands it is sending to your IC-7700, for example:

2019-12-23 22:26:48.707 > CIVModule.DisplayLine: Port = P, Hex = FE FE 98 E0 14 C 0 67 FD
2019-12-23 22:26:48.707 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 1
2019-12-23 22:26:48.737 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 2
2019-12-23 22:26:48.770 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 3
2019-12-23 22:26:48.800 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 4
2019-12-23 22:26:48.830 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 5
2019-12-23 22:26:48.863 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 6
2019-12-23 22:26:48.895 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 7
2019-12-23 22:26:48.924 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 8
2019-12-23 22:26:48.955 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 9
2019-12-23 22:26:48.988 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 10
2019-12-23 22:26:48.988 > response timeout SetCWSpeed

Your IC-7700 occasionally does not respond to a "read meter" request:

2019-12-23 22:26:47.849 > CIVModule.SendCommand: FE FE 98 E0 15 11 FD
2019-12-23 22:26:47.879 > CIVModule.DisplayLine: Port = P, Hex = FE FE 98 E0 15 11 FD
2019-12-23 22:26:47.879 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 1
2019-12-23 22:26:47.910 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 2
2019-12-23 22:26:47.941 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 3
2019-12-23 22:26:47.974 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 4
2019-12-23 22:26:48.005 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 5
2019-12-23 22:26:48.038 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 6
2019-12-23 22:26:48.065 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 7
2019-12-23 22:26:48.098 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 8
2019-12-23 22:26:48.128 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 9
2019-12-23 22:26:48.159 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 10
2019-12-23 22:26:48.159 > response timeout Request meter

Is your computer connected directly to the radio, or is there an "intermediary"?

73,

Dave, AA6YQ




Tom Schaefer NY4I
 

To answer Dave’s thought about others using it, TR4W uses the CW by serial port feature. I added what I call CWBYCAT to the TR4W contest logger. Mostly Elecraft, late Icom and Kenwood rigs. All done with serial port commands natively generated by the program (versus hard coded command sequences in macros).

Tom NY4I

Principal Solutions Architect
Better Software Solutions, Inc.
727-437-2771

Mark Robinson
 

OK thanks Dave,

Glad we sorted this out.

I did get WW taking to my RigBlaster through a Com port but although the RB front led was flashing the rig was not keying. I think the RB switching transistor must be damaged but it isn't something that I will use right now.

I hope Win4Icom gets 'fixed" sometime in the future.

Thanks for all your help.   It looks like I should get a WinKey as a good interface device for all these cw programs.

73 Mark N1UK

Ron Rosson
 

Tom (Win4Icom Author) recommends a winkeyer from K1EL or build your own.

I love my winkeyer and it works perfectly with both DXLab and Win4Icom.

--
73 de KF5JRA
Ron
kf5jra at oneinsane dot org

On Dec 23, 2019, at 1:47 PM, Dave Fugleberg <davefugleberg@...> wrote:

Mark, you mentioned you're using Win4Icom. If that works like Win4K3, that may be your issue.
I used to use DTR keying for CW on my K3, but found that it didn't work through Win4K3. I checked with Tom, VA2FSQ, and he told me that the virtual  radio com ports in Win4K3 do not pass those handshake lines. You might check with him to see if that's true with Win4Icom as well.
I worked around the problem by adding a Winkeyer clone to my station.

On Mon, Dec 23, 2019 at 2:27 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

Thank you for the information

Looking at my WW configuration

All I have set in the CW' Keying Section is

PTT port (com8):  DTR


So maybe it is defaulting to CAT control ?

 It works well.

My Icom control ports are Com 7 and Com 8

+ That means WinWarbler is wiggling the DTR signal on COM8 to generate dots and dashes. Assuming you have Commander running, you might try switching that panel to "Xcvr Ctrl App" to see if you like it better.

         73,

                Dave, AA6YQ





Mark Robinson
 

I see that the 7610 has a dedicated cw speed  knob, so adjusting the tx speed with winwarbler in CAT mode is pretty easy to do.

73 Mark N1UK

On 23-Dec-19 6:25 PM, Dave AA6YQ wrote:
+ AA6YQ comments below

I am running through Win4Icom with a Com0Com virtual com port to my IC 7610

+ Win4Icom doesn't convey the "CW Speed" instruction to your radio. I reported this to Tom awhile ago.

73,

Dave, AA6YQ