Program | version | Released date | Note |
---|---|---|---|
CheckCall | 7.08 | 2022/9/20 | |
Lookup4CNTY | 1.03 | 2023/1/25 | |
LookupMaster | 1.15 | 2023/11/15 | |
ModeConverter | 1.01 | 2023/9/25 | |
SummaryV2 | 2.04 | 2022/7/20 | |
SummaryBandMode | 1.12 | 2023/9/25 | |
SummaryThisYear | 2.05 | 2023/11/30 | New option "Show top 10 QSO/DXCC this year statistics" added under "option" menu. |
SummaryIOTA | 2.63 | 2019/6/6 | |
UDP decoder | 1.04 | 2019/8/4 |
When callsign is populated in Logbook entry window then it will check whether matched callsign are listed in the text file or not. If it finds matched callsign then data are displayed. If it does not then "not found" is displayed.
You can send data to one of user fields in Logbook entry window. Check "Enable to transfer data to Logger32 User_1/2/3 field" in the menu. Click "Field to transfer" to select field you send.
Drag mouse to select text and release mouse button. Selected text is sent to Logbook entry window. In this sample, User5 field is configured for USER_1 and USER_1 is selected in CheckCall.
This is dedicated for users who are challenging USACA award and works for QSO only with KH6, KL7, or W.
Callsign lookup using QRZ XML or HamQTH ADIF service. It send State and County data to Logbook entry window. (You need to subscribe QRZ XML service if you want to use. HamQTH ADIF service is free.)
Check if he/she is eQSL user or not. It send text “eQSL yyyy-mm-dd” to COMMENT field or USER_3 field in Logbook entry window. (yyyy-mm-dd is the last date when user uploaded log to eQSL)
Check if his/her county is new or not. It send “new county” if it is not worked, or “not confirmed” if it is not confirmed yet to QSLMSG field, USER_1 field or USER_2 field in Logbook entry window. You may play audio alert. Lookup4Cnty read exported ADIF automatically when it runs.
LookupMaster support QRZxml, HamQTHxml, HamQTHadif, HamCall, QRZRUxml and QRZCQxml. It only works together with Logger32. You can use either of them by selecting from the menu.
It supports CheckCall. Select proper text file you want to use. Text file should be placed in the same folder as LookupMaster.exe.
CheckCall status appears only if "Enable CheckCall" is checked.
ModeConverter replace "<Mode:4>
This is revised version of previous Summary.
SummaryV2 shows worked number in selected year and mode in main form. If you prefer you can see various all time charts and all time award summary.
SummaryV2 need to read Logbook ADIF exported by Logger32. When you run SummaryV2 for the first time, you are prompted to select the Logbook ADIF.
Download SummaryV2.zip, unzip. Place SummaryV2.exe anywhere you like.
This is simple summary utility which shows QSOs by Band/Mode and DXCC/WAZ/WAS worked/confirmed by Band/Mode. (Confirmd by QSL+LoTW only)
SummaryBandMode need to read Logbook ADIF exported by Logger32. Download SummaryBandMode.zip, unzip. Place SummaryBandMode.exe anywhere you like.
This small utility shows summary by Mode/Month of this year with various charts. Default this year is current year. You may select any year. You are asked to select logbook adi file when you first run updated SummaryThisYear. When you want to change logbook adi file then you need close/open SummaryThisYear.
You should place Prefix.csv in the same folder as SummaryThisYear.exe.
You must select the file path for myqsos.csv and Logbook adif exported by Logger32 when you run SummaryIOTA at first time. Click File in the Menu bar. myqsos.csv can be downloaded at IOTA page.
This is a utility which decode UDP message distributed by JTDX/WSJT-X and display decoded message, DT graph and dB graph. It receives UDP message at UDP port from Logger32 RPTR UDP port or JTDX/WSJT-X UDP port directly.
CheckCallPartial ver2.01
CheckCNTY ver1.03
CheckFriend ver1.0
Clock ver2.01
ClubLogUpload ver4.14
LookupEQSL ver1.0
ViewAppDataDirectory ver1.0
WorkedConfirmedSummay ver1.03
yourRado ver1.04
1. How to run as administrator
a. Right click on abcXYZ.exe.
b. Click Property.
c. Select Compatibility tab.
d. Check "Run this program as administrator"
e. Click "OK"
2. How to configure as one of utility program in Logger32
a. Click Tools
b. Click Utility program setup.
c. Configure menu item and utility program path.
d. This utility program can be run from Utilities menu.
3. Does utility program work in this case?
<Run Windows as local user>
In the case that utility run from Logger32 utility menu,
Run Logger32 as administrator, Run utility as administrator ---> OK
Run Logger32 as administrator, Run utility as NOT administrator ---> OK
Run Logger32 as NOT administrator, Run utility as NOT administrator ---> OK
Run Logger32 as NOT administrator, Run utility as administrator ---> NOT work
In the case that utility run directly,
Run Logger32 as administrator, Run utility as administrator ---> OK
Run Logger32 as administrator, Run utility as NOT administrator ---> NOT work
Run Logger32 as NOT administrator, Run utility as NOT administrator---> OK
Run Logger32 as NOT administrator, Run utility as administrator ---> NOT work
<Run Windows as Administrator>
In the case that utility run from Logger32 utility menu,
Run Logger32 as administrator, Run utility as administrator ---> OK
Run Logger32 as administrator, Run utility as NOT administrator ---> OK
Run Logger32 as NOT administrator, Run utility as NOT administrator ---> OK
Run Logger32 as NOT administrator, Run utility as administrator ---> OK
In the case that utility run directly,
Run Logger32 as administrator, Run utility as administrator ---> OK
Run Logger32 as administrator, Run utility as NOT administrator ---> OK
Run Logger32 as NOT administrator, Run utility as NOT administrator ---> OK
Run Logger32 as NOT administrator, Run utility as administrator ---> OK
It is suggested that Logger32.exe (and Logger32autoinstaller.exe/autoinstaller.exe) should be run as "Run as administrator.
WYSIWYG HTML Editor