Frank Lammel wrote:
I loaded rev 1.94 yesterday evening.Does anybody had similar
problems?
Hi Frank,
I'm very surprised that you had these problems with 1.94. The VOX issue
was addressed specifically, and many have said it works perfectly now.
So I suspect that either the MCU 1.94 or
I'll restore it to its former glory, don't worry. But not until I get
back from Dayton.
73,
Wayne
N6KR
Harrison F. Hooker wrote:
Bob,
Thanks for your work on this issue. The early FW versions really,
really
worked! I found with the early versions I could use it, to great
advantage,
for
I'm glad to hear that there's only one little birdie of concern to the
list. This is a major victory :) The K3 uses down-conversion to a low
first I.F. (so we can offer narrowband crystal filters). It's nearly
impossible to eliminate all birdies using this kind of conversion
scheme.
Weak
Ron Spencer wrote:
Anyone else notice (and I know this will be difficult with hardly any
openings) that the sensitivity of the K3 on 6 is down? Compared to the
746 I
have it seems down quite a bit (even with the K3 preamp on).
Ron,
The K3 is optimized for high dynamic range. For example,
800 Hz is the highest pitch you can select for your sidetone. But this
has no effect on auto-spot. It will search the same amount above/below
any selected pitch.
On May 14, 2008, at 9:27 AM, G4ILO wrote:
K4IA wrote:
On another note, I have to question why a pitch of 800hz is the
K3 beta-test firmware revision 1.96 is now available. As with other
beta releases, we encourage you to load it, but if you'd rather see how
things go for everyone else, *then* load it, we'll understand. Please
send any problem reports to [EMAIL PROTECTED]
For release notes and instructions on
I've just updated the Programmer's Reference to rev B and sent it to
Bob and Don. It'll be available on our web site by tomorrow, most
likely. Still quite a few updates needed, but it's getting closer to
reality.
73,
Wayne
N6KR
---
http://www.elecraft.com
Stewart Baker wrote:
With the difference in K3 sensitivity between the HF and 6m bands
does the 50uV RF input = S9 still hold good ?
Yes. The difference is so small that it's a small fraction of an S-unit.
73,
Wayne
N6KR
---
http://www.elecraft.com
On May 19, 2008, at 11:08 AM, O. Johns wrote:
Can Lyle or someone tell me if there are plans to have the sidetone
run from 300 to 1000 by 10 Hz increments in some future firmware
version? Is there some basic reason it can't be done? I note that
page 9 of the K3 Owners Manual C1 says that
We've been working on the K3's external ALC implementation. If you have
an amplifier that supplies a negative-going ALC signal, and you don't
mind loading new firmware and making a simple hardware mod, please
email me directly.
73,
Wayne
N6KR
___
We've identified the problem and are working on a firmware update that
will fix it. This will be part of a beta-test release that also
includes an initial implementation of external ALC. We hope to have it
out in the next couple of days.
73,
Wayne
N6KR
---
http://www.elecraft.com
As I mentioned in my last email, we're working on a new beta firmware
release that will fix the 6-m power shutdown problem.
Meanwhile, there's a simple workaround that, used with caution, will
let you operate at high power on 6 m with the existing firmware:
1. Locate the PA TEMP menu entry
K3 beta-test firmware revision 1.99 is now available. Highlights
include:
* Per-band power output setting (great for use with amps and
transverters)
* ANTIVOX gain increased
* Support for external amplifier ALC
* MIC up/down button functions
* Remote control (CAT) enhancements
*
Several issues with revision 1.99 have been reported that didn't come
up in our field test group. We're working on these and expect to have
an updated beta release soon.
If you haven't yet loaded 1.99 you may want to hold off until then.
Thanks for the quick feedback--
Wayne
N6KR
---
K3 beta-test firmware revision 2.00 is now available. It includes one
new feature (transverter band data) and two improvements based on
feedback users sent us about revision 1.99. Full details appear below.
The use of beta-test firmware is encouraged, but optional. Please send
any problem
Ed K1EP wrote:
Are the version numbers for the MCU, DSP, etc. revisions just
sequential (i.e. 2.00 followed 1.99)
Yes.
or does the change from 1 to 2 signify anything?
Not really. It's a good estimate of the square root of my cumulative
hair loss over two years of intense firmware
I've located the problem and will update the firmware shortly.
tnx
Wayne
N6KR
---
http://www.elecraft.com
___
Elecraft mailing list
Post to: Elecraft@mailman.qth.net
You must be a subscriber to post to the list.
Subscriber Info (Addr. Change, sub,
K3 beta-test firmware revision 2.02 is now available. It includes one
new feature (channel hopping, especially useful on 60 meters) and a
correction to CW/VOX behavior. Full details appear below.
For instructions on how to obtain and load beta firmware, please see:
Thanks for catching this, Mike. I thought we were switching back to
RF/SWR metering in CW modes automatically if CONFIG:EXT ALC was set to
OFF.
Wayne
N6KR
| I upgraded my firmware to v2.02 Friday (13th!) night and now notice
the
| following:
|
| Previously the CMP and ALC display
Carl,
The character '@', when embedded in a KYtext CW keying packet, will
do one of two things:
1. terminate the transmission, or
2. send .--.-. which is the Morse pattern for '@' (you can also think of
it as the prosign AC)
To select which behavior you want, go into CONFIG:CW WGHT and
Hi Joe,
This has been corrected in firmware rev. 2.03 (field test release from
two weeks ago). Also corrected was loss of filter bandwidth settings on
band change (FA and FB commands), DATA A and PSK-D mode set/get
inversion (MD command), and power control QRO/QRP reporting in
extended mode
I can not find the text definitions in the manual (Rev C-1, Nov 18,
2007), or the errata sheet (C1-5, May 6, 2008) for 'CONFIG' settings
for the following:
FM DEV
FM MODE
MIC BTN
PWR SET
RFI DET
EXT ALC (TECH MD)
Hi Bob,
These will be covered in the next errata sheet (C1-7), which will be
K3 beta-test firmware revision 2.10 is now available. Full details
appear below and in the release notes.
The use of beta-test firmware is encouraged, but optional. Please send
any problem reports to [EMAIL PROTECTED]
For instructions on how to obtain and load beta firmware, please see:
The K3 can be used at QRO power levels (13-120 W) when powered from a
car battery or a large gel cell. Here are a few things to keep in mind:
- A battery that's significantly discharged will have higher internal
resistance, which will cause the voltage to drop when high current is
drawn.
On Jun 26, 2008, at 9:29 AM, Bill NY9H wrote:
So I made a field case for th K3 ... and one for a pair of 7ah
batteries
all fits into pelican 1520
Aside from a minor concern of not adequately cooling the right side
panel with the
pair of regulators mounted...( wayne??),
The
Dave,
I wanted to run a possible solution past you.
I could prevent the rig from being keyed (by any method) during the
first couple of seconds that it's powered up. Instead, it could detect
this case, and display a repeating message (something like: KEYLINE IS
ACTIVE) until you either
:
Wayne,
Given the situation, reasons, and consequences, I believe something
like what you suggested would be the best solution. If you can extend
the time beyond 'the first couple of seconds' (enough time to change
the menu or power down), that would be helpful IMHO.
73,
Don W3FPR
wayne burdick
This is another way of describing what I'm proposing, John. If /KEY is
found asserted anytime during the 2-second power-on sequence, the K3
might show ERR KEY and prevent TX until the line as been released. If
re-asserted anytime after that, the message would go away by itself,
and TX would
Don,
The K3 could inhibit all methods of transmit that appear to be active
during the first 2 seconds of power-on, even the KY and TX commands
from a PC.
Don't forget that I control both the horizontal and the vertical :)
73,
Wayne
N6KR
On Jun 28, 2008, at 7:07 AM, Don Wilhelm wrote:
Hi all,
While working on the next revision of the owner's manual, I've been
thinking that it gives a decidedly top-down (deductive) look at the
K3's controls and features. But for many people, a bottom-up
(inductive) approach leads to quicker results.
Imagine if, as a new user of the K3,
Just in case there's confusion on this point:
- Operating tips are short-form, covering the use of a single feature.
- Operating scripts would be much longer, step-by-step tutorial
guides covering a class of K3 operation or setup in depth.
There's room for both. With Operating Scripts, our
K3 beta-test firmware revision 2.13 is now available. Full details
appear below and in the release notes.
The use of beta-test firmware is encouraged, but optional. Please send
any problem reports to [EMAIL PROTECTED]
For instructions on how to obtain and load beta firmware, please see:
We created a text-only guide to the K3 front panel some time ago. It
was posted on the web by another group. We've now added it to our own
site:
http://www.elecraft.com/K3/K3%20Control%20Locations.txt
In related news: We're working on improvements to our K3voice PC
application, adding full
The next K3 beta firmware release will include dramatically better
bass response in receive mode (50-200 Hz). The result is fuller,
richer audio, which many of you have asked for.
Lyle (KK7P) and I are completing the full beta test suite, and hope to
do the release early next week. But we
I plan to change VFO coarse tuning in general so that it quantizes.
Tapping CLR to accomplish this strikes me as further control
overloading, which I want to avoid. Besides that, CLR clears the RIT
offset even if RIT is off.
Wayne
Sent from my iPhone
On Sep 21, 2009, at 4:12 AM, Brett
, Mike wrote:
Quantizes? What's that mean? ;-o
Mike NF4L
Wayne Burdick wrote:
I plan to change VFO coarse tuning in general so that it quantizes.
__
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help
an idea - I may want
a particular offset from 00, so let me do it myself if I desire,
but please do not force it on me.
73,
Don W3FPR
Wayne Burdick wrote:
Sorry -- geekSpeak :)
Suppose the VFO were tuned to, say, 7040.23, in CW mode. Further
assume your CONFIG:VFO CRS menu
Hi Leigh,
I've now implemented *optional* coarse tuning quantization (or
rounding). It'll be in the upcoming beta release. You can turn it on/
off in the menu.
1.5 kHz as a coarse tuning step size might be problematic since it
wouldn't be aligned at 10-kHz points as you tune across the
David G3UNA, wrote:
A quick look at the circuit diagram shows that buttons are taken
from a
potential divider to CD74HC4051M inputs. These switches (unless I've
misread the diagram) will therefore take the input current of the
multiplexer which is typically 1uA. I don't know the spec for
Hi all,
We're getting very close to a long-awaited K3 beta firmware release.
Since the changes are extensive, we'd like to send the code to a new
group of pre-testers in addition to our usual field-test group.
Please read the release notes below. If you're interested, and can
start testing
The K3 has a CONFIG menu entry called AFSK TX. If you set it to FIL
ON, a 400-Hz transmit-mode audio filter is inserted, centered around
the mark/space tones. This is only available when the rig is set for
AFSK A mode. It should be effective against low-frequency hum coming
in through the
I'll look into this on the K3 end.
73,
Wayne
N6KR
On Sep 29, 2009, at 9:30 AM, Julian, G4ILO wrote:
Tom, DL2RUM wrote:
I could send only one command for the text to send, but then there
is no
way to interrupt the transmission. It seems the ˆD don't clear the
buffer
and stops
Hi Dan,
I recommend a pair of Best Buy Insignia, 4-inch, 3-way surround
speakers (same as the KLH Model 970A or other similar models). These
are unpowered bookcase speakers, but provide plenty of volume when
used with the K3. They're very inexpensive and sound great. Size:
about 4W x 8H x
We've had many requests to provide an 0.5-kHz VFO tuning step size in
SSB modes. I'd like to substitute this for the current 2.5 kHz
selection. The new set of steps sizes for SSB would then be:
0.1, 0.5, 1.0, 5.0
Most operators probably don't find 2.5 kHz steps to be particularly
Very quick response from some K3 owners suggests that 2.5 kHz steps in
SSB mode *are* useful, after all -- for quickly scanning the band
(including when using the RIT/XIT control to move the VFO in coarse
steps).
It may be that 5.0 kHz steps in could be sacrificed, instead, in order
to
Deane Walkington wrote:
The real question is what filter configuration I should consider.
The FM
filter is probably a given. I am not really interested in AM
transmissions
but do I need the AM filter to listen to the AM broadcast bands?
No; you can listen to AM with the FM filter, and
I can add up to two more FM coarse tuning rates easily.
Wayne
N6KR
On Sep 29, 2009, at 2:48 PM, Julian, G4ILO wrote:
While we're on the subject of step sizes I suppose it is worth
thinking about
the requirements of those who will be using the K3 on FM. Currently it
appears there are
6 wide, and like the K3, 10 deep and 4 high.
73,
Wayne
N6KR
On Sep 29, 2009, at 5:31 PM, Larry - K2GN wrote:
I've looked for over an hour and I can't find the dimensions of a P3.
Got to plan desk top configuration to fit it in.
__
Chuck Guenther wrote:
Is there any problem using the Rx input jack for the RF gain cal
No. Works equally well.
Suppose that I do an RF gain cal, then change the filter
gain (in the Crystal filter configuration part of the K3 utility) of
the
roofing filter I used during the gain cal?
Hi Chris,
You can set CONFIG:SPLT SV to YES, which will preserve the states of
SPLIT, RIT, and XIT on a per-band basis.
You may also have a logging program issue as noted by Joe.
73,
Wayne
N6KR
On Sep 30, 2009, at 9:31 AM, Chris Page wrote:
Help please!
Does anyone know of a way to
See:
http://www.elecraft.com/K2_perf.htm#Main%20RX%20Table
We add these to our table as results come in from ARRL testing.
73,
Wayne
N6KR
__
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help:
Added to my list.
73,
Wayne
N6KR
On Sep 30, 2009, at 10:54 AM, Geoffrey Downs wrote:
12.5kHz sounds like a good idea in relation to the channelised part
of 2m - certainly for the UK and, I presume, the rest of EU too.
73
Geoff
G3UCK
Soon.
The latest version on our web site is D4. If you have a PC near the
rig, downloading the .pdf and reading it with Acrobat in the short
term will save a lot of paper :)
73,
Wayne
N6KR
On Oct 1, 2009, at 11:17 AM, Ken Kopp wrote:
My Owner's manual is a couple of versions old (Ver.
95% of the MCU code is in C. I only use assembler where necessary to
speed up algorithms.
The DSP code, on the other hand, is all written in assembler. If you
have other questions about this, please send them to Lyle, KK7P (lyle
at elecraft dot com).
73,
Wayne
N6KR
On Oct 1, 2009, at
I think we've beaten this one to death.
My goal is to completely eliminate the need for the K2x and K3x meta
commands. No more modality, no more issues. Thanks in advance for your
patience.
Wayne
N6KR
__
Elecraft mailing list
Home:
That's on the list.
73,
Wayne
N6KR
On Oct 2, 2009, at 9:27 AM, Stewart wrote:
Wayne,
Will your command changes incorporate the ability to read and
write to the K3 memories ?
__
Elecraft mailing list
Home:
No, but this is high on my list.
(I've given up trying to do everything at once.)
tnx
Wayne
On Oct 1, 2009, at 11:23 PM, David Pratt wrote:
In a recent message, Wayne Burdick n...@elecraft.com wrote ...
The latest field-test revision is 3.40, which also includes several
new features.
Do
Working on it
Wayne
N6KR
On Oct 3, 2009, at 2:03 PM, Brian Alsop wrote:
I've played with the last command. It is exactly what I have needed
since obtaining the K3As an interim measure, how about making
such commands sticky?
73 de Brian/K3KO
If CONFIG:SPLT SV is set to YES, then the state of SPLIT, RIT, and XIT
will all be saved on band change and in memories as well.
73,
Wayne
N6KR
On Oct 3, 2009, at 7:36 PM, Jim Rinehart wrote:
I can't save a split function, same band, to a K3 memory. It saves
both VFO's correctly but not the
Jim,
If it's an issue with the S-meter, it may well be corrected by the
corrected RF GAIN calibration procedure due out in the next beta
release. I can send it to you to try.
Generally if you connect an antenna to three radios and one of them
sounds louder, it means that radio has more
Edgar Iniesta wrote:
Hola ando buscando un transceptor para la banda de 160 metros,
¿quien me
puede ayudar?, les estaré muy agradecido ya que soy nuevo en la
radioafición. Por favor contactar conmigo por esta vía...
Hola Edgardo,
Hay muchos transmisores-receptores que trabajarán en 160
K3 beta-test firmware revision 3.41 (with DSP rev. 2.37) is now
available. See release notes below.
More refinements are in the works. But alas, it was time to shoot the
engineers and get some interim feedback on the many new features in
this revision.
--
IMPORTANT NOTE
Hi Toby,
We can modify the present behavior if required. Our EU field testers
reported that it worked on all repeaters they tried it with.
73,
Wayne
N6KR
On Oct 6, 2009, at 11:51 AM, dj7...@muenchen-mail.de wrote:
Hi Wayne and the list,
without having actually testing this:
* EU
This is a very likely P3 add-on. All the hooks will be in place.
73,
Wayne
N6KR
rfenab...@gmail.com wrote:
(Snip)
One of the things that makes getting the modulation up to snuff is
to view the output on a modulation monitor. I use an old Kenwood
SM220 in the trap position which allows
We had more requests for this than any other FM/repeater-related
change, so apparently there are lots of legacy repeaters still in use
out there.
This revision of firmware includes two other requested changes for FM/
repeater use: adjustable PL tone deviation, and repeater/PL TONE
update
On my list.
tnx
Wayne
N6KR
Jan Erik Holm wrote:
PLEASE ...make it so that [1750 Hz burst at start] can be switched
off.
In Sweden this is not needed for repeater work, after
repeater been activated with 1750Hz it is carrier
operated.
I'll fix this.
tnx
Wayne
On Oct 6, 2009, at 5:09 PM, Julian VK4CMV wrote:
Hi - I've set up DATA mode to use VOX - and this works just fine.
The reason I've done this is that I have a number of different sound
card
based programs that use different methods for PTT - so VOX seemed to
be
You're right, Ken: The manual mistakenly claimed that the sub's S-
meter parameters were separate, and the firmware perpetuated the myth
by allowing you to tap SUB when looking at SMTR OF and SC.
The next manual revision will correct this.
Sub and main S-meter calibration both benefit from
Mike,
Now that you've done rf gain cal, you'll still need to adjust SMTR OF
SC so that you get S9 with 50 uV and S2-3 with 1 uV. RF gain cal
linearizes the dsp's internal representation, while SMTR OF SC set
the actual meter indication.
Try the factory defaults first.
73,
Wayne
Lyle and I will discuss your findings, retest the passband and get
back to you. However, I'm virtually certain that 3.41 is vastly
different from 3.30, as others have noted, so this is a mystery.
73,
Wayne
N6KR
On Oct 7, 2009, at 4:14 PM, mark roz wrote:
To me there is no difference
We're going to add a final instruction to K3 Utility explaining that
SMTR OF and SC must be adjusted after running RF GAIN calibration. I
suggest doing this with SMTR MD = ABS, preamp ON. Under these
conditions you should be able to set SMTR OF and SC such that 50 uV
produces an S9
Typo. I meant to say SMTR NOR in the paragraph below.
Wayne
Wayne Burdick wrote:
We're going to add a final instruction to K3 Utility explaining that
SMTR OF and SC must be adjusted after running RF GAIN calibration. I
suggest doing this with SMTR MD = ABS, preamp ON. Under these
conditions
I'm not observing any keying problems, either. How are you keying the
rig? How is HRD set up? I'm not an expert with HRD; is there a way to
reset it to defaults to see if it could be a configuration issue?
Tnx
Wayne,
N6KR
http://www.elecraft.com
On Oct 8, 2009, at 7:00 PM, Dick Roth,
Hi Nick,
I still can't duplicate this. Please describe exactly how both the K3
and HRD are set up.
In particular: Do you have a sub receiver, or at least have the aux
DSP module installed? K3 MCU rev 3.41 allows applications to query the
revision number of the aux DSP even if the KRX3
Dunc,
Please send me as much derail as possible about this if/when it happens.
Tnx
Wayne
N6KR
http://www.elecraft.com
On Oct 9, 2009, at 1:56 PM, Dunc Carter - W5DC d...@vibrotek.com wrote:
3.41 fixed the occasional big roar but an occasional small tone
remains when
NR is on and
I think I can prevent this with a change to K3 firmware. If so, I'll
get another beta version out as quickly as possible.
Wayne
N6KR
__
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help:
I just sent a new version of K3 firmware to everyone who reported a
problem with HRD and K3 revision 3.41.
Turns out that HRD (Ham Radio Deluxe, a PC software app) polls for sub
receiver status periodically, even if one isn't installed, which can
result in long timeout delays. In the new
I'll start looking into this again on Monday.
73,
Wayne
N6KR
http://www.elecraft.com
On Oct 10, 2009, at 6:21 PM, Jim Chick jimchic...@yahoo.co.uk wrote:
Hi Steve
In my previous e-mail I suggested it was the NB! not so it was in
fact NR
and the symtoms are exactly as you describe,
Most K3 users will not notice, nor benefit from, a lower AF cutoff in
DSP hardware. Our most recent firmware already lowers the response
somewhat. Those lacking spectacular hearing and an application for
ultralow bass can forego the upgrade.
I have an original DSP in my K3, and I find its
K3 beta-test firmware revision 3.42 (with DSP rev. 2.37) is now
available. It corrects a problem with CW keying (and possibly transmit
in general) when using HRD (Ham Radio Deluxe) software. See release
notes below.
Please send any problem reports to k3supp...@elecraft.com. Beta
firmware
Rys,
Sounds like you may have an LPA problem, but there may be a simple
work-around. If necessary I can send you modified firmware based on
test results. Also: Have you tried running transmit gain calibration?
Please contact me directly -- I'll check my mail frequently.
Wayne
N6KR
SIG RMV does not move real signals. It shifts the internal signal
sources such that the net is zero. All you will hear is a slight
change in filter center pitch.
That said, it should, as you noted be used after checking cable
orientation.
73,
Wayne
N6KR
http://www.elecraft.com
On
I already replied to him directly.
73,
Wayne
N6KR
On Oct 12, 2009, at 11:04 AM, Dave AA6YQ wrote:
Perhaps someone here can help. If so, please respond to Rys at
r...@ippt.gov.pl
73,
Dave, AA6YQ
-Original Message-
From: topband-boun...@contesting.com
Working on it
Wayne
N6KR
On Oct 12, 2009, at 12:38 PM, w9rit wrote:
Hello,
I also get the tone when using the NR.
Same configuration described using the PF2 button to switch between
speaker
and headphones.
The tone does go away by hitting any other button (NB, PRE, XFIL,
etc.)
On my task list.
73,
Wayne
N6KR
On Oct 12, 2009, at 1:28 PM, Arie Kleingeld PA3A wrote:
All,
About the NR.
YES, the new algorithms really work! I can even dig out the weak CW
sigs
better.
Now my question.
I use the first NR settings (1-1 to 4-4) in CW and the mixed ones
for SSB.
Hi Bob,
I have a spare XG1 I can send you if you want to do gain calibration,
but don't have any other means of getting an S9 and S1 signal source.
This is almost certainly a simple calibration issue. You should start
by running K3 Utility's RF GAIN Cal routine, selecting factory
defaults,
I believe the add-on LPF module for the DSP board will be available
soon. We'll post details at that time. It's easy to install.
The rolloff of this module is 4.5 kHz, and it completely eliminates
all high-frequency artifacts resulting from the CODEC's 12-kHz sample
rate.
I can't hear the
Hi Tony,
You'll get somewhat better isolation using the BNC jack for the sub
receiver's aux antenna, rather than the non-transmit KAT3 antenna.
Either way, the trip point of the KRX3's carrier-operated relay is
typically 1 to 2 watts. To play it safe let's say you want to keep it
down to
Michael van Hauten wrote:
Dear elecraft -team,
during the last 2 years all new modules and software updates had
been designed for the K3. Is the K2 out of the focus or is there a
chance for all the K2 users to get new modules and upgrades in the
future ?
The K2 is a very mature
This is high on my list.
73,
Wayne
N6KR
On Oct 13, 2009, at 3:38 PM, Randy Farmer wrote:
Somehow all the text disappeared from my previous post. If VFO A is
LOCKed, turning the RIT knob will still QSY VFO A when the CONFIG:
VFO OFS is set to ON
It's official: we're running out of DSP cycles not just during NR on/
off but also under worst-case load.
I get a continuous DSP red LED and distorted audio (with a buzz) under
the following conditions:
CW
CWT on
NR on, set to F1-x
DSP NB on, any setting
FIR IF filter (WIDTH
On Oct 14, 2009, at 6:16 PM, Wayne Burdick wrote:
It's official: we're running out of DSP cycles not just during NR on/
off but also under worst-case load
This was not intended for the reflector. Sorry for the bandwidth!
Lyle and I will come up with a fix and get it into the next beta
Hi Barry,
Set CONFIG:SPLT SV to YES. This preserves the on/off states of SPLT,
RIT, and XIT on band change.
Wayne
N6KR
On Oct 15, 2009, at 9:08 AM, Barry Pfeil wrote:
In the year I have had my K3 I have used it mainly for contesting
and hardly ever operated in split mode. Lately I have
I wrote:
I get a continuous DSP red LED and distorted audio under
the following conditions
A few of you have asked me what the DSP red LED is for. This is an
LED on the top edge of the DSP board that lights up to remind your
humble firmware crew when we've made a mistake that causes
There's no issue with program memory in the K2; we could upgrade to a
larger part. But we spent years on K2 firmware and optimized it for
the rig's intended usage, and it's a business decision to focus on
other products for the time being.
73,
Wayne
N6KR
On Oct 15, 2009, at 2:41 PM, David
In split mode, VFO B is always the transmit frequency, and it is
always displayed, unless you have a special display mode in effect.
73,
Wayne
N6KR
On Oct 15, 2009, at 4:59 PM, The Smiths wrote:
Better yet, wouldn't it be much nicer if the display could change to
the Xmit freq. when
Maybe we could obnoxiously flash the Delta F LED when you're in
SPLIT. Menu option, of course :)
Wayne
On Oct 15, 2009, at 5:14 PM, The Smiths wrote:
There in lies the problem, in CW I keep my CWT and text reader on,
therefore blocking the freq. of VFO B. I was learned well into
Jim wrote:
I know you can listen to two conversations on different VFO's
(Frequencies
at the same time when you have the Sub Receiver Installed; However
with no
Sub Receiver I believe this is this correct? If you don't have
the sub
receiver listening using a set of headphones like a
Just turn off CONFIG:VFO OFS so the offset control can't change the
VFO frequency.
73,
Wayne
http://www.elecraft.com
On Oct 16, 2009, at 12:13 AM, DM4iM hamra...@vr-web.de wrote:
Elecrafters,
when you are on a Frequency working someone or calling , it may happen
that you accidently
It may be possible to do full duplex with the sub receiver on a
different band and antenna from main, since it's very well-shielded.
I'll give this a try. Some firmware changes will be required.
73,
Wayne
http://www.elecraft.com
On Oct 16, 2009, at 7:21 AM, Bill W4ZV
201 - 300 of 4645 matches
Mail list logo
