> I sure am glad I didn't know the improperly timed K3 FSK generated by
> the K3's paddle to FSK conversion doesn't work.......
The variable length stop bit, lack of diddles, and lack of unshift on
space (?) can certainly cause problems in marginal conditions. While
you may not see it with strong signals, ask folks like W7AY or G3YYD
who write RTTY software how much SNR you loose due to the erratic timing
of the paddle sent CW. Even worse, ask them about character loss due
to framing errors when each character does not start at the proper time.
There are very few users who can consistently send one character every
160 ms on keyer paddles and that's what it takes to generate "clean",
properly timed RTTY (at 45.45 baud - it's even worse at 75 baud).
73,
... Joe, W4TV
On 4/6/2014 1:09 PM, Sam Morgan wrote:
I sure am glad I didn't know the improperly timed K3 FSK generated by
the K3's paddle to FSK conversion doesn't work.......
I guess I will need to delete my recent contacts with HC8ART and W1AW/*
to name a few.
Perhaps it's not proper FSK to a purest, but for the quick switch to
catch a wanted RTTY contact, it works a charm, and there was no
hesitation from the receiving stations, as if they had to do anything
special to decode this improperly timed FSK sent with the K3's paddle.
just saying....
On 4/6/2014 11:36 AM, Joe Subich, W4TV wrote:
Using the K3's native RS-232 and Line-In/Line Out does not address some
issues like:
snip
*properly timed FSK* vs. the paddle
to FSK conversion,
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:Elecraft@mailman.qth.net
This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to arch...@mail-archive.com
