VQSpot is a simple program developed for sending DX-Spots automatically when
QSO are logged into VQLog (Please read the guidance notes below).
You can download and use this software for free for your own private use,
however please understand that I don't offer any kind of support and I don't
promise to develop new versions in the future (VQSpot is not a part of VQLog,
it's a separate program, however it is integrated in the standard setup of VQLog
3.1 build 11, and later).
VQSpot does not require installation. Simply copy the four files contained in
the ZIP to
the same folder of the hard disk where you have VQLog's files (The folder
with the files
log.mdb, config.mdb, etc)
This version of VQSpot only works if you have
version 3.1 build 81 (or later) of VQLog.
Run VQSpot besides VQLog (start both programs). VQSpot will detect every new QSO
being logged in VQLog and it will send a formatted DX-Spot to the DX-Cluster
looking like: DX de EA6VQ: 144300.0 EA6TST JM19MP<TR>JM08ZZ Tnx
QSO ("Tnx QSO" is whatever text you have entered in the
VQSpot is only useful if you enter QSO in real time, this is at the
same moment you make them. It you enter old QSO they won't be sent.
VQSpot is not intended to be used when you are running a pileup,
otherwise you will flood the DX-Cluster with useless spots. Use it mainly
when you are working DX in search and pounce mode.
VQSpot is intended to be used for reporting QSO in the VHF and up
bands, where most of the QSO reported are DX. So far it works for the HF
bands but this could change as soon as I detect an improper use of the
The only responsible of the DX-Spots sent is YOU, so make
sure you make an appropriate use of the program.
Some additional information:
VQSpot does not send spots directly to the DX-Cluster, but making use of
an intermediate page hosted at
https://www.dxmaps.com. This means:
I can centrally restrict the use of the system (or even
definitively suspend it) when there is an improper use of it.
I WILL ban any user that sends spots with inappropriate or
All sent spots are in a log, that I can analyze at any time and that
it's publicly available upon request.
If after reading all the above you still think that VQSpot is evil and
that it will "collapse the DX-Cluster" or so, please be so kind not
to annoy me with your irrational fears.... I'm really fed up of
having to justify every single action I take or program I make, so don't
waste your time E-Mailing me.
Changes in version 1.8:
Not restricted to use the default file names and locations of
configuration and log files.
Changes in version 1.7:
Support of version 3.1 (build 81) of VQLog
Saves window position and size
Changes in version 1.6:
When a satellite, split or cross-band QSO was entered, the own TX
frequency was spotted, instead of the RX frequency.
Changes in version 1.5:
Fixed a problem (Run-time error 3044) during startup.
Changes in version 1.4:
When it was run with an empty log it showed an error
Button to minimize it more easily.
Pressing the ESC key also minimize it.
Changes in version 1.3:
Minor changes to better adapt it to VQLog 3.1
Changes in version 1.2:
Former versions had problems sending spots when PC was not set to UTC time.
Changes in version 1.1:
Possibility to request confirmation before sending the spot (recommended
and default option)
Spot was only sent if the PC had the UTC time.
Control QSO start and end times when determining whether it must be sent
Initial screen show the guidance notes and additional information.