This
page has been moved here.
http://www.asahi-net.or.jp/~yy7a-ysd/UtilityProgram/UtilityProgram.htm
Utility Program
for Logger32
by ja1nlx
last updated 2017/2/2
I have developed
some utility program to be used with Logger32. You can download each program on
this page.
If you have
difficulty to download then send me email.
ayoshida
<at> my.email.ne.jp
Utility |
Status |
Last update |
2017/1/28 |
||
Under testing |
Coming soon |
|
2016/11/22 |
||
2016/11/9 |
||
2016/2/29 |
||
2016/3/5 |
||
2016/10/9 |
||
Under testing |
2017/2/2 |
|
2016/9/20 |
||
2016/5/22 |
||
See below |
2016/4/3 |
|
2016/12/18 |
||
2016/12/18 |
||
2016/9/1 |
||
2016/11/27 |
||
|
||
2016/8/4 |
||
|
||
|
||
2017/1/18 |
||
2016/4/6 |
Tips to use utlities
There is no menu bar in some utilities. Right click
on the window to show menu.
a.
I
recommend you to setup a utility as one of utility programs in Logger32.
b.
Almost
all utilities should be run together with Logger32. Utility communicate to
Logger32 using Logger32 external inteface. External interface allow to use max
5 utilies at same time. If connection is established successfully then you see
“Connected to Logger32-n”, “L32-n” etc
in the window or pull down menu. (n=1 to 5)
c.
Logger32 should run always as administrator. This is suggested in
Logger32 Help file.
If Logger32 run as administrator then utility program should
run also as administrator. Otherwise utility does not work correctly.
If Logger32 run as NOT administrator then utility program
should run also as NOT administrator. Otherwise utility does not work
correctly.
d.
If utility runs as compatible mode (Windows XP SP3 etc) you get a
little diffrent appearance. I reccomend you to set Windows XP SP3 compatible
mode.
CheckCallPartial
check callsign partially when you type at least 2 letters in callsign field of
Logbook entry window. The database files are xxx.scp file which can be
downloaded from following page.
http://www.supercheckpartial.com/
If you do not
like to use MASTER.scp etc for contest then you can use YourLogbook.scp.
CheckCallPartial has a function to create YourLogbook.scp reading exported
Logbook.adi.
When you type
“E5” then it shows like this
When you type
“1” after “5” then it shows like this
UtilityPlus ver2.0 coming soon
If you are interested in this utility
then send me email. I will send you files for your test,
This is “All in one” utility and support the
function of CheckCall(option), CheckIOTA(option), ClubLogUpload with
DupeCheck(option), FreqPad(option) and Date/Time(UTC). This is fully redesigned
version of previous UtilityPlus.
(only one file to be opened at same time for
CheckCall, only callsign/Band/Mode check for DupeCheck, only UTC display for
Clock etc)
Summary ver1.0
This is utility when you use Logger32 during
contest or your DX pedition. It show some “How many QSOs I have worked ?” in
real time.
RegistryEditor for Logger32
ver1.0
This is a tool for Windows 10
user to change registry setting easily. It provides capabilities to change
following color settings.
a.
Active Titlebar color and Titlebar text forecolor
b.
Inactive Titlebar color and Titlebar text forecolor
c.
Menu color. Menu text forecolor
d.
Titlebar font. Menu font
To use this utility follow steps described in
ReadMe. Always make backup of your current registry settings.
Clock ver1.23
Clock is a stand alone utility program. It shows
Local time, UTC and memo. Window’s
height and width are adjusted automatically and positioned anywhere.
New option added.
Bug fixed (when window’s right side reach screen
right side (by auto adjust width) it did not move to left)
<How to use>
a.
Make a folder and place Clock.exe in the folder.
b.
Run Clock.
c.
Move the window anywhere you like. I prefer to
place Clock in the task bar.
d.
Right click on the window to show menu.
This is a utility which upload a QSO on ClubLog
everytime you log in Logger32.Following ADIF fields are uploaded and ClubLog
accept this.
<CALL>
<RST_SENT>
<RST_RCVD>
<NAME>
<BAND>
<MODE>
<GRIDSQUARE>
<IOTA>
<APP_COUNTRY>
<QSO_DATE>
<TIME_ON>
All fields data except <QSO_DATE> and
<TIME_ON> are received directly from Logger32 via external interface.
<QSO_DATA> and <TIME_ON> are calculated and added when QSO is
logged. This does not affect other 3rd party utility which may use
ADIF audit trail.txt, Clublog Dump file.txt or eQSL dump file.txt.
<How to use>
a.
Make a folder and place ClubLogUpload.exe in the
folder.
b.
Run ClubLogUpload. Move the window anywhere you
like.
c.
Right click on the window to show menu.
d.
Click Setup ClubLog first to set email,password and
callsign for ClubLog. Callsign is a callsign in ClubLog where you want to
upload QSO. Click Apply.
WinKey+ ver3.37
WinKeyMini
ver1.0 Red text
below is for WinKeyMini
WinKey+ and WinKeyMini work
only together with Logger32 and control WinKey device. It has been developed to
use mainly during MY DX pedition. However it is good for daily operation for
you as well. Please do not ask me to add more features.
1.
It provides max 12 buttons (F1 – F12) , Space key
and Return key for sending message. max 8 buttons (F1 – F8) for WinKeyMini
2.
Following entry box are available.
a.
Callsign box: type his callsign here.(mandatory)
b.
Sent/Rcvd RST box: (efault 5NN no box for WinKeyMini
c.
Name box: type his name here (optional)
3.
Following macros are avaolabale.
a.
<HISCALL>: inserts his callsign entered in
callsign box
b.
<5NN>: sends “5NN” message with temporaly
increased CW speed
c.
<NAME>: inserts hs name entered in name box.
d.
<ADD1>: inserts additional message
e.
<ADD2>: inserts additional message
f.
<ADD3>: inserts additional message <ADD1> and
<ADD2> fro WinKeyMini
g.
<CLEAR>: clears entry box
h.
<LOG>: Logger32 log this QSO
4.
Keyboard sending is avalable. not available for
WinKeyMini
5.
Following control buttons are available on the
panel.
a.
22WPM: clicking this button increase/decrease CW
speed.
b.
CW-1: clicking this button switch CW output port
(CW-1 or CW-2)
c.
+5WPM: clicking this button sets temporal
increasing CW speed (+1 to + 15WPM)
d.
Iambic A: clicking this button switch Winkey mode
(Iambic a, Iambic B and Ultramatic)
e.
<ADD1> and <<ADD2> and <ADD3>:
enable/disable addtional message sending.
no <ADD3> for WinKeyMini
f.
CLR: clicking clear entry box
g.
Space: clicking send Space key message if “Enable
Space key ” option is checked.
h.
Return: clicking send Return key message if “Enable
Return key ” option is checked.
i.
Dupe check is available. (Callsign/Band/Mode) no Dupe check for
WinKeyMini
CheckIOTA Plus ver3.75
When callsign/IOTA are entered
(manual or clicking DX spot) in Logbook entry window it shows “New”, “Not
confirmed”, “Worked” and current total IOTAs workd in a small window..
When DX spot come and IOTA
reference number is populated by comment then 1) it shows “New” or “Not
confirmed” and 2) it shows all IOTA spots in the table with “G” (granted),
“S” (submitted), “NC” (not
confirmed and “!” (New) mark.
CheckIOTAPLus check IOTA only for
QSO on HF Bands (IOTA standard award). IOTA rule has been changed since Jan
2016.
<How
to use>
a.
Make a folder and place CheckIOTAPlus.exe in the folder.
b.
Run CheckIOTAPlus. Move the window anywhere you like.
c.
Export the latest Logbook adif.
d.
Right click on the window to show menu and click Create CheckIOTAPlus
files first.
e.
4 files are created in the CheckIOTAPlus folder. Worked.txt,
Confirmed.txt, Submitted.txt and Granted.txt.
f.
When new IOTA QSO is logged then this IOTA is added in Worked.txt. You
must do Create CheckIOTAPlus files step whenever you get
confirmed/Submitted/Granted IOTAs.
DupeCheck ver2.42
Bug fixed. Space separated
DupeCheck.txt file is used in this version instead of comma separetaed file.
<General>
a. This utility is useful for
contesting and daily logging with Logger32 and provides you “Worked before”
message and sound alarm.
b. You have many options in this
utility, message appearance and dupe check options (call, call/Band and
call/Band/Mode).
c. This utility does not check
previous QSOs in Logger32 Logbook but check internal text file. QSO info
(callsign, Band and Mode) is written in internal text file and saved as
DupeCheck.txt in the folder when QSO is logged in Logger32. Data format is like JA1NLX 20M CW
d. Dupe check will start when
callsign field in Logbook entry window is changed by manual entry or clicking
DX spot. You see “xxx New”, “xxx Worked”, “xxx new this Band”, “xxx worked this
Band” , “xxx new this Band/Mode”, “xxx
worked this Band/Mode” on message area.
e. Right click on message area to
show menu.
h. If you want to use for daily
logging then you must export/convert
adif to DupeCheck.txt first. “Create
DupeCheck.txt” will do this conversion.
<How to use>
1. How to use in contest
a. Delete
DupeCheck.txt if it exist in DupeCheck folder when you start new contest. If
you are using DupeCheck for daily logging then existing DupeCheck.txt must be
saved
in safety
area. You move saved DupeCheck.txt into DupeCheck folder after contest.
b. Run
DupeCheck. Ready to go now.
2. How to use in daily logging
a. Export
current Logbook in adif.
b. Run
DupeCheck.
c. Right
click on message area, click File, Create DupeCheck.txt and select adif.
d. Watch
progress bar.
e. When the
progress bar disappears it is ready to go now.
<Note>
a. DupeCheck check whether call
or call/band or call/band/mode exist in DupeCheck.txt or not when you enter
call in Logbook entry window or you click DX spot.
b. DupeCheck.txt is loaded when
you run DupeCheck and saved when you close DupeCheck.
c. If QSO is logged in Logger32
then call/band/mode is saved in internal loaded DupeCheck.txt and DupeCheck.txt
in the folder at same time.
d. If you create new
DupeCheck.txt then current DupeCheck.txt is replaced by new one. If you need
then current DupeCheck.txt should be saved in safety folder before you click
“Create DupeCheck.txt”
e. If you run multiple utilities
(using external interface implemented in Logger32) and see any problem then let
me know.
BandPlan and BandPlanMini
BandPlan. It shows 500KHz freq width.
BandPlan2
ver2.0 2016/4/3
BandPlanMini This is same as BandPlan except it’s
width. It shows 250KHz freq width
BandPlanMini2 ver2.0 2016/4/3
<General>
a. It works only together with
Logger32.
b. It shows corresponded BandPlan bmp picture when Band is changed (BMP
pictures are created by Steve W6SFK. Thanks Steve).
c. It shows current radio Frequency and Mode on title bar.
d. Radio Freq/Mode are changed when clicking on the picture. Mode is derived
from Band/Mode table in Logger32.
e. It shows
tuning bar (vertical red line) on the picture.
f. Text
appearance on title bar can be configured. Font name, size, bold, Italic,
forecolor and backcolor. Freq format on title bar is user selectable,
21040KHz,21.040MHz or 21.040.0MHz.
Right click on title bar to show option menu.
g. Title bar
height is automatically adjusted when font is changed.
h. “X” on
title bar is in Green backlight when the utility establish connection to
Logger32. Clicking “X” close the utility.
<How to
download>
If you prefer
BandPlan then downloads BandPlan and one of BMP set for BandPlan.
If you prefer
BandPlanMini then download BandPlanMini and one of BPP set for BandPlanMini.
Changes
in the latest version:
BandPlan2
ver2.0 and BadplanMini2 ver2.0 are available. Frequency bar removed to reduce
size. Right click on right side bar to show menu.
Program
BMP set
for BandPlan
BMP set
for BandPlanMini
<How to
install>
1) Unzip
downloaded zip file (BandPlan or BandPlanMini). You have BandPlan.exe (or
BandPlanMini.exe).
2) Make
BandPlan folder (or BandPlanMini folder) anywhere you prefer. Copy BandPlan.exe
(or BandPlanMini.exe) in the folder.
3) Unzip
downloaded zip file (one of BMP set). You have BMP folder (contains 160.bmp,
80a.bmp, 80b.bmp etc). Copy BMP folder in the BandPlan folder (or BandPlanMini
folder)
<How to run BandPlan>
It should
read BandPlanMini below if you install BandPlanMini.
1) Configure
BandPlan.exe as one of utility program to run from Utility menu in Logger32 .
a.
On the Logger32 Menu Bar select: Tools/Utility Program Setup to open the
Utility Program menu setup window.
b. On an available line enter the
item BandPlan and with the Browse button on the right go to the Logger32
folder, open the BandPlan folder then click the BandPlan.exe file to set the
link.
c. If you want the BandPlan
utility to autostart, check the box to the left on the BandPlan item line then
select Apply.
2) Run
BandPlan. You will find the BandPlan window at the top left of your screen.
3) Resize the
window to view the entire map then drag to any location on your screen.
4) Right
click the BandPlan top title bar and you can select the font style, font size,
title bar color and freq format.
5) Click “X”
to close BandPlan.
<How to
use BandPlan>
It should
read BandPlanMini below if you install BandPlanMini.
1) Run
BandPlan.
2) The BandPlan window should now
display the current radio frequency and mode. Mouse click anywhere on the
BandMap. The radio will change to that frequency and mode. If you click an out
of band location on the BandMap you will get a "Not supported
frequency" message. It is very important that you have edited your Logger32
Bands and Modes database for your QTH.
On the
Logger32 Menu Bar select: Tools/Setup Bands & Modes. Here you may edit the
Bands, Modes and frequency limits for your QTH. Refer to the Logger32 Help
Files. When you t une the radio frequency the BandPlan map will automatically
change to the correct map when you reach an active band listed in your Bands
& Modes database.
<How to
make your BMP file>
At first I recommend you to use
one of provided BMP files which is contained BMP set above. When you are
familiar to BandPlan then try to modify existing BMP files or create your own
BMP files. Windows Paint, PhotoShop or something similar will work for you. a.
Picture size must be 600 x 60 pixels (width x height)
Frequency
span must be 500KHz. 0KHz(or 500KHz) should start at 50 pixels from left side
of picture and 500KHz (or 0KHz) should end at 550 pixels from left side of
picture.
If you have
any difficulty then do not hesitate to send me email. We may help you to
modify/create your bmp files.
CallsignLookup utility
Each utility works together with
Logger32 ver3.45.0 and after. It does not work as
stand-alone. Please read ReadMe.doc in each package first before you
use. I am sorry but Lookup_QRZCQ_XML is discontinued.
Lookup_QRZ_XML ver3.12
Country field added to show country name in this version.
QRZ
XML service is not free.
Lookup_HamQTH_XML
ver1.97
Country field added to show country name in this version.
HamQTH
XML service is free, however you must be registered. This is much faster than
their ADIF service.
Lookup_HamQTH_ADIF
ver1.94
HamQTH
ADIF service is free, however you must be registered.
CheckCall ver5.35
Fully re-designed
version.
CheckColor
ver2.4
CheckColor is an external
program which reads Logger32.ini (or your ini) and shows a color box for most
of highlight/background color you configure.
As you know Logger32 provides many choices of highlight/background color. Can
you always understand what each color means when you see the Logbook Page
Window, Award Table or DX Spot Window, etc? Probably not. This will help you!
a.
It shows DX spots received from Logger32.
b.
It shows reference number and different backcolor for IOTA, RDA, WWFF
and DME award in column “Plus”
It is not easy to populate reference number while reading comment. There are
many patterns you type reference number. This is not 100%, however I think 80%
will be OK.
c.
It shows IOTA accepted status in column “A” (Y: accepted, N: not
accepted, empty: not added in IOTA database)
You must download your myqsos.csv and copy it in CheckSpotPlus folder to use
this feature.
d.
It shows “not valid for DXCC” as “X” in “X” column.
e.
Column “Comment” can be hidden.
f.
Each column width can be adjusted and restored at re-start.
CheckSpot is useful to
check how the callsign you are interested has been spotted. (Freq ? Mode ? and
Time ?)
It works ONLY together with Logger32 (after ver 3.35.0)
1) It receives DX spot adif from Logger32 when Logger32 displays DX spot in
DXSpot window.
2) It saves received adif in CheckSpot.txt which is created in the same folder
as CheckSpot.exe. (Append mode)
3) You can select save mode. (after ver2.5.2)
a. All: All spots received are saved in CheckSpot.txt
b. Only spots with highlighted color: Only highlighted color spots (may be your
interested spots) are saved.
c. Only spots with specified callsigns: Only sots with specified callsigns are
saved. You can specify any callsigns, HK0NA, 3D2YA, A35AY etc etc.
Specified callsigns are saved in CheckSpotCall.txt in the same folder as
CheckSpot.exe.
4) If you put a specific callsign in callsign box (e.g. T32C, YJ0VK, OJ0X etc)
then it shows matched data in the table reading CheckSpot.txt.
5) This table is refreshed when it receives DX spot adif which has a exactly
matched callsign as one entered in callsign box.
note: It does not refresh if you put callsign with wild card !.
6) Each line is back-colored with same color as in Logger32 DXSpot window.
7) Left-clicking any spot in the table transfers callsign in Logbook Entry
window and changes Radio Freq/Mode.
8) Aux table is provided.
FreqPad+ ver1.2
FreqPad+ ver 1.2 is fully
revised. It works only together with Logger32. It is mainly for Short Wave
Radio listening, however is for chcking net frequency, IOTA frequecy etc.
General features.....
a.
Your own frequecy list is displayed. If you click
any of them the radio is tuned to this frequency/mode.
b.
Radio is tuned by 10Hz, 100Hz, 1KHz, 5KHz, 10KHz,
100KHz or 1MHz step.
SummaryIOTAMini ver2.53
It supports
“DXCC matches one IOTA” status (ClubLog confirmation)
1) It reads downloaded
"myqsos.csv" and show ALL IOTA stats summary.
2) It reads exported adif and show Worked IOTA summary.
SummaryMini ver4.6.1
In this version KH5/K is in the deleted list.
SummayMini
ver4.5.0 reads Logbook ADIF exported by Logger32 and simply shows following
Table and Chart by all operators or each operator.
Chart may not work at all with Windows 7 , 8 and 10 system. This happens
when VB run-time files has not been installed properly in the system.
Mschart20.ocx
will be attached in the package. This may fix the problem. Please email me if
you are interested. I will send you program for your test.
1) QSOs/Band/Mode
2) QSOs/Band/Mode Chart
3) QSOs/Band/Continent Table
4) QSOs/Band/Continents Chart.
5) Award table Total number
worked/confirmed for DXCC, DXCC Challenge, WAC, WAZ, IOTA and USA-CA
6) Summary by selected operator
7) Summary by selected year. This is a new feature in this version.