last updated 2016/5/25
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
Tips to use utlities
a. There is no menu bar in some utilities. Right click on the window to show menu.
b. I recommend you to setup a utility as one of utility programs in Logger32.
c. 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)
d. 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.
e. 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.
In this version icon is showed in task bar.
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.
Bug fixed. (run-time error when QSO is logged)
This is a utility which upload a QSO on ClubLog everytime you log in Logger32.Following ADIF fields are uploaded and ClubLog accept this.
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.
Changes in appearance in this version.
WinKey+ works only together with Logger32 and control WinKey device. It has been developped 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.
2. Following entry box are available.
a. Callsign box: type his callsign here.(mandatory)
b. Sent/Rcvd RST box: (efault 5NN
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. <LOG>: Logger32 log this QSO
4. Keyboard sending is avalable.
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>: enable/disable addtional message sending.
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 mesage if “Enable Return key ” option is checked.
Bug fixed. 2016/4/5
This is utility which shows “New”, “Not confirmed”, “Worked” and current total IOTAs workd in a small window.. This window is positioned anywhere you prefer.
<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.
Bug fixed. Space separated DupeCheck.txt file is used in this version instead of comma separetaed file.
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.
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
e. If you run multiple utilities (using external interface implemented in Logger32) and see any problem then let me know.
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
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.
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 tune 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.
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.
QRZ XML service is not free.
a. As requested, new option “Always stay there” added. It always stay there regardless “Lookup every time” option checked/unchecked.
HamQTH XML service is free, however you must be registered. This is much faster than their ADIF service.
a. Bug fixed
b. “Callsign not found” is displayed in info field.
c. “Transfer all selected fields on lookup” option added.
d. Changes in appearabce
HamQTH ADIF service is free, however you must be registered.
a. Bug fixed
b. QTH field removed, instead Addr field added.
c. For JA callsign State field (Primary administrative subdivision field) JA prefecture code is displayed if ZIP is in Addr field. This is useful for JA award hunters.
d. New option “Mailing address for label printing” added. When you open this window then all text are displayed in one line. You must insert CR/LF by hitting Enter key. Selected text are copied on Windows clipboard.
e. New option “Transfer all selected fields on lookup” added.
More changes for better looking in this version...2016/5/8
This has been fully re-coded version.
1) It works only together with Logger32.
2) It supports CSV and Space separated file.
3) Text font, forecolor and backcolor are selectable.Window’s size is adjusted aytomatically.
4) It supports two files at same time.
5) Right click to show menu.
Note: Transferring selected text to Logger32 feature is removed.
Text file should be like this…..
JA1NLX xxxx yyyy
The important things is that a) callsign must be the first string in the line and b) the character after callsign must be comma or space.
Previously used Text file can be used in this version.
If CheckCall does not work properly with your text file then yout text file may contain “LF” code. “LF” code is generated by UNIX OS. Windows OS generate “CRLF” code instead.
This is downsized version of CheckCall.
1) It works only together with Logger32.
2) It supports CSV and Space separated text file. One file at same time is allowed.
3) Text font, foredolor and backcolor are selectable. Window’s size is automatically adjusted. Window can be positioned anywhere manually.
4) Right click on the window to show Menu.
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!
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.
XLStoADIF ver1.0 under development
This is simple convertor, XLS to ADIF.
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.
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.
1) It reads downloaded
"myqsos.csv" and show ALL IOTA stats summary.
2) It reads exported adif and show Worked IOTA summary.
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.
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.