I have been working on firmware version 1.22 for the MK-1. Right now it’s in the Alpha test stage, though there is still some development to be done. This is mostly a bug fix release to address some problems found in V1.21. Most of the issues involved the USB drive save/restore. I am also working on debugging problems with a couple of keyboards that people have found not to work. More news to come as it develops.
5 comments to MK-1 V1.22 firmware in progress |
|
|
Copyright © 2012 HamGadgets News - All Rights Reserved |
|
Dale,
the keyers on the market has pb with recording the messages…
As I found all of them does not accepting the manually added different lengths pauses between letters, words and sentences during the recording the messages. All letters are always glued together or eventually they are separated by internal fix spacing. Unfortunately the spacing need to be changed for different speed of course to have smooth and crystal clear CW so it’s impossible to put just fix spacing for 5wpm and 45wpm speeds isn’t it?
How it is solved in MK-1 s/w please?
Thank You for support before purchasing the MK-1…
73 – Petr, OK1RP
Petr,
Actually, “fixed spacing” is possible at any speed. Spacing between dots & dashes = 1 dit, between letters = 3 dits, between words = 6 dits. While it’s very common to use longer spaces when sending by hand, you can’t really fault the keyer for sending Morse properly spaced and timed.
With the MK-1 (and, to a certain degree, the PicoKeyer as well) you can insert half-spaces and extra letter spaces, or use Farnsworth spacing to send characters with longer gaps between letters and words. Of course that is only needed when recording messages; when sending by hand you can use whatever spacing you please.
73,
Dale – N0XAS
Dale,
thank You for reply.
In fact fixed spacing for different speed is unusable I guess.
I tested it during years ago on several keyers like LogiKey K3, K4CMOS, PicoKeyer, OK2TEJ also on internal keyers like Orion 565, Elecraft K2, K3 and in all cases there were the same problem…keyers did not followed manually inserted/recorded spacing from the paddle when replyed the messages from memory. In all cases kayers shortened spaces or in better cases “standardized” spaces between letters, words and sentences to fix programmed length.
The problem is that spacing must be variable and fully depending to the operator and his paddle inputs ans actual speed I think. You know it is the same like the speaker will try to record the speech where somewhere between the words he have to have “dramatic pause” to express some important feeling and recording machine will shortening this pause to standard one as same as the other pauses in the speech.
Well if the fixed spacing is pre-defined between dots & dashes = 1 dit, between letters = 3 dits, between words = 6 dits then the keyer need to be able to recognize where I would like to put words space, where letters space and where sentences long space…in most cases long pause causes the keyer going out of the recording mode.
Do You know that there is some chance to test the MK-1 s/w?
If You would like to get help then I am ready to support You with the development.
My best regards,
73 – Petr, OK1RP
FOC 1745
VHSC 315
Dale ,
I woul sure like to beta test v1.22 for my MK-1 masterkeyer. If i beg for many weeks can I become one?
Thanks in advance!!
Kirby, K7EC
BEG, BEG, BEG, BEG
I have to admit, I am several weeks (OK, a couple of months) behind schedule for getting V1.22 out to beta. I’ll work on doing that this coming week, I promise. There’s one remaining bug I want to address before ending the Alpha phase.