K3 FIRMWARE UPDATE: MCU 1.87, DSP 1.69 (Finally!)
Locked
123
123
 
Administrator
|
Dr. Werner Furlan wrote:
> when I transmit in SSB I am not able to get 100 % HF output. > peak power is around 40 Watts whatever I do, reading on the LP-100 peak > power meter. (using a Heil Proset with HC 5 Element) > RF display is about 40 % max. > > But! when I key the transceiver with the CW paddle in SSB (new feature, > very welcome!) I suddenly get full output also with normal speech. > > If I twist the power a little up or down, I am back on 40 % output, > with one Dit > in CW I can have the full power back. > > I am curious, if I am the only one with this problem. > btw, modulation reports on the air are excellent. Loud and clear, vy > good > readability. Hi Werner, Have you tried doing power calibration on all bands as described in the manual? You need to do TUNE on each band, into a dummy load, at both 5 W and 50 W. This should get you reasonably close at 100 W. However, for best initial power-setting accuracy in SSB modes and in DATA A and AFSK A, I'd recommend doing a quick TUNE. This is more accurate than setting the POWER control, which at present uses a lookup table to determine the approximate drive value required. You can also use a non-zero value of CONFIG:TXG VCE to adjust the nominal drive level in voice modes vs. CW mode. You might try setting this to +1.0 or so. 73, Wayne N6KR --- http://www.elecraft.com _______________________________________________ Elecraft mailing list Post to: [hidden email] You must be a subscriber to post to the list. Subscriber Info (Addr. Change, sub, unsub etc.): http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/subscribers.htm Elecraft web page: http://www.elecraft.com |
RE: K3 FIRMWARE UPDATE: MCU 1.87, DSP 1.69 (Finally!)
|
|
In reply to this post by wayne burdick
> MCU 1.87 / DSP 1.69, 5-3-08 > * AM RECEIVE WIDTH RANGE INCREASED: The WIDTH control in AM > mode now has a range of 2.8 to 10.0 kHz. Wider settings provide > outstanding fidelity for hi-fi speech and other wide-band signals. > This is the *IF* filter bandwidth -- the traditional way to show > bandwidth for AM, because the required IF bandwidth is twice the > modulation bandwidth. > NORM selects an IF bandwidth of 6.0 kHz in this mode. WIDTH > settings above 6.0 kHz will not be useful unless you have an FM- > bandwidth crystal filter installed (at FL1). Audio response is limited to 4.2 KHz with either the FM filter (13 KHz) or AM filter (6 KHz) at FL1. With the AM filter, 4.2 KHz is wider than necessary. With the FM filter, the 4.2 KHz high cut is less than the 10 KHZ of IF bandwidth. Why is the IF bandwidth and audio response excessively restricted with the FM filter? It should be possible to achieve at least 12 KHz of IF bandwidth and 6 KHz or more of audio bandwidth depending on the filter skirts. > * IF A 2.8 KHZ FILTER IS INSTALLED, SSB "NORM" BW is 2.8 kHz > (was fixed at 2.7 kHz). Can this be extended to CW and Data? It appears that "NORM" is currently fixed at 400 Hz regardless of mode and filter. 500 Hz would be more appropriate for CW with the 500 Hz crystal filter and even wider values might be appropriate for some DATA A modes with a 1000 Hz or 1.8 KHz filter. > * AUTO-SPOT (SPOT with CWT ON) now works with both very > weak and very strong signals. Auto-spot consistently tunes to a tone 50 Hz low (50 Hz below the value set for pitch). > * SSB TRANSMIT BANDPASS EXTENDED AT LOW END. Improvement > is about 2 dB at 300 Hz, 3 dB at 200 Hz, and 6 dB at 100 Hz. Can this be made optional? Excess LF response only wastes power at low frequencies and occupies excess bandwidth. > Additional improvement possible via TX EQ. Will TX EQ be made mode and/or input dependent? Setting TX EQ for voice screws up the audio response for digital mode (AFSK A and DATA A) operation. The same is true for RX EQ. 73, ... Joe, W4TV _______________________________________________ Elecraft mailing list Post to: [hidden email] You must be a subscriber to post to the list. Subscriber Info (Addr. Change, sub, unsub etc.): http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/subscribers.htm Elecraft web page: http://www.elecraft.com |
Re: K3 FIRMWARE UPDATE: MCU 1.87, DSP 1.69 (Finally!)
|
|
G'day,
----- Original Message ----- From: "Joe Subich, W4TV" <[hidden email]> To: "'wayne burdick'" <[hidden email]>; "'Elecraft Reflector'" <[hidden email]> Sent: Sunday, May 04, 2008 1:24 PM Subject: RE: [Elecraft] K3 FIRMWARE UPDATE: MCU 1.87, DSP 1.69 (Finally!) | > * AUTO-SPOT (SPOT with CWT ON) now works with both very | > weak and very strong signals. | | Auto-spot consistently tunes to a tone 50 Hz low (50 Hz below | the value set for pitch). CW auto tuning to my XG1 on either low or high O/P setting auto tunes to my 650Hz pitch setting. Confirmed by Spectrogram 16 display. With BW set to 1000Hz the capture range, in my case with 650Hz pitch, is -220Hz to +195Hz at 1 microvolt I/P signal. Outside those limits it can take two pushes of SPOT to auto spot, or much beyond those limits the auto spot will tune the wrong direction. However I feel I'm not that tone deaf that I can't get to within +/-100Hz by ear. Regards, Mike VP8NO _______________________________________________ Elecraft mailing list Post to: [hidden email] You must be a subscriber to post to the list. Subscriber Info (Addr. Change, sub, unsub etc.): http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/subscribers.htm Elecraft web page: http://www.elecraft.com |
Re: K3 FIRMWARE UPDATE: MCU 1.87, DSP 1.69 (Finally!)
|
Administrator
|
In reply to this post by Joe Subich, W4TV-3
>> * IF A 2.8 KHZ FILTER IS INSTALLED, SSB "NORM" BW is 2.8 kHz >> (was fixed at 2.7 kHz). > > Can this be extended to CW and Data? It appears that "NORM" is > currently fixed at 400 Hz regardless of mode and filter. 500 Hz > would be more appropriate for CW with the 500 Hz crystal filter > and even wider values might be appropriate for some DATA A modes > with a 1000 Hz or 1.8 KHz filter. Added to the list -- thanks. > >> * AUTO-SPOT (SPOT with CWT ON) now works with both very >> weak and very strong signals. > > Auto-spot consistently tunes to a tone 50 Hz low (50 Hz below > the value set for pitch). I can't duplicate this. I tried various sidetone pitches and found that auto-spot got to within a few Hz every time. What sidetone pitch are you using? I suppose some kind of band noise could interfere with the operation of CWT as well. > >> * SSB TRANSMIT BANDPASS EXTENDED AT LOW END. Improvement >> is about 2 dB at 300 Hz, 3 dB at 200 Hz, and 6 dB at 100 Hz. > > Can this be made optional? Excess LF response only wastes > power at low frequencies and occupies excess bandwidth. We could add a menu entry for this -- it's on the list. Meanwhile, the low end is rolled off a bit in hardware, too, so in practice I don't think you'll have any problems with this. > >> Additional improvement possible via TX EQ. > > Will TX EQ be made mode and/or input dependent? Setting TX EQ > for voice screws up the audio response for digital mode (AFSK A > and DATA A) operation. The same is true for RX EQ. I believe both RX and TX EQ are bypassed in DATA modes. If not, they should be. I'll mention this to Lyle. Per-mode settings are on the list, too. tnx Wayne N6KR > > 73, > > ... Joe, W4TV > > > > --- http://www.elecraft.com _______________________________________________ Elecraft mailing list Post to: [hidden email] You must be a subscriber to post to the list. Subscriber Info (Addr. Change, sub, unsub etc.): http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/subscribers.htm Elecraft web page: http://www.elecraft.com |
|
|
In reply to this post by Julian, G4ILO
> ...listening to the K3 on 29.600 FM via my
> FT-817 the audio sounds a bit distorted or "scratchy" on voice peaks which > suggests that the deviation is too high. I'd like to be able to adjust this > to see if it is or not. If you see a dull red glow to the west, it is my face turning beet red. Reasons/excuses aside, the released code has deviation at about 6 kHz instead of 3 kHz. This is now fixed in my development code. Meanwhile, to set the deviation using K3 Utility: Click on the Command Tester tab, in the edit line, type !dd40; and deviation should be right. This only needs to be sent once per session. If you leave the K3 on, the deviation setting should not be changed when you change modes/bands/etc. Sorry for missing this one, Julian. 73, Lyle KK7P _______________________________________________ Elecraft mailing list Post to: [hidden email] You must be a subscriber to post to the list. Subscriber Info (Addr. Change, sub, unsub etc.): http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/subscribers.htm Elecraft web page: http://www.elecraft.com |
|
|
In reply to this post by wayne burdick
hi Wayne,
to make a long story short - all ok now!! explanation between the lines: wayne burdick schrieb am 4 May 2008 um 10:04: > > when I transmit in SSB I am not able to get 100 % HF output. > > peak power is around 40 Watts whatever I do, reading on the LP-100 peak > > power meter. (using a Heil Proset with HC 5 Element) RF display is about > > 40 % max. > > > > But! when I key the transceiver with the CW paddle in SSB (new feature, > > very welcome!) I suddenly get full output also with normal speech. > > > > If I twist the power a little up or down, I am back on 40 % output, with > > one Dit in CW I can have the full power back. > Have you tried doing power calibration on all bands as described in the > manual? You need to do TUNE on each band, into a dummy load, at both 5 W > and 50 W. This should get you reasonably close at 100 W. no I did not - until now. In the manual I misunderstood the first sentence of this chapter: "is normally done at assembly time or by the factory." So I skiped this step :-( I did it now - and it seemed to help. > However, for best initial power-setting accuracy in SSB modes and in > DATA A and AFSK A, I'd recommend doing a quick TUNE. This is more > accurate than setting the POWER control, which at present uses a lookup > table to determine the approximate drive value required. I limited the tune power to 8 Watts - my automatic tuner does not need more to tune. When I set Tuner power to normal, the output power I see on the wattmeter corresponds very well with the K3 setting. Another observation: the ATU problem seems to be solved now. I don't know how this is linked, but it seems to work now, when I set the 2.7 filter frequency offset to its correct value of -.89 thank you vy much, 73! de Werner OE9FWV -- Veni, Vedi, WeeWee: I came. I saw. I had to go. Email powered by Pegasus Mail free at <http://www.pmail.com> Homepage: <http://www.qsl.net/oe9fwv/> Fone +43 5522 75013 Fax +43 820 555 85 2621 Mobile +43 664 6340014 Elecraft K2 #5203 K3 #656 _______________________________________________ Elecraft mailing list Post to: [hidden email] You must be a subscriber to post to the list. Subscriber Info (Addr. Change, sub, unsub etc.): http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/subscribers.htm Elecraft web page: http://www.elecraft.com |
Re: K3 FIRMWARE UPDATE: MCU 1.87, DSP 1.69 (Finally!)
|
|
In reply to this post by KK7P
Can someone confirm the default file location for the K3 update utility when
updating through the Internet? Tnx! ----- Original Message ----- From: "Lyle Johnson" <[hidden email]> To: "G4ILO" <[hidden email]> Cc: <[hidden email]> Sent: Sunday, May 04, 2008 2:47 PM Subject: Re: [Elecraft] K3 FIRMWARE UPDATE: MCU 1.87, DSP 1.69 (Finally!) >> ...listening to the K3 on 29.600 FM via my >> FT-817 the audio sounds a bit distorted or "scratchy" on voice peaks >> which >> suggests that the deviation is too high. I'd like to be able to adjust >> this >> to see if it is or not. > > If you see a dull red glow to the west, it is my face turning beet red. > Reasons/excuses aside, the released code has deviation at about 6 kHz > instead of 3 kHz. > > This is now fixed in my development code. > > Meanwhile, to set the deviation using K3 Utility: > > Click on the Command Tester tab, in the edit line, type > > !dd40; > > and deviation should be right. This only needs to be sent once per > session. If you leave the K3 on, the deviation setting should not be > changed when you change modes/bands/etc. > > Sorry for missing this one, Julian. > > 73, > > Lyle KK7P > > _______________________________________________ > Elecraft mailing list > Post to: [hidden email] > You must be a subscriber to post to the list. > Subscriber Info (Addr. Change, sub, unsub etc.): > http://mailman.qth.net/mailman/listinfo/elecraft > Help: http://mailman.qth.net/subscribers.htm > Elecraft web page: http://www.elecraft.com > _______________________________________________ Elecraft mailing list Post to: [hidden email] You must be a subscriber to post to the list. Subscriber Info (Addr. Change, sub, unsub etc.): http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/subscribers.htm Elecraft web page: http://www.elecraft.com |
Re: K3 FIRMWARE UPDATE: MCU 1.87, DSP 1.69 (Finally!)
|
|
In reply to this post by Bob Cunnings NW8L
I have PWR set to 5W. I'm sending a pure tone at 1KHz which is my preferred center frequency for data modes. I increase the LINE level until I get 5 bars of ALC. If I stop when it gets to 4 the ALC display is flickering like the bars keep on being redrawn. I'm getting 5 bars with LINE = 36. However, the power meter reading stops increasing at about 2.8W, when LINE=32 which gives 4 bars. I cannot get more than 2.8W with PWR=5W when sending a pure tone. The meter reads exactly what PWR is set to in CW mode. When transmitting an idle signal the meter reads a bit less than half the value it showed on the pure tone. If I set PWR to 12W I'm currently getting about 6.5W on the pure tone. Now if I set PWR to 12W, giving as I say about 6.5W out, and then back the PWR control down, then the power starts to reduce once PWR gets to 6.5W, and when I get to 5W the meter also shows 5W out. It holds that level on subsequent transmits, and if I transmit an idle tone I get just over 2W shown on my (non peak reading) meter, which is what you would expect at that level. If I then press TUNE, and then try transmiting in DATA A again, either a pure tone or an idle signal, the output reverts to the lower level again.
Julian, G4ILO. K2 #392 K3 #222 KX3 #110
* G4ILO's Shack - http://www.g4ilo.com * KComm - http://www.g4ilo.com/kcomm.html * KTune - http://www.g4ilo.com/ktune.html |
RE: K3 FIRMWARE UPDATE: MCU 1.87, DSP 1.69 (Finally!)
|
|
In reply to this post by wayne burdick
> >> * AUTO-SPOT (SPOT with CWT ON) now works with both very > >> weak and very strong signals. > > > > Auto-spot consistently tunes to a tone 50 Hz low (50 Hz below > > the value set for pitch). > > I can't duplicate this. I tried various sidetone pitches and > found that auto-spot got to within a few Hz every time. What > sidetone pitch are you using? I suppose some kind of band noise > could interfere with the operation of CWT as well. I first noticed it with a CW pitch of 600 Hz. The auto spot will eventually "zero in" after three or four tries but my ear is more accurate than the auto-spot. It may be band noise or simply timing out between CW characters because it is always accurate with a continuous tone (e.g. XG-2). > > > >> Additional improvement possible via TX EQ. > > > > Will TX EQ be made mode and/or input dependent? Setting TX EQ > > for voice screws up the audio response for digital mode (AFSK A > > and DATA A) operation. The same is true for RX EQ. > > I believe both RX and TX EQ are bypassed in DATA modes. If not, they > should be. I'll mention this to Lyle. I would hope so but that does not seem to be the case with RX EQ. When I set up the RX EQ to help a little with the high end in AM (band 7 = +2, Band 8 = +4), I see the tilt in AFSK A and DATA A. It's obvious since EQ "band 7" is just slightly higher than the standard 2295 Hz space in RTTY and results is an obvious level difference between mark and space tones. > Per-mode settings are on the list, too. That will be helpful. 73, ... Joe, W4TV _______________________________________________ Elecraft mailing list Post to: [hidden email] You must be a subscriber to post to the list. Subscriber Info (Addr. Change, sub, unsub etc.): http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/subscribers.htm Elecraft web page: http://www.elecraft.com |
|
Administrator
|
Joe Subich, W4TV wrote:
>> >> I believe both RX and TX EQ are bypassed in DATA modes. If not, they >> should be. I'll mention this to Lyle. > > I would hope so but that does not seem to be the case with RX EQ. > When I set up the RX EQ to help a little with the high end in AM > (band 7 = +2, Band 8 = +4), I see the tilt in AFSK A and DATA A. > It's obvious since EQ "band 7" is just slightly higher than the > standard 2295 Hz space in RTTY and results is an obvious level > difference between mark and space tones. I looked into this and, in fact, EQ still applies in DATA modes. I'll change this when I get a chance. 73, Wayne N6KR --- http://www.elecraft.com _______________________________________________ Elecraft mailing list Post to: [hidden email] You must be a subscriber to post to the list. Subscriber Info (Addr. Change, sub, unsub etc.): http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/subscribers.htm Elecraft web page: http://www.elecraft.com |
RE: K3 FIRMWARE UPDATE: MCU 1.87, DSP 1.69 (Finally!)
|
|
In reply to this post by Joe Subich, W4TV-3
I second this suggestion. I personally did not like the extra bass in my audio. I have compensated for this using the TX EQ. But as you say, doing that is less than ideal for data modes. I also find, apart from the excessive FM deviation that I mentioned before, that the FM sounds a bit "thin" compared to SSB. I'm wondering if the FM audio needs a bit more de-emphasis. If it's just a matter of personal preference, then I can't use TX EQ to adjust it to my liking as long as there is only one TX EQ setting for all modes.
Julian, G4ILO. K2 #392 K3 #222 KX3 #110
* G4ILO's Shack - http://www.g4ilo.com * KComm - http://www.g4ilo.com/kcomm.html * KTune - http://www.g4ilo.com/ktune.html |
Re: K3 FIRMWARE UPDATE: MCU 1.87, DSP 1.69 (Finally!)
|
|
In reply to this post by Joe Subich, W4TV-3
I agree that auto-spot doesn't seem as reliable as in earlier
versions. When I inject a continuous tone, it works fine, always coming within a few Hz. For actual cw signals it now seems to be more easily fooled, often tuning low - noticeably different to me, one who uses the feature constantly. In previous versions I rarely needed to press spot more than once, and repeated invocation of auto-spot resulted in little change of frequency (a few Hz or so if the signal was stable). Now, once tuned in, repeated pressing of spot often results in the frequency jumping around some tens of Hz, rather than the more repeatable performance in earlier versions. I noticed it right away when operating cw today. Bob NW8L On Sun, May 4, 2008 at 4:49 PM, Joe Subich, W4TV <[hidden email]> wrote: > > > > >> * AUTO-SPOT (SPOT with CWT ON) now works with both very > > >> weak and very strong signals. > > > > > > Auto-spot consistently tunes to a tone 50 Hz low (50 Hz below > > > the value set for pitch). > > > > I can't duplicate this. I tried various sidetone pitches and > > found that auto-spot got to within a few Hz every time. What > > sidetone pitch are you using? I suppose some kind of band noise > > could interfere with the operation of CWT as well. > > I first noticed it with a CW pitch of 600 Hz. The auto spot will > eventually "zero in" after three or four tries but my ear is more > accurate than the auto-spot. It may be band noise or simply timing > out between CW characters because it is always accurate with a > continuous tone (e.g. XG-2). > > > Elecraft mailing list Post to: [hidden email] You must be a subscriber to post to the list. Subscriber Info (Addr. Change, sub, unsub etc.): http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/subscribers.htm Elecraft web page: http://www.elecraft.com |
Re: K3 FIRMWARE UPDATE: MCU 1.87, DSP 1.69 (Finally!)
|
|
In reply to this post by Julian, G4ILO
After posting about my problem with not getting the dialled up power output in DATA A mode, it occurred to me that perhaps it might be a good idea to run the Low-Power (5W) Wattmeter Calibration. When I assembled my K3 I never had to touch this adjustment because it produced 5W as accurate as I could measure it right out of the box.
Well, now I can't seem to get this to work. I tuned to 20m (14.071 fwiw), put the ATU out of circuit and connected my dummy load power meter to ANT1, which is selected. I set PWR=5.0. In the CONFIG menu I located the WMTR LP menu entry, which has the value 100. When I press TUNE the power meter reads 3W, which perhaps not coincidentally is the power level I set for tuning using the TUN PWR menu entry. When I press TUNE the SWR is displayed not the value of WMTR LP, and rotating the VFO A knob seems to have no effect on the output power anyway. I don't think there is anything wrong with the power meter calibration as PWR=5.0 produces 5W on CW and FM, but how exactly is the low power wattmeter calibration supposed to work?
Julian, G4ILO. K2 #392 K3 #222 KX3 #110
* G4ILO's Shack - http://www.g4ilo.com * KComm - http://www.g4ilo.com/kcomm.html * KTune - http://www.g4ilo.com/ktune.html |
|
|
In reply to this post by KK7P
This is great. With what other brand can you beat up on the
developers, and see the developers humbled by their own mistakes. We understand Lyle. And I thought that was the sunset. Stan Rife W5EWA Houston, TX K2 SN 4216 K3 SN 0690 Lyle Johnson wrote: >> ...listening to the K3 on 29.600 FM via my >> FT-817 the audio sounds a bit distorted or "scratchy" on voice peaks >> which >> suggests that the deviation is too high. I'd like to be able to >> adjust this >> to see if it is or not. > > If you see a dull red glow to the west, it is my face turning beet > red. Reasons/excuses aside, the released code has deviation at about > 6 kHz instead of 3 kHz. > > This is now fixed in my development code. > > Meanwhile, to set the deviation using K3 Utility: > > Click on the Command Tester tab, in the edit line, type > > !dd40; > > and deviation should be right. This only needs to be sent once per > session. If you leave the K3 on, the deviation setting should not be > changed when you change modes/bands/etc. > > Sorry for missing this one, Julian. > > 73, > > Lyle KK7P > > _______________________________________________ > Elecraft mailing list > Post to: [hidden email] > You must be a subscriber to post to the list. > Subscriber Info (Addr. Change, sub, unsub etc.): > http://mailman.qth.net/mailman/listinfo/elecraft > Help: http://mailman.qth.net/subscribers.htm > Elecraft web page: http://www.elecraft.com > _______________________________________________ Elecraft mailing list Post to: [hidden email] You must be a subscriber to post to the list. Subscriber Info (Addr. Change, sub, unsub etc.): http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/subscribers.htm Elecraft web page: http://www.elecraft.com |
|
|
In reply to this post by Bob Cunnings NW8L
Hello,
I also confirm that the auto-spot is broken. My CW pitch is set at 600 Hz (only note tested) and it now takes several attempts to get it to set near 600 Hz. The old version worked very well for me. 73, Harry W8YMO ----------------------------------- > -----Original Message----- > From: [hidden email] [mailto:elecraft- > [hidden email]] On Behalf Of Bob Cunnings > Sent: Sunday, May 04, 2008 7:17 PM > To: Elecraft Reflector > Subject: Re: [Elecraft] K3 FIRMWARE UPDATE: MCU 1.87, DSP 1.69 > (Finally!) > > I agree that auto-spot doesn't seem as reliable as in earlier > versions. When I inject a continuous tone, it works fine, always > coming within a few Hz. For actual cw signals it now seems to be more > easily fooled, often tuning low - noticeably different to me, one who > uses the feature constantly. In previous versions I rarely needed to > press spot more than once, and repeated invocation of auto-spot > resulted in little change of frequency (a few Hz or so if the signal > was stable). Now, once tuned in, repeated pressing of spot often > results in the frequency jumping around some tens of Hz, rather than > the more repeatable performance in earlier versions. > > I noticed it right away when operating cw today. > > Bob NW8L > > On Sun, May 4, 2008 at 4:49 PM, Joe Subich, W4TV <lists@microham- > usa.com> wrote: > > > > > > > >> * AUTO-SPOT (SPOT with CWT ON) now works with both very > > > >> weak and very strong signals. > > > > > > > > Auto-spot consistently tunes to a tone 50 Hz low (50 Hz below > > > > the value set for pitch). > > > > > > I can't duplicate this. I tried various sidetone pitches and > > > found that auto-spot got to within a few Hz every time. What > > > sidetone pitch are you using? I suppose some kind of band noise > > > could interfere with the operation of CWT as well. > > > > I first noticed it with a CW pitch of 600 Hz. The auto spot will > > eventually "zero in" after three or four tries but my ear is more > > accurate than the auto-spot. It may be band noise or simply timing > > out between CW characters because it is always accurate with a > > continuous tone (e.g. XG-2). > > > > _______________________________________________ Elecraft mailing list Post to: [hidden email] You must be a subscriber to post to the list. Subscriber Info (Addr. Change, sub, unsub etc.): http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/subscribers.htm Elecraft web page: http://www.elecraft.com |
RE: K3 FIRMWARE UPDATE: MCU 1.87, DSP 1.69 (Finally!)
|
|
Ditto here. While it wasn't "perfect" before, the new version often over-shoots the frequency. It appears considerably less damped than before and often quits before things settle down. I personally prefer the old version.
Rick AI1V K3 728
|
|
|
In reply to this post by wayne burdick
I noticed the exact same thing as Harrison, below! Auto-spot is broken.
But if I have to say something nice, NR works better (on SSB at least) than it did before! Windy > AI1V > Sun, 04 May 2008 20:00:52 -0700 > > Ditto here. While it wasn't "perfect" before, the new version often > over-shoots the frequency. It appears considerably less damped than > before > and often quits before things settle down. I personally prefer the > old > version. > > Rick > AI1V > K3 728 >> >> Harrison Hooker wrote: > > Hello, > > I also confirm that the auto- >> spot is broken. My CW pitch is set at 600 Hz > (only note tested) >> and it now takes several attempts to get it to set near > 600 Hz. >> The old version worked very well for me. > > 73, Harry W8YMO Elecraft mailing list Post to: [hidden email] You must be a subscriber to post to the list. Subscriber Info (Addr. Change, sub, unsub etc.): http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/subscribers.htm Elecraft web page: http://www.elecraft.com |
Re: K3 FIRMWARE UPDATE: MCU 1.87, DSP 1.69 (Finally!)
|
|
Another thing that must be mentioned is that the improved QSK is a
treat... I just finished a qso under poor condx and even with levels cranked up to hear a faint signal in QRN the QSK was very smooth - even better than before. Since I use headphones I really appreciate this. Bob NW8L On Sun, May 4, 2008 at 10:40 PM, KM5Q <[hidden email]> wrote: > I noticed the exact same thing as Harrison, below! Auto-spot is broken. > But if I have to say something nice, NR works better (on SSB at least) than > it did before! > > Windy _______________________________________________ Elecraft mailing list Post to: [hidden email] You must be a subscriber to post to the list. Subscriber Info (Addr. Change, sub, unsub etc.): http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/subscribers.htm Elecraft web page: http://www.elecraft.com |
|
|
In reply to this post by wayne burdick
<quote author="wayne burdick">
>> * SSB TRANSMIT BANDPASS EXTENDED AT LOW END. Improvement >> is about 2 dB at 300 Hz, 3 dB at 200 Hz, and 6 dB at 100 Hz. > > Can this be made optional? Excess LF response only wastes > power at low frequencies and occupies excess bandwidth. > We could add a menu entry for this -- it's on the list. Meanwhile, the > low end is rolled off a bit in hardware, too, so in practice I don't > think you'll have any problems with this. Hi. At what frequencies are the low end rolled off in hardware ? I think it should be as "flat" as possible and then rolled off by the microphone (low-cut switc etc.) or the TX eq. The TEN-TEC Omni VII for instance has a menu for TX roll-off (70-300Hz). Adding this will be a fine way for users to set the TX roll-off to the point they want. The only thing one must remember with the Omni VII is that if you set the TX bandwidth to 2400 Hz and the TX roll-off to 70Hz it will sound too "muddy". Then one must move the TX roll-off to around 200Hz to cut off the low end. This also "add's" the 200Hz you set in the TX roll-off to the upper side of the passband (moving it from 2470Hz to 2600Hz). This way the TX bandwidth is still 2400 Hz, and the TX frequency passband are 200Hz - 2600Hz. Alternativly, one can have one single SSB TX bandwidth menu who cuts off at specified frequencies: 2400 Hz : 300 - 2700 Hz 2600 Hz : 200 - 2800 Hz (default?) 2800 Hz : 200 - 3000 Hz 3000 Hz : 100 - 3100 Hz (requires 6kHz IF filter) 3500 Hz : 70 - 3570 Hz (requires 6kHz IF filter) 4000 Hz : 50 - 4050 Hz (requires 6kHz IF filter) This is maybe "easier" and more user friendly as it cuts off the low end as well, and it's easier to get a good sound without adjusting several menu's. Having a bit more low end and more bandwidth is fine when using 10m or 6m locally for ragchew on a quiet band. Best regards LA4AMA Roar |
Re: K3 FIRMWARE UPDATE: MCU 1.87, DSP 1.69 (Finally!)
|
|
In reply to this post by Joe Subich, W4TV-3
Joe Subich, W4TV wrote:
> wider than necessary. With the FM filter, the 4.2 KHz high cut is > less than the 10 KHZ of IF bandwidth. Why is the IF bandwidth and > audio response excessively restricted with the FM filter? It should > be possible to achieve at least 12 KHz of IF bandwidth and 6 KHz or > more of audio bandwidth depending on the filter skirts. FM bandwidth is a complicated issue, but I believe that, to a first approximation, you can add the peak audio frequency to the peak deviation and then double it for deviation the other way and the other sideband. This covers the dominant sideband frequencies, but actual sidebands are infinite. The most common VHF deviation is +/-2.5kHz. For communications quality audio, that gives a total bandwidth of about 10.6kHz. I'm not sure how Elecraft define deviation. Maybe they define it as peak to peak, i.e. +/1.5kHz, in which case they might get 3.5kHz maximum safe audo frequency in 10kHz. They probably can't go much above 10kHz, because they need to be compatible with 12.5kHz channeling on VHF, or even 10kHz channeling on European CB and PMR 446. Of course, for lower instantaneous peak deviations, one could get more distortion free bandwidth. I would guess that communications FM devices are designed for communication type RF bandwidths, however it is possible that cheap, or even most, devices don't explicitly limit the audio bandwidth, and simply rely on their being little audio power at high enough frequencies to suffer distortion as a result of IF bandwidth limits. The important points are that the required bandwidth for FM is rather more than twice the maximum audio frequency and that FM communications equipment, whilst maybe not designed to police audio bandwidth, isn't particularly designed for wide bandwidths. -- David Woolley "The Elecraft list is a forum for the discussion of topics related to Elecraft products and more general topics related ham radio" List Guidelines <http://www.elecraft.com/elecraft_list_guidelines.htm> _______________________________________________ Elecraft mailing list Post to: [hidden email] You must be a subscriber to post to the list. Subscriber Info (Addr. Change, sub, unsub etc.): http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/subscribers.htm Elecraft web page: http://www.elecraft.com |
«
Return to Elecraft
|
1 view|%1 views
| Free forum by Nabble | Edit this page |