I have a fully loaded K3 / 100 watt sn3418 for sale. Perfect working and
cosmetic condition. Non smoker. K3 / 100 comes with the following options:
KAT3 internal ATU, KRX3 second receiver with matched 2.7Khz 5 pole filter,
KXV3A 2nd RX, IF out, transverter interface option, 2.7KHz 5 pole SSB
filte
We had a good net this morning with 31 participants over a 24 minute period.
There was some splatter from 316 for the first half of the net, but we
managed OK. We had five K2s this week, two of them QRP! Here is the list
of participants.
Station NameQTH Rig S/N
WB6CLZ Mike
On 2/6/2011 7:54 PM, Kevin Rock wrote:
>
> Good Evening,
> My grey day turned blustery and then rainy a short time ago. After the
> second net I was in a big hurry to get something to eat so rushed off.
It was 72F [22.22C ... see, we here in the Colonies and even out on the
western frontier
Good Evening,
My grey day turned blustery and then rainy a short time ago. After the
second net I was in a big hurry to get something to eat so rushed off. I
think it was the smell of bread dough rising which was driving me crazy
:) Luckily I had moved it off the wood stove because th
Hmmm..seems like this failed FW load is caused by operator
forgetfullness..don't think that's a word...by owners of Microham
products.
I sure don't need "windoze' to remind me to turn something off or
check some other device is present and running etc, etc, etc.
Maybe I live in the dark ages in O
The serial communications are tested before sending firmware. There is a per
block checksum test and Ack. There is no on chip storage of sufficient to
buffer very much firmware. The program store is 128KB and the available RAM is
less than 4K.
I can work on the error messages, and specific sug
Dick
On Feb 6, 2011, at 15:08, Dick Dievendorff wrote:
> The PIC18F8722 microcontroller used has 128KB of flash program memory and a
> bit less than 4KB of RAM. Its a Harvard architecture machine, not the Von
> Neumann model. Your "simple" suggestion is infeasible. There is no place on
> ch
>From what I have been reading about the protocol used, it seems it is not at
all robust. Someone else said this as well. The ACKs and NAKs are a good
start. These are at times being lost it appears. The utility should have a
timer that lets it resend a frame if there is not ACK or NAK that gets ba
Hi all,
I have loaded virtually every firmware version that ever came out without a
single incident, using several different USB adapters (never had a real
serial port with the K3) and several computers. So I don't have problem with
this at all. With this said, it does appear that a few things co
We do check each block with a checksum. We do have a per block ACK. I can't
tell if a Microham device us inline...
Dick
On Feb 6, 2011, at 15:43, "Craig - AE6RR" wrote:
> Dick,
>
> Would it be possible to check each record or block of data for validity
> (checksum, CRC, etc.) and acknowledg
Thank you for the numerous reponses. The K2 and the P3 have been sold. See
you on the air with my other K/2 and my K3. Great products.
--
View this message in context:
http://elecraft.365791.n2.nabble.com/P3-and-K2-SOLD-tp5998606p5998606.html
Sent from the Elecraft mailing list archive at Nabble
With all the email traffic on the K3 and the microKEYER II / updating
software, I felt compelled to respond.
I have the K3, the P3, and the microKEYER II. For the past two years I
have used the microKEYER II as the transport for upgrading the K3 and
for four months for the P3. I upgrade on ev
Dick,
Would it be possible to check each record or block of data for validity
(checksum, CRC, etc.) and acknowledge (ACK) or request a resend (NAK) from
the PC before writing it to flash? If a data block is corrupted a resend
could be quested multiple times before giving up, declaring an error an
Hi Jack,
Would you please be so kind as to explain what you mean by holding onto
a run frequency.
Also why the 8 pole vs the 5 pole, if you dont mind.
Don
KD8NNU
On Sun, Feb 6, 2011 at 6:09 AM, Jack Brabham wrote:
> Larry,
>
> The 250hz 8 pole is amazingly good in a RTTY contest and appears
The PIC18F8722 microcontroller used has 128KB of flash program memory and a bit
less than 4KB of RAM. Its a Harvard architecture machine, not the Von Neumann
model. Your "simple" suggestion is infeasible. There is no place on chip to
buffer the firmware in its entirety.
Dick, K6KR
On Feb 6, 2
On 2/6/11 3:36 PM, Don Wilhelm wrote:
> I do not know how any additional degree of "robustness" in K3 Utility
> could correct for that condition.
>
Simple... Don't write ANYTHING to the K3 EEPROM (I assume) until the K3
has received the ENTIRE firmware file w/o errors. Blocks with errors can
alw
Craig and all,
Dick has indicated several times that the firmware does have checking
data bits, and they are used for validity checks and as an indication
that the firmware downloads are successful.
What is happening in the discussion that has ensued is that the MicroHam
device is adding (or
Joe,
Thanks for clarifying this and explaining the operation.
I now have a cable attached to the serial port on my computer that is my
spare or download cable. I handle all of the normal radio communications
via my microKEYER interfaces (one dedicated to each radio). I find this
very convenient
On 2/6/2011 10:23 AM, Ron D'Eau Claire wrote:
> Good observation about the plumbing Lu. I'll remember that. Even though the
> K3 is an amazing bit of technology, sometimes I long for the rough
> simplicity of the homebrew station I started out with years ago, Hi!
I don't. Right after I retired i
Bob,
I had the same experience with my first K3 firmware upgrade. I had the
radio connected to the microKEYER II in the normal operating configuration
and was trying out the utility, checking filter settings etc. and decided to
do a firmware upgrade. I had forgotten about micrcoHAM's warning and
Hi Larry,
I do a lot of SSB work and now starting the digital stuff. I find that
I am always going down to 1.8 or less on SSB phone in noisy conditions.
So if to do it again I would not have gotton the 2.1.
Second am finding that I am going down to 100 hz for psk work and I am
thinking about
My first time FW upgrade failed too. The problem? I use Router a
virtual port defining piece of software microHAM uses for their
product's interfaces to such things as the microKEYER II.
In their manual is a warning in Yellow to not perform FW upgrades via
the microKEYER II interface which uses
Don et al,
This is a follow up to my original post, and will hopefully help others
in this similar situation.
I went to the Elecraft website "and read the KUSB serial to USB driver
notes", which I originally failed to do. I then went to the FTDI
website, located the correct driver, and found t
Your experience apparently reflects that of most K3 owners, Lu.
That's no comfort for those who do have problems, but it's almost impossible
to fix something until it can be made to fail on command by the one who is
doing the fixing.
When the problems are concentrated on a statistically small nu
My first time FW upgrade failed too. The problem? I use Router a
virtual port defining piece of software microHAM uses for their
product's interfaces to such things as the microKEYER II.
In their manual is a warning in Yellow to not perform FW upgrades via
the microKEYER II interface which uses
I see posts like these often here, and (knock on wood) I have *never*
experienced any problem whatsoever in loading firmware into my K3 (#3192)
since I have owned it. I dont understand why there is so much angst
regarding firmware updates!
The computer I use is a Dell GX280 mini desktop. It has
On 2/6/2011 7:10 AM, Dave Hachadorian wrote:
> I do RTTY and SSB contesting too. I settled on the stock 2.7 for ssb
> ragchewing, 1.8 for ssb contesting, and 250 for cw and rtty contesting. I
> had some others, but sold them. In the config menu, tell the K3 that the
> 1.8 is really a 2.1, and te
On 2/6/2011 8:40 AM, K9ZTV wrote:
>
>
> On 2/6/2011 7:49 AM, Jack Brabham wrote:
>> Baring the remote possibility that Elecraft comes up with a more
>> sophisticated system for doing these down loads, my plan is to limit
>> doing these in the future to about once a year, due to their being such
>>
I am not disputing your point, but want to add that the USB->serial adapters I
have had, 3 different types, were prone to lightning damage if not
disconnected. I have suffered damage to a serial port, too, over 25 years ago
when the discrete driver chips were replaceable. But not in 10 years i
On Sun, 06 Feb 2011 09:36:59 -0600
Jack Brabham wrote:
Jack,
> Hardly a day goes by that there is not at least one "firmware
> download problem" string running on the reflector.
>
Most of which turns out are caused by USB to Serial adapters,
Those using real serial reports very rarely report f
Grant,
On 2/6/2011 8:20 AM, Grant Youngman wrote:
> It seems to be very few people that have a problem updating firmware.
Hardly a day goes by that there is not at least one "firmware download
problem" string running on the reflector.
> And it's amazing that it still gets blamed on the Utility
Old-fashioned I guess but I use the serial port instead of USBworks every
time.
__
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:Elecraft@mailman.qth.n
Hi Larry,
I do RTTY and SSB contesting too. I settled on the stock 2.7 for ssb
ragchewing, 1.8 for ssb contesting, and 250 for cw and rtty contesting. I
had some others, but sold them. In the config menu, tell the K3 that the
1.8 is really a 2.1, and tell the k3 that the 250 is a 400. That
This brings up a question. I have seen posts where people selling their
Elecraft K3 since it's intro stating in the ad that the warranty can be
transferred. I haven't seen Anything on their website indicating this as fact.
It appears the warranty is to the original buyer unless it's bought as a g
The minimum is the 5-pole 2.7 kHz filter included in the base price.
73 de Dick, K6KR
On Feb 6, 2011, at 7:01, "Larry stowell" wrote:
> I just got back to the "Frost Fest" and played with a K3 I'm 95% sure I'm
> going buy a K3. I want to
> start and build. I have to start with the K3/100 as
Each of the firmware files is checked for line by line checksum validity and
the presence of a file end record during FTP (which isn't used in the Beta
unzip process) and the firmware files are read into the PC's RAM and similarly
verified before initiating firmware load. We don't access the fil
On 2/6/11 8:47 AM, R. Kevin Stover wrote:
> Don and all,
>
> It isn't the K3 utility's problem either.
> Just how is the utility's supposed lack of robustness affect the
> connection between radio and computer? It doesn't.
The actual connection, no. BUT, K3 utility's lack of robustness DOES
allow
It seems to be very few people that have a problem updating firmware.
And it's amazing that it still gets blamed on the Utility, the radio, file
integrity, whatever. Of course it could be any of these, but that isn't nearly
as likely as a broken USB/RS232 driver. Most of us have never had a pr
I have the P3 factory assembled For Sale. It is a wonderful colorful addition
to my shack, but it is also useless to me. I can find no practical use for
the P3, and it just occupies space in my shack. I am the original owner and
it is in pristine condition. Insured and shipped to your door in the
Larry,
The 250hz 8 pole is amazingly good in a RTTY contest and appears to me
to be about as narrow as can be used. The 500 hz 8 pole Inrad is a
little more versatile but not quite as good at holding onto a run frequency.
I use the 1.8kc for SSB contesting but I think the Inrad 1.5 kc would b
I would.
I don't now the inner workings of the utility but I assume there's
something built in to check file integrity before the upgrade process.
If not then that would be something to seriously think about adding.
Easy enough to check MD5sums.
On Sun, 6 Feb 2011 07:55:15 -0500
"Lee Trout" wrot
Craig,
The last few times I have attempted downloads to my K3 they failed and
it took a few days to get it running again.
I've ended up having to remove the K3 from my station setup, and put it
on my work bench where I have a "Vintage PC" with a native serial port.
Baring the remote possibilit
Don and all,
It isn't the K3 utility's problem either.
Just how is the utility's supposed lack of robustness affect the
connection between radio and computer? It doesn't.
The entire planet has been sold a bill of goods concerning laptops,
mostly because of the "gee whiz" factor. They are compromi
I just got back to the "Frost Fest" and played with a K3 I'm 95% sure I'm going
buy a K3. I want to
start and build. I have to start with the K3/100 as 10 watts won't drive my
amp. I have a SteppIR
so the tuner isn't needed. My question what is the minimum filters. I don't do
CW, I do RTTY
cont
Craig's problem brings up a question. If, for whatever reason, one or more of
the downloaded firmware files is corrupted, do you need to delete all the
downloaded files from your computer, do a new download from Elecraft so that a
reload doesn't just grab the corrupted file again? Thanks, Lee
Greg ab7r hit it on the head. I didn't have my PS amps up enough. Cranked
her up and the TX gain test went like nobody's business. I will be making my
first contact with this rig today. I will post here before I go on the air.
73
Dohn Smythe N8EWY
_
Hello!
I have just recently assemled KRC2 band decoder fro sale. It is fully tested
with the latest firmware. It just exceeds my needs at the moment, I have
some other decoders in function.
Please contact me off the list if you are interested (EU desirable)
73 Robert, S57AW
_
I get 240 +- 2v here in Bracknell in Berkshire.
73 de M0XDF, K3 #174, P3 #108
--
No sensible decision can be made any longer without taking into account not
only the world as it is, but the world as it will be.
-Isaac Asimov, scientist and writer (1920-1992)
On 6 Feb 2011, at 09:36, David Cutter
I can't speak for other countries, but here in the UK I used 240V +-7%
(223V to 257V) for normal service but for brown to peak I used 240V +-10%
(216 to 264V), which is very rarely seen here. The 264V is used to test
safety trips and the like according to British Standards such as the the
gene
49 matches
Mail list logo