[DXLog.net - Support] Observations Using the DXLOG at the CQWWRTTY
9a5k at 9a5k.com
Mon Sep 30 09:47:59 CEST 2013
Thanks for your report.
Also, just short info regarding callsign grab from rx decoder window.
If callsign field is empty and message to be transmitted contains
$LOGGEDCALL macro, last recognized callsign will be
grabbed automatically from primary decoder RX window for that radio.
I plan to add two more things when grabbing a callsign.
First one: some shortcut to grab a callsign from secondary RX windows
(instead of primary).
Second one: allow to browse back through the list of recognized callsigns
in primary or secondary rx window.
This means, if callsign field is empty, you will grab last know callsign.
Press it again and you will grab previous know callsign from rx window...
Chris - 9A5K
On Mon, Sep 30, 2013 at 7:42 AM, Ulf Schneider <uschneid at posteo.de> wrote:
> Hello all,
> I used DXLog for CQ WW RTTY too and it performed very well. Being lazy and
> not an RTTY operator at all up to now, I simply used the included MMVARI
> and I was really excited that everything was set up and working within less
> than 2 minutes. Frequency correction worked and the Band Map showed all
> spots after adjusting the RTTY band edges in bandplan_0.txt. The plan was
> to give out some points for two hours or so, but it was so much fun, that I
> stuck to the radio for almost 12 hours altogether.
> Most zones were correct and typing in a state instead of double-clicking
> was OK for me, as I'm quick typer. If you put the $CR macro at the end of
> the [+] message, you have plenty of time to get it in there. I hardly used
> the mouse, except for marking the callsign.
> Ulf DK5TX
> Support mailing list
> Support at dxlog.net
More information about the Support