Date   

Re: K3 RTTY issues with N1MM+

Bill KO7SS
 

On Sat, Oct 3, 2020 at 10:00 AM, Ronald PA3EWP wrote:
So we changed it to AFSK and all worked fine again.
Problem solved !

73, Bill KO7SS


Re: Elecraft K3s with P3 and Steppir SDA100

AE7AP
 

Craig:
I have a sketch of how mine is hooked up, but I don't see how to attach it, so I will send it to you separately.  It is, generally as follows:

K3s-RJ-45 from Elecraft CBLP3Y
P3-XCVR DB-9(M) :  DB-9(F) from CBLP3Y
P3-PC DB-9(F):  DB-9(M) from SteppIR Y-Cable
SDA100-Data in/Radio DB-9(M):  DB-9(F) from SteppIR Y-Cable
Elecraft CBLP3Y-DB-9(M):  DB-9(F) from SteppIR Y-Cable

I have to have software (DXLab, N1MM, etc.) running in order for the SDA100 Autotrack to work.  In DXLab Commander, I have the "Interrogation" box clicked and a 250 ms scan interval & a "1" in the Scan Dwell box.  I don't know that these settings matter, but it works well.

73,
Rob - AE7AP


Re: K3 for CW

K9MA
 

Hi Martin,

On the issue of receiver latency compromising QSK operation, I don't think the T/R switching necessarily introduces any significant latency. (My RJ-1 vacuum relay switches in 1.4 ms!) Receiver recovery can be made fast enough by proper AGC design. However, a DSP unavoidably introduces delay, in addition to the inherent delay of any narrow filter. I think the DSP delay can be reduced by using a faster processor and/or sampling rate, but I'm not sure. Perhaps someone can fill us in.

73,
Scott K9MA

On 10/4/2020 3:20 AM, Martin Kratoska wrote:
Hi Scott,

your observation is correct, at least in particular. I don't have now any ricebox to confirm this. Anyway some numbers can be measured with Keying Analyzer by Nick, WA5BDU (attached), of course some not. I agree, a separate RX and TX with a 6AH6 antenna switch is unbeatable stellar performer although it introduces some level of attenuation into RX path. The "processorless" were much better (speaking about QSK) than the modern DSP/DDS gear. AFAIK the RX "recovery time" is mostly introduced by firmware built-in delays. Manufacturers won't allow any artifacts on the receiver audio during the switching time, unfortunately no firmware allows to adjust it. Anyway, the K3 with new synthesizers KSYN3A is still the best QSK radio on the market - if you have other info, tell me, please.

My idea is to extend the WA5BDU gem to measure RX audio. It seems that it will need another channel detecting the presence of an audio signal. I plan to get in touch with WA5BDU to do this.

73,
Martin, OK1RR

Dne 04. 10. 20 v 3:11 K9MA napsal(a):
Hello Martin,

I've been using QSK for many, many years, going back to the days of vacuum tube radios. The one thing that disappoints me about the K3 and other modern DSP radios is that the receiver latency is so long that even at 30 wpm or so, you can't hear between dots and dashes, only between letters or words. Even my old FT-1000D (no DSP) is much better. Have you noticed that? I really miss the transparency fast QSK gave us. I guess that's the price we must pay for the benefits of QSK.

73,
Scott K9MA

On 10/3/2020 7:31 PM, Martin Kratoska wrote:
I am 99.99% on CW. I have 250-400-1k-1k8-2k8 8-pole filter set in both main and sub RX (10 filters total!). My K3 #7554 with new synthesizers is the best radio I used in my 50+ years of ham radio activity. Good QSK is a mandatory for me, I do often also QRQ up to 60 wpm.

Your choice of K3 is excellent.

73,
Martin, OK1RR

P.S. I strongly hate clicking antenna relays, the fast & silent PIN diode switching (K3 and KPA500) is mandatory for any rig in the future.


Dne 02. 10. 20 v 17:39 SGS 126 napsal(a):
I have recently gotten back into CW and I want to get a K3 purely for CW. I have seen plenty of K3/100/AT for under $2000. My code speed is between 13-18 wpm, but I am trying to get proficient so that is why I am looking at the K3 to use for code and build up my proficiency. I presently have an Icom 7300 which I know would work fine but I like that the Elecraft uses PIN diodes for switching. Any recommendations on must-have filters?

Thanks, Ben KJ4CC




















-- 
Scott  K9MA

k9ma@...


Re: Elecraft K3s with P3 and Steppir SDA100

craigt@...
 
Edited

Randy

Thanks.

It is my understanding that with a couple of cables, the K3/P3 will communicate with the SDA100 with no extra software.  I an not sure of the wiring (how to go from the K3s through the P3) to the SDA100 with a couple of setting changes on the K3 and the SDA100?

I have the SDA100 set to Kenwood 4800/4800 also

Craig


Re: Elecraft K3s with P3 and Steppir SDA100

Randy Farmer W8FN
 

I used a SteppIR with the SDA100 controller for several years. I used PstRotatorAz set to track my logging programs (DX4WIN for general logging and N1MM+ for contesting). I purchased a two-port Gearmo USB to RS232 converter and used one port to drive the SDA100. You connect the RS232 interface to the SDA100 DATA IN port. It worked very well. PstRotatorAz is an excellent program that will do lots of things besides control rotators, and it's well worth the small one-time registration cost.

73...
Randy, W8FN

On 10/4/2020 8:29 PM, craigt@... wrote:
I am looking for some guidance using the Elecraft K3s with P3 and Steppir SDA100.  What cables needed and what settings are needed on both the K3s and SDA100 to get the Steppir BigIR to automatically switch bands?  if you have a wiring diagram that would be great also.

Thank you for our help in advance

Craig WØLV


Elecraft K3s with P3 and Steppir SDA100

craigt@...
 

I am looking for some guidance using the Elecraft K3s with P3 and Steppir SDA100.  What cables needed and what settings are needed on both the K3s and SDA100 to get the Steppir BigIR to automatically switch bands?  if you have a wiring diagram that would be great also.

Thank you for our help in advance

Craig WØLV


Re: K3 RTTY issues with N1MM+

Harry WX8C
 

I believe I may have experienced the same issue as described by Ronald.  My setup was basically the same as his except I was operating SO1V.  I went back and verified that all of my settings are as Joe describes.  I should add that I cannot easily independently verify what is actually being transmitted and everything looks normal in the MK2 message screen as well as the N1MM message screen.  The specific condition that I see that I do not recall being normal is that on the MK2 I can see the PTT2 LED de-activate but then I can see the FSK LED continue to flash for approximately 1 second.

Harry
WX8C


Re: K3 RTTY issues with N1MM+

Jim - WS6X
 

Thanks, Joe!

The only config setting that differed from your suggestions was TX Port was set to “Sound + COM-TxD (FSK).” That would explain why AFSK worked. I’m not sure when that got changed, except I was fiddling with it during the contest trying to get something to work. Anyway, everything seems to be OK now.

Thanks again,

Jim – WS6X


Re: K3 RTTY issues with N1MM+

Robert W5AJ
 

wonder if the other computer – on AFSK had VOX on

or which route the PTT was wired with different test rigs

for K3,  you might resolve using the “Comm PTT” on Ports setup page

Not my favorite but worth testing (That’s a writelog screen – assume N1MM has similar)

 

PI4C,  PI4CO and PI4COM are all found in the recent RBN link given on web page

 

https://public.tableau.com/profile/oh2bbt#!/vizhome/CQWorldwideDXContestRTTY2020RBNstatistics/DXCallanalyse

 

Recall doing repeat as was copying different callsigns with and without “M”

 

73 P40P

 

Robert

Midland, Texas

 

From: Elecraft-K3@groups.io [mailto:Elecraft-K3@groups.io] On Behalf Of Ronald PA3EWP
Sent: Saturday, October 03, 2020 4:35 AM
To: Elecraft-K3@groups.io
Subject: [Elecraft-K3] K3 RTTY issues with N1MM+

 

Hello,

 

During the RTTY contest last weekend we noticed a problem that our transmitted text was abrupted.

A lot of times our call was transmitted as PI4C or PI4CO instead of PI4COM.

 

We used the latest version of N1MM+, MMTTY, Microkeyer MK2 and a Elecraft K3.

N1MM was configured as SO2V.

 

If I looked at the digital interface window the text was transmitted, at the end the software disabled the PTT of the radio.

But the radio was still busy transmitting the text, the FSK led was still flashing, but the software disabled the PTT.

I try to find what was happening or was changed, but I couldn’t find any solution for it.

 

So we changed it to AFSK and all worked fine again.

If I started MMTTY without N1MM it worked fine.

 

I checked it at after the contest and I come to the following conclusion:

The same computer setup with another K3 radio, other Microkeyer interface => same results.

Same computer setup with TS990, no problem

Other computer setup with the same K3, same problem.

 

I asked a friend to test his K3 and he has the same issue.

 

I hope someone has a solution for it, I am sure it must be something simple, but I can’t find it.

 

 

 

Ronald

PA3EWP

 

Contestgroup Oude Maas

30th anniversary callsign: PI30COM

http://www.pi4com.nl

 

 

 


Re: K3 for CW

Robert W5AJ
 

Ben, an excellent choice
the 250Hz helped my 160 meter country count, could hear better!!
Indeed the DSP part of that was cranked to 150hz (that's about as tight and still being useful)

Look at the filter curves. The 400hz maybe more of a 350hz filter (ah, memory...)
I set the configuration of the 250hz to start at 300hz and the 400hz filter to kick in at 450hz.
just a preference
The 400hz is also great RTTY filter

it's correct to say don't use the 250hz as much as 400hz but it's worth being there.
if it's one or the other - 400hz

also in one of the QST reviews of K3 - there is a sidebar on the filters
it's worth finding and reading

73 W5AJ




Robert
Midland, Texas

-----Original Message-----
From: Elecraft-K3@groups.io [mailto:Elecraft-K3@groups.io] On Behalf Of Lou Kolb
Sent: Saturday, October 03, 2020 12:07 PM
To: Elecraft-K3@groups.io
Subject: Re: [Elecraft-K3] K3 for CW

Ben,

I can tell you that when I got my k3-100 10 years ago, my CW operation jumped from 50 per cent to around 80 per cent. As you've surmised, it's a great CW rig.
As for filters, I suggest iether the 400hz or 200hz filters. The 200 is a good idea if you want to do a lot of contest or DX operating. If your operating is more casual, the 400hz filter does a fine job. I use an 8 pole 400hz filter, which does a terific job. Good luck. Lou WA3MIX

On 10/2/20, SGS 126 <brloper@...> wrote:
I have recently gotten back into CW and I want to get a K3 purely for
CW. I have seen plenty of K3/100/AT for under $2000. My code speed is
between
13-18 wpm, but I am trying to get proficient so that is why I am
looking at the K3 to use for code and build up my proficiency. I
presently have an Icom
7300 which I know would work fine but I like that the Elecraft uses
PIN diodes for switching. Any recommendations on must-have filters?

Thanks, Ben KJ4CC






Re: K3 RTTY issues with N1MM+

Joe Subich, W4TV
 

At the start of the contest however, I noticed that the K3 was
sending rather slowly, with a bit of "jerky" quality. After a few
minutes, as the problem got progressively worse, I started looking
for answers. I checked all the usual stuff:
Make sure you have selected COM-TxD(FSK) and *NOT* Sound + COM-TxD (FSK)
in MMTTY's MISC -> Tx Port.

73,

... Joe, W4TV


On 2020-10-04 7:35 AM, Jim - WS6X wrote:
I experienced a very similar problem using FSK, which switching to AFSK
completely solved. Following is an email I composed after the contest, but
never sent.

I encountered a first-time problem with the K3s in the CQWW RTTY test last
weekend. I was using MMTTY, N1MM+, microKEYER II, Win 10. I always use the
K3s in FSK mode.
After a bit of sleuthing, I couldn't decide if this is a K3 problem, but
thought I'd submit to this group for starters. I will also check with the
MMTTY group, and if necessary the N1MM group.
Here's the story:
As usual, I had the setup all ready to go in the morning and even made a
handful of contacts. Everything worked as normal.
At the start of the contest however, I noticed that the K3 was sending
rather slowly, with a bit of "jerky" quality. After a few minutes, as the
problem got progressively worse, I started looking for answers. I checked
all the usual stuff:
- All K3 settings, microKEYER II, N1MM configuration and MMTTY setup were as
I have used them for years;
- I had not done a recent - in the past several days -- N1MM update;
- Thinking it might be a Win 10 timing error, I disabled the anti-virus
software and turned off all unnecessary background processes;
- Tried changing the baud rate in MMTTY and the K3;
- RFI? I reduced the power to QRP, transmitted into a dummy load, added more
ferrite on several cables.
.all to no avail. By this time I was getting worried. On a hunch, I switched
to AFSK. Behold! Transmission was back to normal. So that's what I used for
the next several hours. However. My band-changing macros default to FSK in
RTTY mode. Every time I changed bands I was back to the same problem.
After I took a 4-hour break for some shut-eye, and started on a different
band, FSK was working normal again. But only for a few minutes before the
stuttering slowdown began again.
Today I did some additional poking around, but I'm not finding the answer.
I've tried MMTTY standalone, everything seems normal. Does this sound like a
K3 problem?

Throughout the week I tried several times with various combinations of the
above. I have not been able to duplicate the problem at all.
Ideas?????
73,
Jim - WS6X


Re: K3 RTTY issues with N1MM+

Joe Subich, W4TV
 

If using FSK, make sure PTT is being generated by MMTTY *not* N1MM+.
Also make sure you have selected "COM-TxD(FSK)" and *NOT* "Sound +
COM-TxD (FSK)" in MMTTY's MISC -> Tx Port dialog. Finally, make sure
the "Char. Wait" and "Diddle Wait" sliders are fully to the left in
MMTTY's TX tab.

Note: those settings must be made from the N1MM+ Digital Window
*NOT* in a stand alone version of MMTTY.

See the example configuration for N1MM+ and MK II in Router (Help
-> Download Documents).

73,

... Joe, W4TV

On 2020-10-03 5:35 AM, Ronald PA3EWP wrote:
Hello,
During the RTTY contest last weekend we noticed a problem that our
transmitted text was abrupted.
A lot of times our call was transmitted as PI4C or PI4CO instead of PI4COM.
We used the latest version of N1MM+, MMTTY, Microkeyer MK2 and a Elecraft
K3.
N1MM was configured as SO2V.
If I looked at the digital interface window the text was transmitted, at the
end the software disabled the PTT of the radio.
But the radio was still busy transmitting the text, the FSK led was still
flashing, but the software disabled the PTT.
I try to find what was happening or was changed, but I couldn't find any
solution for it.
So we changed it to AFSK and all worked fine again.
If I started MMTTY without N1MM it worked fine.
I checked it at after the contest and I come to the following conclusion:
The same computer setup with another K3 radio, other Microkeyer interface =>
same results.
Same computer setup with TS990, no problem
Other computer setup with the same K3, same problem.
I asked a friend to test his K3 and he has the same issue.
I hope someone has a solution for it, I am sure it must be something simple,
but I can't find it.
Ronald
PA3EWP
Contestgroup Oude Maas
30th anniversary callsign: PI30COM
http://www.pi4com.nl <http://www.pi4com.nl/>


Re: K3 RTTY issues with N1MM+

Jim - WS6X
 

I experienced a very similar problem using FSK, which switching to AFSK completely solved. Following is an email I composed after the contest, but never sent.

 

>>>> 

I encountered a first-time problem with the K3s in the CQWW RTTY test last weekend. I was using MMTTY, N1MM+, microKEYER II, Win 10. I always use the K3s in FSK mode.

 

After a bit of sleuthing, I couldn’t decide if this is a K3 problem, but thought I’d submit to this group for starters. I will also check with the MMTTY group, and if necessary the N1MM group.

 

Here’s the story:

As usual, I had the setup all ready to go in the morning and even made a handful of contacts. Everything worked as normal.

At the start of the contest however, I noticed that the K3 was sending rather slowly, with a bit of “jerky” quality. After a few minutes, as the problem got progressively worse, I started looking for answers. I checked all the usual stuff:

- All K3 settings, microKEYER II, N1MM configuration and MMTTY setup were as I have used them for years;

- I had not done a recent – in the past several days -- N1MM update;

- Thinking it might be a Win 10 timing error, I disabled the anti-virus software and turned off all unnecessary background processes;

- Tried changing the baud rate in MMTTY and the K3;

- RFI? I reduced the power to QRP, transmitted into a dummy load, added more ferrite on several cables…

 

…all to no avail. By this time I was getting worried. On a hunch, I switched to AFSK. Behold! Transmission was back to normal. So that’s what I used for the next several hours. However… My band-changing macros default to FSK in RTTY mode. Every time I changed bands I was back to the same problem.

 

After I took a 4-hour break for some shut-eye, and started on a different band, FSK was working normal again. But only for a few minutes before the stuttering slowdown began again.

 

Today I did some additional poking around, but I’m not finding the answer. I’ve tried MMTTY standalone, everything seems normal. Does this sound like a K3 problem?

>>>> 

 

Throughout the week I tried several times with various combinations of the above. I have not been able to duplicate the problem at all.

Ideas?????

73,

Jim – WS6X

 


Re: K3 RTTY issues with N1MM+

Jeff Wilson
 

Hi Ron
I use K3 (S/n 1900 factory updated) with a home brew ACC cable to a USB to RS232 adapter into Win10 pro 2004 x64 updated computer running latest N1MM+ for FSK RTTY during contest sans problem.  Latest EXTFSK64 and MMTTY also installed.  So no N1MM issues with truncated FSK sending here.


Re: K3 for CW

 

Hi Scott,

your observation is correct, at least in particular. I don't have now any ricebox to confirm this. Anyway some numbers can be measured with Keying Analyzer by Nick, WA5BDU (attached), of course some not. I agree, a separate RX and TX with a 6AH6 antenna switch is unbeatable stellar performer although it introduces some level of attenuation into RX path. The "processorless" were much better (speaking about QSK) than the modern DSP/DDS gear. AFAIK the RX "recovery time" is mostly introduced by firmware built-in delays. Manufacturers won't allow any artifacts on the receiver audio during the switching time, unfortunately no firmware allows to adjust it. Anyway, the K3 with new synthesizers KSYN3A is still the best QSK radio on the market - if you have other info, tell me, please.

My idea is to extend the WA5BDU gem to measure RX audio. It seems that it will need another channel detecting the presence of an audio signal. I plan to get in touch with WA5BDU to do this.

73,
Martin, OK1RR

Dne 04. 10. 20 v 3:11 K9MA napsal(a):

Hello Martin,

I've been using QSK for many, many years, going back to the days of vacuum tube radios. The one thing that disappoints me about the K3 and other modern DSP radios is that the receiver latency is so long that even at 30 wpm or so, you can't hear between dots and dashes, only between letters or words. Even my old FT-1000D (no DSP) is much better. Have you noticed that? I really miss the transparency fast QSK gave us. I guess that's the price we must pay for the benefits of QSK.

73,
Scott K9MA

On 10/3/2020 7:31 PM, Martin Kratoska wrote:
I am 99.99% on CW. I have 250-400-1k-1k8-2k8 8-pole filter set in both main and sub RX (10 filters total!). My K3 #7554 with new synthesizers is the best radio I used in my 50+ years of ham radio activity. Good QSK is a mandatory for me, I do often also QRQ up to 60 wpm.

Your choice of K3 is excellent.

73,
Martin, OK1RR

P.S. I strongly hate clicking antenna relays, the fast & silent PIN diode switching (K3 and KPA500) is mandatory for any rig in the future.


Dne 02. 10. 20 v 17:39 SGS 126 napsal(a):
I have recently gotten back into CW and I want to get a K3 purely for CW. I have seen plenty of K3/100/AT for under $2000. My code speed is between 13-18 wpm, but I am trying to get proficient so that is why I am looking at the K3 to use for code and build up my proficiency. I presently have an Icom 7300 which I know would work fine but I like that the Elecraft uses PIN diodes for switching. Any recommendations on must-have filters?

Thanks, Ben KJ4CC










Re: K3 for CW

Rob Sherwood
 

The Ten-Tec Orion was the first to go back to a relative low first IF with roofing filters, followed by DSP I think in 2004.  Then in 2008 the K3 overwhelmed the Orion II.  Rob, NC0B


On Oct 3, 2020, at 7:15 PM, K9MA <K9ma@...> wrote:


Hi Mike,

There's no doubt that the crystal filters greatly improve the dynamic range of the K3. The dynamic range of the DSP is inherently limited by the resolution of the A/D converter, though they are getting better. I think Elecraft was one of the first to combine the benefits of crystal filters with the DSP, with excellent results. I'm looking forward to seeing test results for the K4.

73,
Scott K9MA

On 10/3/2020 7:47 PM, Michael Kopec via groups.io wrote:
Hi Scott. The filters are roofing filters and really only take over on strong 9+ sigs while the dsp handles the weaker sigs. Elecraft has/published an article on this. 73 de Mike K8NS
On Saturday, October 3, 2020, 08:26:09 PM EDT, K9MA <k9ma@...> wrote:


If you look at the published curves for the two filters, you will see that the skirts of the narrow one aren't really much better than the wide one. So, even with the narrow filter, below 400 Hz, the DSP is doing most of the work.

73,
Scott K9MA

On 10/3/2020 5:44 PM, Steve VE3RX wrote:
I agree with Thomas. While I'm not a real "CW" operator, I do use it during some contests. I have the 400 and 250, 8 pole filters. I find the 400 is usually good enough, and with the DSP bandwidth width, I can trim down the bandwidth from there. Once I hit 250, it is real tight and I find not too much better than the DSP turned down to 300Hz with the 400 filter. That said, the odd time, I do need 100-150Hz or so for some real tight DX with pileups, it does help. The only thing I don't know is how different it would be with 400Hz filter and DSP turned down to 100Hz vs a 250 filter and DSP width turned down to 100Hz.
I think you will be happy with a 400 filter, to start with. You can always add another filter later if you feel up to it. There is not a lot of difference in bandwidth between the 250 and 400Hz (8 pole) filters, maybe about 65Hz at -6dB. Not sure of the difference with the 5 pole filters.

73
Steve

73
Steve


-- Scott  K9MAk9ma@...


-- 
Scott  K9MA

k9ma@...


Re: K3 for CW

K9MA
 

Hi Mike,

There's no doubt that the crystal filters greatly improve the dynamic range of the K3. The dynamic range of the DSP is inherently limited by the resolution of the A/D converter, though they are getting better. I think Elecraft was one of the first to combine the benefits of crystal filters with the DSP, with excellent results. I'm looking forward to seeing test results for the K4.

73,
Scott K9MA

On 10/3/2020 7:47 PM, Michael Kopec via groups.io wrote:
Hi Scott. The filters are roofing filters and really only take over on strong 9+ sigs while the dsp handles the weaker sigs. Elecraft has/published an article on this. 73 de Mike K8NS
On Saturday, October 3, 2020, 08:26:09 PM EDT, K9MA <k9ma@...> wrote:


If you look at the published curves for the two filters, you will see that the skirts of the narrow one aren't really much better than the wide one. So, even with the narrow filter, below 400 Hz, the DSP is doing most of the work.

73,
Scott K9MA

On 10/3/2020 5:44 PM, Steve VE3RX wrote:
I agree with Thomas. While I'm not a real "CW" operator, I do use it during some contests. I have the 400 and 250, 8 pole filters. I find the 400 is usually good enough, and with the DSP bandwidth width, I can trim down the bandwidth from there. Once I hit 250, it is real tight and I find not too much better than the DSP turned down to 300Hz with the 400 filter. That said, the odd time, I do need 100-150Hz or so for some real tight DX with pileups, it does help. The only thing I don't know is how different it would be with 400Hz filter and DSP turned down to 100Hz vs a 250 filter and DSP width turned down to 100Hz.
I think you will be happy with a 400 filter, to start with. You can always add another filter later if you feel up to it. There is not a lot of difference in bandwidth between the 250 and 400Hz (8 pole) filters, maybe about 65Hz at -6dB. Not sure of the difference with the 5 pole filters.

73
Steve

73
Steve


-- Scott  K9MAk9ma@...


-- 
Scott  K9MA

k9ma@...


Re: K3 for CW

K9MA
 

Hello Martin,

I've been using QSK for many, many years, going back to the days of vacuum tube radios. The one thing that disappoints me about the K3 and other modern DSP radios is that the receiver latency is so long that even at 30 wpm or so, you can't hear between dots and dashes, only between letters or words. Even my old FT-1000D (no DSP) is much better. Have you noticed that? I really miss the transparency fast QSK gave us. I guess that's the price we must pay for the benefits of QSK.

73,
Scott K9MA

On 10/3/2020 7:31 PM, Martin Kratoska wrote:
I am 99.99% on CW. I have 250-400-1k-1k8-2k8 8-pole filter set in both main and sub RX (10 filters total!). My K3 #7554 with new synthesizers is the best radio I used in my 50+ years of ham radio activity. Good QSK is a mandatory for me, I do often also QRQ up to 60 wpm.

Your choice of K3 is excellent.

73,
Martin, OK1RR

P.S. I strongly hate clicking antenna relays, the fast & silent PIN diode switching (K3 and KPA500) is mandatory for any rig in the future.


Dne 02. 10. 20 v 17:39 SGS 126 napsal(a):
I have recently gotten back into CW and I want to get a K3 purely for CW. I have seen plenty of K3/100/AT for under $2000. My code speed is between 13-18 wpm, but I am trying to get proficient so that is why I am looking at the K3 to use for code and build up my proficiency. I presently have an Icom 7300 which I know would work fine but I like that the Elecraft uses PIN diodes for switching. Any recommendations on must-have filters?

Thanks, Ben KJ4CC













-- 
Scott  K9MA

k9ma@...


Re: K3 for CW

Michael Kopec
 

Hi Scott. The filters are roofing filters and really only take over on strong 9+ sigs while the dsp handles the weaker sigs. Elecraft has/published an article on this. 73 de Mike K8NS

On Saturday, October 3, 2020, 08:26:09 PM EDT, K9MA <k9ma@...> wrote:


If you look at the published curves for the two filters, you will see that the skirts of the narrow one aren't really much better than the wide one. So, even with the narrow filter, below 400 Hz, the DSP is doing most of the work.

73,
Scott K9MA

On 10/3/2020 5:44 PM, Steve VE3RX wrote:
I agree with Thomas. While I'm not a real "CW" operator, I do use it during some contests. I have the 400 and 250, 8 pole filters. I find the 400 is usually good enough, and with the DSP bandwidth width, I can trim down the bandwidth from there. Once I hit 250, it is real tight and I find not too much better than the DSP turned down to 300Hz with the 400 filter. That said, the odd time, I do need 100-150Hz or so for some real tight DX with pileups, it does help. The only thing I don't know is how different it would be with 400Hz filter and DSP turned down to 100Hz vs a 250 filter and DSP width turned down to 100Hz.
I think you will be happy with a 400 filter, to start with. You can always add another filter later if you feel up to it. There is not a lot of difference in bandwidth between the 250 and 400Hz (8 pole) filters, maybe about 65Hz at -6dB. Not sure of the difference with the 5 pole filters.

73
Steve

73
Steve


-- Scott  K9MAk9ma@...


Re: K3 for CW

Brian K0DTJ
 

I just spent a fun afternoon in the CA QSO party on 20 meters CW. In a crowd of S9++ signals I could always find a run frequency where I could hear all the way to the noise floor without QRM using the 400 Hz roofing filter and the DSP set at 350-400 Hz. For S&P I may set the DSP a little tighter.

It just doesn't get any better. :-)

73,
Brian, K0DTJ