Too Much Space Between Letters Using CWX

  • 1
  • Question
  • Updated 2 years ago
When using CWX for sending CW, there is too much space (time) between letters sent by CWX. What is the fix? (using a 6500 running 1.7.30)
Thanks
Photo of Dave

Dave

  • 3 Posts
  • 0 Reply Likes

Posted 2 years ago

  • 1
Photo of Bill W2PKY

Bill W2PKY

  • 440 Posts
  • 76 Reply Likes
@Dayton I talked to Scott about providing a participial space between characters. Maybe there could be a user preference for the timing of the space character?  The other additional control could be the speed of various characters. IE send CQ @ 80WPM and ur call @30WPM? So in the message enter speed Ctl then text characters then speed ctl char and the rest of the message. Have heard other keyer programs that can do this.
Photo of Dave

Dave

  • 3 Posts
  • 0 Reply Likes
Thanks Bill, your ideas sound great for a solution.

73, Dave, W9DR
Photo of Burt Fisher

Burt Fisher

  • 1010 Posts
  • 365 Reply Likes
Too little space
Photo of W7NGA

W7NGA

  • 396 Posts
  • 155 Reply Likes
Baby bear said .. 'just right'
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9013 Posts
  • 3412 Reply Likes
We coded CWX to follow the PARIS timings.  
  • Dash length: Dot length x 3
  • Pause between elements: Dot length
  • Pause between characters: Dot length x 3
  • Pause between words: Dot length x 7
If this is not the case, please let us know (a scope trace with timings would be beneficial)
Photo of Bill W2PKY

Bill W2PKY

  • 440 Posts
  • 76 Reply Likes
For me the issue is the space between words. When sending my call for example, would like less space between my call and KN or TU. Problem has been when using a space after my call the other side would start transmitting before the KN or TU was sent because the space between words timing is so long. So I have stopped using space characters for now.
Photo of Bob Wright, N7ZO

Bob Wright, N7ZO

  • 260 Posts
  • 65 Reply Likes
Hi Bill,

The hardware Winkeyer command set has, among other things, a gap (1/2 dit) insertion character to fine tune the spacing.  This is missing from the Flex implementation.  Also the Flex does not have the embedded speed change commands that are quite handy in contests.  These are just two of the reasons I am still using a hardware Winkeyer.

If I send "5nn tu" with full spacing, half the time the other station is already transmitting before I even get to the "tu" part.

73, Bob, N7ZO
(Edited)
Photo of Dave

Dave

  • 3 Posts
  • 0 Reply Likes
Thanks Tim for the explanation. I have been using CWX with PowerSDR for 10 years and when I started using CWX with SmartSDR, my ears/brain heard a different timing of letters that are together but sounds like there is a spaces between them.

I will try timing the spaces on a scope 
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9013 Posts
  • 3412 Reply Likes
Please do.  And if you see a discrepancy please let me know by opening a HelpDesk ticket.
(Edited)
Photo of K1UO - Larry

K1UO - Larry

  • 730 Posts
  • 119 Reply Likes
Was PSDR based on the Farnsworth CW timing method?  I vaguely remember Flex did a complete rewrite of their CW coding for SSDR. 
Photo of Walt - KZ1F

Walt - KZ1F

  • 3040 Posts
  • 641 Reply Likes
Tim, fwiw, I think cwx, indeed, speed is just right.