[DXLog.net - Support] Observations Using the DXLOG at the CQWWRTTY
9a5k at 9a5k.com
Mon Sep 30 09:28:43 CEST 2013
Did you changed country file to CTY_WT_MOD.dat or it is on default settings
I was using CTY_WT_MOD.data during the Sunday afternoon and it was quite
If someone has some examples where it didn't do it properly (maybe some of
JA stations), let me know,
so I can check this and fix if needed. Thanks in advance for the info.
Regarding clicking in rx decoder window, I have to do two things.
First one is to add "-" as allowed delimiter, as some of the stations
sending 599-15-15 or something like that..
This can't be clicked properly, because dxlog.net doesn't recognize "-" as
separator, it is looking for space character.
Second one is to recognize what is the content of the field and to copy it
to proper destination in the log line.
In CQ WW RTTY example, we have three possible fields to be filled, third
one (state is optional).
So, DXLog should recognize if you click on the call sign. If clicked text
isn't callsign, then it should check if
clicked content is ok to fit in some of the other fields. So, if RCVD field
is defined as WAZZONE type, this will
allow only integer type between 1 and 40... if clicked content doesn't fit
within this rules, it will be checked against
next field which accepts multipliers from custom list, in this case they
are US states... etc.
Also, I've noticed that worked state window wasn't enabled in the software.
So, it is changed in 2.0.17, and it is available
(also this is just definition in contest config file).
Problem with 2Tone as primary decoder is also notified here. It seems that
2Tone has a little bit different way of TX-ing characters.
I've tried with MMTTY as primary and 2Tone as secondary decoder, and
opposite, as 2Tone as primary and MMTTY as secondary decoder.
MMTTY was working as expected, esc key worked fine to cancel current
message. But, 2Tone wasn't. Have to check this differences,
because communication interface should be the same in MMTTY and 2Tone.
And finally, MMVARI and FSK type.. I've checked MMVARI documentation, and
noticed couple of problems with current implementation.
First of all, RX sound card choices where enumerated wrong in MMVARI drop
down menu. If you check this, you will notice that they are same
as TX sound card choices, which is of course wrong. This drop down menus
are filled dynamically, and by mistake in both cases there are
output device enumerated. I've fixed this for 2.0.17 and now have to add
additional menu, where FSK mode can be activated.
All this should be ready for 2.0.17 release which will be available this
Chris - 9A5K
On Mon, Sep 30, 2013 at 6:02 AM, Hector Garcia XE2K <
j_hector_garcia at sbcglobal.net> wrote:
> Thanks for the fast response
> Let me complement some points,
> the zone was pre filled, most countries and US calls show a zone, most
> DXCC show his correct zone
> not the most Russian , US was almost all 05
> the JA's those show as 25
> tks for the advise in the double click next time
> I was working 2Tone main , MMVARI secundary
> MMVARI always work , I do not install or have MMTTY at the moment working
> with DXLOG
> yes on Writelog and stand alone
> Difference in the freq from the bandmap and Status now is fixed
> Thank you for the tip
> Yes I was using the List in the bandmap, was the best option
> RUN SP typed and working fine, now I will make it my RTTY and CW daily
> use F keys with that
> thanks, If I look that do not read the manual or the Help , yes I didn't
> I'm lost
> Again thank you Bob
> J.Hector Garcia XE2K / AD6D
> Mexicali B.C DM22fp / El Centro
> P.O.Box 73
> El Centro CA 92244-0073
> Tweeter @XE2K
> From: "Bob Wilson, N6TV" <n6tv at arrl.net>
> To: DXLog.net Reflector <support at dxlog.net>
> Sent: Sunday, September 29, 2013 8:24 PM
> Subject: Re: [DXLog.net - Support] Observations Using the DXLOG at the
> On Sun, Sep 29, 2013 at 7:11 PM, Hector Garcia XE2K <
> j_hector_garcia at sbcglobal.net> wrote:
> > the module only allow capture the ZONE number but there is no space
> > the STATE or PROVINCE during the CLICK in the screen
> > need to be used the space bar and write the state next to the zone,
> > that manual
> I couldn't figure out how DXLog.net was pre-filling the Zone. It didn't
> seem like it was looking it up in cty_wt_mod.dat properly. Some JA
> stations were not even listed in zone 25?
> > the ESC do not cancel the F keys message when you press 2 or more times
> > or 2 keys one after the other , you need to wait to pass all the
> > message
> Right, Escape it stops the message, but it doesn't clear the buffer like
> you expect it to.
> > ERROR message
> > WndTXProc.CPP waveoutWrite error line154
> I think that must be part of 2Tone not DXLog.net.
> > TXfsk switch case 0:error clic cancel
> > and later again the same error window
> > this error made that the 2tone rx window show all received text is blue
> > like the transmitted message , after one more tx from me the
> > color in RX back to black and blue for TX
> I used MMTTY for transmitting FSK, 2Tone and MMTTY for receive windows. I
> couldn't get MMVARI to work inside DXLog.net, even though it works OK
> > The freq reading in the VFO A in the bandmap and also the logged is
> > different
> Yes, try Options -> Interface specific options -> Use decoder freq
> correction (uncheck this option and frequency display should be fixed).
> REQUEST if is possible for later updates
> > Will like to be included this options:
> > --Check partials do not allow to select with the mouse (click) the call
> > and get inserted in the entry area.
> This seems to work already (was new in 2.0.12), but you have to
> double-click on the call in the check partial window, not single click.
> --Will like to be able to get access to the F keys (keyboard) clicking any
> > screen from the LOG (Digital, check partials, status, etc Not only the
> > log window)
> Maybe you are using Options -> Windows -> Floating? Try using the other
> option; all the Function keys seem to work OK when any DXLog.net window has
> the focus.
> But it would be nice for DXLog.net to automatically grab the focus every 5
> or 10 seconds like N1MM does.
> > -- Be able to expand or contract the BANDMAP to see more a detail the
> > where was the QSO I will like to see 30-40 khz at most
> First, consider using the LIST tab in the bandmap, to see all spots.
> Second, you can press Alt+Scroll wheel up/down while the mouse is over the
> window and it will expand or contract. Funny bug, Ctrl+mouse wheel
> up/down, both directions make the window smaller! :-)
> --- Get an easy access key or where to click to select standar and S&P
> > message
> Ctrl+Tab swaps Run and S&P modes and messages (status shown in clock
> window), but first type RUNSP [Enter] in the logging window to enable
> RUN/S&P switching.
> Bob, N6TV
> Support mailing list
> Support at dxlog.net
> Support mailing list
> Support at dxlog.net
More information about the Support