[Dx4win] Very Satisfied with DX4WIN

[n4qs at vci.net]

There is no reason why we all have to be resigned to the fact that DX4WIN
must be frozen in time and there will never be any more enhancements.  Paul,
after a seven year hiatus, recently added FT4 and FT8 as new modes and
provided support for QRZ.COM XML integration, along with some other nice
features like automatic updates.

For those of us you are weak signal DX enthusiasts, we would like to see UDP
Broadcast support so that we can automatically import digital contacts from
WSJT-X.  This is a major feature that is now supported by almost all other
logging programs.  DX4WIN has for years provided a very nice, seamless
integration between MMTTY and DX4WIN.  Providing the same for WSJT-X is all
that we are asking.  It is a major feature that is vitally needed,
especially as the summer E season approaches on 6 meters.

Last summer there were several openings on 6m from the Midwest in NA into
Europe where my entire screen in WSJT-X was lit up in red.  I needed to know
in real time which stations were new countries for me on 6M (any mode), but
I had to hand type each call into the QSO window of DX4WIN.  This was very
hectic and awkward when so many were calling at once.  I basically had to
ignore DX4WIN and work the pile up in WSJT-X.  After the dust settled, I
then imported the ADI file from WSJT-X into DX4WIN to find out if I had
worked any new ones.

I have recently tested another logging program that handles this integration
between WSJT-X and the logger very nicely.  The two programs talk to each
other exchanging data via UDP broadcast.  A window from the general logger
displays the calls from WSJT-X and tells you which ones are new for DXCC.
If you click on a call in WSJT-X to begin calling that station, the callsign
is immediately put into the Callsign field of the general logger.  A QRZ.COM
XML lookup takes place from the logger and the station's info is displayed
so that you can again confirm callsign, locations, grid, etc.--all while the
contact in WSJT-X is taking place.  Then when the contact is over and added
to the log in WSJT-X, it is also immediately added in the logging program.
You can immediately send a spot if desired.  All of this happens very fast
and seamlessly between the two programs -- very similar to how MMTTY is
currently integrated into DX4WIN.

Some may ask why I just don't go with the other logging program if I like it
so much.  I actually prefer many other features within DX4WIN mainly because
it can easily accommodate my 187,000+ contacts without getting too slow and
because it also provides group support for my DX-pedition calls.  And yes,
the country and awards databases maintained by Jim, AD1C, are the best.
Thank you Jim.  But the one glaring weakness in DX4WIN, based on the current
standard among virtually all actively supported logging programs, is the
lack of UDP broadcast support for communicating with other programs like
WSJT-X and FlDigi.

I might add that the other popular loggers also offer the option to
automatically upload to many services such as Lotw, Clublog, QRZ.com and
others.  This summer, as 6 meters heats up, it would be nice to have the
option to turn on automatic updates to Clublog so that each contact is
immediately uploaded to Clublog.  That way DX stations on the other end can
use the link on my QRZ.com page to see if they made it into may log.  I have
used this feature in Belize and Grand Cayman using N1MM+ and it worked very
well.

All the other loggers provide the option to turn UDP broadcast support on or
off and the same goes for automatic updates to Lotw or Clublog.  So, for
those users of DX4WIN who do not have any interest in these features, Paul
should allow them to simply not turn them on.  In short, UDP broadcast
support is a current standard within the hobby that needs to be incorporated
into DX4WIN.  I hope that we can use this forum to continue to discuss new
enhancements as our fascinating hobby continues to evolve.

73,

Dave, N4QS  

-----Original Message-----
From: dx4win-bounces at mailman.qth.net <dx4win-bounces at mailman.qth.net> On
Behalf Of WA7AA
Sent: Thursday, April 16, 2020 11:25 AM
To: dx4win at mailman.qth.net
Subject: Re: [Dx4win] Very Satisfied with DX4WIN

On 16-Apr-20 08:02, Michael Mathis wrote:
> I am very satisfied with DX4WIN: User since 1999, never posted to group -
silent majority? Minority??  Whatever, it matters not.  I like it!  Avid
DXer and very casual contester.  Upgrades are welcome and appreciated.
Freedom to choose the program that we like and prefer is wonderful!  Thank
you Paul and Jim!
>
> Mike, N4MIK

It seems now almost mandatory that every few years we get a few people
theatrically "leaving DX4Win" after not getting "upgrades". When pressed on
what those upgrades should be, the answer is either silence or a vague hand
motion about FT8 or some other digital flavor-of-the-day-mode integration.
Interestingly, when this happens, the bells-and-whistles logger of choice
seems to be different every time. This is always followed by the obligatory
"if it wasn't for AD1C...", but as invaluable as Jim's hard work is, it is
never explained just how these other magical loggers are supposedly doing
the same callsign/manager database maintenance without his divine
intervention.

Do we seriously need to compromise simplicity, reliability, and familiarity
of the logger we've been using for decades for an ever increasing number of
digital modes, online QSO repositories or whatever will become a fad down
the road? My vote is no. Leave DX4Win be.

73 & stay safe, everyone.

Zoran WA7AA

______________________________________________________________
DX4WIN mailing list
Home: http://mailman.qth.net/mailman/listinfo/dx4win
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:DX4WIN at mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html