Be thankful that you're not seeing your sodium lamps replaced with LED
solutions, the number of streetlights in the average suburb are quite
simply staggering.
Don't think for a second that these LED lamps were designed for low noise
or that compliance with EMC standards will prevent unwanted inte
I have been running both my K3 and KX3 on 630m and 2200m for the last 18 months
using commercially available Transverters. The transverters require 5 watts of
drive and it is easy to adjust to this output on both of the Elecraft rigs.
Just search for 630m band transverter, or 2200m band transver
Yellow sodium vapor street lights can be a significant source of nighttime RFI
on the lower bands. They are ignited at dusk by an RF arc that typically lasts
between 5 and 10 seconds, the lamp lights, and the arc is extinguished. This
arc noise sounds like a constant, dense static and is easily
Don & Wes,
I'm stymied by what caused the problem.
Sometimes using N1MM with MMTTY there is a
bit of software change and PTT-KEY change
but never just running MMTTY alone with
the K3s. When I went to N1MM it was with
AFSK A and it was already in the data mode
as my last 20M Q was with WSJTX.
Make sure the pitch in the K3 matches MMTTY.
On 9/17/2017 12:37 PM, Gary Smith wrote:
Hard to enter a short subject that is
complete...
__
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mail
Gary,
One thing to check is when you change from WSJTX to MMTTY, does the K3
data mode change to AFSK A in LSB mode? If not, the software is to
blame. The sequence of commands (or lack of commands) sent to the K3
may be part of the problem.
You certainly can use DATA A for RTTY if you shif
Gary,
What bandwidth are you using in AFSK A. Normally it defaults to 400 to
500 Hz, but your switch from DATA A to AFSK A may be confusing it.
I cannot speak to interaction between WSJTX and MMTTY, but you may find
something there in the switchover.
Normally in MMTTY, you tune to a specific
Thanks for the info, Ed. I'm going to have to figure out my own antenna for
this band.
Wayne
N6KR
http://www.elecraft.com
> On Sep 17, 2017, at 12:01 PM, Edward R Cole wrote:
>
> Thanks Wayne.
>
> I have been using my K3 (SN 4043) purchased in 2010 on 495 to 502 KHz from
> 2012 as par
Solved: PIC16C72A was defective.
I had the chance to get a second K2 for reference testing. The KSB2 of
that K2 works perfectly in my K2, but not vice versa. The error is
isolated to my KSB2, but now I'd need to seek for the culprit.
I noticed a strange behavior at U1.16, which drives the DAC-Co
You guys may already know this, but there exists software that can read a graph
and generate data from it. For instance, it can turn a plot on a device's PDF
datasheet into real data. Just Google it. The one I've seen electronics people
using is called "engauge".
Al W6LX
__
On 9/17/2017 12:28 PM, Terry Brown wrote:
Please reply to me directly if you would please. We have far too many OT
threads that take on a life of their own.
The Tower Talk reflector would be a great place to get this sort of advice.
TowerTalk mailing list
towert...@contesting.com
http://list
Hard to enter a short subject that is
complete...
Have a K3s using USB to the computer & the
internal card for digital modes.
I wanted to work a few Q's in the RTTY
contest and have been using WSJT-X for FT8
contacts.
In the K3s WSJTX requires Data A for FT8
and in MMTTY it requires AFSK A
Hello All,
Please reply to me directly if you would please. We have far too many OT
threads that take on a life of their own.
I own a KX2, KX3, PX3, KXPA100, and K2. I love my Elecraft rigs. I have learned
much from this list so thought I would ask a question.
Background: I took down my 50
Thanks Wayne.
I have been using my K3 (SN 4043) purchased in 2010 on 495 to 502 KHz
from 2012 as part of the ARRL Experimental 500-KHz Group using
experimental license WD2XSH/45. Primarily using std CW or WSPR at
about 4w ERP. Our experimental license specified using power up to
20w ERP so
Don,
again thank you for your suggestions and information.
I'll look for a new EEPROM and then I'll follow your recommendations (I know
the procedure to unsolder an IC, but to be honest I'm not enthusiastic to use
it).
Ciao
Giorgio - IZ0DIO & KW4NE
-Messaggio originale-
Da: Don Wilhelm
Georgio,
The last menu selection does not survive a power cycle. It is "sticky"
until power off/on.
ST L is the default selection upon initially entering the menu.
Yes, you might have a bad address in the EEPROM. Since you have to copy
the menu settings anyway, try doing a Master Reset (hol
Hello Don,
thank you for your suggestion, but before desoldering U7 (not easy) and
changing it I'd like to be sure that the problem is the EEPROM. It seem a
little odd to me that this problem come only with the ATU setting and it's not
so usual that a single EEPROM address is damaged. Another st
If you are exiting the menu correctly, then the problem is likely with a
memory location in the EEPROM IC U7 on the control board.
If you replace U7, you will have to do a Master Reset followed by CAL
PLL and CAL FIL as well as re-entering all the other menu items.
Download the K2 A to B instruct
Yes, Don. Consider also that this behavior is only for the ATU menu as all
the others menu setting are correctly stored.
Ciao
Giorgio
Da: IZ0DIO [mailto:iz0...@yahoo.it]
Inviato: domenica 17 settembre 2017 07:43
A: 'elecraft@mailman.qth.net'
Oggetto: K2 menu issue
I've a problem usin
Georgio,
Are you exiting the menu (two taps - not a hold - of the menu button)
after you select auto? If not, the behavior will be as you describe.
73,
Don W3FPR
On 9/17/2017 1:42 AM, IZ0DIO via Elecraft wrote:
I've a problem using my K2/100 with KAT100: every time I switch off K2 the
ATU m
20 matches
Mail list logo
