WriteLog
[Top] [All Lists]

Re: [WriteLog] 1 pix > 1000 words

To: "Napa" <napa@webryders.net>, <writelog@contesting.com>,"K6VVA - KP2CW" <eric@hilding.com>
Subject: Re: [WriteLog] 1 pix > 1000 words
From: "FireBrick" <w9ol@billnjudy.com>
Reply-to: FireBrick <w9ol@billnjudy.com>
Date: Wed, 28 Apr 2004 06:23:19 -0500
List-post: <mailto:writelog@contesting.com>
The keypad is called XKeys and can be found in the TigerDirect.com catalog.
I've used one with my mfj memory keyer for years.
A different key programmed for a different cw message.
But they are prone to rf. But a phone call to the company provided some info on 
rfi
proofing the case.
I had to modify it by opening it, and covering the electronics with foil which 
was
grounded. That cured the rfi.
It works very well.
They have a larger, more keys, unit also. Tain't cheap though.


----- Original Message ----- 
From: "Napa" <napa@webryders.net>
To: <writelog@contesting.com>; "K6VVA - KP2CW" <eric@hilding.com>
Sent: Wednesday, April 28, 2004 5:37 AM
Subject: Re: [WriteLog] 1 pix > 1000 words


> Where does one get the macro strips or macro keypads ? This looks kinda cool
> ! could be used for a myriad of tasks.
> Thanks....Randy N1KWF
>
> ----- Original Message ----- 
> From: "K6VVA - KP2CW" <eric@hilding.com>
> To: <writelog@contesting.com>
> Sent: Wednesday, April 28, 2004 3:48 AM
> Subject: [WriteLog] 1 pix > 1000 words
>
>
> > I've re-threaded my most recent post about SSB messages, and appreciated
> > the responses.
> >
> > Several previous direct emails about my overall "Crusade" for a higher
> > percentage of NON-Robotic alternative voice-keying confirmed that there
> are
> > indeed a few on the planet who have actually grasped the concept of what
> > this is all about.
> >
> > Suggestion:   Look at the following pix & then come back and "let's talk":
> >
> > http://www.k6vva.com/lcmcc
> >
> > After returning from Visalia on Sunday, once again my voice went out due
> to
> > a weird form of Laryngitis, which is what prompted the whole issue of
> going
> > beyond-robotic-voice-keying when I couldn't speak for almost the whole
> > month of December, and couldn't operate SSB in the 10m contest.  Had the
> SS
> > been this coming weekend, I would be screwed.
> >
> > As I've said before, this is NOT for everyone...it is:
> >
> > 1. For those who, for whatever reason (cold, flu, Laryngitis or whatever),
> > still want to operate an SSB contest WITHOUT HAVING TO SPEAK, and yet do
> > NOT want to sound like a #&^! "robot" with callsigns & serial numbers.
> >
> > 2. For those who want to bride the gap between #&^! "robotism" and fully
> > automated voice-keying until the real whiz bang super-technology can be
> > cost effectively implement in the Ham Contesting realm.
> >
> > 3. For those want to substantially reduce operator fatigue in SSB
> contests,
> > while at-the-same-time improve efficiency...and NOT wear out their voices.
> >
> > 4. For those who recognize the benefits of pushing ONE Macro Button for a
> > myriad of functions instead of "ALT + Somekey, CTRL + Somekey, etc.), and
> > do NOT want to clog up your computer with TSR's or other WinDOZE
> > Gremlins.  These Macros work completely INDEPENDENTLY.  On CW, specific CW
> > messages can be programmed directly into the keys and NO software
> "message"
> > spaces are needed.  Changing bands, changing rigs, etc. can all be done
> > with ONE BUTTON...color coded for type of functionality.  The Macro keys
> > can be instantly re-programmed.  Velcro'd at an angle above the keyboard,
> I
> > can quickly substitute pre-programmed key strips for different contests in
> > seconds.
> >
> > 4. For those who want to venture into the realm of more
> > Automation-Automation-Automation in general.
> >
> > Until you've been unable to speak and desire to work an SSB contest, what
> > this is all about probably won't register with you.  That's OK.
> >
> > I Beta Tested v1.0 (partial functionality) as KP2CW in the ARRL CW DX
> > Contest.  Notwithstanding my "Operator QLF" since this was the 1st major
> > contest I had done in 30 years, I could NOT have made the 4,600 QSOs I did
> > without it, because I was in a fog most of the time due to sleep
> > deprivation even before the contest started.
> >
> > The need for separate keys for MORE than "10" SSB messages was born out of
> > past experience in the SS ... and to do more "Automation" ... FD, SS, or
> > whatever, MORE than "10" SSB message memories in WriteLog or any other
> > Contest Logger are necessities.
> >
> > But once again, one must be able to fully grasp what this is really all
> > about...and the "WHY" of the need for individual exchange component
> > messages like in SS:
> >
> > 1. Your Number?
> > 2. Your Call?
> > 3. Your Precedence?
> > 4. Your Check?
> > 5. Your Section?  (a/k/a "QTH")
> >
> > Too many times a request may only need be made for ONE of these, and NOT
> > the whole exchange.  One color-coded section with BOLD PRINT on the
> > backlighted keys makes it simple-simple-simple.  No "memorizing"
> > necessary...only a few "Test Drives" before you can "Rock 'n Roll".
> >
> > But once again, this is NOT for everyone....only those who want to go
> > "beyond...into the future", and NOT be screwed from working an SSB contest
> > if you have no voice, and want to reduce the degree of "robotism" :-)
> >
> > Perhaps the pix will help more to "catch the vision".
> >
> > 73...
> >
> > Rick, K6VVA - KP2CW (Trustee)
> >
> >
> >
> > _______________________________________________
> > WriteLog mailing list
> > WriteLog@contesting.com
> > http://lists.contesting.com/mailman/listinfo/writelog
> > WriteLog on the web:  http://www.writelog.com/
> >
> >
>
>
> _______________________________________________
> WriteLog mailing list
> WriteLog@contesting.com
> http://lists.contesting.com/mailman/listinfo/writelog
> WriteLog on the web:  http://www.writelog.com/
>
>


_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web:  http://www.writelog.com/

<Prev in Thread] Current Thread [Next in Thread>