Work around for the DXPedition and General DXCC tracking modes for switching
between CW and RTTY macros in WL....
Create two "dummy" logs, one containing your CW macros, the other your RTTY
macros. These "dummy" logs only exist to hold the different macros required
for each mode. Label them with "CW" and "RTTY" in the log file names to easily
differentiate between the two.
When you want to change modes just go to Setup/CW/RTTY/SSB memories, Browse to
the correct "dummy" log name and import the correct macros for that mode. Then
reconfigure the Rttyrite window settings to the new mode, port, TNC, etc. and
you're ready to go. No muss, very little fuss!
Gary AL9A
Sent from my Kindle HDX
On December 28, 2014, at 6:29 AM, "Joe Subich, W4TV" <lists@subich.com> wrote:
> Over time, though, I have a rich enough archive of old contests, such
> that I usually have the exact contest from which I can import
> messages. Thus, I never run into the problem of messages being for
> the wrong mode. More important the messages are already customized
> for the current contest.
The one thing that this does not address is the use of DXPedition or
General DXCC tracking modes for day to day operation or unsupported
contests. In day to day operation one is likely to encounter CW,
digital and phone modes interchangeably (unless one is allergic to
the microphone or does not know CW <G>) and in that case, overloading
the CW messages for RTTY (Data) is a problem for several reasons:
1) one would not want to send cut numbers or even 5NN in RTTY,
2) embedded CW keyer commands are sent as text in RTTY,
3) the structure of RTTY and CW exchanges may be a bit different -
particularly in non-contest settings.
73,
... Joe, W4TV
On 2014-12-28 12:35 AM, Ed Muns wrote:
> The following comment doesn't directly address your concern, but it
> describes how I avoid this issue.
>
> I save each contest in its own folder along with any other files pertaining
> to that contest, like a 3830 writeup, a custom prefill file, the
> ADIF/Cabrillo/TQSL files, etc. When I open WriteLog for a new contest, I
> import the messages from the last (similar or identical) contest by browsing
> to the *.wl file of the prior contest. Obviously, I don't import messages
> from a contest with a different mode. Over time, though, I have a rich
> enough archive of old contests, such that I usually have the exact contest
> from which I can import messages. Thus, I never run into the problem of
> messages being for the wrong mode. More important the messages are already
> customized for the current contest.
>
> For example, when I operated as W1AW/6 on RTTY, I imported from one of my
> prior basic RTTY contest *.wl files, made some minor adjustments to my
> messages and was ready to go. I have evolved to specific Fn messages being
> the same function, e.g., CQ, Run Exchange, S&P exchange, QRV, individual
> exchange elements, requests for individual exchange element fills, QRZ, etc.
> So, customizing for the current contest is quick and easy.
>
> Ed W0YK
>
> ------------------------------------------------------------------
>
> Jim AD1C wrote:
> I would be happy if WriteLog would just ignore the RTTY-specific
> macros in the CW/SSB/Digi memories (like Tx and Rx). It would make
> switching between CW and RTTY so much easier. It was a pain when I
> was operating as W1AW/0 earlier this year.
>
> _______________________________________________
> 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/
|