[TRLog] Clarifier kill vs. Clarifier zero
Thomas M. Schaefer
Sun, 18 Aug 2002 17:56:12 -0600
I think the historical reason for not having custom commands for the ASCII
command sets like Kenwood has been because of some of the hex codes,
especially with ICOM. It seems to me that it would be a workable solution to
allow you to place xFDh or x0Fh to indicate a hex value. I might be wrong,
but I do not think that ability has been added. It would be handy to issue
custom commands to hex command set radios.
----- Original Message -----
From: "Guy Olinger, K2AV" <firstname.lastname@example.org>
To: "TRLog Reflector" <email@example.com>
Sent: Sunday, August 18, 2002 2:52 PM
Subject: [TRLog] Clarifier kill vs. Clarifier zero
> This pertains to the MP.
> Actually having the clarifier 'killed' is one of those distractions
> that kill rate later in the contest when the mind is a bit foggy. It's
> another action that has to be remembered. Someone calls up or down a
> bit, and the natural action is to listen up or down by tweaking the
> clarifier. If you have to fumble and remember to turn the CLAR on
> after you realize the knob isn't working, you've probably missed the
> Is there any reason why action "RX CLAR OFF" couldn't be replaced with
> "CLAR CLEAR" for an MP?
> Or alternatively...
> Is there a TR command that can be used to create a literal MP command
> string to attach to an F key? That would allow us to roll our own
> combos, rather than embedding MP issues in what are otherwise more
> straight-forward commands.
> Or perhaps it's time to give us a macro language we can use, and farm
> out some of the subtlety. Particularly on "niche" requests.
> 73, Guy
> TRLog mailing list