There is one overwhelming reason that we'll see touchscreens:
As radios become even more software driven, we'll see more and more new
features added (like ESSB).
The engineers and developers have to find a way to add those functions
to existing buttons (push this button 3 times, or go to a
I foresee Bluetooth or newer technology tablets or phone size units that
control our radio as an option to control our radios . So touchscreen
control seems like more than a fad.
On Monday, March 28, 2016, Gary wrote:
> Bill
> I agree, similarly with an Elad, not my choice
I have an additional two KIO3 units available after upgrading my remaining
K3s. I sold the first two I had for $50 shipped.
73, Ken, K6LA / VY2TT
__
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
> On Mar 28, 2016, at 9:56 PM, Don Wilhelm wrote:
>
> Tim,
>
> The default bandwidths are to work well with the internal decoder where you
> tune to the desired signal with the VFO,
> If you are using a computer application, widen the bandwidth and let the
> software
Tim,
The default bandwidths are to work well with the internal decoder where
you tune to the desired signal with the VFO,
If you are using a computer application, widen the bandwidth and let the
software application do the decoding.
73,
Don W3FPR
On 3/28/2016 8:57 PM, Tim Henrion wrote:
> On Mar 28, 2016, at 7:46 PM, Don Wilhelm wrote:
>
> Note that the default bandwidth for DATA A and AFSK A data submodes is narrow
> on the KX3.
Another one for the ‘Feature Request’ list. The “audio” data submode bandwidths
are way too narrow out of the box. Does
Bill
I agree, similarly with an Elad, not my choice BUT there is always the
possibility some feature or other may be a popular item Elecraft can look at
implementing in future FW and/or hardware.
Competition drives innovation and that is good for all parties.
Touch screen is not likely to be
Im just too lazy to reach all the way up to the rig to touch the screen with my
dirty fingers and smudge up the screen.
In a nutshell, why I dont like touchscreens on radios...
George NE2I
On Monday, March 28, 2016 6:39 PM, Bill wrote:
Actually, this does effect
On 3/28/2016 6:34 PM, tomb18 wrote:
> I often get this message and I never use n1mm+.
N1MM+ polling abuses the transceiver. Try setting the N1MM+ polling
speed to 50% less or 100% less. If you see this issue with other
software, make sure the other software is not overrunning the K3
I use the same amp with my K3S. Just connect from the "Key Out" jack to the
"STBY" jack on the amp. I get very good audio reports. Forget the "ALC".
Bill, AA4R
-Original Message-
From: John Shadle
Sent: Monday, March 28, 2016 4:51 PM
To: elecraft@mailman.qth.net
Subject:
Wow, I got three responses within 10 minutes and all were very helpful.
Thank you all! No need for further help on the list. I may be back in
touch with a couple of you who sent me information. This is an amazing
source of information.
73's
Terry, N7TB
Terry,
What data submodes are you using?
Fldigi is a soundcard oriented application and you should be using DATA
A for PSK and AFSK for RTTY. If you are trying to use data submodes of
PSKD or FSKD, you will receive just fine, but transmit will not happen
with Fldigi.
Typically, PSK will
Actually, this does effect Elecraft users. There may be some good ideas
that we will want to see incorporated on future Elecraft products. For
example, the use of a touch screen for a lot of its controls. I do not
care for touch screen myself, but it is the sign of the times on many
things and
I am new to fldigi. I am using the SignaLink USB to interface between my
KX3 and computer. I have my KX3 connected to fldigi using Hamlib rig
control. That seems to work fine tracking the VFO and placing software into
the right mode when I change it on the KX3. First, could someone tell me
Just a quick point of clarification (since I did my graduate work in a
similar field). I would say it's more like a "pidgin" language in contesting
exchanges, yes, but in a regular QSO, CW is still basically just an encoding
system for the underlying language the QSO is in.
The only difference
I often get this message and I never use n1mm+.In my case it seems to have
something to do with Vox, happening if I put my headphones down on the
counterTom
Sent from my Samsung Galaxy smartphone. Original message From:
Don Wilhelm Date: 2016-03-28
Dennis,
All the reports of this error message seem to be related to the use of
N1MM+, so if you have not done so, I suggest you ask the folks at N1MM
support about it.
Yes, that message should only occur if the key line or PTT is shorted
during a power on sequence.
So my question is "What
All - I'm about to write a president's letter for our local club
publication on learning CW, and this entire thread is a good
source of ideas. Thank you.
Peter -
I learned 5 WPM in 1960 for my novice license, but never used
it. I learned 5 WPM again in 2001 for my extra, but didn't start
Haven't tried it yet on the P3 but for the same feature on the PX3 if you make
the RCF value a bit less than the span you can use Half span or Full span.
So a macro
#SPN000100;#RCF+004500; will set the span to 10 kHz and position VFO A just
above the left side of the display.
Cheers,
Fred
I wrote earlier today about what triggers the ERR KEY error on the
screen of the K3. I have had several suggestions about what it is, so
I'll reply to them generically.
The contest this past weekend was an SSB contest. The ERR KEY message
(and not ERR PTT) appeared 40 or 50 times. Yes,
John,
I don't know what other folks do, and I don't have an amplifier, BUT ---
Using amplifier ALC is a good way to create splatter on the bands, so it
should not be used if you are to present a clean signal. ALC can be
used as a crude means of power control - the amplifier is overdriven, so
Most of my CW work is for eme where the signal is marginal "at
best". Without having a large SNR on the signal I have not found any
CW decoder to work well (skimmer seems to be best). On CW-eme the
output is gibberish.
Inventing a digital code designed for weak-signal is way better
I'm considering adding a THP HL-1.2KFX solid state amp to the K3S station I
have, and was wondering how others have done this. There seems to be
conflicting info on the "right way" to do things.
1. The THP manual states that ALC should be used to control the amp, but
2. Elecraft support (and
Seeing Rick’ post has me thinking… I rarely use my KX3 for decode CW but… maybe
a future feature is to have a one button “speed is” on the KX3?
I know it is ‘there’ but one key touch would be a nice feature to see how fast
the other guy is moving at.
Frank KG9H
Yeah, but it is a real kick when the program sends your call to you which can
happen if you are practicing with a dx call!
From: Elecraft on behalf of Hisashi T
Fujinaka
Sent: Monday, March 28, 2016
Jim, Paul
Paul, Jim is correct. Practice, practice, practice, then sooner than not you
will be copying in your head.
Jim's ASA training and experience works for him. For me it was USAF CW
Intercept and over 7 years experience. I don't use skimmers or cw decoders.
My K3 has one, and to be honest, I
Since this is Not an Elecraft product can this thread please be taken somewhere
else?
From: John Kramer
To: Bill
Cc: elecraft@mailman.qth.net
Sent: Monday, March 28, 2016 12:02 PM
Subject: Re: [Elecraft] IC-7300 video - things to come
Morserunner works under Wine on my Mac, or at least it used to. I quit
using it because it would suck me completely in and then several hours
would disappear. And none of those computer QSOs would QSL! :)
On Mon, 28 Mar 2016, lstavenhagen wrote:
Well, to take the other side for a moment, I
Well, to take the other side for a moment, I promise I'm not a curmudgeon hi
hi. I'm a software engineer in my day job and am accustomed to embracing new
technologies when required; I have a lot of admiration for things like
MorseRunner and CW Skimmer & reversebeacon.net and so forth.
All that
I paid for my IC-7300 a few weeks back, and it has arrived with my dealer in
the UK.
I am flying to the UK in two weeks time to fetch it. Super excited……but I am
keeping
my KX3 :)
73
John
On 28 Mar 2016, at 5:02 PM, Bill wrote:
I am amazed at what the touch screen
Same here, LS. As I've gotten older my muscle
coordination has deteriorated a tad, so ...; most
seemed to result from an open heart surgery I had
three years ago which also killed my kidneys
(which came back after five weeks of dialysis --
whew!), making poor CW sending seem a minor price
to
On Mon,3/28/2016 5:43 AM, Jim Sheldon wrote:
None of the decoders out there, including the better ones (internal to
the K3/K3S and the KX3) decode CW even close to accurately unless the
conditions are ideal and the sending operator is close to perfect in
his/her sending so the ultimate answer
+1 from me. I recently finished CWA Level 3 and with the 8 week class and lots
and lots of practice moved from a comfort level of 20 wpm to comfortable head
copy at 30 wpm. Just be aware that because of demand for the classes and a
shortage of instructors you may have to wait six months or
Don't feel too bad, I kind of have the inverse problem: I can copy at a much
greater rate than I can send lol. Also, I never learned to translate CW into
keyboard keystrokes, mainly because I just refuse to get a computer anywhere
near my rigs lol. I prefer to just pound brass, so I think I'm
I am amazed at what the touch screen can do and all the choices the 7300
offers. That said, I do not see me using a touch screen - too old school
I guess. But, the video is interesting:
https://groups.yahoo.com/neo/groups/ic-7300/conversations/messages/2272
I am only posting this for
Peter,
The CW Operators Club has a CW Academy has a course tailor made for you. Sign
up for a level 2 or 3 class to increase your speed and your contesting skills.
Check out http://www.cwops.org/cwacademy.html for details.
73,
Brian, K0DTJ
>
> Any suggestions (besides suck it up and learn to
+1 to what Fred Cady said. I'm a fairly new CW op and just graduated from CW
Academy level 3. In that class, they teach you how to head copy high speed
contest CW, primarily using Morse Runner and RufzXP, but also by live practice
in the weekly CWT tests. If you want some free, structured,
Dennis,
Some questions that might perhaps throw some light on what is happening:
What method are you using for CW keying? Are you using PTT control in CW?
How is N1MM+ configured to do CW and PTT keying?
One particular area to look at:
What is CONFIG:PTT-KEY set to on the K3? In the N1MM+
Hi Peter,
Good for you! N1NN+ is great and CW contesting is even better.
There are a couple of programs that will help you improve your copy for call
signs and numbers. These are Morse Runner and Rufz.
http://www.dxatlas.com/morserunner/
http://www.rufzxp.net/
Morse runner even simulates N1MM
I think W1UE is already a very proficient CW operator! I had the ERR Key
message while operating as WP2AA this month. If I recall it was from
accidentally plugging the headphones into the PTT connection of the Heil
mic adapter. It was a little bit of a scare just minutes before the ARRL
DX Phone
Hi Dennis,
Good for you! N1NN+ is great and CW contesting is even better.
There are a couple of programs that will help you improve your copy for call
signs and numbers. These are Morse Runner and Rufz.
http://www.dxatlas.com/morserunner/
http://www.rufzxp.net/
Morse runner even simulates N1MM
Peter,
None of the decoders out there, including the better ones (internal to
the K3/K3S and the KX3) decode CW even close to accurately unless the
conditions are ideal and the sending operator is close to perfect in
his/her sending so the ultimate answer is "suck it up" and learn to
decode
I do have an op that is having problems with this in conjunction with
his Remote Rig setup, but that wasn't the case for me this past
weekend. No remote rig was involved this past weekend.
Dennis W1UE
On 3/28/2016 8:23 AM, Gerry Hull wrote:
Were you remote, Dennis?
I notice on the VY1AAA
Were you remote, Dennis?
I notice on the VY1AAA remote, if the sequencing is not right, I would get
ERR_KEY on the rig as well.
It seemed to happen just as I was logging a QSO (no ESM, just VOX).
This was Windows 10 locally, with the RRC. I wonder if this is the dreaded
serial overlap issues
I became enamoured with N1MM+ after this weekend's contest and wanted to
see if I can use it for other stuff like CW. I got the keying working with
my K3S so that's no problem. The issue is I can't decode 30 WPM CW in my
head. I need help.
I've been using the K3 Util terminal for CW contests and
I have both K3 and KX3 and I sometimes use them outside in a field
operation. Here in Russia we have one funny QRP contest called "Frost-red
nose" where extra points are given for low temperature environment during
field operation. The contest happens in January when in some places
This past weekend I experienced numerous ERR KEY messages. According to
the manual, this ERR code is returned when one "attempts to key the
transmitter or activate PTT during power on". When this would happen,
there was no power turn on, nor shorted keying lines- it was in
operation with N1MM+
Hi Paul / N6HZ
I’ve downloaded the beta version 1.42.
And I tried to install the beta version, but the PX3 will become off.
I tried to install the current version, the PX3 does not turn off.
Best regard,
Nakamura / JE0LFI
--
View this message in context:
48 matches
Mail list logo