Prepared for Mario K2ZD Feb.19.2019
(edited Mar.2019)
This is how my screen looks like after initial setup in Options /Macros/ etc. I'll back to this later.
Will skip similar things from WSJT, the only difference is at first sight, one can switch between long display (used for FT8) and single display known from WSJT. It's easy to do by clicking on 2D sign in upper right corner of the screen.
Of course any MSHV need to be tweaked to line up with radio audio levels and operator preferences, so if needed display can be tuned to get proper contrast and brightness. Two sliders below “TUNE DISPLAY” – right side of screen will help.
Additionally I have different waterfall speed set to 6 or 7 sometimes – this is only operator preference. I just like it this way.
Similar as in WSJT, we need to set “Sync Def” parameter which is in my case -1 – same as -30 in WSJT.
There’s no difference if we set -1 or -30 in WSJT, it’s just decoder parameter to skip sync count. So -1 here will do the job.
Other screen parameters should be obvious, let’s go to “Settings”.
If we look in MSHV folder ( assume it’s installed according with Installer hint – best in other partition than C:\) We will find few files/folders containing vital information letting us to tweak the program behaviour without annoying false decodes.
Let’s dig deeper inside “Settings” folder.
In my case it’s located in E:\MSHV\Settings
Files with name starting ms_xxxx are setup files in text format, even if they have different extensions. No reason to change anything inside so let’s go to our target folder “database” - here E:\MSHV\settings\database
Starting from first file:
msbcn_db.dbbn contains beacon information – we can skip it
msloc_db contains calls and qra locator for known (all HF & VHF) stations. But in my opinion quite obsolete, note there’s no W7GJ in it, or other 6m hams. But if You add any station in main MSHV window, this station along with qra locator will be added here at the bottom of file. Almost the same as in WSJT. This file is used as HF & VHF calls database.
msloc_db_mshv_original – it’s the main copy of above file without changes.
mstn_db contains dx cluster calls and addresses used in spotting stations you are hearing – psk reporter spotting feature, same as in WSJT-X or JTDX.
msloc_db_jt65_deep_search this is the file of our main interest. In my case this file is EMPTY.
You might ask why? Well, to be exact my file contains ONLY callsigns which were added by me before EME QSO, when listened to anyone, or prior known coming DXpedition. Decoding algorithm used by WSJT and similar software sometimes get fooled by invisible birdies, noises etc. Additionally MSHV is equipped with feature called “AP” decoding = nothing more than “A priori” partial guessing commonly used in VHF communication via aircraft scatter, troposcatter and other paths with heavy Doppler. Removing all calls from the file will prevent You to see false decodes with callsigns never heard on 6m, but known form HF or other VHF lists. I can’t see any logical reason to keep 1000 calls mostly not active, silent keys or HF’ers while digging the space for CP/W7GJ or VK3DUT callsign. Actually in my WSJT 9.7 which is the best version IMO, these calls are removed as well. The only “cons” is You will have to add your QSO partner manually at first QSO attempt to see Astro data etc.. If You need to reinstall program, simply copy the file and overwrite after reinstallation with your calls in there.
This is shortly all we need to do, here so back to the main window - “Decode” tab.
My usual settings,
additionally You can play with “Aggressive levels of JT65” but this need
further investigation – depending on local noise, birdies and using previously
mentioned “deep search database” file. My settings are:
Decoder aggressive level = 7 and Deep search level = 75.
Decoder aggressive level = 7 and Deep search level = 75.
Do
not tick the AP feature for FT8/JT65 J - this
will flood your screen with false decodes crap.
As You can see I am
using BW palette – two reasons – first, human eye is more sensitive to find
even weakest white spot on black pattern, second reason, it looks the same as
WSJT.
That’s all for a start, I think.
My setup now is WSJT9.7 with moon data files from WSJT 10 and MSHV in background as second program without PTT. During V84SAA dxp both WSJT9.7 and MSHV were used with 3rd WSJT10 in the background.
My setup now is WSJT9.7 with moon data files from WSJT 10 and MSHV in background as second program without PTT. During V84SAA dxp both WSJT9.7 and MSHV were used with 3rd WSJT10 in the background.
Both WSJT performed very good, MSHV gave 1-2 decode less on SH, but
for me old good WSJT 9.7 was real killer.
