K3 BETA FIRMWARE RELEASE -- MCU rev 1.94
Locked
123
123
K3 BETA FIRMWARE RELEASE -- MCU rev 1.94
 
Administrator
|
Thanks to your input on the last firmware release (1.88), we've made a
number of important improvements. For the first time, we're posting new firmware as "beta." Upgrading is optional: if you want to minimize your risk, you might want to wait until we've blessed it as a normal production firmware release. (Or until all your friends have it and you're a little jealous.) We'd love to have as many thrill-seekers as possible take the plunge and load the new firmware now. We think it's greatly improved, and it will certainly clear up many of the issues noted over the past week. Even though we're headed to Dayton in a couple of days, we'll be monitoring closely for any additional issues. For release notes and instructions on how to load beta firmware, please see: http://www.elecraft.com/K3/k3_software.htm The instructions (linked from within the release notes) explain how to create a separate folder for the beta revision. This will allow you to easily revert to an older revision if you find it necessary. Hopefully not! For your convenience I've also provide the release notes below. 73, Wayne N6KR * * * MCU 1.94 / DSP 1.73, 5-12-08 * VOX: Increased sensitivity. Typical VOX GN settings now ~30-50. * VOICE MONITOR: Eliminated “scratchy” artifacts with compression set to high levels. * FM DEVIATION ADJUSTABLE: Use CONFIG:FM DEV menu entry (default: 5.0 kHz). * Flash memory driver improved to prevent occasional receive dropouts, “ERR PL1”, and “FPF LOAD PENDING” messages. * XMIT SWITCH IN MENU: Tapping XMIT while in menu correctly starts/ends transmit. * PASSBAND SHIFT BELOW “0.00” CORRECTED: The SHIFT control no longer allows continued rotation below 0.00. (This was occurring only with sidetone pitch < 500 Hz.) * SQUELCH/RF GAIN CONTROL CHANGES: By default, the RF/SQL concentric pots control main and subreceiver RF gain, and squelch is controlled by two CONFIG menu entries (SQ MAIN and SQ SUB). But setting SQ MAIN to "=SUB POT" assigns SUB RF/SQL pot to both main and sub squelch, and in this case, the main RF/SQL pot controls both main and sub RF gain. Setting SQ MAIN back to a numeric value restores the default assignments. Note: Squelch applies only to FM mode at present. --- 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 BETA FIRMWARE RELEASE -- MCU rev 1.94
|
|
Unfortunately I see little improvement in the CW auto-spot feature,
broken in the last release. It is still much less accurate than the original algorithm, and less consistent in it's behavior. Try this - tune in a good steady (S6 or S7) cw signal. Set tuning to FINE, enable CWT and then press SPOT repeatedly, observing the frequency display. The beta version (like 1.88) settles on a considerably different frequency almost every time - moving 5 Hz or more commonly, and sometimes as much as 20 Hz or more. There is a tendency to tune low. The original version, on the other hand, rarely moves more than 1 or 2 Hz with each auto-spot invocation, bearing out the fact that it is more accurate in general, or less likely to get confused (by noise, varying morse code speed etc.). Since I have two K3 units here, I set one up with 1.78/1.58 and the other with the beta firmware, and then compared their auto-spot behavior side by side on the same received signal using an antenna switch. The difference is quite pronounced. Here are some series of freqs (last three digits) resulting from 10 successive invocations of auto-spot on the same steady S7 signal on 40 meters (at 13 wpm or so, fortunately a long winded transmission): v178/158 (TEXT DEC threshold = AUTO) 125, 125, 125, 129, 130, 130, 127, 128, 129, 129 beta (TEXT DEC threshold = AUTO) 115, 118, 124, 079 (!), 106, 106, 124, 107, 112, 100 beta (TEXT DEC threshold = 5) 124, 123, 109, 116, 118, 122, 117, 116, 120, 123 The newer firmware version tends to "bounce around" more with a tendency to tune low, often requiring multiple invocations of auto-spot to hit the right pitch, whereas the original algorithm generally tunes right the first time. With threshold set to 5 in the beta version auto-spot is a bit better, but all too often it takes multiple tries to hit the right pitch, as it still tends low. If I set the threshold much higher, it doesn't want to tune at all for signals that the original algorithm handled easily. I'm not sure what the "improvements" to auto-spot introduced in 1.88 were supposed to do, but IMO the feature is still negatively affected by the attempt. A side by side comparison of the two versions, on the same signal, is very revealing in this case - can someone else try this? Too bad, since I use the feature a lot it's back to 1.78/1.58 for now. It "just works". Bob NW8L On Mon, May 12, 2008 at 7:08 PM, wayne burdick <[hidden email]> wrote: > Thanks to your input on the last firmware release (1.88), we've made a > number of important improvements. > > For the first time, we're posting new firmware as "beta." Upgrading is > optional: if you want to minimize your risk, you might want to wait until > we've blessed it as a normal production firmware release. (Or until all your > friends have it and you're a little jealous.) > > We'd love to have as many thrill-seekers as possible take the plunge and > load the new firmware now. We think it's greatly improved, and it will > certainly clear up many of the issues noted over the past week. Even though > we're headed to Dayton in a couple of days, we'll be monitoring closely for > any additional issues. > > For release notes and instructions on how to load beta firmware, please see: > > http://www.elecraft.com/K3/k3_software.htm > > The instructions (linked from within the release notes) explain how to > create a separate folder for the beta revision. This will allow you to > easily revert to an older revision if you find it necessary. Hopefully not! > > For your convenience I've also provide the release notes below. > > 73, > Wayne > N6KR > > * * * > > MCU 1.94 / DSP 1.73, 5-12-08 > > * VOX: Increased sensitivity. Typical VOX GN settings now ~30-50. > > * VOICE MONITOR: Eliminated "scratchy" artifacts with compression set to > high levels. > > * FM DEVIATION ADJUSTABLE: Use CONFIG:FM DEV menu entry (default: 5.0 > kHz). > > * Flash memory driver improved to prevent occasional receive dropouts, "ERR > PL1", and > "FPF LOAD PENDING" messages. > > * XMIT SWITCH IN MENU: Tapping XMIT while in menu correctly starts/ends > transmit. > > * PASSBAND SHIFT BELOW "0.00" CORRECTED: The SHIFT control no longer allows > continued rotation below 0.00. (This was occurring only with sidetone > pitch < 500 Hz.) > > * SQUELCH/RF GAIN CONTROL CHANGES: By default, the RF/SQL concentric pots > control main and subreceiver RF gain, and squelch is controlled by two > CONFIG menu > entries (SQ MAIN and SQ SUB). But setting SQ MAIN to "=SUB POT" assigns > SUB RF/SQL pot to both main and sub squelch, and in this case, the main > RF/SQL > pot controls both main and sub RF gain. Setting SQ MAIN back to a numeric > value > restores the default assignments. Note: Squelch applies only to FM mode > at present. > > --- > > 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 > 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
|
On May 12, 2008, at 7:53 PM, Bob Cunnings wrote: > Unfortunately I see little improvement in the CW auto-spot feature, > broken in the last release. It is still much less accurate than the > original algorithm, and less consistent in it's behavior. Bob, Thanks for the convincing evidence. (A prime example of why we've decided to do beta firmware releases.) The original auto-spot (1.78) used the equivalent of THR = 7 (fixed). Please try this with both 1.78 and 1.94, if you don't mind. If you find that 1.78 is better, I'll take it up with Lyle (KK7P) and we'll see what might have changed in the DSP code. In any case, the main problem with this setting is that very weak signals will not auto-spot at all. Hence my attempt to add flexibility by letting the operator set the THR level. An alternative would be to go back to the original algorithm, but have the first press of SPOT use THR = 7; then, if you press it a second time within a couple of seconds, use THR = 1 (to ensure that it works with weaker signals). OK with you? 73, Wayne N6KR _______________________________________________ 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
I have to agree that the CWT worked better under the old firmware but I
think I'll put up with it until it's fixed rather than go back to an older version. I'm using the beta firmware now and notice less bouncing around of the CWT indicator but it still locks in on the wrong frequency unless you punch it multiple times. Steve Ellington [hidden email] ----- Original Message ----- From: "Bob Cunnings" <[hidden email]> To: "wayne burdick" <[hidden email]> Cc: "Elecraft Reflector" <[hidden email]> Sent: Monday, May 12, 2008 10:53 PM Subject: Re: [Elecraft] K3 BETA FIRMWARE RELEASE -- MCU rev 1.94 > Unfortunately I see little improvement in the CW auto-spot feature, > broken in the last release. It is still much less accurate than the > original algorithm, and less consistent in it's behavior. > > Try this - tune in a good steady (S6 or S7) cw signal. Set tuning to > FINE, enable CWT and then press SPOT repeatedly, observing the > frequency display. The beta version (like 1.88) settles on a > considerably different frequency almost every time - moving 5 Hz or > more commonly, and sometimes as much as 20 Hz or more. There is a > tendency to tune low. The original version, on the other hand, rarely > moves more than 1 or 2 Hz with each auto-spot invocation, bearing out > the fact that it is more accurate in general, or less likely to get > confused (by noise, varying morse code speed etc.). > > Since I have two K3 units here, I set one up with 1.78/1.58 and the > other with the beta firmware, and then compared their auto-spot > behavior side by side on the same received signal using an antenna > switch. The difference is quite pronounced. Here are some series of > freqs (last three digits) resulting from 10 successive invocations of > auto-spot on the same steady S7 signal on 40 meters (at 13 wpm or so, > fortunately a long winded transmission): > > v178/158 (TEXT DEC threshold = AUTO) > 125, 125, 125, 129, 130, 130, 127, 128, 129, 129 > > beta (TEXT DEC threshold = AUTO) > 115, 118, 124, 079 (!), 106, 106, 124, 107, 112, 100 > > beta (TEXT DEC threshold = 5) > 124, 123, 109, 116, 118, 122, 117, 116, 120, 123 > > The newer firmware version tends to "bounce around" more with a > tendency to tune low, often requiring multiple invocations of > auto-spot to hit the right pitch, whereas the original algorithm > generally tunes right the first time. With threshold set to 5 in the > beta version auto-spot is a bit better, but all too often it takes > multiple tries to hit the right pitch, as it still tends low. If I set > the threshold much higher, it doesn't want to tune at all for signals > that the original algorithm handled easily. > > I'm not sure what the "improvements" to auto-spot introduced in 1.88 > were supposed to do, but IMO the feature is still negatively affected > by the attempt. A side by side comparison of the two versions, on the > same signal, is very revealing in this case - can someone else try > this? > > Too bad, since I use the feature a lot it's back to 1.78/1.58 for now. > It "just works". > > Bob NW8L > > > > On Mon, May 12, 2008 at 7:08 PM, wayne burdick <[hidden email]> wrote: >> Thanks to your input on the last firmware release (1.88), we've made a >> number of important improvements. >> >> For the first time, we're posting new firmware as "beta." Upgrading is >> optional: if you want to minimize your risk, you might want to wait until >> we've blessed it as a normal production firmware release. (Or until all >> your >> friends have it and you're a little jealous.) >> >> We'd love to have as many thrill-seekers as possible take the plunge and >> load the new firmware now. We think it's greatly improved, and it will >> certainly clear up many of the issues noted over the past week. Even >> though >> we're headed to Dayton in a couple of days, we'll be monitoring closely >> for >> any additional issues. >> >> For release notes and instructions on how to load beta firmware, please >> see: >> >> http://www.elecraft.com/K3/k3_software.htm >> >> The instructions (linked from within the release notes) explain how to >> create a separate folder for the beta revision. This will allow you to >> easily revert to an older revision if you find it necessary. Hopefully >> not! >> >> For your convenience I've also provide the release notes below. >> >> 73, >> Wayne >> N6KR >> >> * * * >> >> MCU 1.94 / DSP 1.73, 5-12-08 >> >> * VOX: Increased sensitivity. Typical VOX GN settings now ~30-50. >> >> * VOICE MONITOR: Eliminated "scratchy" artifacts with compression set to >> high levels. >> >> * FM DEVIATION ADJUSTABLE: Use CONFIG:FM DEV menu entry (default: 5.0 >> kHz). >> >> * Flash memory driver improved to prevent occasional receive dropouts, >> "ERR >> PL1", and >> "FPF LOAD PENDING" messages. >> >> * XMIT SWITCH IN MENU: Tapping XMIT while in menu correctly starts/ends >> transmit. >> >> * PASSBAND SHIFT BELOW "0.00" CORRECTED: The SHIFT control no longer >> allows >> continued rotation below 0.00. (This was occurring only with sidetone >> pitch < 500 Hz.) >> >> * SQUELCH/RF GAIN CONTROL CHANGES: By default, the RF/SQL concentric >> pots >> control main and subreceiver RF gain, and squelch is controlled by two >> CONFIG menu >> entries (SQ MAIN and SQ SUB). But setting SQ MAIN to "=SUB POT" >> assigns >> SUB RF/SQL pot to both main and sub squelch, and in this case, the >> main >> RF/SQL >> pot controls both main and sub RF gain. Setting SQ MAIN back to a >> numeric >> value >> restores the default assignments. Note: Squelch applies only to FM >> mode >> at present. >> >> --- >> >> 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 >> > _______________________________________________ > 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 -------------------------------------------------------------------------------- No virus found in this incoming message. Checked by AVG. Version: 8.0.100 / Virus Database: 269.23.16/1429 - Release Date: 5/12/2008 6:14 PM _______________________________________________ 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
Ok, here are 10 frequencies (last 3 digits) obtained by repeatedly
invoking auto-spot with a steady S8 cw signal, around 15 wpm: unit A - 1.78/1.58 (THR = 7) 845, 845, 845, 844, 845, 845, 845, 845, 844, 844 unit B - beta 1.94/1.73 (THR = 7) 830, 823, 829, 840, 840, 846, 831, 837, 838, 832 more variation observed with the beta version, and still often settling on the low side. Hope this helps, Bob NW8L On Mon, May 12, 2008 at 9:13 PM, wayne burdick <[hidden email]> wrote: > > On May 12, 2008, at 7:53 PM, Bob Cunnings wrote: > >> Unfortunately I see little improvement in the CW auto-spot feature, >> broken in the last release. It is still much less accurate than the >> original algorithm, and less consistent in it's behavior. > > Bob, > > Thanks for the convincing evidence. (A prime example of why we've decided to > do beta firmware releases.) > > The original auto-spot (1.78) used the equivalent of THR = 7 (fixed). Please > try this with both 1.78 and 1.94, if you don't mind. If you find that 1.78 > is better, I'll take it up with Lyle (KK7P) and we'll see what might have > changed in the DSP code. > > In any case, the main problem with this setting is that very weak signals > will not auto-spot at all. Hence my attempt to add flexibility by letting > the operator set the THR level. > > An alternative would be to go back to the original algorithm, but have the > first press of SPOT use THR = 7; then, if you press it a second time within > a couple of seconds, use THR = 1 (to ensure that it works with weaker > signals). > > OK with you? > > 73, > Wayne > N6KR > > 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 BETA FIRMWARE RELEASE -- MCU rev 1.94
|
|
In reply to this post by wayne burdick
The Easter egg in v1.94 Beta is more sidetone volume!
Or did I miss this in the release notes? 73, john WA1ABI _______________________________________________ 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 BETA FIRMWARE RELEASE -- MCU rev 1.94
|
|
In reply to this post by wayne burdick
I'm not sure if this has been mentioned before, but after a F/W upgrade, I
found that I need power down the K3, then re-press the power button. Otherwise, some anomalies exist, including elevated headphone hiss and slight clicks in the monitor when sending CW. I've now noticed this on at least the last two F/W upgrades. Re-booting the power immediately after the flash has cleared the issue every time. Paul, W9AC _______________________________________________ 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 BETA FIRMWARE RELEASE -- MCU rev 1.94
|
|
In reply to this post by Bob Cunnings NW8L
Bob, Try setting the threshold to 2 or 3 (CWT Hold). With a fixed threshold, it seems very close to the previous performance on all but the strongest signals (and even the old FW was a bit touchy with S9+20 signals). 73, ... Joe, W4TV > -----Original Message----- > From: [hidden email] > [mailto:[hidden email]] On Behalf Of Bob Cunnings > Sent: Monday, May 12, 2008 10:53 PM > To: wayne burdick > Cc: Elecraft Reflector > Subject: Re: [Elecraft] K3 BETA FIRMWARE RELEASE -- MCU rev 1.94 > > > Unfortunately I see little improvement in the CW auto-spot feature, > broken in the last release. It is still much less accurate than the > original algorithm, and less consistent in it's behavior. > > Try this - tune in a good steady (S6 or S7) cw signal. Set tuning to > FINE, enable CWT and then press SPOT repeatedly, observing the > frequency display. The beta version (like 1.88) settles on a > considerably different frequency almost every time - moving 5 Hz or > more commonly, and sometimes as much as 20 Hz or more. There is a > tendency to tune low. The original version, on the other hand, rarely > moves more than 1 or 2 Hz with each auto-spot invocation, bearing out > the fact that it is more accurate in general, or less likely to get > confused (by noise, varying morse code speed etc.). > > Since I have two K3 units here, I set one up with 1.78/1.58 and the > other with the beta firmware, and then compared their auto-spot > behavior side by side on the same received signal using an antenna > switch. The difference is quite pronounced. Here are some series of > freqs (last three digits) resulting from 10 successive invocations of > auto-spot on the same steady S7 signal on 40 meters (at 13 wpm or so, > fortunately a long winded transmission): > > v178/158 (TEXT DEC threshold = AUTO) > 125, 125, 125, 129, 130, 130, 127, 128, 129, 129 > > beta (TEXT DEC threshold = AUTO) > 115, 118, 124, 079 (!), 106, 106, 124, 107, 112, 100 > > beta (TEXT DEC threshold = 5) > 124, 123, 109, 116, 118, 122, 117, 116, 120, 123 > > The newer firmware version tends to "bounce around" more with a > tendency to tune low, often requiring multiple invocations of > auto-spot to hit the right pitch, whereas the original algorithm > generally tunes right the first time. With threshold set to 5 in the > beta version auto-spot is a bit better, but all too often it takes > multiple tries to hit the right pitch, as it still tends low. If I set > the threshold much higher, it doesn't want to tune at all for signals > that the original algorithm handled easily. > > I'm not sure what the "improvements" to auto-spot introduced in 1.88 > were supposed to do, but IMO the feature is still negatively affected > by the attempt. A side by side comparison of the two versions, on the > same signal, is very revealing in this case - can someone else try > this? > > Too bad, since I use the feature a lot it's back to 1.78/1.58 for now. > It "just works". > > Bob NW8L > > > > On Mon, May 12, 2008 at 7:08 PM, wayne burdick > <[hidden email]> wrote: > > Thanks to your input on the last firmware release (1.88), > we've made a > > number of important improvements. > > > > For the first time, we're posting new firmware as "beta." > Upgrading is > > optional: if you want to minimize your risk, you might want > to wait until > > we've blessed it as a normal production firmware release. > (Or until all your > > friends have it and you're a little jealous.) > > > > We'd love to have as many thrill-seekers as possible take > the plunge and > > load the new firmware now. We think it's greatly improved, > and it will > > certainly clear up many of the issues noted over the past > week. Even though > > we're headed to Dayton in a couple of days, we'll be > monitoring closely for > > any additional issues. > > > > For release notes and instructions on how to load beta > firmware, please see: > > > > http://www.elecraft.com/K3/k3_software.htm > > > > The instructions (linked from within the release notes) > explain how to > > create a separate folder for the beta revision. This will > allow you to > > easily revert to an older revision if you find it > necessary. Hopefully not! > > > > For your convenience I've also provide the release notes below. > > > > 73, > > Wayne > > N6KR > > > > * * * > > > > MCU 1.94 / DSP 1.73, 5-12-08 > > > > * VOX: Increased sensitivity. Typical VOX GN settings now ~30-50. > > > > * VOICE MONITOR: Eliminated "scratchy" artifacts with > compression set to > > high levels. > > > > * FM DEVIATION ADJUSTABLE: Use CONFIG:FM DEV menu entry > (default: 5.0 > > kHz). > > > > * Flash memory driver improved to prevent occasional > receive dropouts, "ERR > > PL1", and > > "FPF LOAD PENDING" messages. > > > > * XMIT SWITCH IN MENU: Tapping XMIT while in menu > correctly starts/ends > > transmit. > > > > * PASSBAND SHIFT BELOW "0.00" CORRECTED: The SHIFT control > no longer allows > > continued rotation below 0.00. (This was occurring only > with sidetone > > pitch < 500 Hz.) > > > > * SQUELCH/RF GAIN CONTROL CHANGES: By default, the RF/SQL > concentric pots > > control main and subreceiver RF gain, and squelch is > controlled by two > > CONFIG menu > > entries (SQ MAIN and SQ SUB). But setting SQ MAIN to > "=SUB POT" assigns > > SUB RF/SQL pot to both main and sub squelch, and in this > case, the main > > RF/SQL > > pot controls both main and sub RF gain. Setting SQ MAIN > back to a numeric > > value > > restores the default assignments. Note: Squelch applies > only to FM mode > > at present. > > > > --- > > > > 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 > > > _______________________________________________ > 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 > Checked by AVG. > Version: 8.0.100 / Virus Database: 269.23.16/1428 - Release > Date: 5/12/2008 7:44 AM > _______________________________________________ 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 BETA FIRMWARE RELEASE -- MCU rev 1.94
|
|
Well, I have, and found that the lower the threshold, the less stable.
Using the beta version, with THR = 2 excursions of 20 Hz between auto-spot invocations are not uncommon - yet on the same signal (S5 or so) the 1.78 version performs very well. The side by side comparison with two rigs using the same signal is telling. I'll play with it a bit more this evening. Bob NW8L On Tue, May 13, 2008 at 8:56 AM, Joe Subich, W4TV <[hidden email]> wrote: > > Bob, > > Try setting the threshold to 2 or 3 (CWT Hold). With a fixed > threshold, it seems very close to the previous performance on > all but the strongest signals (and even the old FW was a bit > touchy with S9+20 signals). > > 73, > > ... Joe, W4TV > > > >> -----Original Message----- >> From: [hidden email] >> [mailto:[hidden email]] On Behalf Of Bob Cunnings >> Sent: Monday, May 12, 2008 10:53 PM >> To: wayne burdick >> Cc: Elecraft Reflector >> Subject: Re: [Elecraft] K3 BETA FIRMWARE RELEASE -- MCU rev 1.94 >> >> >> Unfortunately I see little improvement in the CW auto-spot feature, >> broken in the last release. It is still much less accurate than the >> original algorithm, and less consistent in it's behavior. >> >> Try this - tune in a good steady (S6 or S7) cw signal. Set tuning to >> FINE, enable CWT and then press SPOT repeatedly, observing the >> frequency display. The beta version (like 1.88) settles on a >> considerably different frequency almost every time - moving 5 Hz or >> more commonly, and sometimes as much as 20 Hz or more. There is a >> tendency to tune low. The original version, on the other hand, rarely >> moves more than 1 or 2 Hz with each auto-spot invocation, bearing out >> the fact that it is more accurate in general, or less likely to get >> confused (by noise, varying morse code speed etc.). >> >> Since I have two K3 units here, I set one up with 1.78/1.58 and the >> other with the beta firmware, and then compared their auto-spot >> behavior side by side on the same received signal using an antenna >> switch. The difference is quite pronounced. Here are some series of >> freqs (last three digits) resulting from 10 successive invocations of >> auto-spot on the same steady S7 signal on 40 meters (at 13 wpm or so, >> fortunately a long winded transmission): >> >> v178/158 (TEXT DEC threshold = AUTO) >> 125, 125, 125, 129, 130, 130, 127, 128, 129, 129 >> >> beta (TEXT DEC threshold = AUTO) >> 115, 118, 124, 079 (!), 106, 106, 124, 107, 112, 100 >> >> beta (TEXT DEC threshold = 5) >> 124, 123, 109, 116, 118, 122, 117, 116, 120, 123 >> >> The newer firmware version tends to "bounce around" more with a >> tendency to tune low, often requiring multiple invocations of >> auto-spot to hit the right pitch, whereas the original algorithm >> generally tunes right the first time. With threshold set to 5 in the >> beta version auto-spot is a bit better, but all too often it takes >> multiple tries to hit the right pitch, as it still tends low. If I set >> the threshold much higher, it doesn't want to tune at all for signals >> that the original algorithm handled easily. >> >> I'm not sure what the "improvements" to auto-spot introduced in 1.88 >> were supposed to do, but IMO the feature is still negatively affected >> by the attempt. A side by side comparison of the two versions, on the >> same signal, is very revealing in this case - can someone else try >> this? >> >> Too bad, since I use the feature a lot it's back to 1.78/1.58 for now. >> It "just works". >> >> Bob NW8L >> >> >> >> On Mon, May 12, 2008 at 7:08 PM, wayne burdick >> <[hidden email]> wrote: >> > Thanks to your input on the last firmware release (1.88), >> we've made a >> > number of important improvements. >> > >> > For the first time, we're posting new firmware as "beta." >> Upgrading is >> > optional: if you want to minimize your risk, you might want >> to wait until >> > we've blessed it as a normal production firmware release. >> (Or until all your >> > friends have it and you're a little jealous.) >> > >> > We'd love to have as many thrill-seekers as possible take >> the plunge and >> > load the new firmware now. We think it's greatly improved, >> and it will >> > certainly clear up many of the issues noted over the past >> week. Even though >> > we're headed to Dayton in a couple of days, we'll be >> monitoring closely for >> > any additional issues. >> > >> > For release notes and instructions on how to load beta >> firmware, please see: >> > >> > http://www.elecraft.com/K3/k3_software.htm >> > >> > The instructions (linked from within the release notes) >> explain how to >> > create a separate folder for the beta revision. This will >> allow you to >> > easily revert to an older revision if you find it >> necessary. Hopefully not! >> > >> > For your convenience I've also provide the release notes below. >> > >> > 73, >> > Wayne >> > N6KR >> > >> > * * * >> > >> > MCU 1.94 / DSP 1.73, 5-12-08 >> > >> > * VOX: Increased sensitivity. Typical VOX GN settings now ~30-50. >> > >> > * VOICE MONITOR: Eliminated "scratchy" artifacts with >> compression set to >> > high levels. >> > >> > * FM DEVIATION ADJUSTABLE: Use CONFIG:FM DEV menu entry >> (default: 5.0 >> > kHz). >> > >> > * Flash memory driver improved to prevent occasional >> receive dropouts, "ERR >> > PL1", and >> > "FPF LOAD PENDING" messages. >> > >> > * XMIT SWITCH IN MENU: Tapping XMIT while in menu >> correctly starts/ends >> > transmit. >> > >> > * PASSBAND SHIFT BELOW "0.00" CORRECTED: The SHIFT control >> no longer allows >> > continued rotation below 0.00. (This was occurring only >> with sidetone >> > pitch < 500 Hz.) >> > >> > * SQUELCH/RF GAIN CONTROL CHANGES: By default, the RF/SQL >> concentric pots >> > control main and subreceiver RF gain, and squelch is >> controlled by two >> > CONFIG menu >> > entries (SQ MAIN and SQ SUB). But setting SQ MAIN to >> "=SUB POT" assigns >> > SUB RF/SQL pot to both main and sub squelch, and in this >> case, the main >> > RF/SQL >> > pot controls both main and sub RF gain. Setting SQ MAIN >> back to a numeric >> > value >> > restores the default assignments. Note: Squelch applies >> only to FM mode >> > at present. >> > >> > --- >> > >> > 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 >> > >> _______________________________________________ >> 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 >> Checked by AVG. >> Version: 8.0.100 / Virus Database: 269.23.16/1428 - Release >> Date: 5/12/2008 7:44 AM >> > > 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 Joe Subich, W4TV-3
On Tue, 13 May 2008 10:56:27 -0400, Joe, W4TV wrote:
> >Bob, > >Try setting the threshold to 2 or 3 (CWT Hold). With a fixed >threshold, it seems very close to the previous performance on >all but the strongest signals (and even the old FW was a bit >touchy with S9+20 signals). > >73, > > ... Joe, W4TV That worked very well here on #806" Tom, N5GE - SWOT 3537 - Grid EM12jq "Those who would give up Essential Liberty to purchase a little Temporary Safety deserve neither Liberty nor Safety" An excerpt from a letter written in 1755 from the Assembly to the Governor of Pennsylvania. Support the entire Constitution, not just the parts you like. http://www.n5ge.com http://www.eQSL.cc/Member.cfm?N5GE _______________________________________________ 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
Amateur Radio Operator N5GE
|
|
|
In reply to this post by Bob Cunnings NW8L
I'm getting the same result as Bob. No matter how I set the threshold, 2,3, Automatic, etc, I cannot get it to perform as well as the old 1.78 version which was just amazing.
Windy KM5Q <quote author="Bob Cunnings"> Well, I have, and found that the lower the threshold, the less stable. Using the beta version, with THR = 2 excursions of 20 Hz between auto-spot invocations are not uncommon - yet on the same signal (S5 or so) the 1.78 version performs very well. The side by side comparison with two rigs using the same signal is telling. I'll play with it a bit more this evening. Bob NW8L On Tue, May 13, 2008 at 8:56 AM, Joe Subich, W4TV <lists@microham-usa.com> wrote: > > Bob, > > Try setting the threshold to 2 or 3 (CWT Hold). With a fixed > threshold, it seems very close to the previous performance on > all but the strongest signals (and even the old FW was a bit > touchy with S9+20 signals). > > 73, > > ... Joe, W4TV |
|
|
Something has happened to the S-meter in this release. All of a sudden I have signals that are 60dB over S9. I am sure there is no more than 6-10dB between S9+10 and S9+60. This is also evident when backing off the RF gain. I have not made any CONFIG changes in order to use the new absolute S-meter setting. I have not recalibrated the S-meter. What is wrong here?
Knut - AB2TC <quote author="Windy Dankoff KM5Q"> I'm getting the same result as Bob. No matter how I set the threshold, 2,3, Automatic, etc, I cannot get it to perform as well as the old 1.78 version which was just amazing. Windy KM5Q
|
|
|
In reply to this post by wayne burdick
I loaded rev 1.94 yesterday evening. My main problem is the not working
VOX in 1.88. However it was more worse than with 1.88! Once set to VOX I couldn't set it back to PTT. It switched the whole time to TX, no matter what MIC gain settings I choosed. (Oh, I didn't tried the VOX gain, it is still at 35, maybe this would help?!). Well, also the TRX seemed to had some kind of other problems. All LEDs swichted to on and off again, the display get's dark and some relays clicked. Then it came back. This happened several times. Does anybody had similar problems? Or did I make another mistake? 73! Frank, DD7ZT wayne burdick schrieb: > Thanks to your input on the last firmware release (1.88), we've made a > number of important improvements. > > For the first time, we're posting new firmware as "beta." Upgrading is > optional: if you want to minimize your risk, you might want to wait > until we've blessed it as a normal production firmware release. (Or > until all your friends have it and you're a little jealous.) > > We'd love to have as many thrill-seekers as possible take the plunge and > load the new firmware now. We think it's greatly improved, and it will > certainly clear up many of the issues noted over the past week. Even > though we're headed to Dayton in a couple of days, we'll be monitoring > closely for any additional issues. > > For release notes and instructions on how to load beta firmware, please > see: > > http://www.elecraft.com/K3/k3_software.htm > > The instructions (linked from within the release notes) explain how to > create a separate folder for the beta revision. This will allow you to > easily revert to an older revision if you find it necessary. Hopefully not! > > For your convenience I've also provide the release notes below. > > 73, > Wayne > N6KR > > * * * > > MCU 1.94 / DSP 1.73, 5-12-08 > > * VOX: Increased sensitivity. Typical VOX GN settings now ~30-50. > > * VOICE MONITOR: Eliminated “scratchy” artifacts with compression set > to high levels. > > * FM DEVIATION ADJUSTABLE: Use CONFIG:FM DEV menu entry (default: 5.0 > kHz). > > * Flash memory driver improved to prevent occasional receive dropouts, > “ERR PL1”, and > “FPF LOAD PENDING” messages. > > * XMIT SWITCH IN MENU: Tapping XMIT while in menu correctly > starts/ends transmit. > > * PASSBAND SHIFT BELOW “0.00” CORRECTED: The SHIFT control no longer > allows > continued rotation below 0.00. (This was occurring only with > sidetone pitch < 500 Hz.) > > * SQUELCH/RF GAIN CONTROL CHANGES: By default, the RF/SQL concentric pots > control main and subreceiver RF gain, and squelch is controlled by > two CONFIG menu > entries (SQ MAIN and SQ SUB). But setting SQ MAIN to "=SUB POT" assigns > SUB RF/SQL pot to both main and sub squelch, and in this case, the > main RF/SQL > pot controls both main and sub RF gain. Setting SQ MAIN back to a > numeric value > restores the default assignments. Note: Squelch applies only to FM > mode at present. > > --- > > 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 > > _______________________________________________ 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 BETA FIRMWARE RELEASE -- MCU rev 1.94 / doesn't work at all (?!)
|
|
No problems here.
Just an "off the wall thought", is the DC supply to your K3 OK ? I had a similar symptoms with a loose PSU connection. 73 Stewart G3RXQ On Wed, 14 May 2008 09:28:11 +0200, Frank Lammel wrote: > I loaded rev 1.94 yesterday evening. My main problem is the not working > VOX in 1.88. However it was more worse than with 1.88! Once set to VOX I > couldn't set it back to PTT. It switched the whole time to TX, no matter > what MIC gain settings I choosed. (Oh, I didn't tried the VOX gain, it > is still at 35, maybe this would help?!). Well, also the TRX seemed to > had some kind of other problems. All LEDs swichted to on and off again, > the display get's dark and some relays clicked. Then it came back. This > happened several times. > > Does anybody had similar problems? Or did I make another mistake? > > 73! > Frank, DD7ZT > > > wayne burdick schrieb: >> Thanks to your input on the last firmware release (1.88), we've made a >> number of important improvements. >> >> For the first time, we're posting new firmware as "beta." Upgrading is >> optional: if you want to minimize your risk, you might want to wait >> until we've blessed it as a normal production firmware release. (Or >> until all your friends have it and you're a little jealous.) >> >> We'd love to have as many thrill-seekers as possible take the plunge and >> load the new firmware now. We think it's greatly improved, and it will >> certainly clear up many of the issues noted over the past week. Even >> though we're headed to Dayton in a couple of days, we'll be monitoring >> closely for any additional issues. >> >> For release notes and instructions on how to load beta firmware, please >> see: >> >> http://www.elecraft.com/K3/k3_software.htm >> >> The instructions (linked from within the release notes) explain how to >> create a separate folder for the beta revision. This will allow you to >> easily revert to an older revision if you find it necessary. Hopefully not! >> >> For your convenience I've also provide the release notes below. >> >> 73, >> Wayne >> N6KR >> >> * * * >> >> MCU 1.94 / DSP 1.73, 5-12-08 >> >> * VOX: Increased sensitivity. Typical VOX GN settings now >> >> * VOICE MONITOR: Eliminated "scratchy" artifacts with compression set >> to high levels. >> >> * FM DEVIATION ADJUSTABLE: Use CONFIG:FM DEV menu entry (default: 5.0 >> kHz). >> >> * Flash memory driver improved to prevent occasional receive dropouts, >> "ERR PL1", and >> "FPF LOAD PENDING" messages. >> >> * XMIT SWITCH IN MENU: Tapping XMIT while in menu correctly >> starts/ends transmit. >> >> * PASSBAND SHIFT BELOW "0.00" CORRECTED: The SHIFT control no longer >> allows >> continued rotation below 0.00. (This was occurring only with >> sidetone pitch < 500 Hz.) >> >> * SQUELCH/RF GAIN CONTROL CHANGES: By default, the RF/SQL concentric pots >> control main and subreceiver RF gain, and squelch is controlled by >> two CONFIG menu >> entries (SQ MAIN and SQ SUB). But setting SQ MAIN to "=SUB POT" assigns >> SUB RF/SQL pot to both main and sub squelch, and in this case, the >> main RF/SQL >> pot controls both main and sub RF gain. Setting SQ MAIN back to a >> numeric value >> restores the default assignments. Note: Squelch applies only to FM >> mode at present. >> >> --- >> >> 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 >> > > _______________________________________________ > 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 DD7ZT
On Wed, 14 May 2008 09:28:11 +0200, you wrote:
>I loaded rev 1.94 yesterday evening. My main problem is the not working >VOX in 1.88. However it was more worse than with 1.88! Once set to VOX I >couldn't set it back to PTT. It switched the whole time to TX, no matter >what MIC gain settings I choosed. (Oh, I didn't tried the VOX gain, it >is still at 35, maybe this would help?!). Well, also the TRX seemed to >had some kind of other problems. All LEDs swichted to on and off again, >the display get's dark and some relays clicked. Then it came back. This >happened several times. > >Does anybody had similar problems? Or did I make another mistake? > >73! >Frank, DD7ZT > Works great here. [# 806) Tom, N5GE - SWOT 3537 - Grid EM12jq "Those who would give up Essential Liberty to purchase a little Temporary Safety deserve neither Liberty nor Safety" An excerpt from a letter written in 1755 from the Assembly to the Governor of Pennsylvania. Support the entire Constitution, not just the parts you like. http://www.n5ge.com http://www.eQSL.cc/Member.cfm?N5GE _______________________________________________ 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
Amateur Radio Operator N5GE
|
Re: K3 BETA FIRMWARE RELEASE -- MCU rev 1.94
|
|
In reply to this post by wayne burdick
No problems here with Beta 1.94, seems to work great, including Autospot.
This just keeps on getting better! Hope I didn't speak too soon... Thanks
|
|
|
In reply to this post by Stewart Baker
Downgrade back to 1.88 made it work again. So I don't think it comes
from outside the box... 73 Frank, DD7ZT Stewart Baker schrieb: > No problems here. > Just an "off the wall thought", is the DC supply to your K3 OK ? > I had a similar symptoms with a loose PSU connection. > > 73 > Stewart G3RXQ > On Wed, 14 May 2008 09:28:11 +0200, Frank Lammel wrote: >> I loaded rev 1.94 yesterday evening. My main problem is the not > working >> VOX in 1.88. However it was more worse than with 1.88! Once set > to VOX I >> couldn't set it back to PTT. It switched the whole time to TX, > no matter >> what MIC gain settings I choosed. (Oh, I didn't tried the VOX > gain, it >> is still at 35, maybe this would help?!). Well, also the TRX > seemed to >> had some kind of other problems. All LEDs swichted to on and off > again, >> the display get's dark and some relays clicked. Then it came > back. This >> happened several times. >> >> Does anybody had similar problems? Or did I make another > mistake? >> 73! >> Frank, DD7ZT >> >> >> wayne burdick schrieb: >>> Thanks to your input on the last firmware release (1.88), we've > made a >>> number of important improvements. >>> >>> For the first time, we're posting new firmware as "beta." > Upgrading is >>> optional: if you want to minimize your risk, you might want to > wait >>> until we've blessed it as a normal production firmware release. > (Or >>> until all your friends have it and you're a little jealous.) >>> >>> We'd love to have as many thrill-seekers as possible take the > plunge and >>> load the new firmware now. We think it's greatly improved, and > it will >>> certainly clear up many of the issues noted over the past week. > Even >>> though we're headed to Dayton in a couple of days, we'll be > monitoring >>> closely for any additional issues. >>> >>> For release notes and instructions on how to load beta > firmware, please >>> see: >>> >>> http://www.elecraft.com/K3/k3_software.htm >>> >>> The instructions (linked from within the release notes) explain > how to >>> create a separate folder for the beta revision. This will allow > you to >>> easily revert to an older revision if you find it necessary. > Hopefully not! >>> For your convenience I've also provide the release notes below. >>> >>> 73, >>> Wayne >>> N6KR >>> >>> * * * >>> >>> MCU 1.94 / DSP 1.73, 5-12-08 >>> >>> * VOX: Increased sensitivity. Typical VOX GN settings now > ~30-50. >>> * VOICE MONITOR: Eliminated "scratchy" artifacts with > compression set >>> to high levels. >>> >>> * FM DEVIATION ADJUSTABLE: Use CONFIG:FM DEV menu entry > (default: 5.0 >>> kHz). >>> >>> * Flash memory driver improved to prevent occasional receive > dropouts, >>> "ERR PL1", and >>> "FPF LOAD PENDING" messages. >>> >>> * XMIT SWITCH IN MENU: Tapping XMIT while in menu correctly >>> starts/ends transmit. >>> >>> * PASSBAND SHIFT BELOW "0.00" CORRECTED: The SHIFT control no > longer >>> allows >>> continued rotation below 0.00. (This was occurring only with >>> sidetone pitch < 500 Hz.) >>> >>> * SQUELCH/RF GAIN CONTROL CHANGES: By default, the RF/SQL > concentric pots >>> control main and subreceiver RF gain, and squelch is controlled > by >>> two CONFIG menu >>> entries (SQ MAIN and SQ SUB). But setting SQ MAIN to "=SUB POT" > assigns >>> SUB RF/SQL pot to both main and sub squelch, and in this case, > the >>> main RF/SQL >>> pot controls both main and sub RF gain. Setting SQ MAIN back to > a >>> numeric value >>> restores the default assignments. Note: Squelch applies only to > FM >>> mode at present. >>> >>> --- >>> >>> 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 >>> >> _______________________________________________ >> 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
Guys,
There is another way to solve the CW spot problem. It's called get on the air and work CW. You will quickly develop the skill of zero beating by ear. You will find that most CW ops don't use any zero beating gizmo. Much faster and easier to do it by ear. Another thing. Narrow filter passbands help. If you're trying to zero beat a CW signal with a 2.8KHz filter, it can be an exercise in futiltiy. And if a human can't do it, don't expect some computerized gizmo to do it well either. Practically speaking, if you've dialed in a 200- 400Hz CW bandwidth and you peak the signal in the passband, your going to be at most 100Hz off. That is really plenty good enough for most situations. How accurate can zero beating by ear be? The data points I have are from RTTY. My display indicator reads out deviation from zero in 5 Hz increments. I can usually get within 10-20 Hz by ear! I'm going to assume the CW accuracy is similar. 73 de Brian/K3KO
|
Re: K3 BETA FIRMWARE RELEASE -- MCU rev 1.94
|
|
On many TCVRs - if you are not in QSK mode - you can just press key
and hear pitch tone (sidetone) and tune signal to zero beat. This is one reason I was opening KEY OUT port settings wish - to have sidetone only without keying to TX by pressing key (in nonQSK), but it is another story ;-) On the other side this ability to tune without some special help depends also on individual ability to recognize tones (musical ear). 73! Lexa, ok1dst K3/10 #727 K3KO napsal(a): > Guys, > > There is another way to solve the CW spot problem. > > It's called get on the air and work CW. You will quickly develop the skill > of zero beating by ear. > You will find that most CW ops don't use any zero beating gizmo. Much > faster and easier to do it by ear. > > Another thing. Narrow filter passbands help. If you're trying to zero beat > a CW signal with a 2.8KHz filter, it can be an exercise in futiltiy. And > if a human can't do it, don't expect some computerized gizmo to do it well > either. > > Practically speaking, if you've dialed in a 200- 400Hz CW bandwidth and you > peak the signal in the passband, your going to be at most 100Hz off. That > is really plenty good enough for most situations. > > How accurate can zero beating by ear be? The data points I have are from > RTTY. My display indicator reads out deviation from zero in 5 Hz > increments. I can usually get within 10-20 Hz by ear! I'm going to > assume the CW accuracy is similar. > > 73 de Brian/K3KO > > > > > > Bob Cunnings wrote: >> Unfortunately I see little improvement in the CW auto-spot feature, >> broken in the last release. It is still much less accurate than the >> original algorithm, and less consistent in it's behavior. >> >> Try this - tune in a good steady (S6 or S7) cw signal. Set tuning to >> FINE, enable CWT and then press SPOT repeatedly, observing the >> frequency display. The beta version (like 1.88) settles on a >> considerably different frequency almost every time - moving 5 Hz or >> more commonly, and sometimes as much as 20 Hz or more. There is a >> tendency to tune low. The original version, on the other hand, rarely >> moves more than 1 or 2 Hz with each auto-spot invocation, bearing out >> the fact that it is more accurate in general, or less likely to get >> confused (by noise, varying morse code speed etc.). >> >> Since I have two K3 units here, I set one up with 1.78/1.58 and the >> other with the beta firmware, and then compared their auto-spot >> behavior side by side on the same received signal using an antenna >> switch. The difference is quite pronounced. Here are some series of >> freqs (last three digits) resulting from 10 successive invocations of >> auto-spot on the same steady S7 signal on 40 meters (at 13 wpm or so, >> fortunately a long winded transmission): >> >> v178/158 (TEXT DEC threshold = AUTO) >> 125, 125, 125, 129, 130, 130, 127, 128, 129, 129 >> >> beta (TEXT DEC threshold = AUTO) >> 115, 118, 124, 079 (!), 106, 106, 124, 107, 112, 100 >> >> beta (TEXT DEC threshold = 5) >> 124, 123, 109, 116, 118, 122, 117, 116, 120, 123 >> >> The newer firmware version tends to "bounce around" more with a >> tendency to tune low, often requiring multiple invocations of >> auto-spot to hit the right pitch, whereas the original algorithm >> generally tunes right the first time. With threshold set to 5 in the >> beta version auto-spot is a bit better, but all too often it takes >> multiple tries to hit the right pitch, as it still tends low. If I set >> the threshold much higher, it doesn't want to tune at all for signals >> that the original algorithm handled easily. >> >> I'm not sure what the "improvements" to auto-spot introduced in 1.88 >> were supposed to do, but IMO the feature is still negatively affected >> by the attempt. A side by side comparison of the two versions, on the >> same signal, is very revealing in this case - can someone else try >> this? >> >> Too bad, since I use the feature a lot it's back to 1.78/1.58 for now. >> It "just works". >> >> Bob NW8L >> >> >> >> On Mon, May 12, 2008 at 7:08 PM, wayne burdick <[hidden email]> wrote: >>> Thanks to your input on the last firmware release (1.88), we've made a >>> number of important improvements. >>> >>> For the first time, we're posting new firmware as "beta." Upgrading is >>> optional: if you want to minimize your risk, you might want to wait until >>> we've blessed it as a normal production firmware release. (Or until all >>> your >>> friends have it and you're a little jealous.) >>> >>> We'd love to have as many thrill-seekers as possible take the plunge and >>> load the new firmware now. We think it's greatly improved, and it will >>> certainly clear up many of the issues noted over the past week. Even >>> though >>> we're headed to Dayton in a couple of days, we'll be monitoring closely >>> for >>> any additional issues. >>> >>> For release notes and instructions on how to load beta firmware, please >>> see: >>> >>> http://www.elecraft.com/K3/k3_software.htm >>> >>> The instructions (linked from within the release notes) explain how to >>> create a separate folder for the beta revision. This will allow you to >>> easily revert to an older revision if you find it necessary. Hopefully >>> not! >>> >>> For your convenience I've also provide the release notes below. >>> >>> 73, >>> Wayne >>> N6KR >>> >>> * * * >>> >>> MCU 1.94 / DSP 1.73, 5-12-08 >>> >>> * VOX: Increased sensitivity. Typical VOX GN settings now ~30-50. >>> >>> * VOICE MONITOR: Eliminated "scratchy" artifacts with compression set to >>> high levels. >>> >>> * FM DEVIATION ADJUSTABLE: Use CONFIG:FM DEV menu entry (default: 5.0 >>> kHz). >>> >>> * Flash memory driver improved to prevent occasional receive dropouts, >>> "ERR >>> PL1", and >>> "FPF LOAD PENDING" messages. >>> >>> * XMIT SWITCH IN MENU: Tapping XMIT while in menu correctly starts/ends >>> transmit. >>> >>> * PASSBAND SHIFT BELOW "0.00" CORRECTED: The SHIFT control no longer >>> allows >>> continued rotation below 0.00. (This was occurring only with sidetone >>> pitch < 500 Hz.) >>> >>> * SQUELCH/RF GAIN CONTROL CHANGES: By default, the RF/SQL concentric >>> pots >>> control main and subreceiver RF gain, and squelch is controlled by two >>> CONFIG menu >>> entries (SQ MAIN and SQ SUB). But setting SQ MAIN to "=SUB POT" >>> assigns >>> SUB RF/SQL pot to both main and sub squelch, and in this case, the >>> main >>> RF/SQL >>> pot controls both main and sub RF gain. Setting SQ MAIN back to a >>> numeric >>> value >>> restores the default assignments. Note: Squelch applies only to FM >>> mode >>> at present. >>> >>> --- >>> >>> 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 >>> >> _______________________________________________ >> 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 alsopb
When tuning by ear using a wide bandwidth filter, I have found that it
is easier if you go from the low tone side to high instead of high to low. I think the higher octave(s) can sometimes confuse you when you go from high to low. Yes, it is pretty easy to get within 10 or 20 hz by ear. For most any CW work I also would think you'd be ok if you could only manage to get within 100 hz. I bet lots of people could be able to do it with some practice. Still, the auto-spot is a neat feature and i'm looking forward to trying it on the K3. I'm looking forward to trying anything on the K3... 73, Drew AF2Z On Wed, 14 May 2008 04:47:30 -0700 (PDT), Brian/K3KO wrote: > >Guys, > >There is another way to solve the CW spot problem. > >It's called get on the air and work CW. You will quickly develop the skill >of zero beating by ear. >You will find that most CW ops don't use any zero beating gizmo. Much >faster and easier to do it by ear. > >Another thing. Narrow filter passbands help. If you're trying to zero beat >a CW signal with a 2.8KHz filter, it can be an exercise in futiltiy. And >if a human can't do it, don't expect some computerized gizmo to do it well >either. > >Practically speaking, if you've dialed in a 200- 400Hz CW bandwidth and you >peak the signal in the passband, your going to be at most 100Hz off. That >is really plenty good enough for most situations. > >How accurate can zero beating by ear be? The data points I have are from >RTTY. My display indicator reads out deviation from zero in 5 Hz >increments. I can usually get within 10-20 Hz by ear! I'm going to >assume the CW accuracy is similar. > >73 de Brian/K3KO > > _______________________________________________ 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 |