https://docs.win-test.com/w/api.php?action=feedcontributions&user=N6TV&feedformat=atomWin-Test Wiki - User contributions [en]2024-03-28T08:40:39ZUser contributionsMediaWiki 1.35.0https://docs.win-test.com/w/index.php?title=FAQ:Problems_Registering_and_Running&diff=4828FAQ:Problems Registering and Running2020-05-21T15:03:55Z<p>N6TV: /* I requested a new registration key but I never received an email with the key */ Added talktalk.net per GM4UYZ</p>
<hr />
<div>==How do I download, install, register and configure Win-Test on a new computer?==<br />
Click one of the following links to view or download the step-by-step illustrated '''Win-Test Installation, Registration and Configuration Guide''' (in PDF format) from http://download.win-test.com/registration/ :<br />
* [http://download.win-test.com/registration/wtreg_en.pdf wtreg_en.pdf] - English version by N6TV ([http://bit.ly/registerwt alternate server])<br />
* [http://download.win-test.com/registration/wtreg_fr.pdf wtreg_fr.pdf] - French version by F6FVY ([http://bit.ly/registerwt_f alternate version by XE1AY])<br />
* [http://download.win-test.com/registration/wtreg_es.pdf wtreg_es.pdf] - Spanish translation by LU5VV ([http://bit.ly/registerwt_ea alternate server]) <br />
* [http://download.win-test.com/registration/wtreg_it.pdf wtreg_it.pdf] - Italian translation by IK2NCJ ([http://bit.ly/registerwt_it alternate server])<br />
* [http://download.win-test.com/registration/wtreg_de.pdf wtreg_de.pdf] - German translation by DL1ELY ([http://bit.ly/registerwt_dl alternate server])<br />
* [http://download.win-test.com/registration/wtreg_pt.pdf wtreg_pt.pdf] - Portuguese translation by CU3HY ([http://bit.ly/registerwt_ct alternate server])<br />
<br />
Volunteers are needed to translate the guide to other languages. Please [http://www.qrz.com/db/n6tv contact N6TV] for the PowerPoint source file.<br />
<br />
==I selected Help | Register Software, but don't see my Computer Code==<br />
Chances are you are running the free "demo" version of Win-Test 4. This version cannot be registered. Download and install the official version from [http://download.win-test.com/v4/bin The Official Version 4 Download Site] (password required).<br />
<br />
==When I attempt to download Win-Test 4 the web site asks for a login and password. What should I use?==<br />
Your '''login''' is usually your '''callsign'''.<br />
<br />
Both your '''login''' and '''password''' are located in the "Win-Test Upgrade" or "Win-Test Purchase" email that you should have received when you purchased or upgraded to Version 4 (including free automatic upgrades). Look for an email:<br />
From: '''robot@win-test.com''' <br />
Subject: '''Win-Test V4 Free Upgrade'''<br />
-or-<br />
Subject: '''Achat de Win-Test - Win-Test purchase'''<br />
or similar.<br />
<br />
If you can't find the email with your unique web site password, you will need to send an email to F5HRY or F6FVY including your:<br />
* Account Number<br />
* Callsign<br />
* Email address used at time of purchase/upgrade<br />
* Your new email address if any<br />
<br />
==I requested a new registration key but I never received an email with the key==<br />
First, check your "Spam" folder, if any. Look for an email:<br />
From: '''robot@win-test.com''' <br />
Subject: '''Code de validation de Win-Test - Win-Test registration key'''<br />
<br />
Next, please note that registration keys are sent to the '''email address you provided when you first purchased Win-Test'''. If you no longer have access to this email address, you will need to send an email to F5HRY or F6FVY including your:<br />
* Account Number<br />
* Callsign<br />
* Old email address<br />
* New email address<br />
<br />
Due to security changes made by many email service providers (Google "DMARC policy"), registration keys sent by the Win-Test robot to '''the following email domains will be discarded automatically''', without any warning or notification:<br />
<br />
* aol.com<br />
* att.net<br />
* comcast.net<br />
* kolumbus.fi<br />
* prodigy.net<br />
* sbcglobal.net<br />
* talktalk.net<br />
* yahoo.com<br />
* ymail.com<br />
<br />
If your registered email address is at one of these domains, contact F5HRY to have your registered email address changed to another domain that still works, such as a Gmail account (gmail.com).<br />
<br />
==Win-Test always starts in "Demo" mode==<br />
Note: Unlike Win-Test Version 3, the [http://download.win-test.com/v4/demo/ free demo version] of Win-Test version 4, and the [http://download.win-test.com/v4/freeware/ free DXpedition version] cannot be registered or "activated"; the full version, which runs in demo mode until it registered via [[Menu:Help#Register_software| Help | Register Software]], is a different file. It must be downloaded from the [http://download.win-test.com/v4/bin password-protected download site] (see above if you don't have the password).<br />
<br />
Every PC has a unique 13-digit '''computer code''' (XXX-XXXX-XXXXXX) and every PC needs a unique 25-digit '''registration key''' (XXXXX-XXXXX-XXXXX-XXXXX-XXXXX).<br />
<br />
The registration keys for Win-Test Version 3 and Win-Test Version 4 are different. Even if you never purchased or installed Win-Test Version 4, you may have received a "free upgrade" email, especially if your purchased Win-Test Version 3 ''after'' '''June, 2008'''. If you received such an email, you are automatically going to receive only Version 4 registration keys when you request a key from the [http://www.win-test.com/rubrique.php3?id_rubrique=1870 Win-Test Registration Page]. Such keys ''do not work'' on Win-Test Version 3, though no error message is displayed. If you still require a Win-Test Version 3 registration key, you will need to request one by sending an email to F5HRY or F6FVY including your:<br />
* Account Number<br />
* Callsign<br />
* Computer Code<br />
Users who have not received a free upgrade to Version 4 and have not purchased an upgrade to Version 4 will still receive Version 3 registration keys from the web site.<br />
<br />
==My virus scanner reports that Win-Test is a virus!==<br />
This is probably a false alarm, especially if you downloaded and installed Win-Test from the [http://download.win-test.com Official Win-Test download site].<br />
<br />
Many virus scanners are especially prone to falsely reporting the "Artemis" or "Themida" virus in Win-Test Version 4, due to the way the executable is constructed.<br />
<br />
You can always upload '''wt.exe''' to [http://www.virustotal.com VirusTotal.com] to test it with multiple scanners. If less than 25% of the virus scanners report an issue, it is likely that Win-Test is ''not infected'', and you will need to add an "exception" to your antivirus software to allow Win-Test to run.</div>N6TVhttps://docs.win-test.com/w/index.php?title=Database_Files&diff=4746Database Files2018-11-10T18:12:08Z<p>N6TV: /* Downloading */ Added OKOMDX.DTB</p>
<hr />
<div>Win-Test has a feature called 'exchange guessing', which aims to fill in the exchange for a specific callsign by searching a database of known contesters' callsigns and their usual exchanges in a database file.<br />
<br />
These database files are available from http://download.win-test.com/databases. <br />
<br />
==Installing a Database file==<br />
<br />
===Downloading===<br />
Win-Test database files come in a binary format (.DTB). The Win-Test Team provides several of these files at http://download.win-test.com/databases. Look for the .DTB or .ZIP files (larger database files are collected in .ZIP archives).<br />
<br />
Here is a - possibly incomplete - list of the database files available and for which contests they are being used.<br />
<br />
AGCW_HNY.DTB AGCW Happy New Year contest<br />
ARI.DTB ARI 40/80 contest<br />
ARIDX.DTB ARI DX Contest (DX side)<br />
ARI_SEZIONI.DTB ARI Sezioni Contest<br />
ARRL_160_DX.DTB ARRL 160 m (contains US stations only)<br />
ARRL_160_USVE.DTB ARRL 160 m (contains US and DX stations)<br />
ARRL-ALL.DTB ARRL 10 m, CQWW 160 m contests, NA Sprint, NCCC Sprint<br />
ARRL-DX.DTB ARRL DX contest (use if you are inside US/VE)<br />
ARRL-USVE.DTB ARRL DX contest (use if you are outside US/VE), or ARRL RTTY Roundup<br />
CQIR.DTB CQIR contest<br />
CQWW.DTB CQWW DX, GACW and JIDX contests<br />
EUSPRINT.DTB EU Sprint contest<br />
EU_HF.DTB EU HF contest<br />
FOC_MARATHON.DTB FOC Marathon<br />
HADX.DTB HADX contest<br />
HELVETIA_DX.DTB Helvetia contest (DX side)<br />
HELVETIA_HB.DTB Helvetia contest (HB side)<br />
IARU_HF.DTB IARU HF contest<br />
IOTA.DTB IOTA contest (Islands activities)<br />
KCJ.DTB KCJ (Keyman's Club of Japan) contest<br />
KOS.DTB King Of Spain contest (from 2005)<br />
LZDX.DTB LZ DX contest<br />
OKOMDX.DTB OK OM DX contest<br />
PACC_DX.DTB PACC contest (DX side)<br />
PACC_PA.DTB PACC contest (PA side)<br />
REFHF.DTB REF HF contest<br />
RSGB.DTB RSGB 160 m and RSGB 21/28 (DX side) contests<br />
RSGB_CMW.DTB RSGB Commonwealth contest (BERU)<br />
SCC.DTB SCC RTTY Championship<br />
SPDX.DTB SP DX contest (DX side)<br />
STEW-PERRY.DTB Stew Perry contest<br />
UBADX.DTB UBA DX contest<br />
UBA_SPRING_DX.DTB UBA Spring contests (DX side)<br />
UBA_SPRING_ON.DTB UBA Spring contests (ON side)<br />
UFT_HF.DTB UFT HF contest<br />
WAG_DL.DTB WAG Contest (DL side), DARC Xmas Contest and DARC 10 M Contest<br />
WAG_DX.DTB WAG Contest (DX side)<br />
YODX.DTB YO DX Contest (DX side)<br />
<br />
For more details, please look at the [http://download.win-test.com/databases/READ_ME.TXT READ_ME.TXT] file in the database site directory.<br />
<br />
===Installing===<br />
After downloading, the corresponding .DTB files need to be copied to the Win-Test 3 installation directory or the Win-Test 4 application data directory. Zip files have to be unpacked before they can be used by Win-Test (which loads .DTB files only).<br />
<br />
For Win-Test version 4, save database files in:<br />
* Windows XP: '''C:\Documents and Settings\All Users\Application Data\Win-Test\databases\'''<br />
* Windows Vista and Windows 7: '''C:\ProgramData\Win-Test\databases\'''<br />
<br />
For Win-Test version 3, save database files in:<br />
* '''C:\Program Files\Win-Test\''' (or the Win-Test installation directory)<br />
<br />
See [[Check_Partial_and_Np1_Files#Location|Check Partial and Np1 Files - Location]] for more info. on how to view these often-hidden directories.<br />
<br />
Win-Test will then load automatically, at start-up, the corresponding database file (according to the actual selected contest), if those files are available.<br />
<br />
===Updating===<br />
Data in .DTB files may be updated with more recent exchange data from your own logs. Simply open a log file, or import a Cabrillo file for any particular contest, and select '''File | Update database''' from the Win-Test menu. To see which .DTB file was updated, select '''File | Explore | /databases directory''', View Details, and click "Date Modified" to sort the list by date. See also [[Database_Files#Brewing_your_own_Database_file|Brewing your own Database file]].<br />
<br />
{{wbox|Warning|If a contest-specific database file such as '''cqww.dtb''' is available, it will also be used by the Check Partial windows ''instead of'' '''master.scp''', which may not be wanted. To override this, use file name '''default.scp''' instead of '''master.scp'''.<br />
}}<br />
<br />
==Exchange Guessing==<br />
Other than the Super Check Partial and N+1 functions in Win-Test, exchange guessing helps the operator to "know what to expect" in the course of a contest QSO. Many contests come with a fixed exchange, be it a county or regional identifier, a QTH locator or a callsign specific identifier. This type of information can be "guessed" by the software so that the operator only has to confirm or correct this information.<br />
<br />
Please note that this feature is different from the Super Check Partial database (MASTER.SCP, DEFAULT.SCP, HF.DTB, VHF.DTB) and also different from the [[Menu:Windows#Extra_Information|Extra data files]] (XDT). See [[Check_Partial_and_Np1_Files|Check Partial and Np1_Files]].<br />
<br />
<br />
===Setting up Exchange Guessing in Win-Test=== <br />
After the database files have been installed, we need to activate the exchange guessing.<br />
<br />
To do this, select '''<tt>Tools | Data entry | Exchange guessing</tt>''' from the Top Menu. <br />
<br />
[[Image:ActivateExchangeGuessing.png|frame|center|Activate Exchange Guessing]]<br />
<br />
<br />
Three options are available:<br />
<br />
* <code>Pressing the spacebar</code> - this will fill in the exchange upon entering a callsign and hitting spacebar to move the entry cursor to the report field. This is the default setting.<br />
* <code>Automatically</code> - this will fill in the exchange as soon as you have entered the last character of the callsign and Win-Test has found an entry for it in the database file. Since this is a more resource intensive operation than the '<tt>Pressing the spacebar</tt>' option, it is not recommended for slow, or low-end, computers.<br />
* <code>After timeout</code> - this option will fill in the exchange after a certain amount of time has elapsed without changes to the callsign.<br />
<br />
<br />
Now, when you enter a callsign in the log entry area, the pre-guessed report will automatically come up. Also, the Check Partial window can show the same information, if it has been enabled by checking the '''<tt>Display exchange</tt>''' option in the context menu.<br />
<br />
<br />
<center><br />
{|<br />
|[[Image:CheckPartialContextMenu.gif|frame|center|The Check Partial Context menu allows you to see pre-guessed report information - this information is in brackets right to the callsign.]]<br />
|[[Image:CheckPartialUsedFilesList.gif|frame|center|Make sure you have loaded the correct version of the DTB file. This window is brought up via the context menu of the Check Partial window by selecting "Used files list...".]]<br />
|}<br />
</center><br />
<br />
Moreover, you can also verify which are the loaded database files through the '''<tt>Used files list...</tt>''' option, in the context menu (see above).<br />
<br />
<br />
Also the Band Map can show the guessed exchange information and highlight the stations accordingly, if the '''<tt>Display options | Exchange</tt>''' has been checked in its context menu.<br />
<br />
<center><br />
{|<br />
|[[Image:ExchangeGuessingBandmap.png|frame|center|Band map with Exchange Guessing enabled]]<br />
|[[Image:BandmapExcGuessEnable.png|frame|center|Exchange Guessing enabling context menu]]<br />
|}<br />
</center><br />
<br />
===A note about Exchange Guessing=== <br />
Exchange guessing is provided as a feature, that is, to assist the operator. It is NOT recommend to be used as a replacement for your ears! <tt>:)</tt>. You should always try to hear the exchange sent from the station you are working as there can be discrepancies in the database files.<br />
<br />
==Brewing your own Database file==<br />
'''Beware:''' This section is for the brave and experienced programmer and power user!<br />
<br />
Win-Test's .DTB files come in a binary format and - by default - are not editable with a simple tool like a text editor or a word processor. Having some programming expertise, you can still sucessfully create/replace an existing .DTB file with your own version. Remember, however, that you can not make Win-Test load a database it doesn't know.<br />
<br />
The file strutcture of the database files is straightforward and simple: As an example, take a look at the first bytes of the WAG_DL.DTB file used for looking up DOKs:<br />
<br />
00000000 44 41 30 41 41 00 00 00 00 00 00 00 00 00 52 31 DA0AA.........R1<br />
00000010 37 00 00 00 00 00 00 00 00 00 44 41 30 42 41 59 7.........DA0BAY<br />
00000020 00 00 00 00 00 00 00 00 42 30 36 00 00 00 00 00 ........B06.....<br />
00000030 00 00 00 00 44 41 30 43 42 00 00 00 00 00 00 00 ....DA0CB.......<br />
00000040 00 00 59 32 34 00 00 00 00 00 00 00 00 00 44 41 ..Y24.........DA<br />
00000050 30 43 57 00 00 00 00 00 00 00 00 00 55 32 33 00 0CW.........U23.<br />
00000060 00 00 00 00 00 00 00 00 44 41 30 44 49 47 00 00 ........DA0DIG..<br />
[...]<br />
<br />
From that hex dump we can see that the file consists of records of equal length of 26 bytes. The callsign is stored as a null-padded string in the first 14 bytes, the corresponding information (the DOK) is contained in the following 12 bytes, also null-padded. <br />
<br />
As another example, let's take a look at the file VHF.DTB, which contains stations active on the VHF/UHF bands and their corresponding QTH locators:<br />
<br />
00000000 34 4E 31 42 00 00 00 00 00 00 00 00 00 00 4B 4E 4N1B..........KN<br />
00000010 30 35 43 52 00 30 31 39 35 00 39 41 31 42 00 00 05CR.0195.9A1B..<br />
00000020 00 00 00 00 00 00 00 00 4A 4E 38 35 4A 58 00 30 ........JN85JX.0<br />
00000030 31 39 35 00 39 41 31 42 20 00 00 00 00 00 00 00 195.9A1B .......<br />
00000040 00 00 4A 4E 38 35 4F 56 00 30 31 39 35 00 39 41 ..JN85OV.0195.9A<br />
00000050 31 43 43 55 00 00 00 00 00 00 00 00 4A 4E 38 35 1CCU........JN85<br />
00000060 4C 49 00 30 31 39 35 00 39 41 31 43 45 51 00 00 LI.0195.9A1CEQ..<br />
[...]<br />
<br />
Here you can basically see the same file structure with the exception that the information field is actually split in two fields, one containing the information to display, and another one which contains information about the content itself - namely when this very piece of information was verified last - here "0195" meaning "January 1995".<br />
<br />
Using a programming environment like Perl, you can create a simple application that will do the job for you. Here is a sample. Please feel free to copy and adapt to your needs.<br />
<br />
The program processes a number of .db plaintext files (line 3). To work around duplicate information (e.g. one station is listed with several different locators), a space character is appended to the callsign (line 11). True duplicates are simply eliminated (line 7).<br />
Once the data collection process is finished, a new .dtb file is created (line 21) and - using Perl's pack() function, the records are created (line 23) and written to the file (line 24). The date information is left at 0195 for simplicity. This could certainly be elaborated to some detail.<br />
<br />
The final product has to be renamed to VHF.DTB before Win-Test will start using it.<br />
<br />
1 #!/usr/bin/perl<br />
2 <br />
3 foreach $f (<*.db>) {<br />
4 open(IN,$f);<br />
5 while(<IN>) {<br />
6 ($c,$q) = split;<br />
7 goto DONE if (length($c) < 1);<br />
8 if (defined($m{$c})) {<br />
9 goto DONE if ($m{$c} eq $q);<br />
10 while (defined($m{$c})) {<br />
11 $c .= ' ';<br />
12 goto DONE if ($m{$c} eq $q);<br />
13 }<br />
14 }<br />
15 $m{$c} = $q;<br />
16 DONE:<br />
17 }<br />
18 close(IN);<br />
19 }<br />
20 <br />
21 open(OUT,"> vhf_new.dtb");<br />
22 foreach (sort keys %m) {<br />
23 $r = pack("a14a6xa4x",$_,$m{$_},"0195");<br />
24 print OUT $r;<br />
25 }<br />
26 close(OUT);<br />
<br />
After all, if you can contribute updated .DTB files of reasonably good quality, the Win-Test team will be happy to incorporate them into their distribution which is available for free on the internet.<br />
<br />
==See also==<br />
Some other methods, to create/update DTB-Files, have been described by F6FVY in the WT Support forum (see: [http://lists.f5mzn.org/pipermail/support/2007-January/072867.html http://lists.f5mzn.org/pipermail/support/2007-January/072867.html]).</div>N6TVhttps://docs.win-test.com/w/index.php?title=Database_Files&diff=4745Database Files2018-11-10T01:43:49Z<p>N6TV: /* Downloading */ Added LZDX.DTB</p>
<hr />
<div>Win-Test has a feature called 'exchange guessing', which aims to fill in the exchange for a specific callsign by searching a database of known contesters' callsigns and their usual exchanges in a database file.<br />
<br />
These database files are available from http://download.win-test.com/databases. <br />
<br />
==Installing a Database file==<br />
<br />
===Downloading===<br />
Win-Test database files come in a binary format (.DTB). The Win-Test Team provides several of these files at http://download.win-test.com/databases. Look for the .DTB or .ZIP files (larger database files are collected in .ZIP archives).<br />
<br />
Here is a - possibly incomplete - list of the database files available and for which contests they are being used.<br />
<br />
AGCW_HNY.DTB AGCW Happy New Year contest<br />
ARI.DTB ARI 40/80 contest<br />
ARIDX.DTB ARI DX Contest (DX side)<br />
ARI_SEZIONI.DTB ARI Sezioni Contest<br />
ARRL_160_DX.DTB ARRL 160 m (contains US stations only)<br />
ARRL_160_USVE.DTB ARRL 160 m (contains US and DX stations)<br />
ARRL-ALL.DTB ARRL 10 m, CQWW 160 m contests, NA Sprint, NCCC Sprint<br />
ARRL-DX.DTB ARRL DX contest (use if you are inside US/VE)<br />
ARRL-USVE.DTB ARRL DX contest (use if you are outside US/VE), or ARRL RTTY Roundup<br />
CQIR.DTB CQIR contest<br />
CQWW.DTB CQWW DX, GACW and JIDX contests<br />
EUSPRINT.DTB EU Sprint contest<br />
EU_HF.DTB EU HF contest<br />
FOC_MARATHON.DTB FOC Marathon<br />
HADX.DTB HADX contest<br />
HELVETIA_DX.DTB Helvetia contest (DX side)<br />
HELVETIA_HB.DTB Helvetia contest (HB side)<br />
IARU_HF.DTB IARU HF contest<br />
IOTA.DTB IOTA contest (Islands activities)<br />
KCJ.DTB KCJ (Keyman's Club of Japan) contest<br />
KOS.DTB King Of Spain contest (from 2005)<br />
LZDX.DTB LZ DX contest<br />
PACC_DX.DTB PACC contest (DX side)<br />
PACC_PA.DTB PACC contest (PA side)<br />
REFHF.DTB REF HF contest<br />
RSGB.DTB RSGB 160 m and RSGB 21/28 (DX side) contests<br />
RSGB_CMW.DTB RSGB Commonwealth contest (BERU)<br />
SCC.DTB SCC RTTY Championship<br />
SPDX.DTB SP DX contest (DX side)<br />
STEW-PERRY.DTB Stew Perry contest<br />
UBADX.DTB UBA DX contest<br />
UBA_SPRING_DX.DTB UBA Spring contests (DX side)<br />
UBA_SPRING_ON.DTB UBA Spring contests (ON side)<br />
UFT_HF.DTB UFT HF contest<br />
WAG_DL.DTB WAG Contest (DL side), DARC Xmas Contest and DARC 10 M Contest<br />
WAG_DX.DTB WAG Contest (DX side)<br />
YODX.DTB YO DX Contest (DX side)<br />
<br />
For more details, please look at the [http://download.win-test.com/databases/READ_ME.TXT READ_ME.TXT] file in the database site directory.<br />
<br />
===Installing===<br />
After downloading, the corresponding .DTB files need to be copied to the Win-Test 3 installation directory or the Win-Test 4 application data directory. Zip files have to be unpacked before they can be used by Win-Test (which loads .DTB files only).<br />
<br />
For Win-Test version 4, save database files in:<br />
* Windows XP: '''C:\Documents and Settings\All Users\Application Data\Win-Test\databases\'''<br />
* Windows Vista and Windows 7: '''C:\ProgramData\Win-Test\databases\'''<br />
<br />
For Win-Test version 3, save database files in:<br />
* '''C:\Program Files\Win-Test\''' (or the Win-Test installation directory)<br />
<br />
See [[Check_Partial_and_Np1_Files#Location|Check Partial and Np1 Files - Location]] for more info. on how to view these often-hidden directories.<br />
<br />
Win-Test will then load automatically, at start-up, the corresponding database file (according to the actual selected contest), if those files are available.<br />
<br />
===Updating===<br />
Data in .DTB files may be updated with more recent exchange data from your own logs. Simply open a log file, or import a Cabrillo file for any particular contest, and select '''File | Update database''' from the Win-Test menu. To see which .DTB file was updated, select '''File | Explore | /databases directory''', View Details, and click "Date Modified" to sort the list by date. See also [[Database_Files#Brewing_your_own_Database_file|Brewing your own Database file]].<br />
<br />
{{wbox|Warning|If a contest-specific database file such as '''cqww.dtb''' is available, it will also be used by the Check Partial windows ''instead of'' '''master.scp''', which may not be wanted. To override this, use file name '''default.scp''' instead of '''master.scp'''.<br />
}}<br />
<br />
==Exchange Guessing==<br />
Other than the Super Check Partial and N+1 functions in Win-Test, exchange guessing helps the operator to "know what to expect" in the course of a contest QSO. Many contests come with a fixed exchange, be it a county or regional identifier, a QTH locator or a callsign specific identifier. This type of information can be "guessed" by the software so that the operator only has to confirm or correct this information.<br />
<br />
Please note that this feature is different from the Super Check Partial database (MASTER.SCP, DEFAULT.SCP, HF.DTB, VHF.DTB) and also different from the [[Menu:Windows#Extra_Information|Extra data files]] (XDT). See [[Check_Partial_and_Np1_Files|Check Partial and Np1_Files]].<br />
<br />
<br />
===Setting up Exchange Guessing in Win-Test=== <br />
After the database files have been installed, we need to activate the exchange guessing.<br />
<br />
To do this, select '''<tt>Tools | Data entry | Exchange guessing</tt>''' from the Top Menu. <br />
<br />
[[Image:ActivateExchangeGuessing.png|frame|center|Activate Exchange Guessing]]<br />
<br />
<br />
Three options are available:<br />
<br />
* <code>Pressing the spacebar</code> - this will fill in the exchange upon entering a callsign and hitting spacebar to move the entry cursor to the report field. This is the default setting.<br />
* <code>Automatically</code> - this will fill in the exchange as soon as you have entered the last character of the callsign and Win-Test has found an entry for it in the database file. Since this is a more resource intensive operation than the '<tt>Pressing the spacebar</tt>' option, it is not recommended for slow, or low-end, computers.<br />
* <code>After timeout</code> - this option will fill in the exchange after a certain amount of time has elapsed without changes to the callsign.<br />
<br />
<br />
Now, when you enter a callsign in the log entry area, the pre-guessed report will automatically come up. Also, the Check Partial window can show the same information, if it has been enabled by checking the '''<tt>Display exchange</tt>''' option in the context menu.<br />
<br />
<br />
<center><br />
{|<br />
|[[Image:CheckPartialContextMenu.gif|frame|center|The Check Partial Context menu allows you to see pre-guessed report information - this information is in brackets right to the callsign.]]<br />
|[[Image:CheckPartialUsedFilesList.gif|frame|center|Make sure you have loaded the correct version of the DTB file. This window is brought up via the context menu of the Check Partial window by selecting "Used files list...".]]<br />
|}<br />
</center><br />
<br />
Moreover, you can also verify which are the loaded database files through the '''<tt>Used files list...</tt>''' option, in the context menu (see above).<br />
<br />
<br />
Also the Band Map can show the guessed exchange information and highlight the stations accordingly, if the '''<tt>Display options | Exchange</tt>''' has been checked in its context menu.<br />
<br />
<center><br />
{|<br />
|[[Image:ExchangeGuessingBandmap.png|frame|center|Band map with Exchange Guessing enabled]]<br />
|[[Image:BandmapExcGuessEnable.png|frame|center|Exchange Guessing enabling context menu]]<br />
|}<br />
</center><br />
<br />
===A note about Exchange Guessing=== <br />
Exchange guessing is provided as a feature, that is, to assist the operator. It is NOT recommend to be used as a replacement for your ears! <tt>:)</tt>. You should always try to hear the exchange sent from the station you are working as there can be discrepancies in the database files.<br />
<br />
==Brewing your own Database file==<br />
'''Beware:''' This section is for the brave and experienced programmer and power user!<br />
<br />
Win-Test's .DTB files come in a binary format and - by default - are not editable with a simple tool like a text editor or a word processor. Having some programming expertise, you can still sucessfully create/replace an existing .DTB file with your own version. Remember, however, that you can not make Win-Test load a database it doesn't know.<br />
<br />
The file strutcture of the database files is straightforward and simple: As an example, take a look at the first bytes of the WAG_DL.DTB file used for looking up DOKs:<br />
<br />
00000000 44 41 30 41 41 00 00 00 00 00 00 00 00 00 52 31 DA0AA.........R1<br />
00000010 37 00 00 00 00 00 00 00 00 00 44 41 30 42 41 59 7.........DA0BAY<br />
00000020 00 00 00 00 00 00 00 00 42 30 36 00 00 00 00 00 ........B06.....<br />
00000030 00 00 00 00 44 41 30 43 42 00 00 00 00 00 00 00 ....DA0CB.......<br />
00000040 00 00 59 32 34 00 00 00 00 00 00 00 00 00 44 41 ..Y24.........DA<br />
00000050 30 43 57 00 00 00 00 00 00 00 00 00 55 32 33 00 0CW.........U23.<br />
00000060 00 00 00 00 00 00 00 00 44 41 30 44 49 47 00 00 ........DA0DIG..<br />
[...]<br />
<br />
From that hex dump we can see that the file consists of records of equal length of 26 bytes. The callsign is stored as a null-padded string in the first 14 bytes, the corresponding information (the DOK) is contained in the following 12 bytes, also null-padded. <br />
<br />
As another example, let's take a look at the file VHF.DTB, which contains stations active on the VHF/UHF bands and their corresponding QTH locators:<br />
<br />
00000000 34 4E 31 42 00 00 00 00 00 00 00 00 00 00 4B 4E 4N1B..........KN<br />
00000010 30 35 43 52 00 30 31 39 35 00 39 41 31 42 00 00 05CR.0195.9A1B..<br />
00000020 00 00 00 00 00 00 00 00 4A 4E 38 35 4A 58 00 30 ........JN85JX.0<br />
00000030 31 39 35 00 39 41 31 42 20 00 00 00 00 00 00 00 195.9A1B .......<br />
00000040 00 00 4A 4E 38 35 4F 56 00 30 31 39 35 00 39 41 ..JN85OV.0195.9A<br />
00000050 31 43 43 55 00 00 00 00 00 00 00 00 4A 4E 38 35 1CCU........JN85<br />
00000060 4C 49 00 30 31 39 35 00 39 41 31 43 45 51 00 00 LI.0195.9A1CEQ..<br />
[...]<br />
<br />
Here you can basically see the same file structure with the exception that the information field is actually split in two fields, one containing the information to display, and another one which contains information about the content itself - namely when this very piece of information was verified last - here "0195" meaning "January 1995".<br />
<br />
Using a programming environment like Perl, you can create a simple application that will do the job for you. Here is a sample. Please feel free to copy and adapt to your needs.<br />
<br />
The program processes a number of .db plaintext files (line 3). To work around duplicate information (e.g. one station is listed with several different locators), a space character is appended to the callsign (line 11). True duplicates are simply eliminated (line 7).<br />
Once the data collection process is finished, a new .dtb file is created (line 21) and - using Perl's pack() function, the records are created (line 23) and written to the file (line 24). The date information is left at 0195 for simplicity. This could certainly be elaborated to some detail.<br />
<br />
The final product has to be renamed to VHF.DTB before Win-Test will start using it.<br />
<br />
1 #!/usr/bin/perl<br />
2 <br />
3 foreach $f (<*.db>) {<br />
4 open(IN,$f);<br />
5 while(<IN>) {<br />
6 ($c,$q) = split;<br />
7 goto DONE if (length($c) < 1);<br />
8 if (defined($m{$c})) {<br />
9 goto DONE if ($m{$c} eq $q);<br />
10 while (defined($m{$c})) {<br />
11 $c .= ' ';<br />
12 goto DONE if ($m{$c} eq $q);<br />
13 }<br />
14 }<br />
15 $m{$c} = $q;<br />
16 DONE:<br />
17 }<br />
18 close(IN);<br />
19 }<br />
20 <br />
21 open(OUT,"> vhf_new.dtb");<br />
22 foreach (sort keys %m) {<br />
23 $r = pack("a14a6xa4x",$_,$m{$_},"0195");<br />
24 print OUT $r;<br />
25 }<br />
26 close(OUT);<br />
<br />
After all, if you can contribute updated .DTB files of reasonably good quality, the Win-Test team will be happy to incorporate them into their distribution which is available for free on the internet.<br />
<br />
==See also==<br />
Some other methods, to create/update DTB-Files, have been described by F6FVY in the WT Support forum (see: [http://lists.f5mzn.org/pipermail/support/2007-January/072867.html http://lists.f5mzn.org/pipermail/support/2007-January/072867.html]).</div>N6TVhttps://docs.win-test.com/w/index.php?title=Supported_rigs&diff=4744Supported rigs2018-11-06T21:12:20Z<p>N6TV: /* Kenwood */ Updated Kenwood serial port settings for TS-590SG, TS990S, TS=2000.</p>
<hr />
<div>Win-Test supports most rigs of today's amateur radio market. The radio or radios (if you use two) and their communication parameters are to be configured in the [[Menu:Options#Configure_interfaces...|Options Menu]] of Win-Test. Typically, you don't even have to guess specific baud rates or parity settings as Win-Test knows most of the default settings.<br />
<br />
==Kenwood==<br />
Virtually all Kenwood rigs are supported by Win-Test. They all use the same CAT command subset needed by Win-Test.<br />
<br />
{{wbox|Note|Additional function for modern Kenwood rigs is supported by LUA scripts by N6TV that you may download from https://bit.ly/wtscripts in file '''TS590scripts.zip'''.}}<br />
<br />
Older Kenwood rigs use by default:<br />
<br />
* Speed: 4800 baud<br />
* Data bits: 8<br />
* Parity: None<br />
* Stop bits: 2<br />
* DTR: Always OFF<br />
* RTS: Handshake<br />
<br />
Newer Kenwood rigs use by default:<br />
<br />
* Speed: 9600 baud<br />
* Data bits: 8<br />
* Parity: None<br />
* Stop bits: 1<br />
* DTR: Always OFF<br />
* RTS: Handshake<br />
<br />
Exception: TS-590S uses two stop bits ''only'' for 4800 baud. For all other baud rates, use only 1 stop bit.<br />
<br />
Models successfully tested:<br />
* TS-480SAT<br />
* TS-480HX<br />
* TS-590S, TS-590SG<br><br />
USB connection default is 115200 baud. COM port connection default is 9600 baud. Be sure to set RTS=Handshake. USB requires installation of the [http://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx Silicon Labs Virtual COM port (VCP) driver]. For VCP installation instructions, see [http://www.kenwood.com/i/products/info/amateur/vcp_e.html this page] on the Kenwood web site).<br />
* TS-850S<br />
* TS-930S PIEXX (Tnx FM5BH)<br />
* TS-940S<br />
* TS-950S<br />
* TS-570DGE<br />
* TS-990S &ndash; Same as TS-590S, see above.<br />
* TS-2000 &ndash; COM port default is 9600 baud, 1 stop bit, RTS=Handshake<br />
* (others are known to work, but not fully tested, e.g. TS-690, TS-450, TS-950SD, etc.)<br />
<br />
==Icom==<br />
<br />
Virtually, all Icom rigs are supported by Win-Test. They all use the same CAT command subset.<br />
<br />
{{wbox|Note|Additional function for modern Icom rigs is supported by LUA scripts by N6TV that you may download from https://bit.ly/wtscripts in file '''IcomScripts.zip'''.}} <br />
<br />
{{wbox|Note|The VFO-B windows with ICOM is almost always grey on older Icom radios [http://lists.f5mzn.org/pipermail/support/2007-February/073046.html].}}<br />
<br />
Best results for Icom radios are usually achieved by checking ''both'' the '''<tt>Don’t poll</tt>''' and the '''<tt>Use CI-V-Transceive</tt>''' options. The band map then moves very smoothly while turning the VFO. Another choice is to ''remove'' the check mark from both of these options.<br />
<br />
* IC-275<br>COM port set to 1200 baud, 8 data bits, no parity and 1 stop bit. Tnx MM0GPZ.<br>See also [[BestPractice3#Setting_up_an_Icom_IC-275H_with_the_microHAM_USB_Interface_IC|Setting up an Icom IC-275H with the microHAM USB Interface IC]].<br />
* IC-475<br />
* IC-703<br />
* IC-706<br>COM port set to 9600 baud, 8 data bits, no parity and 1 stop bit. Tnx F6IFY<br />
* IC-706 Mk II<br />
* IC-706 Mk II G<br />
* IC-718<br />
* IC-725<br />
* IC-728<br />
* IC-729<br />
* IC-735<br />
* IC-736<br />
* IC-737<br />
* IC-738<br />
* IC-746<br />
* IC-746 Pro<br />
* IC-751<br />
* IC-756<br />
* IC-756 Pro<br />
* IC-756 Pro II<br />
* IC-756 Pro III<br />
* IC-761<br />
* IC-765<br />
* IC-775 (or IC 775 DSP)<br>COM port set to 1200 baud, 8 data bits, no parity and 1 stop bit. Tnx EA3IN. (also succesfully tested up to 9600 baud. I2WIJ)<br />
* IC-781<br />
* IC-910<br />
* IC-970<br />
* IC-1275<br />
* IC-7000<br />
* IC-7100<br />
* IC-7200<br />
* IC-7300<br />
* IC-7400 - not listed, but you may select IC-746 Pro, which uses the same hex address: 66h<br />
* IC-7410<br />
* IC-7600<br />
* IC-7610<br />
* IC-7700<br />
* IC-7800<br />
* IC-7850<br />
* IC-7851<br />
* IC-9100<br />
<br />
===Other Icom radios===<br />
* Icom generic: This setting can be used to connect an Icom rig not listed. You need to set the Icom rig's address (found in the rig manual) in the wt.ini file in the [Interfaces] section. Please see [[WT.INI#Generic_ICOM_radio|WT.INI]] for more details.<br />
* IC-728<br>Use the Icom generic setting with hex address 38h and set COM port to 1200 baud, 8 data bits, no parity, 1 stop bit. Tnx VK6NU<br />
* IC-746 PRO<br>In fact, the IC 7400 (below) is the European version of the IC 746 PRO. It uses the same hex address and should work with the same settings. Tnx F8CRH<br />
* IC-910H<br>Use the Icom generic setting with hex address 60h and set COM port to 4800 baud, 8 data bits, no parity, 1 stop bit. Works on all 3 bands (2m, 70 and 23 cm). Tnx F6BEE<br />
* IC-7400<br>Use the Icom generic setting with hex address 66h and set COM port to 9600 baud (also successfully tested with 1200 and 19200 baud and TRX set accordingly), 8 data bits, no parity, 2 stop bits. Tnx F8CRH<br />
<br />
==Yaesu==<br />
<br />
{{wbox|Note|Additional function for modern Yaesu rigs is supported by LUA scripts by N6TV that you may download from https://bit.ly/wtscripts in file '''YaesuScripts.zip'''.}} <br />
<br />
* FT-100<br />
* FT-450<br />
* FT-757GX II<br />
* FT-817<br />
* FT-847<br />
* FT-857<br />
* FT-891<br />
* FT-897<br />
* FT-900<br />
* FT-920<br />
* FT-950<br />
* FT-990<br>COM port set to 4800 bauds, 8 data bits, no parity, no flow control and 2 stop bits.<br>For DTR and RTS, see FT-1000D below. Tnx F6GOX, NX5M.<br />
* FT-991<br>Use the Yaesu USB driver. See screen shots of recommended menu settings well-documented by HB9AMO at http://www.hb9amo.net/wt-ft991.php <br />
* FT-1000D<br>COM port set to 4800 bauds, 8 data bits, no parity, no flow control and 2 stop bits.<br>When using a powered CAT interface such as the Yaesu FIF-232C CAT interface box and CT-62 cable, set DTR and RTS to '''Always OFF'''.<br>When using a "passive" (not powered) interface cable such as the [http://k1nu.home.comcast.net/~k1nu/k1nu/Products/control.html K1NU CAT Control Cable], set DTR to '''Always OFF''', RTS to '''Always ON'''. Tnx F5FLN, NX5M, NQ4I.<br />
* FT-1000MP (including Mark V)<br>COM port set to 4800 bauds, 8 data bits, no parity, no flow control and 2 stop bits. Tnx FM5BH and F8CRH.<br />
* FT-2000<br />
* FTdx-1200<br />
* FTdx-3000<br />
* FTdx-5000<br />
* FTdx-9000<br />
<br />
{{wbox|Note|Sub-VFO programming from within the band map is available for the FT-1000MP, FT-2000 and FTDdx-9000 only}}.<br />
<br />
==Ten-Tec==<br />
<br />
* Jupiter<br />
* Orion (aka Orion I)<br />
* Orion II<br />
* Omni VI<br>Use the Icom generic setting, with 04h hex address, and set COM port to 9600 baud (can be modified in TRX if needed), 8 data bits, no parity, 1 stop bit. Tnx F6IFY<br />
* Omni VII<br />
<br />
<br />
{{wbox|Note|Sub-VFO programming from within the band map is available for the Orion only.}}<br />
<br />
==Elecraft==<br />
<br />
{{wbox|Note|Additional function for Elecraft rigs is supported by LUA scripts by N6TV that you may download from https://bit.ly/wtscripts in file '''K3scripts.zip''', '''KX3Scripts.zip''', and '''P3scripts.zip'''.}} <br />
<br />
* Elecraft K2<br />
* Elecraft K3<br />
* Elecraft K3S<br />
* Elecraft KX3<br />
<br />
==Others==<br />
* FlexRadio SDR-1000<br />
* Flex 6300 and others - Set radio type to '''Kenwood''', and select the virtual COM port listed in SmartSDR CAT for rig control and virtual WinKey.<br />
* [http://dxatlas.com/omnirig/ OmniRig] - Setting radio type to OmniRig will allow the radio's COM port to be shared with other applications such as [http://winrad.org/ Winrad] and [http://www.hdsdr.de/ HDSDR].</div>N6TVhttps://docs.win-test.com/w/index.php?title=Menu:Operating&diff=4743Menu:Operating2018-07-01T22:37:34Z<p>N6TV: /* The second footswitch binds to the secondary radio */ Note that footswitch option only works for EZMaster.</p>
<hr />
<div><big><big>Menu:Operating</big></big><br />
<!-- Adopted to Stylesheet DL6RAI --><br />
<br />
The following controls are only available if <code>Technique | SO2R</code> or <code>Technique | Advanced SO2R</code> are checked. They are specific to SO2R operation. For more information on SO2R, please see [[Running_a_contest|Running a Contest]].<br />
<br />
==Listen to the primary radio==<br />
Shortcut: <tt>'''[AltGr-A]'''</tt> or <tt>'''[Ctrl-Alt-A]'''</tt>.<br />
This switches the headphones to the primary radio.<br />
<br />
==Listen to the secondary radio/headphone toggle==<br />
Shortcut: <tt>'''[AltGr-T]'''</tt> or <tt>'''[Ctrl-Alt-T]'''</tt>.<br />
This switches the headphones to the secondary radio.<br />
<br />
==Listen to the secondary radio during transmit/headphone latch==<br />
Shortcut: <tt>'''[AltGr-L]'''</tt> or <tt>'''[Ctrl-Alt-L]'''</tt>.<br />
This option automatically switches the headphones to the secondary radio on transmit.<br />
<br />
==Listen both radio/headphone split==<br />
Shortcut: <tt>'''[AltGr-S]'''</tt> or <tt>'''[Ctrl-Alt-S]'''</tt>.<br />
Switches to both radios (left radio on the left headphone, right radio on the right headphone).<br />
<br />
==Revert to automatic control==<br />
Shortcut: <tt>'''[AltGr-R]'''</tt> or <tt>'''[Ctrl-Alt-R]'''</tt>.<br />
Restores automatic control.<br />
<br />
==Technique==<br />
Here you can choose the operating technique: <br />
* SO1R / MultiOp<br />
* SO2R<br />
* Advanced SO2R<br />
This menu entry enables/disables the above mentioned listening functions.<br />
<br />
==Modify the scenarios==<br />
Shortcut: in the [[Menu:Windows#Secondary_Radio|Secondary Radio Window]], just ''double-click'' on the scenario ''name''.<br />
<br />
Here you can configure the SO2R "scenarios," which define how pressing a function key will affect headphone audio for an SO2R operator, in both Run and S&P modes.<br />
<br />
[[Image:Scenarios.PNG|center|frame|Modify the SO2R scenarios]]<br />
<br />
See [[SO2R/Advanced_SO2R#Setting_up_scenarios|SO2R/Advanced SO2R/Setting up scenarios]] for more information.<br />
<br />
==Shift binds to the secondary radio==<br />
When checked, the ['''<tt>Shift</tt>'''] key can be pressed to bind the keyboard input focus to the secondary radio window.<br />
<br />
See [[SO2R/Shift_binds_second_radio|SO2R/Shift binds second radio]] for important keyboard mapping considerations before selecting this option.<br />
<br />
When a binding key is used, the color background of the QSO area is changed.<br />
<br />
==Caps Lock binds to the secondary radio==<br />
When checked, the ['''<tt>Caps Lock</tt>'''] key can be pressed to bind the keyboard input focus to the secondary radio window.<br />
<br />
See [[SO2R/Caps_Lock_bind_to_the_secondary_radio|SO2R/Caps Lock binds to the secondary radio]] for more information.<br />
<br />
When a binding key is used, the color background of the QSO area is changed.<br />
<br />
==The second footswitch binds to the secondary radio==<br />
When checked, the second footswitch can be pushed to bind the keyboard focus to the secondary radio window. This option is only supported for the EZMaster SO2R controller.<br />
<br />
[[Menus|Back to Menus]]</div>N6TVhttps://docs.win-test.com/w/index.php?title=Supported_rigs&diff=4742Supported rigs2018-04-01T22:20:34Z<p>N6TV: /* Others */ Add Flex</p>
<hr />
<div>Win-Test supports most rigs of today's amateur radio market. The radio or radios (if you use two) and their communication parameters are to be configured in the [[Menu:Options#Configure_interfaces...|Options Menu]] of Win-Test. Typically, you don't even have to guess specific baud rates or parity settings as Win-Test knows most of the default settings.<br />
<br />
==Kenwood==<br />
Virtually all Kenwood rigs are supported by Win-Test. They all use the same CAT command subset needed by Win-Test.<br />
<br />
{{wbox|Note|Additional function for modern Kenwood rigs is supported by LUA scripts by N6TV that you may download from https://bit.ly/wtscripts in file '''TS590scripts.zip'''.}}<br />
<br />
Kenwood rigs use by default:<br />
<br />
* Speed: 4800 Bauds<br />
* Data bits: 8<br />
* Parity: None<br />
* Stop bits: 2<br />
<br />
Exception: TS-590S uses two stop bits ''only'' for 4800 baud. For all other baud rates, use only 1 stop bit.<br />
<br />
Models successfully tested:<br />
* TS-480SAT<br />
* TS-480HX<br />
* TS-590S, TS-590SG<br><br />
USB connection only; the serial port may not work. See [http://lists.f5mzn.org/pipermail/support/2011-July/081291.html Reflector post by RA3AUU]. USB requires installation of the [http://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx Silicon Labs Virtual COM port (VCP) driver]. For VCP installation instructions, see [http://www.kenwood.com/i/products/info/amateur/vcp_e.html this page] on the Kenwood web site).<br />
* TS-850S<br />
* TS-930S PIEXX (Tnx FM5BH)<br />
* TS-940S<br />
* TS-950S<br />
* TS-570DGE<br />
* TS-990S<br />
* TS-2000<br />
* (others are known to work, but not fully tested, e.g. TS-690, TS-450, TS-950SD, etc.)<br />
<br />
==Icom==<br />
<br />
Virtually, all Icom rigs are supported by Win-Test. They all use the same CAT command subset.<br />
<br />
{{wbox|Note|Additional function for modern Icom rigs is supported by LUA scripts by N6TV that you may download from https://bit.ly/wtscripts in file '''IcomScripts.zip'''.}} <br />
<br />
{{wbox|Note|The VFO-B windows with ICOM is almost always grey on older Icom radios [http://lists.f5mzn.org/pipermail/support/2007-February/073046.html].}}<br />
<br />
Best results for Icom radios are usually achieved by checking ''both'' the '''<tt>Don’t poll</tt>''' and the '''<tt>Use CI-V-Transceive</tt>''' options. The band map then moves very smoothly while turning the VFO. Another choice is to ''remove'' the check mark from both of these options.<br />
<br />
* IC-275<br>COM port set to 1200 baud, 8 data bits, no parity and 1 stop bit. Tnx MM0GPZ.<br>See also [[BestPractice3#Setting_up_an_Icom_IC-275H_with_the_microHAM_USB_Interface_IC|Setting up an Icom IC-275H with the microHAM USB Interface IC]].<br />
* IC-475<br />
* IC-703<br />
* IC-706<br>COM port set to 9600 baud, 8 data bits, no parity and 1 stop bit. Tnx F6IFY<br />
* IC-706 Mk II<br />
* IC-706 Mk II G<br />
* IC-718<br />
* IC-725<br />
* IC-728<br />
* IC-729<br />
* IC-735<br />
* IC-736<br />
* IC-737<br />
* IC-738<br />
* IC-746<br />
* IC-746 Pro<br />
* IC-751<br />
* IC-756<br />
* IC-756 Pro<br />
* IC-756 Pro II<br />
* IC-756 Pro III<br />
* IC-761<br />
* IC-765<br />
* IC-775 (or IC 775 DSP)<br>COM port set to 1200 baud, 8 data bits, no parity and 1 stop bit. Tnx EA3IN. (also succesfully tested up to 9600 baud. I2WIJ)<br />
* IC-781<br />
* IC-910<br />
* IC-970<br />
* IC-1275<br />
* IC-7000<br />
* IC-7100<br />
* IC-7200<br />
* IC-7300<br />
* IC-7400 - not listed, but you may select IC-746 Pro, which uses the same hex address: 66h<br />
* IC-7410<br />
* IC-7600<br />
* IC-7610<br />
* IC-7700<br />
* IC-7800<br />
* IC-7850<br />
* IC-7851<br />
* IC-9100<br />
<br />
===Other Icom radios===<br />
* Icom generic: This setting can be used to connect an Icom rig not listed. You need to set the Icom rig's address (found in the rig manual) in the wt.ini file in the [Interfaces] section. Please see [[WT.INI#Generic_ICOM_radio|WT.INI]] for more details.<br />
* IC-728<br>Use the Icom generic setting with hex address 38h and set COM port to 1200 baud, 8 data bits, no parity, 1 stop bit. Tnx VK6NU<br />
* IC-746 PRO<br>In fact, the IC 7400 (below) is the European version of the IC 746 PRO. It uses the same hex address and should work with the same settings. Tnx F8CRH<br />
* IC-910H<br>Use the Icom generic setting with hex address 60h and set COM port to 4800 baud, 8 data bits, no parity, 1 stop bit. Works on all 3 bands (2m, 70 and 23 cm). Tnx F6BEE<br />
* IC-7400<br>Use the Icom generic setting with hex address 66h and set COM port to 9600 baud (also successfully tested with 1200 and 19200 baud and TRX set accordingly), 8 data bits, no parity, 2 stop bits. Tnx F8CRH<br />
<br />
==Yaesu==<br />
<br />
{{wbox|Note|Additional function for modern Yaesu rigs is supported by LUA scripts by N6TV that you may download from https://bit.ly/wtscripts in file '''YaesuScripts.zip'''.}} <br />
<br />
* FT-100<br />
* FT-450<br />
* FT-757GX II<br />
* FT-817<br />
* FT-847<br />
* FT-857<br />
* FT-891<br />
* FT-897<br />
* FT-900<br />
* FT-920<br />
* FT-950<br />
* FT-990<br>COM port set to 4800 bauds, 8 data bits, no parity, no flow control and 2 stop bits.<br>For DTR and RTS, see FT-1000D below. Tnx F6GOX, NX5M.<br />
* FT-991<br>Use the Yaesu USB driver. See screen shots of recommended menu settings well-documented by HB9AMO at http://www.hb9amo.net/wt-ft991.php <br />
* FT-1000D<br>COM port set to 4800 bauds, 8 data bits, no parity, no flow control and 2 stop bits.<br>When using a powered CAT interface such as the Yaesu FIF-232C CAT interface box and CT-62 cable, set DTR and RTS to '''Always OFF'''.<br>When using a "passive" (not powered) interface cable such as the [http://k1nu.home.comcast.net/~k1nu/k1nu/Products/control.html K1NU CAT Control Cable], set DTR to '''Always OFF''', RTS to '''Always ON'''. Tnx F5FLN, NX5M, NQ4I.<br />
* FT-1000MP (including Mark V)<br>COM port set to 4800 bauds, 8 data bits, no parity, no flow control and 2 stop bits. Tnx FM5BH and F8CRH.<br />
* FT-2000<br />
* FTdx-1200<br />
* FTdx-3000<br />
* FTdx-5000<br />
* FTdx-9000<br />
<br />
{{wbox|Note|Sub-VFO programming from within the band map is available for the FT-1000MP, FT-2000 and FTDdx-9000 only}}.<br />
<br />
==Ten-Tec==<br />
<br />
* Jupiter<br />
* Orion (aka Orion I)<br />
* Orion II<br />
* Omni VI<br>Use the Icom generic setting, with 04h hex address, and set COM port to 9600 baud (can be modified in TRX if needed), 8 data bits, no parity, 1 stop bit. Tnx F6IFY<br />
* Omni VII<br />
<br />
<br />
{{wbox|Note|Sub-VFO programming from within the band map is available for the Orion only.}}<br />
<br />
==Elecraft==<br />
<br />
{{wbox|Note|Additional function for Elecraft rigs is supported by LUA scripts by N6TV that you may download from https://bit.ly/wtscripts in file '''K3scripts.zip''', '''KX3Scripts.zip''', and '''P3scripts.zip'''.}} <br />
<br />
* Elecraft K2<br />
* Elecraft K3<br />
* Elecraft K3S<br />
* Elecraft KX3<br />
<br />
==Others==<br />
* FlexRadio SDR-1000<br />
* Flex 6300 and others - Set radio type to '''Kenwood''', and select the virtual COM port listed in SmartSDR CAT for rig control and virtual WinKey.<br />
* [http://dxatlas.com/omnirig/ OmniRig] - Setting radio type to OmniRig will allow the radio's COM port to be shared with other applications such as [http://winrad.org/ Winrad] and [http://www.hdsdr.de/ HDSDR].</div>N6TVhttps://docs.win-test.com/w/index.php?title=Supported_rigs&diff=4741Supported rigs2018-03-30T23:59:59Z<p>N6TV: /* Icom */ Added IC-7400 (tnx HB9FAP), and IC-7610 (new in 4.28)</p>
<hr />
<div>Win-Test supports most rigs of today's amateur radio market. The radio or radios (if you use two) and their communication parameters are to be configured in the [[Menu:Options#Configure_interfaces...|Options Menu]] of Win-Test. Typically, you don't even have to guess specific baud rates or parity settings as Win-Test knows most of the default settings.<br />
<br />
==Kenwood==<br />
Virtually all Kenwood rigs are supported by Win-Test. They all use the same CAT command subset needed by Win-Test.<br />
<br />
{{wbox|Note|Additional function for modern Kenwood rigs is supported by LUA scripts by N6TV that you may download from https://bit.ly/wtscripts in file '''TS590scripts.zip'''.}}<br />
<br />
Kenwood rigs use by default:<br />
<br />
* Speed: 4800 Bauds<br />
* Data bits: 8<br />
* Parity: None<br />
* Stop bits: 2<br />
<br />
Exception: TS-590S uses two stop bits ''only'' for 4800 baud. For all other baud rates, use only 1 stop bit.<br />
<br />
Models successfully tested:<br />
* TS-480SAT<br />
* TS-480HX<br />
* TS-590S, TS-590SG<br><br />
USB connection only; the serial port may not work. See [http://lists.f5mzn.org/pipermail/support/2011-July/081291.html Reflector post by RA3AUU]. USB requires installation of the [http://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx Silicon Labs Virtual COM port (VCP) driver]. For VCP installation instructions, see [http://www.kenwood.com/i/products/info/amateur/vcp_e.html this page] on the Kenwood web site).<br />
* TS-850S<br />
* TS-930S PIEXX (Tnx FM5BH)<br />
* TS-940S<br />
* TS-950S<br />
* TS-570DGE<br />
* TS-990S<br />
* TS-2000<br />
* (others are known to work, but not fully tested, e.g. TS-690, TS-450, TS-950SD, etc.)<br />
<br />
==Icom==<br />
<br />
Virtually, all Icom rigs are supported by Win-Test. They all use the same CAT command subset.<br />
<br />
{{wbox|Note|Additional function for modern Icom rigs is supported by LUA scripts by N6TV that you may download from https://bit.ly/wtscripts in file '''IcomScripts.zip'''.}} <br />
<br />
{{wbox|Note|The VFO-B windows with ICOM is almost always grey on older Icom radios [http://lists.f5mzn.org/pipermail/support/2007-February/073046.html].}}<br />
<br />
Best results for Icom radios are usually achieved by checking ''both'' the '''<tt>Don’t poll</tt>''' and the '''<tt>Use CI-V-Transceive</tt>''' options. The band map then moves very smoothly while turning the VFO. Another choice is to ''remove'' the check mark from both of these options.<br />
<br />
* IC-275<br>COM port set to 1200 baud, 8 data bits, no parity and 1 stop bit. Tnx MM0GPZ.<br>See also [[BestPractice3#Setting_up_an_Icom_IC-275H_with_the_microHAM_USB_Interface_IC|Setting up an Icom IC-275H with the microHAM USB Interface IC]].<br />
* IC-475<br />
* IC-703<br />
* IC-706<br>COM port set to 9600 baud, 8 data bits, no parity and 1 stop bit. Tnx F6IFY<br />
* IC-706 Mk II<br />
* IC-706 Mk II G<br />
* IC-718<br />
* IC-725<br />
* IC-728<br />
* IC-729<br />
* IC-735<br />
* IC-736<br />
* IC-737<br />
* IC-738<br />
* IC-746<br />
* IC-746 Pro<br />
* IC-751<br />
* IC-756<br />
* IC-756 Pro<br />
* IC-756 Pro II<br />
* IC-756 Pro III<br />
* IC-761<br />
* IC-765<br />
* IC-775 (or IC 775 DSP)<br>COM port set to 1200 baud, 8 data bits, no parity and 1 stop bit. Tnx EA3IN. (also succesfully tested up to 9600 baud. I2WIJ)<br />
* IC-781<br />
* IC-910<br />
* IC-970<br />
* IC-1275<br />
* IC-7000<br />
* IC-7100<br />
* IC-7200<br />
* IC-7300<br />
* IC-7400 - not listed, but you may select IC-746 Pro, which uses the same hex address: 66h<br />
* IC-7410<br />
* IC-7600<br />
* IC-7610<br />
* IC-7700<br />
* IC-7800<br />
* IC-7850<br />
* IC-7851<br />
* IC-9100<br />
<br />
===Other Icom radios===<br />
* Icom generic: This setting can be used to connect an Icom rig not listed. You need to set the Icom rig's address (found in the rig manual) in the wt.ini file in the [Interfaces] section. Please see [[WT.INI#Generic_ICOM_radio|WT.INI]] for more details.<br />
* IC-728<br>Use the Icom generic setting with hex address 38h and set COM port to 1200 baud, 8 data bits, no parity, 1 stop bit. Tnx VK6NU<br />
* IC-746 PRO<br>In fact, the IC 7400 (below) is the European version of the IC 746 PRO. It uses the same hex address and should work with the same settings. Tnx F8CRH<br />
* IC-910H<br>Use the Icom generic setting with hex address 60h and set COM port to 4800 baud, 8 data bits, no parity, 1 stop bit. Works on all 3 bands (2m, 70 and 23 cm). Tnx F6BEE<br />
* IC-7400<br>Use the Icom generic setting with hex address 66h and set COM port to 9600 baud (also successfully tested with 1200 and 19200 baud and TRX set accordingly), 8 data bits, no parity, 2 stop bits. Tnx F8CRH<br />
<br />
==Yaesu==<br />
<br />
{{wbox|Note|Additional function for modern Yaesu rigs is supported by LUA scripts by N6TV that you may download from https://bit.ly/wtscripts in file '''YaesuScripts.zip'''.}} <br />
<br />
* FT-100<br />
* FT-450<br />
* FT-757GX II<br />
* FT-817<br />
* FT-847<br />
* FT-857<br />
* FT-891<br />
* FT-897<br />
* FT-900<br />
* FT-920<br />
* FT-950<br />
* FT-990<br>COM port set to 4800 bauds, 8 data bits, no parity, no flow control and 2 stop bits.<br>For DTR and RTS, see FT-1000D below. Tnx F6GOX, NX5M.<br />
* FT-991<br>Use the Yaesu USB driver. See screen shots of recommended menu settings well-documented by HB9AMO at http://www.hb9amo.net/wt-ft991.php <br />
* FT-1000D<br>COM port set to 4800 bauds, 8 data bits, no parity, no flow control and 2 stop bits.<br>When using a powered CAT interface such as the Yaesu FIF-232C CAT interface box and CT-62 cable, set DTR and RTS to '''Always OFF'''.<br>When using a "passive" (not powered) interface cable such as the [http://k1nu.home.comcast.net/~k1nu/k1nu/Products/control.html K1NU CAT Control Cable], set DTR to '''Always OFF''', RTS to '''Always ON'''. Tnx F5FLN, NX5M, NQ4I.<br />
* FT-1000MP (including Mark V)<br>COM port set to 4800 bauds, 8 data bits, no parity, no flow control and 2 stop bits. Tnx FM5BH and F8CRH.<br />
* FT-2000<br />
* FTdx-1200<br />
* FTdx-3000<br />
* FTdx-5000<br />
* FTdx-9000<br />
<br />
{{wbox|Note|Sub-VFO programming from within the band map is available for the FT-1000MP, FT-2000 and FTDdx-9000 only}}.<br />
<br />
==Ten-Tec==<br />
<br />
* Jupiter<br />
* Orion (aka Orion I)<br />
* Orion II<br />
* Omni VI<br>Use the Icom generic setting, with 04h hex address, and set COM port to 9600 baud (can be modified in TRX if needed), 8 data bits, no parity, 1 stop bit. Tnx F6IFY<br />
* Omni VII<br />
<br />
<br />
{{wbox|Note|Sub-VFO programming from within the band map is available for the Orion only.}}<br />
<br />
==Elecraft==<br />
<br />
{{wbox|Note|Additional function for Elecraft rigs is supported by LUA scripts by N6TV that you may download from https://bit.ly/wtscripts in file '''K3scripts.zip''', '''KX3Scripts.zip''', and '''P3scripts.zip'''.}} <br />
<br />
* Elecraft K2<br />
* Elecraft K3<br />
* Elecraft K3S<br />
* Elecraft KX3<br />
<br />
==Others==<br />
* FlexRadio SDR-1000<br />
* [http://dxatlas.com/omnirig/ OmniRig] - Setting radio type to OmniRig will allow the radio's COM port to be shared with other applications such as [http://winrad.org/ Winrad] and [http://www.hdsdr.de/ HDSDR].</div>N6TVhttps://docs.win-test.com/w/index.php?title=Check_Partial_and_Np1_Files&diff=4740Check Partial and Np1 Files2018-01-30T07:01:15Z<p>N6TV: /* Files names list */ Added NA Sprint Super Check Partial file (NA_SPRINT.DTA)</p>
<hr />
<div>The [[Menu:Windows#Check_Partials|Check Partials Window]] displays callsigns whenever 2 or 3 characters are entered in the callsign field, based on the contents of certain files.<br />
==Check Partial and N+1 Files==<br />
<br />
Pre version 3.3.5, Win-Test used a native database format for Check Partials and N+1 checking, called the<br />
DTB database file format which was mostly associated with a specific contest.<br />
<br />
With that version, both the SCP and the DTA formats are additionally supported by Win-Test.<br />
<br />
<ul><br />
<li> Win-Test accepts SCP plain text files. SCP stands for Super Check Partial. The structure of the file is simple, one callsign per line, no ordering required. SCP is the preferred format for Win-Test.<br />
<br />
<li> Secondly CT compatible binary DTA files (MASTER.DTA) are supported by Win-Test. These files are usually available before the major contest. <br />
<ul><br />
<li> [http://www.supercheckpartial.com http://www.supercheckpartial.com] this is the main reference site for SCP and DTA files. Fully updated.<br />
<li> [http://www.qsl.net/k1tr/master.htm http://www.qsl.net/k1tr/master.htm] this site maintain a MASTER.DTA file for North American VHF/UHF Contests<br />
<li> [http://www.datomonline.com/suppfiles.html http://www.datomonline.com/suppfiles.html] this site was used by NA users (actually outdated!)<br><br />
<p> </p><br />
</ul><br />
<br />
<li> Finally, DTB files are supported for backward compatibility.<br />
</ul><br />
<br />
Win-Test now accepts specialized Check Partial files, separated by band and by mode for any given contest. <br />
This should improve log accuracy and QSO rate. To get more details on how to name these files so that they can be found by Win-Test in the right situation, see [[Check_Partial_and_Np1_Files#Naming_Convention|Naming Convention]] below, or read [http://download.win-test.com/files/checkPartial/%23_READ_ME_%23.TXT http://download.win-test.com/files/checkPartial/READ_ME.TXT].<br />
<br />
{{wbox|Note|If a contest-specific check partial file or database (.dtb) file is present in the Win-Test directory shown below, it will be used as the default file for partial and N+1 checks ''instead of'' '''MASTER.SCP'''. To override this, use the file name '''DEFAULT.SCP''' or '''DEFAULT.DTA''' instead of '''MASTER.SCP''' or '''MASTER.DTA'''.}}<br />
===Location===<br />
These files must be located in the appropriate directory:<br />
<br />
For Win-Test version 4, save check partial files in:<br />
* Windows XP: <tt>'''C:\Documents and Settings\All Users\Application Data\Win-Test\databases\'''</tt><br />
* Windows Vista or Windows 7: <tt>'''C:\ProgramData\Win-Test\databases\'''</tt><br />
{{wbox|Note|When renaming or saving '''MASTER.SCP''', '''DEFAULT.SCP''' etc. make sure that the file name is not '''MASTER.SCP.SCP''', or '''DEFAULT.SCP.txt''', which will prevent these files from loading. See instructions below explaining how to make the full file name visible in Windows.}}<br />
<br />
For Win-Test version 3:<br />
* <tt>'''C:\Program Files\Win-Test\'''</tt> (or the Win-Test installation directory)<br />
<br />
====Viewing hidden files and folders====<br />
By default, Windows hides some of these directories, making them invisible. You can view them via [[Menu:File_open#Explore|File | Explore | /databases directory]], or even better, make all hidden folders visible, and make all file extensions (.SCP, .DTA, etc.) visible too.<br />
<br />
To display hidden files and folders and extensions:<br />
=====Windows XP=====<br />
# Open '''Folder Options''' in the Windows '''Control Panel'''. <br />
## Click '''Start''', and then click '''Control Panel'''.<br />
## Double-click '''Folder Options'''.<br />
# On the '''View''' tab, under '''Hidden files and folders''', click '''Show hidden files and folders'''.<br />
# ''Remove'' the check mark next to '''Hide extensions for known file types'''.<br />
# Click '''OK'''.<br />
<br />
=====Windows Vista and Windows 7=====<br />
# Open Folder Options by clicking the '''Start''' button, clicking '''Control Panel''', clicking '''Appearance and Personalization''', and then clicking '''Folder Options'''.<br />
# Click the '''View''' tab.<br />
# Under '''Advanced settings''', click '''Show hidden files, folders, and drives'''.<br />
# ''Remove'' the check mark next to '''Hide extensions for known file types'''.<br />
# Click '''OK'''.<br />
<br />
===Naming Convention===<br />
Win-Test allows the usage of 3 different formats :<br />
<br />
* <b>SCP</b> files : Plain textual - One capitalized callsign per line. No ordering required.<br />
* <b>DTA</b> files : Binary CT format - You can use MEdit (http://dxatlas.com/MEdit/Files/MEdit.zip) to work on these files<br />
* <b>DTB</b> files : Binary WT format - Kept for backward compatibility.<br />
<br />
Note that the "compact" DTA format offered by MEdit is accepted by WT.<br />
<br />
The preferred format is SCP.<br />
<br />
From version 3.3.0, WT allows one file per band, mode and contest.<br />
<br />
This means that one can build specialized files for a specific contest, and even for one band and/or mode in that contest.<br />
<br />
The naming convention of the check partial files are (where * stands for SCP or DTA or DTB) :<br />
<br />
* <tt>fileName_band_mode.*</tt><br />
* <tt>fileName_mode.*</tt><br />
* <tt>fileName_band.*</tt><br />
* <tt>fileName.*</tt><br />
<br />
===Search order===<br />
The first matching file is used for check partial searches<br />
<br />
# <tt>DEFAULT.*</tt><br />
# <tt>fileName_band_mode.*</tt><br />
# <tt>fileName_mode.*</tt><br />
# <tt>fileName_band.*</tt><br />
# <tt>fileName.*</tt><br />
# <tt>MASTER.*</tt><br />
# <tt>HF.*</tt> or <tt>VHF.*</tt><br />
<br />
If more than one type of file exists with the same name, the search order is based on the file extension:<br />
# <tt>*.DTA</tt><br />
# <tt>*.SCP</tt><br />
# <tt>*.DTB</tt><br />
<br />
So if both MASTER.DTA and MASTER.SCP exist, but no other files, MASTER.DTA will be used.<br />
<br />
If Win-Test does not find a specialized file for the current contest, it will use the MASTER.* files, or if that is not found, the HF.* and VHF.* files.<br />
<br />
To see which file is actually being used, right click on the [[Menu:Windows#Check_Partials|Check Partials Window]] and select '''Used files list...''':<br />
<br />
[[Image:Check Partial Files List.PNG|frame|center|Right click on Check Partials window and select Used files list... to determine which file is being used for super check]]<br />
<br />
===Files names list===<br />
<br />
9KCC15 : 9K CC contest<br />
AGCW_HNY : AGCW Happy New Year contest<br />
AA_DX : All Asian contest - DX side<br />
AA_AA : All Asian contest - Asian side<br />
ARI_DX : ARI contest - DX side<br />
ARI_I : ARI contest - Italian side<br />
ARI_SEZIONI : ARI Sezioni contest<br />
ARRL_10_DX : ARRL 10m contest - DX side<br />
ARRL_10_USVE : ARRL 10m contest - K/VE side<br />
ARRL_160_DX : ARRL 160m contest - DX side<br />
ARRL_160_USVE : ARRL 160m contest - K/VE side<br />
ARRL_DX_DX : ARRL DX contest - DX side<br />
ARRL_DX_USVE : ARRL DX contest - K/VE side<br />
ARRL_FD : ARRL Field Day<br />
ARRL_SS : ARRL SweepStakes<br />
BALTIC : Baltic contest<br />
CIS : CIS contest<br />
CQM : CQ-M contest<br />
CQWW_160M : CQWW DX 160m contest<br />
CQWW : CQWW DX contest<br />
WPX : CQWW WPX contest<br />
CROATIAN : Croatian contest<br />
DARC_10 : DARC 10m contest<br />
DARC_XMAS : DARC X-Mas contest<br />
EU_HF : EU HF Championship<br />
EU_SPRINT : EU Sprint<br />
FOC_MARATHON : FOC Marathon<br />
GACW : GACW DX contest<br />
HADX : HA DX contest<br />
HELVETIA_DX : Helvatia contest (DX side)<br />
HELVETIA_HB : Helvetia contest (HB side)<br />
IARU_FD_R1 : IARU Field Day Rgn 1<br />
IARU_HF : IARU HF championships<br />
IOTA : IOTA contest<br />
JIDX_DX : JIDX contest (DX side)<br />
JIDX_JA : JIDX contest (JA side)<br />
KCJ : KCJ contest<br />
KCJ_160 : KCJ Top band contest<br />
KOS : King Of Spain contest<br />
LZ_DX : LZ DX contest<br />
LOTW : LOTW contest<br />
NA_SPRINT : North American Sprint<br />
NAQP : North American QSO Party<br />
NRAU_BALTIC : NRAU Baltic contest<br />
OC_DX_DX : Oceania DX contest (DX side)<br />
OC_DX_OC : Oceania DX contest (Oceania side)<br />
OKOM_DX_DX : OK/OM DX contest (DX side)<br />
OKOM_DX_OKOM : OK/OM DX contest (OK/OM side)<br />
PACC_DX : PACC contest (DX side)<br />
PACC_PA : PACC contest (PA side)<br />
TX_QP : TX QSO Party<br />
RAC : RAC Canaday Day and RAC Canada Winter contests<br />
RDAC_DX : RDA contest (DX side)<br />
RDAC_UA : RDA contest (Russian side)<br />
RDXC : Russian DX contest<br />
REF_HF_DX : REF HF (DX side)<br />
REF_HF_F : REF HF (F side)<br />
REF_160_DX : REF 160m (DX side)<br />
REF_160_F : REF 160m (F side)<br />
RSGB_1510_DX : RSGB 15/10 (DX side)<br />
RSGB_1510_UK : RSGB 15/10 (UK side)<br />
RSGB_160_DX : RSGB 160m (DX side)<br />
RSGB_160_UK : RSGB 160m (UK side)<br />
RSGB_80_CC : RSGB 80 CC contest<br />
RSGB_AFS : RSGB AFS<br />
RSGB_CMW : RSGB Commonwealth<br />
R_160_DX : Russian 160 (DX side)<br />
R_160_UA : Russian 160 (UA side)<br />
SAC_DX : SAC (DX side)<br />
SAC_SC : SAC (Scandinavian side)<br />
SP_DX_DX : SP DX contest (DX side)<br />
SP_DX_SP : SP DX contest (SP side)<br />
STEW_PERRY : Stew Perry Challenge<br />
TOEC : TOE contest<br />
UBA_DX : UBA DX contest<br />
UBA_SPRING_DX : UBA Spring (DX side)<br />
UBA_SPRING_ON : UBA Spring (ON side)<br />
UFT_HF : UFT HF contest<br />
UK_DX : Ukranian DX contest<br />
WAE_DX : WAE contest (DX side)<br />
WAE_EU : WAE contest (EU side)<br />
WAG_DX : WAG (DX side)<br />
WAG_DL : WAG (DL side)<br />
YO_DX_DX : YO DX contest (DX side)<br />
YO_DX_YO : YO DX contest (YO side)<br />
YU_DX : YU DX contest <br />
<br />
For example, if you want to use a specific ARRL DX (DX side) for 80m you must name it :<br />
<br />
ARRL_DX_DX_80.* (where * stands for SCP or DTA or DTB)</div>N6TVhttps://docs.win-test.com/w/index.php?title=FAQ:Problems_Registering_and_Running&diff=4739FAQ:Problems Registering and Running2017-08-03T06:05:16Z<p>N6TV: /* I requested a new registration key but I never received an email with the key */ Added prodigy.net (now provided by Yahoo)</p>
<hr />
<div>==How do I download, install, register and configure Win-Test on a new computer?==<br />
Click one of the following links to view or download the step-by-step illustrated '''Win-Test Installation, Registration and Configuration Guide''' (in PDF format) from http://download.win-test.com/registration/ :<br />
* [http://download.win-test.com/registration/wtreg_en.pdf wtreg_en.pdf] - English version by N6TV ([http://bit.ly/registerwt alternate server])<br />
* [http://download.win-test.com/registration/wtreg_fr.pdf wtreg_fr.pdf] - French version by F6FVY ([http://bit.ly/registerwt_f alternate version by XE1AY])<br />
* [http://download.win-test.com/registration/wtreg_es.pdf wtreg_es.pdf] - Spanish translation by LU5VV ([http://bit.ly/registerwt_ea alternate server]) <br />
* [http://download.win-test.com/registration/wtreg_it.pdf wtreg_it.pdf] - Italian translation by IK2NCJ ([http://bit.ly/registerwt_it alternate server])<br />
* [http://download.win-test.com/registration/wtreg_de.pdf wtreg_de.pdf] - German translation by DL1ELY ([http://bit.ly/registerwt_dl alternate server])<br />
* [http://download.win-test.com/registration/wtreg_pt.pdf wtreg_pt.pdf] - Portuguese translation by CU3HY ([http://bit.ly/registerwt_ct alternate server])<br />
<br />
Volunteers are needed to translate the guide to other languages. Please [http://www.qrz.com/db/n6tv contact N6TV] for the PowerPoint source file.<br />
<br />
==I selected Help | Register Software, but don't see my Computer Code==<br />
Chances are you are running the free "demo" version of Win-Test 4. This version cannot be registered. Download and install the official version from [http://download.win-test.com/v4/bin The Official Version 4 Download Site] (password required).<br />
<br />
==When I attempt to download Win-Test 4 the web site asks for a login and password. What should I use?==<br />
Your '''login''' is usually your '''callsign'''.<br />
<br />
Both your '''login''' and '''password''' are located in the "Win-Test Upgrade" or "Win-Test Purchase" email that you should have received when you purchased or upgraded to Version 4 (including free automatic upgrades). Look for an email:<br />
From: '''robot@win-test.com''' <br />
Subject: '''Win-Test V4 Free Upgrade'''<br />
-or-<br />
Subject: '''Achat de Win-Test - Win-Test purchase'''<br />
or similar.<br />
<br />
If you can't find the email with your unique web site password, you will need to send an email to F5HRY or F6FVY including your:<br />
* Account Number<br />
* Callsign<br />
* Email address used at time of purchase/upgrade<br />
* Your new email address if any<br />
<br />
==I requested a new registration key but I never received an email with the key==<br />
First, check your "Spam" folder, if any. Look for an email:<br />
From: '''robot@win-test.com''' <br />
Subject: '''Code de validation de Win-Test - Win-Test registration key'''<br />
<br />
Next, please note that registration keys are sent to the '''email address you provided when you first purchased Win-Test'''. If you no longer have access to this email address, you will need to send an email to F5HRY or F6FVY including your:<br />
* Account Number<br />
* Callsign<br />
* Old email address<br />
* New email address<br />
<br />
Due to security changes made by many email service providers (Google "DMARC policy"), registration keys sent by the Win-Test robot to '''the following email domains will be discarded automatically''', without any warning or notification:<br />
<br />
* aol.com<br />
* att.net<br />
* comcast.net<br />
* kolumbus.fi<br />
* prodigy.net<br />
* sbcglobal.net<br />
* yahoo.com<br />
* ymail.com<br />
<br />
If your registered email address is at one of these domains, contact F5HRY to have your registered email address changed to another domain that still works, such as a Gmail account (gmail.com).<br />
<br />
==Win-Test always starts in "Demo" mode==<br />
Note: Unlike Win-Test Version 3, the [http://download.win-test.com/v4/demo/ free demo version] of Win-Test version 4, and the [http://download.win-test.com/v4/freeware/ free DXpedition version] cannot be registered or "activated"; the full version, which runs in demo mode until it registered via [[Menu:Help#Register_software| Help | Register Software]], is a different file. It must be downloaded from the [http://download.win-test.com/v4/bin password-protected download site] (see above if you don't have the password).<br />
<br />
Every PC has a unique 13-digit '''computer code''' (XXX-XXXX-XXXXXX) and every PC needs a unique 25-digit '''registration key''' (XXXXX-XXXXX-XXXXX-XXXXX-XXXXX).<br />
<br />
The registration keys for Win-Test Version 3 and Win-Test Version 4 are different. Even if you never purchased or installed Win-Test Version 4, you may have received a "free upgrade" email, especially if your purchased Win-Test Version 3 ''after'' '''June, 2008'''. If you received such an email, you are automatically going to receive only Version 4 registration keys when you request a key from the [http://www.win-test.com/rubrique.php3?id_rubrique=1870 Win-Test Registration Page]. Such keys ''do not work'' on Win-Test Version 3, though no error message is displayed. If you still require a Win-Test Version 3 registration key, you will need to request one by sending an email to F5HRY or F6FVY including your:<br />
* Account Number<br />
* Callsign<br />
* Computer Code<br />
Users who have not received a free upgrade to Version 4 and have not purchased an upgrade to Version 4 will still receive Version 3 registration keys from the web site.<br />
<br />
==My virus scanner reports that Win-Test is a virus!==<br />
This is probably a false alarm, especially if you downloaded and installed Win-Test from the [http://download.win-test.com Official Win-Test download site].<br />
<br />
Many virus scanners are especially prone to falsely reporting the "Artemis" or "Themida" virus in Win-Test Version 4, due to the way the executable is constructed.<br />
<br />
You can always upload '''wt.exe''' to [http://www.virustotal.com VirusTotal.com] to test it with multiple scanners. If less than 25% of the virus scanners report an issue, it is likely that Win-Test is ''not infected'', and you will need to add an "exception" to your antivirus software to allow Win-Test to run.</div>N6TVhttps://docs.win-test.com/w/index.php?title=Supported_rigs&diff=4738Supported rigs2017-07-25T18:05:40Z<p>N6TV: /* Kenwood */ Added link to LUA scripts</p>
<hr />
<div>Win-Test supports most rigs of today's amateur radio market. The radio or radios (if you use two) and their communication parameters are to be configured in the [[Menu:Options#Configure_interfaces...|Options Menu]] of Win-Test. Typically, you don't even have to guess specific baud rates or parity settings as Win-Test knows most of the default settings.<br />
<br />
==Kenwood==<br />
Virtually all Kenwood rigs are supported by Win-Test. They all use the same CAT command subset needed by Win-Test.<br />
<br />
{{wbox|Note|Additional function for modern Kenwood rigs is supported by LUA scripts by N6TV that you may download from https://bit.ly/wtscripts in file '''TS590scripts.zip'''.}}<br />
<br />
Kenwood rigs use by default:<br />
<br />
* Speed: 4800 Bauds<br />
* Data bits: 8<br />
* Parity: None<br />
* Stop bits: 2<br />
<br />
Exception: TS-590S uses two stop bits ''only'' for 4800 baud. For all other baud rates, use only 1 stop bit.<br />
<br />
Models successfully tested:<br />
* TS-480SAT<br />
* TS-480HX<br />
* TS-590S, TS-590SG<br><br />
USB connection only; the serial port may not work. See [http://lists.f5mzn.org/pipermail/support/2011-July/081291.html Reflector post by RA3AUU]. USB requires installation of the [http://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx Silicon Labs Virtual COM port (VCP) driver]. For VCP installation instructions, see [http://www.kenwood.com/i/products/info/amateur/vcp_e.html this page] on the Kenwood web site).<br />
* TS-850S<br />
* TS-930S PIEXX (Tnx FM5BH)<br />
* TS-940S<br />
* TS-950S<br />
* TS-570DGE<br />
* TS-990S<br />
* TS-2000<br />
* (others are known to work, but not fully tested, e.g. TS-690, TS-450, TS-950SD, etc.)<br />
<br />
==Icom==<br />
<br />
Virtually, all Icom rigs are supported by Win-Test. They all use the same CAT command subset.<br />
<br />
{{wbox|Note|Additional function for modern Icom rigs is supported by LUA scripts by N6TV that you may download from https://bit.ly/wtscripts in file '''IcomScripts.zip'''.}} <br />
<br />
{{wbox|Note|The VFO-B windows with ICOM is almost always grey on older Icom radios [http://lists.f5mzn.org/pipermail/support/2007-February/073046.html].}}<br />
<br />
Best results for Icom radios are usually achieved by checking ''both'' the '''<tt>Don’t poll</tt>''' and the '''<tt>Use CI-V-Transceive</tt>''' options. The band map then moves very smoothly while turning the VFO. Another choice is to ''remove'' the check mark from both of these options.<br />
<br />
* IC-275<br>COM port set to 1200 baud, 8 data bits, no parity and 1 stop bit. Tnx MM0GPZ.<br>See also [[BestPractice3#Setting_up_an_Icom_IC-275H_with_the_microHAM_USB_Interface_IC|Setting up an Icom IC-275H with the microHAM USB Interface IC]].<br />
* IC-475<br />
* IC-703<br />
* IC-706<br>COM port set to 9600 baud, 8 data bits, no parity and 1 stop bit. Tnx F6IFY<br />
* IC-706 Mk II<br />
* IC-706 Mk II G<br />
* IC-718<br />
* IC-725<br />
* IC-728<br />
* IC-729<br />
* IC-735<br />
* IC-736<br />
* IC-737<br />
* IC-738<br />
* IC-746<br />
* IC-746 Pro<br />
* IC-751<br />
* IC-756<br />
* IC-756 Pro<br />
* IC-756 Pro II<br />
* IC-756 Pro III<br />
* IC-761<br />
* IC-765<br />
* IC-775 (or IC 775 DSP)<br>COM port set to 1200 baud, 8 data bits, no parity and 1 stop bit. Tnx EA3IN. (also succesfully tested up to 9600 baud. I2WIJ)<br />
* IC-781<br />
* IC-910<br />
* IC-970<br />
* IC-1275<br />
* IC-7000<br />
* IC-7100<br />
* IC-7200<br />
* IC-7300<br />
* IC-7410<br />
* IC-7600<br />
* IC-7700<br />
* IC-7800<br />
* IC-7850<br />
* IC-7851<br />
* IC-9100<br />
<br />
===Other Icom radios===<br />
* Icom generic: This setting can be used to connect an Icom rig not listed. You need to set the Icom rig's address (found in the rig manual) in the wt.ini file in the [Interfaces] section. Please see [[WT.INI#Generic_ICOM_radio|WT.INI]] for more details.<br />
* IC-728<br>Use the Icom generic setting with hex address 38h and set COM port to 1200 baud, 8 data bits, no parity, 1 stop bit. Tnx VK6NU<br />
* IC-746 PRO<br>In fact, the IC 7400 (below) is the European version of the IC 746 PRO. It uses the same hex address and should work with the same settings. Tnx F8CRH<br />
* IC-910H<br>Use the Icom generic setting with hex address 60h and set COM port to 4800 baud, 8 data bits, no parity, 1 stop bit. Works on all 3 bands (2m, 70 and 23 cm). Tnx F6BEE<br />
* IC-7400<br>Use the Icom generic setting with hex address 66h and set COM port to 9600 baud (also successfully tested with 1200 and 19200 baud and TRX set accordingly), 8 data bits, no parity, 2 stop bits. Tnx F8CRH<br />
<br />
==Yaesu==<br />
<br />
{{wbox|Note|Additional function for modern Yaesu rigs is supported by LUA scripts by N6TV that you may download from https://bit.ly/wtscripts in file '''YaesuScripts.zip'''.}} <br />
<br />
* FT-100<br />
* FT-450<br />
* FT-757GX II<br />
* FT-817<br />
* FT-847<br />
* FT-857<br />
* FT-891<br />
* FT-897<br />
* FT-900<br />
* FT-920<br />
* FT-950<br />
* FT-990<br>COM port set to 4800 bauds, 8 data bits, no parity, no flow control and 2 stop bits.<br>For DTR and RTS, see FT-1000D below. Tnx F6GOX, NX5M.<br />
* FT-991<br>Use the Yaesu USB driver. See screen shots of recommended menu settings well-documented by HB9AMO at http://www.hb9amo.net/wt-ft991.php <br />
* FT-1000D<br>COM port set to 4800 bauds, 8 data bits, no parity, no flow control and 2 stop bits.<br>When using a powered CAT interface such as the Yaesu FIF-232C CAT interface box and CT-62 cable, set DTR and RTS to '''Always OFF'''.<br>When using a "passive" (not powered) interface cable such as the [http://k1nu.home.comcast.net/~k1nu/k1nu/Products/control.html K1NU CAT Control Cable], set DTR to '''Always OFF''', RTS to '''Always ON'''. Tnx F5FLN, NX5M, NQ4I.<br />
* FT-1000MP (including Mark V)<br>COM port set to 4800 bauds, 8 data bits, no parity, no flow control and 2 stop bits. Tnx FM5BH and F8CRH.<br />
* FT-2000<br />
* FTdx-1200<br />
* FTdx-3000<br />
* FTdx-5000<br />
* FTdx-9000<br />
<br />
{{wbox|Note|Sub-VFO programming from within the band map is available for the FT-1000MP, FT-2000 and FTDdx-9000 only}}.<br />
<br />
==Ten-Tec==<br />
<br />
* Jupiter<br />
* Orion (aka Orion I)<br />
* Orion II<br />
* Omni VI<br>Use the Icom generic setting, with 04h hex address, and set COM port to 9600 baud (can be modified in TRX if needed), 8 data bits, no parity, 1 stop bit. Tnx F6IFY<br />
* Omni VII<br />
<br />
<br />
{{wbox|Note|Sub-VFO programming from within the band map is available for the Orion only.}}<br />
<br />
==Elecraft==<br />
<br />
{{wbox|Note|Additional function for Elecraft rigs is supported by LUA scripts by N6TV that you may download from https://bit.ly/wtscripts in file '''K3scripts.zip''', '''KX3Scripts.zip''', and '''P3scripts.zip'''.}} <br />
<br />
* Elecraft K2<br />
* Elecraft K3<br />
* Elecraft K3S<br />
* Elecraft KX3<br />
<br />
==Others==<br />
* FlexRadio SDR-1000<br />
* [http://dxatlas.com/omnirig/ OmniRig] - Setting radio type to OmniRig will allow the radio's COM port to be shared with other applications such as [http://winrad.org/ Winrad] and [http://www.hdsdr.de/ HDSDR].</div>N6TVhttps://docs.win-test.com/w/index.php?title=Supported_rigs&diff=4737Supported rigs2017-07-25T18:00:50Z<p>N6TV: /* Elecraft */ Added link to LUA scripts for Elecraft</p>
<hr />
<div>Win-Test supports most rigs of today's amateur radio market. The radio or radios (if you use two) and their communication parameters are to be configured in the [[Menu:Options#Configure_interfaces...|Options Menu]] of Win-Test. Typically, you don't even have to guess specific baud rates or parity settings as Win-Test knows most of the default settings.<br />
<br />
==Kenwood==<br />
Virtually all Kenwood rigs are supported by Win-Test. They all use the same CAT command subset needed by Win-Test.<br />
<br />
Kenwood rigs use by default:<br />
<br />
* Speed: 4800 Bauds<br />
* Data bits: 8<br />
* Parity: None<br />
* Stop bits: 2<br />
<br />
Exception: TS-590S uses two stop bits ''only'' for 4800 baud. For all other baud rates, use only 1 stop bit.<br />
<br />
Models successfully tested: <br />
* TS-850S<br />
* TS-930S PIEXX (Tnx FM5BH)<br />
* TS-940S<br />
* TS-950S<br />
* TS-570DGE<br />
* TS-590S -- USB connection only; the serial port may not work. See [http://lists.f5mzn.org/pipermail/support/2011-July/081291.html Reflector post by RA3AUU]. USB requires installation of the [http://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx Silicon Labs Virtual COM port (VCP) driver]. For VCP installation instructions, see [http://www.kenwood.com/i/products/info/amateur/vcp_e.html this page] on the Kenwood web site).<br />
* (others are known to work, but not fully tested, e.g. TS-690, TS-450, TS-950SD, TS-2000, etc.)<br />
<br />
==Icom==<br />
<br />
Virtually, all Icom rigs are supported by Win-Test. They all use the same CAT command subset.<br />
<br />
{{wbox|Note|Additional function for modern Icom rigs is supported by LUA scripts by N6TV that you may download from https://bit.ly/wtscripts in file '''IcomScripts.zip'''.}} <br />
<br />
{{wbox|Note|The VFO-B windows with ICOM is almost always grey on older Icom radios [http://lists.f5mzn.org/pipermail/support/2007-February/073046.html].}}<br />
<br />
Best results for Icom radios are usually achieved by checking ''both'' the '''<tt>Don’t poll</tt>''' and the '''<tt>Use CI-V-Transceive</tt>''' options. The band map then moves very smoothly while turning the VFO. Another choice is to ''remove'' the check mark from both of these options.<br />
<br />
* IC-275<br>COM port set to 1200 baud, 8 data bits, no parity and 1 stop bit. Tnx MM0GPZ.<br>See also [[BestPractice3#Setting_up_an_Icom_IC-275H_with_the_microHAM_USB_Interface_IC|Setting up an Icom IC-275H with the microHAM USB Interface IC]].<br />
* IC-475<br />
* IC-703<br />
* IC-706<br>COM port set to 9600 baud, 8 data bits, no parity and 1 stop bit. Tnx F6IFY<br />
* IC-706 Mk II<br />
* IC-706 Mk II G<br />
* IC-718<br />
* IC-725<br />
* IC-728<br />
* IC-729<br />
* IC-735<br />
* IC-736<br />
* IC-737<br />
* IC-738<br />
* IC-746<br />
* IC-746 Pro<br />
* IC-751<br />
* IC-756<br />
* IC-756 Pro<br />
* IC-756 Pro II<br />
* IC-756 Pro III<br />
* IC-761<br />
* IC-765<br />
* IC-775 (or IC 775 DSP)<br>COM port set to 1200 baud, 8 data bits, no parity and 1 stop bit. Tnx EA3IN. (also succesfully tested up to 9600 baud. I2WIJ)<br />
* IC-781<br />
* IC-910<br />
* IC-970<br />
* IC-1275<br />
* IC-7000<br />
* IC-7100<br />
* IC-7200<br />
* IC-7300<br />
* IC-7410<br />
* IC-7600<br />
* IC-7700<br />
* IC-7800<br />
* IC-7850<br />
* IC-7851<br />
* IC-9100<br />
<br />
===Other Icom radios===<br />
* Icom generic: This setting can be used to connect an Icom rig not listed. You need to set the Icom rig's address (found in the rig manual) in the wt.ini file in the [Interfaces] section. Please see [[WT.INI#Generic_ICOM_radio|WT.INI]] for more details.<br />
* IC-728<br>Use the Icom generic setting with hex address 38h and set COM port to 1200 baud, 8 data bits, no parity, 1 stop bit. Tnx VK6NU<br />
* IC-746 PRO<br>In fact, the IC 7400 (below) is the European version of the IC 746 PRO. It uses the same hex address and should work with the same settings. Tnx F8CRH<br />
* IC-910H<br>Use the Icom generic setting with hex address 60h and set COM port to 4800 baud, 8 data bits, no parity, 1 stop bit. Works on all 3 bands (2m, 70 and 23 cm). Tnx F6BEE<br />
* IC-7400<br>Use the Icom generic setting with hex address 66h and set COM port to 9600 baud (also successfully tested with 1200 and 19200 baud and TRX set accordingly), 8 data bits, no parity, 2 stop bits. Tnx F8CRH<br />
<br />
==Yaesu==<br />
<br />
{{wbox|Note|Additional function for modern Yaesu rigs is supported by LUA scripts by N6TV that you may download from https://bit.ly/wtscripts in file '''YaesuScripts.zip'''.}} <br />
<br />
* FT-100<br />
* FT-450<br />
* FT-757GX II<br />
* FT-817<br />
* FT-847<br />
* FT-857<br />
* FT-891<br />
* FT-897<br />
* FT-900<br />
* FT-920<br />
* FT-950<br />
* FT-990<br>COM port set to 4800 bauds, 8 data bits, no parity, no flow control and 2 stop bits.<br>For DTR and RTS, see FT-1000D below. Tnx F6GOX, NX5M.<br />
* FT-991<br>Use the Yaesu USB driver. See screen shots of recommended menu settings well-documented by HB9AMO at http://www.hb9amo.net/wt-ft991.php <br />
* FT-1000D<br>COM port set to 4800 bauds, 8 data bits, no parity, no flow control and 2 stop bits.<br>When using a powered CAT interface such as the Yaesu FIF-232C CAT interface box and CT-62 cable, set DTR and RTS to '''Always OFF'''.<br>When using a "passive" (not powered) interface cable such as the [http://k1nu.home.comcast.net/~k1nu/k1nu/Products/control.html K1NU CAT Control Cable], set DTR to '''Always OFF''', RTS to '''Always ON'''. Tnx F5FLN, NX5M, NQ4I.<br />
* FT-1000MP (including Mark V)<br>COM port set to 4800 bauds, 8 data bits, no parity, no flow control and 2 stop bits. Tnx FM5BH and F8CRH.<br />
* FT-2000<br />
* FTdx-1200<br />
* FTdx-3000<br />
* FTdx-5000<br />
* FTdx-9000<br />
<br />
{{wbox|Note|Sub-VFO programming from within the band map is available for the FT-1000MP, FT-2000 and FTDdx-9000 only}}.<br />
<br />
==Ten-Tec==<br />
<br />
* Jupiter<br />
* Orion (aka Orion I)<br />
* Orion II<br />
* Omni VI<br>Use the Icom generic setting, with 04h hex address, and set COM port to 9600 baud (can be modified in TRX if needed), 8 data bits, no parity, 1 stop bit. Tnx F6IFY<br />
* Omni VII<br />
<br />
<br />
{{wbox|Note|Sub-VFO programming from within the band map is available for the Orion only.}}<br />
<br />
==Elecraft==<br />
<br />
{{wbox|Note|Additional function for Elecraft rigs is supported by LUA scripts by N6TV that you may download from https://bit.ly/wtscripts in file '''K3scripts.zip''', '''KX3Scripts.zip''', and '''P3scripts.zip'''.}} <br />
<br />
* Elecraft K2<br />
* Elecraft K3<br />
* Elecraft K3S<br />
* Elecraft KX3<br />
<br />
==Others==<br />
* FlexRadio SDR-1000<br />
* [http://dxatlas.com/omnirig/ OmniRig] - Setting radio type to OmniRig will allow the radio's COM port to be shared with other applications such as [http://winrad.org/ Winrad] and [http://www.hdsdr.de/ HDSDR].</div>N6TVhttps://docs.win-test.com/w/index.php?title=Supported_rigs&diff=4736Supported rigs2017-07-25T17:58:15Z<p>N6TV: /* Yaesu */ Added link to LUA scripts</p>
<hr />
<div>Win-Test supports most rigs of today's amateur radio market. The radio or radios (if you use two) and their communication parameters are to be configured in the [[Menu:Options#Configure_interfaces...|Options Menu]] of Win-Test. Typically, you don't even have to guess specific baud rates or parity settings as Win-Test knows most of the default settings.<br />
<br />
==Kenwood==<br />
Virtually all Kenwood rigs are supported by Win-Test. They all use the same CAT command subset needed by Win-Test.<br />
<br />
Kenwood rigs use by default:<br />
<br />
* Speed: 4800 Bauds<br />
* Data bits: 8<br />
* Parity: None<br />
* Stop bits: 2<br />
<br />
Exception: TS-590S uses two stop bits ''only'' for 4800 baud. For all other baud rates, use only 1 stop bit.<br />
<br />
Models successfully tested: <br />
* TS-850S<br />
* TS-930S PIEXX (Tnx FM5BH)<br />
* TS-940S<br />
* TS-950S<br />
* TS-570DGE<br />
* TS-590S -- USB connection only; the serial port may not work. See [http://lists.f5mzn.org/pipermail/support/2011-July/081291.html Reflector post by RA3AUU]. USB requires installation of the [http://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx Silicon Labs Virtual COM port (VCP) driver]. For VCP installation instructions, see [http://www.kenwood.com/i/products/info/amateur/vcp_e.html this page] on the Kenwood web site).<br />
* (others are known to work, but not fully tested, e.g. TS-690, TS-450, TS-950SD, TS-2000, etc.)<br />
<br />
==Icom==<br />
<br />
Virtually, all Icom rigs are supported by Win-Test. They all use the same CAT command subset.<br />
<br />
{{wbox|Note|Additional function for modern Icom rigs is supported by LUA scripts by N6TV that you may download from https://bit.ly/wtscripts in file '''IcomScripts.zip'''.}} <br />
<br />
{{wbox|Note|The VFO-B windows with ICOM is almost always grey on older Icom radios [http://lists.f5mzn.org/pipermail/support/2007-February/073046.html].}}<br />
<br />
Best results for Icom radios are usually achieved by checking ''both'' the '''<tt>Don’t poll</tt>''' and the '''<tt>Use CI-V-Transceive</tt>''' options. The band map then moves very smoothly while turning the VFO. Another choice is to ''remove'' the check mark from both of these options.<br />
<br />
* IC-275<br>COM port set to 1200 baud, 8 data bits, no parity and 1 stop bit. Tnx MM0GPZ.<br>See also [[BestPractice3#Setting_up_an_Icom_IC-275H_with_the_microHAM_USB_Interface_IC|Setting up an Icom IC-275H with the microHAM USB Interface IC]].<br />
* IC-475<br />
* IC-703<br />
* IC-706<br>COM port set to 9600 baud, 8 data bits, no parity and 1 stop bit. Tnx F6IFY<br />
* IC-706 Mk II<br />
* IC-706 Mk II G<br />
* IC-718<br />
* IC-725<br />
* IC-728<br />
* IC-729<br />
* IC-735<br />
* IC-736<br />
* IC-737<br />
* IC-738<br />
* IC-746<br />
* IC-746 Pro<br />
* IC-751<br />
* IC-756<br />
* IC-756 Pro<br />
* IC-756 Pro II<br />
* IC-756 Pro III<br />
* IC-761<br />
* IC-765<br />
* IC-775 (or IC 775 DSP)<br>COM port set to 1200 baud, 8 data bits, no parity and 1 stop bit. Tnx EA3IN. (also succesfully tested up to 9600 baud. I2WIJ)<br />
* IC-781<br />
* IC-910<br />
* IC-970<br />
* IC-1275<br />
* IC-7000<br />
* IC-7100<br />
* IC-7200<br />
* IC-7300<br />
* IC-7410<br />
* IC-7600<br />
* IC-7700<br />
* IC-7800<br />
* IC-7850<br />
* IC-7851<br />
* IC-9100<br />
<br />
===Other Icom radios===<br />
* Icom generic: This setting can be used to connect an Icom rig not listed. You need to set the Icom rig's address (found in the rig manual) in the wt.ini file in the [Interfaces] section. Please see [[WT.INI#Generic_ICOM_radio|WT.INI]] for more details.<br />
* IC-728<br>Use the Icom generic setting with hex address 38h and set COM port to 1200 baud, 8 data bits, no parity, 1 stop bit. Tnx VK6NU<br />
* IC-746 PRO<br>In fact, the IC 7400 (below) is the European version of the IC 746 PRO. It uses the same hex address and should work with the same settings. Tnx F8CRH<br />
* IC-910H<br>Use the Icom generic setting with hex address 60h and set COM port to 4800 baud, 8 data bits, no parity, 1 stop bit. Works on all 3 bands (2m, 70 and 23 cm). Tnx F6BEE<br />
* IC-7400<br>Use the Icom generic setting with hex address 66h and set COM port to 9600 baud (also successfully tested with 1200 and 19200 baud and TRX set accordingly), 8 data bits, no parity, 2 stop bits. Tnx F8CRH<br />
<br />
==Yaesu==<br />
<br />
{{wbox|Note|Additional function for modern Yaesu rigs is supported by LUA scripts by N6TV that you may download from https://bit.ly/wtscripts in file '''YaesuScripts.zip'''.}} <br />
<br />
* FT-100<br />
* FT-450<br />
* FT-757GX II<br />
* FT-817<br />
* FT-847<br />
* FT-857<br />
* FT-891<br />
* FT-897<br />
* FT-900<br />
* FT-920<br />
* FT-950<br />
* FT-990<br>COM port set to 4800 bauds, 8 data bits, no parity, no flow control and 2 stop bits.<br>For DTR and RTS, see FT-1000D below. Tnx F6GOX, NX5M.<br />
* FT-991<br>Use the Yaesu USB driver. See screen shots of recommended menu settings well-documented by HB9AMO at http://www.hb9amo.net/wt-ft991.php <br />
* FT-1000D<br>COM port set to 4800 bauds, 8 data bits, no parity, no flow control and 2 stop bits.<br>When using a powered CAT interface such as the Yaesu FIF-232C CAT interface box and CT-62 cable, set DTR and RTS to '''Always OFF'''.<br>When using a "passive" (not powered) interface cable such as the [http://k1nu.home.comcast.net/~k1nu/k1nu/Products/control.html K1NU CAT Control Cable], set DTR to '''Always OFF''', RTS to '''Always ON'''. Tnx F5FLN, NX5M, NQ4I.<br />
* FT-1000MP (including Mark V)<br>COM port set to 4800 bauds, 8 data bits, no parity, no flow control and 2 stop bits. Tnx FM5BH and F8CRH.<br />
* FT-2000<br />
* FTdx-1200<br />
* FTdx-3000<br />
* FTdx-5000<br />
* FTdx-9000<br />
<br />
{{wbox|Note|Sub-VFO programming from within the band map is available for the FT-1000MP, FT-2000 and FTDdx-9000 only}}.<br />
<br />
==Ten-Tec==<br />
<br />
* Jupiter<br />
* Orion (aka Orion I)<br />
* Orion II<br />
* Omni VI<br>Use the Icom generic setting, with 04h hex address, and set COM port to 9600 baud (can be modified in TRX if needed), 8 data bits, no parity, 1 stop bit. Tnx F6IFY<br />
* Omni VII<br />
<br />
<br />
{{wbox|Note|Sub-VFO programming from within the band map is available for the Orion only.}}<br />
<br />
==Elecraft==<br />
<br />
* Elecraft K2<br />
* Elecraft K3<br />
* Elecraft K3S<br />
* Elecraft KX3<br />
<br />
==Others==<br />
* FlexRadio SDR-1000<br />
* [http://dxatlas.com/omnirig/ OmniRig] - Setting radio type to OmniRig will allow the radio's COM port to be shared with other applications such as [http://winrad.org/ Winrad] and [http://www.hdsdr.de/ HDSDR].</div>N6TVhttps://docs.win-test.com/w/index.php?title=Supported_rigs&diff=4735Supported rigs2017-07-25T17:56:04Z<p>N6TV: /* Icom */ Added IC-7851. Added link to LUA scripts. Updated note about VFO B.</p>
<hr />
<div>Win-Test supports most rigs of today's amateur radio market. The radio or radios (if you use two) and their communication parameters are to be configured in the [[Menu:Options#Configure_interfaces...|Options Menu]] of Win-Test. Typically, you don't even have to guess specific baud rates or parity settings as Win-Test knows most of the default settings.<br />
<br />
==Kenwood==<br />
Virtually all Kenwood rigs are supported by Win-Test. They all use the same CAT command subset needed by Win-Test.<br />
<br />
Kenwood rigs use by default:<br />
<br />
* Speed: 4800 Bauds<br />
* Data bits: 8<br />
* Parity: None<br />
* Stop bits: 2<br />
<br />
Exception: TS-590S uses two stop bits ''only'' for 4800 baud. For all other baud rates, use only 1 stop bit.<br />
<br />
Models successfully tested: <br />
* TS-850S<br />
* TS-930S PIEXX (Tnx FM5BH)<br />
* TS-940S<br />
* TS-950S<br />
* TS-570DGE<br />
* TS-590S -- USB connection only; the serial port may not work. See [http://lists.f5mzn.org/pipermail/support/2011-July/081291.html Reflector post by RA3AUU]. USB requires installation of the [http://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx Silicon Labs Virtual COM port (VCP) driver]. For VCP installation instructions, see [http://www.kenwood.com/i/products/info/amateur/vcp_e.html this page] on the Kenwood web site).<br />
* (others are known to work, but not fully tested, e.g. TS-690, TS-450, TS-950SD, TS-2000, etc.)<br />
<br />
==Icom==<br />
<br />
Virtually, all Icom rigs are supported by Win-Test. They all use the same CAT command subset.<br />
<br />
{{wbox|Note|Additional function for modern Icom rigs is supported by LUA scripts by N6TV that you may download from https://bit.ly/wtscripts in file '''IcomScripts.zip'''.}} <br />
<br />
{{wbox|Note|The VFO-B windows with ICOM is almost always grey on older Icom radios [http://lists.f5mzn.org/pipermail/support/2007-February/073046.html].}}<br />
<br />
Best results for Icom radios are usually achieved by checking ''both'' the '''<tt>Don’t poll</tt>''' and the '''<tt>Use CI-V-Transceive</tt>''' options. The band map then moves very smoothly while turning the VFO. Another choice is to ''remove'' the check mark from both of these options.<br />
<br />
* IC-275<br>COM port set to 1200 baud, 8 data bits, no parity and 1 stop bit. Tnx MM0GPZ.<br>See also [[BestPractice3#Setting_up_an_Icom_IC-275H_with_the_microHAM_USB_Interface_IC|Setting up an Icom IC-275H with the microHAM USB Interface IC]].<br />
* IC-475<br />
* IC-703<br />
* IC-706<br>COM port set to 9600 baud, 8 data bits, no parity and 1 stop bit. Tnx F6IFY<br />
* IC-706 Mk II<br />
* IC-706 Mk II G<br />
* IC-718<br />
* IC-725<br />
* IC-728<br />
* IC-729<br />
* IC-735<br />
* IC-736<br />
* IC-737<br />
* IC-738<br />
* IC-746<br />
* IC-746 Pro<br />
* IC-751<br />
* IC-756<br />
* IC-756 Pro<br />
* IC-756 Pro II<br />
* IC-756 Pro III<br />
* IC-761<br />
* IC-765<br />
* IC-775 (or IC 775 DSP)<br>COM port set to 1200 baud, 8 data bits, no parity and 1 stop bit. Tnx EA3IN. (also succesfully tested up to 9600 baud. I2WIJ)<br />
* IC-781<br />
* IC-910<br />
* IC-970<br />
* IC-1275<br />
* IC-7000<br />
* IC-7100<br />
* IC-7200<br />
* IC-7300<br />
* IC-7410<br />
* IC-7600<br />
* IC-7700<br />
* IC-7800<br />
* IC-7850<br />
* IC-7851<br />
* IC-9100<br />
<br />
===Other Icom radios===<br />
* Icom generic: This setting can be used to connect an Icom rig not listed. You need to set the Icom rig's address (found in the rig manual) in the wt.ini file in the [Interfaces] section. Please see [[WT.INI#Generic_ICOM_radio|WT.INI]] for more details.<br />
* IC-728<br>Use the Icom generic setting with hex address 38h and set COM port to 1200 baud, 8 data bits, no parity, 1 stop bit. Tnx VK6NU<br />
* IC-746 PRO<br>In fact, the IC 7400 (below) is the European version of the IC 746 PRO. It uses the same hex address and should work with the same settings. Tnx F8CRH<br />
* IC-910H<br>Use the Icom generic setting with hex address 60h and set COM port to 4800 baud, 8 data bits, no parity, 1 stop bit. Works on all 3 bands (2m, 70 and 23 cm). Tnx F6BEE<br />
* IC-7400<br>Use the Icom generic setting with hex address 66h and set COM port to 9600 baud (also successfully tested with 1200 and 19200 baud and TRX set accordingly), 8 data bits, no parity, 2 stop bits. Tnx F8CRH<br />
<br />
==Yaesu==<br />
<br />
Note: When connecting modern Yaesu radios, additional function is supported from LUA scripts by N6TV that may be downloaded from https://bit.ly/wtscripts in file YaesuScripts.zip .<br />
<br />
* FT-100<br />
* FT-450<br />
* FT-757GX II<br />
* FT-817<br />
* FT-847<br />
* FT-857<br />
* FT-891<br />
* FT-897<br />
* FT-900<br />
* FT-920<br />
* FT-950<br />
* FT-990<br>COM port set to 4800 bauds, 8 data bits, no parity, no flow control and 2 stop bits.<br>For DTR and RTS, see FT-1000D below. Tnx F6GOX, NX5M.<br />
* FT-991<br>Use the Yaesu USB driver. See screen shots of recommended menu settings well-documented by HB9AMO at http://www.hb9amo.net/wt-ft991.php <br />
* FT-1000D<br>COM port set to 4800 bauds, 8 data bits, no parity, no flow control and 2 stop bits.<br>When using a powered CAT interface such as the Yaesu FIF-232C CAT interface box and CT-62 cable, set DTR and RTS to '''Always OFF'''.<br>When using a "passive" (not powered) interface cable such as the [http://k1nu.home.comcast.net/~k1nu/k1nu/Products/control.html K1NU CAT Control Cable], set DTR to '''Always OFF''', RTS to '''Always ON'''. Tnx F5FLN, NX5M, NQ4I.<br />
* FT-1000MP (including Mark V)<br>COM port set to 4800 bauds, 8 data bits, no parity, no flow control and 2 stop bits. Tnx FM5BH and F8CRH.<br />
* FT-2000<br />
* FTdx-1200<br />
* FTdx-3000<br />
* FTdx-5000<br />
* FTdx-9000<br />
<br />
{{wbox|Note|Sub-VFO programming from within the band map is available for the FT-1000MP, FT-2000 and FTDdx-9000 only}}.<br />
<br />
==Ten-Tec==<br />
<br />
* Jupiter<br />
* Orion (aka Orion I)<br />
* Orion II<br />
* Omni VI<br>Use the Icom generic setting, with 04h hex address, and set COM port to 9600 baud (can be modified in TRX if needed), 8 data bits, no parity, 1 stop bit. Tnx F6IFY<br />
* Omni VII<br />
<br />
<br />
{{wbox|Note|Sub-VFO programming from within the band map is available for the Orion only.}}<br />
<br />
==Elecraft==<br />
<br />
* Elecraft K2<br />
* Elecraft K3<br />
* Elecraft K3S<br />
* Elecraft KX3<br />
<br />
==Others==<br />
* FlexRadio SDR-1000<br />
* [http://dxatlas.com/omnirig/ OmniRig] - Setting radio type to OmniRig will allow the radio's COM port to be shared with other applications such as [http://winrad.org/ Winrad] and [http://www.hdsdr.de/ HDSDR].</div>N6TVhttps://docs.win-test.com/w/index.php?title=Supported_rigs&diff=4734Supported rigs2017-07-25T17:51:39Z<p>N6TV: /* Elecraft */ Added K3S and KX3</p>
<hr />
<div>Win-Test supports most rigs of today's amateur radio market. The radio or radios (if you use two) and their communication parameters are to be configured in the [[Menu:Options#Configure_interfaces...|Options Menu]] of Win-Test. Typically, you don't even have to guess specific baud rates or parity settings as Win-Test knows most of the default settings.<br />
<br />
==Kenwood==<br />
Virtually all Kenwood rigs are supported by Win-Test. They all use the same CAT command subset needed by Win-Test.<br />
<br />
Kenwood rigs use by default:<br />
<br />
* Speed: 4800 Bauds<br />
* Data bits: 8<br />
* Parity: None<br />
* Stop bits: 2<br />
<br />
Exception: TS-590S uses two stop bits ''only'' for 4800 baud. For all other baud rates, use only 1 stop bit.<br />
<br />
Models successfully tested: <br />
* TS-850S<br />
* TS-930S PIEXX (Tnx FM5BH)<br />
* TS-940S<br />
* TS-950S<br />
* TS-570DGE<br />
* TS-590S -- USB connection only; the serial port may not work. See [http://lists.f5mzn.org/pipermail/support/2011-July/081291.html Reflector post by RA3AUU]. USB requires installation of the [http://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx Silicon Labs Virtual COM port (VCP) driver]. For VCP installation instructions, see [http://www.kenwood.com/i/products/info/amateur/vcp_e.html this page] on the Kenwood web site).<br />
* (others are known to work, but not fully tested, e.g. TS-690, TS-450, TS-950SD, TS-2000, etc.)<br />
<br />
==Icom==<br />
<br />
Virtually, all Icom rigs are supported by Win-Test. They all use the same CAT command subset. <br />
<br />
{{wbox|Note|The VFO-B windows with ICOM is always grey [http://lists.f5mzn.org/pipermail/support/2007-February/073046.html].}}<br />
<br />
Best results for Icom radios are usually achieved by checking ''both'' the '''<tt>Don’t poll</tt>''' and the '''<tt>Use CI-V-Transceive</tt>''' options. The band map then moves very smoothly while turning the VFO. Another choice is to ''remove'' the check mark from both of these options.<br />
<br />
* IC-275<br>COM port set to 1200 baud, 8 data bits, no parity and 1 stop bit. Tnx MM0GPZ.<br>See also [[BestPractice3#Setting_up_an_Icom_IC-275H_with_the_microHAM_USB_Interface_IC|Setting up an Icom IC-275H with the microHAM USB Interface IC]].<br />
* IC-475<br />
* IC-703<br />
* IC-706<br>COM port set to 9600 baud, 8 data bits, no parity and 1 stop bit. Tnx F6IFY<br />
* IC-706 Mk II<br />
* IC-706 Mk II G<br />
* IC-718<br />
* IC-725<br />
* IC-728<br />
* IC-729<br />
* IC-735<br />
* IC-736<br />
* IC-737<br />
* IC-738<br />
* IC-746<br />
* IC-746 Pro<br />
* IC-751<br />
* IC-756<br />
* IC-756 Pro<br />
* IC-756 Pro II<br />
* IC-756 Pro III<br />
* IC-761<br />
* IC-765<br />
* IC-775 (or IC 775 DSP)<br>COM port set to 1200 baud, 8 data bits, no parity and 1 stop bit. Tnx EA3IN. (also succesfully tested up to 9600 baud. I2WIJ)<br />
* IC-781<br />
* IC-910<br />
* IC-970<br />
* IC-1275<br />
* IC-7000<br />
* IC-7100<br />
* IC-7200<br />
* IC-7300<br />
* IC-7410<br />
* IC-7600<br />
* IC-7700<br />
* IC-7800<br />
* IC-7850<br />
* IC-9100<br />
<br />
===Other Icom radios===<br />
* Icom generic: This setting can be used to connect an Icom rig not listed. You need to set the Icom rig's address (found in the rig manual) in the wt.ini file in the [Interfaces] section. Please see [[WT.INI#Generic_ICOM_radio|WT.INI]] for more details.<br />
* IC-728<br>Use the Icom generic setting with hex address 38h and set COM port to 1200 baud, 8 data bits, no parity, 1 stop bit. Tnx VK6NU<br />
* IC-746 PRO<br>In fact, the IC 7400 (below) is the European version of the IC 746 PRO. It uses the same hex address and should work with the same settings. Tnx F8CRH<br />
* IC-910H<br>Use the Icom generic setting with hex address 60h and set COM port to 4800 baud, 8 data bits, no parity, 1 stop bit. Works on all 3 bands (2m, 70 and 23 cm). Tnx F6BEE<br />
* IC-7400<br>Use the Icom generic setting with hex address 66h and set COM port to 9600 baud (also successfully tested with 1200 and 19200 baud and TRX set accordingly), 8 data bits, no parity, 2 stop bits. Tnx F8CRH<br />
<br />
==Yaesu==<br />
<br />
Note: When connecting modern Yaesu radios, additional function is supported from LUA scripts by N6TV that may be downloaded from https://bit.ly/wtscripts in file YaesuScripts.zip .<br />
<br />
* FT-100<br />
* FT-450<br />
* FT-757GX II<br />
* FT-817<br />
* FT-847<br />
* FT-857<br />
* FT-891<br />
* FT-897<br />
* FT-900<br />
* FT-920<br />
* FT-950<br />
* FT-990<br>COM port set to 4800 bauds, 8 data bits, no parity, no flow control and 2 stop bits.<br>For DTR and RTS, see FT-1000D below. Tnx F6GOX, NX5M.<br />
* FT-991<br>Use the Yaesu USB driver. See screen shots of recommended menu settings well-documented by HB9AMO at http://www.hb9amo.net/wt-ft991.php <br />
* FT-1000D<br>COM port set to 4800 bauds, 8 data bits, no parity, no flow control and 2 stop bits.<br>When using a powered CAT interface such as the Yaesu FIF-232C CAT interface box and CT-62 cable, set DTR and RTS to '''Always OFF'''.<br>When using a "passive" (not powered) interface cable such as the [http://k1nu.home.comcast.net/~k1nu/k1nu/Products/control.html K1NU CAT Control Cable], set DTR to '''Always OFF''', RTS to '''Always ON'''. Tnx F5FLN, NX5M, NQ4I.<br />
* FT-1000MP (including Mark V)<br>COM port set to 4800 bauds, 8 data bits, no parity, no flow control and 2 stop bits. Tnx FM5BH and F8CRH.<br />
* FT-2000<br />
* FTdx-1200<br />
* FTdx-3000<br />
* FTdx-5000<br />
* FTdx-9000<br />
<br />
{{wbox|Note|Sub-VFO programming from within the band map is available for the FT-1000MP, FT-2000 and FTDdx-9000 only}}.<br />
<br />
==Ten-Tec==<br />
<br />
* Jupiter<br />
* Orion (aka Orion I)<br />
* Orion II<br />
* Omni VI<br>Use the Icom generic setting, with 04h hex address, and set COM port to 9600 baud (can be modified in TRX if needed), 8 data bits, no parity, 1 stop bit. Tnx F6IFY<br />
* Omni VII<br />
<br />
<br />
{{wbox|Note|Sub-VFO programming from within the band map is available for the Orion only.}}<br />
<br />
==Elecraft==<br />
<br />
* Elecraft K2<br />
* Elecraft K3<br />
* Elecraft K3S<br />
* Elecraft KX3<br />
<br />
==Others==<br />
* FlexRadio SDR-1000<br />
* [http://dxatlas.com/omnirig/ OmniRig] - Setting radio type to OmniRig will allow the radio's COM port to be shared with other applications such as [http://winrad.org/ Winrad] and [http://www.hdsdr.de/ HDSDR].</div>N6TVhttps://docs.win-test.com/w/index.php?title=Supported_rigs&diff=4733Supported rigs2017-07-25T17:49:02Z<p>N6TV: /* Yaesu */ Change httsp to https</p>
<hr />
<div>Win-Test supports most rigs of today's amateur radio market. The radio or radios (if you use two) and their communication parameters are to be configured in the [[Menu:Options#Configure_interfaces...|Options Menu]] of Win-Test. Typically, you don't even have to guess specific baud rates or parity settings as Win-Test knows most of the default settings.<br />
<br />
==Kenwood==<br />
Virtually all Kenwood rigs are supported by Win-Test. They all use the same CAT command subset needed by Win-Test.<br />
<br />
Kenwood rigs use by default:<br />
<br />
* Speed: 4800 Bauds<br />
* Data bits: 8<br />
* Parity: None<br />
* Stop bits: 2<br />
<br />
Exception: TS-590S uses two stop bits ''only'' for 4800 baud. For all other baud rates, use only 1 stop bit.<br />
<br />
Models successfully tested: <br />
* TS-850S<br />
* TS-930S PIEXX (Tnx FM5BH)<br />
* TS-940S<br />
* TS-950S<br />
* TS-570DGE<br />
* TS-590S -- USB connection only; the serial port may not work. See [http://lists.f5mzn.org/pipermail/support/2011-July/081291.html Reflector post by RA3AUU]. USB requires installation of the [http://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx Silicon Labs Virtual COM port (VCP) driver]. For VCP installation instructions, see [http://www.kenwood.com/i/products/info/amateur/vcp_e.html this page] on the Kenwood web site).<br />
* (others are known to work, but not fully tested, e.g. TS-690, TS-450, TS-950SD, TS-2000, etc.)<br />
<br />
==Icom==<br />
<br />
Virtually, all Icom rigs are supported by Win-Test. They all use the same CAT command subset. <br />
<br />
{{wbox|Note|The VFO-B windows with ICOM is always grey [http://lists.f5mzn.org/pipermail/support/2007-February/073046.html].}}<br />
<br />
Best results for Icom radios are usually achieved by checking ''both'' the '''<tt>Don’t poll</tt>''' and the '''<tt>Use CI-V-Transceive</tt>''' options. The band map then moves very smoothly while turning the VFO. Another choice is to ''remove'' the check mark from both of these options.<br />
<br />
* IC-275<br>COM port set to 1200 baud, 8 data bits, no parity and 1 stop bit. Tnx MM0GPZ.<br>See also [[BestPractice3#Setting_up_an_Icom_IC-275H_with_the_microHAM_USB_Interface_IC|Setting up an Icom IC-275H with the microHAM USB Interface IC]].<br />
* IC-475<br />
* IC-703<br />
* IC-706<br>COM port set to 9600 baud, 8 data bits, no parity and 1 stop bit. Tnx F6IFY<br />
* IC-706 Mk II<br />
* IC-706 Mk II G<br />
* IC-718<br />
* IC-725<br />
* IC-728<br />
* IC-729<br />
* IC-735<br />
* IC-736<br />
* IC-737<br />
* IC-738<br />
* IC-746<br />
* IC-746 Pro<br />
* IC-751<br />
* IC-756<br />
* IC-756 Pro<br />
* IC-756 Pro II<br />
* IC-756 Pro III<br />
* IC-761<br />
* IC-765<br />
* IC-775 (or IC 775 DSP)<br>COM port set to 1200 baud, 8 data bits, no parity and 1 stop bit. Tnx EA3IN. (also succesfully tested up to 9600 baud. I2WIJ)<br />
* IC-781<br />
* IC-910<br />
* IC-970<br />
* IC-1275<br />
* IC-7000<br />
* IC-7100<br />
* IC-7200<br />
* IC-7300<br />
* IC-7410<br />
* IC-7600<br />
* IC-7700<br />
* IC-7800<br />
* IC-7850<br />
* IC-9100<br />
<br />
===Other Icom radios===<br />
* Icom generic: This setting can be used to connect an Icom rig not listed. You need to set the Icom rig's address (found in the rig manual) in the wt.ini file in the [Interfaces] section. Please see [[WT.INI#Generic_ICOM_radio|WT.INI]] for more details.<br />
* IC-728<br>Use the Icom generic setting with hex address 38h and set COM port to 1200 baud, 8 data bits, no parity, 1 stop bit. Tnx VK6NU<br />
* IC-746 PRO<br>In fact, the IC 7400 (below) is the European version of the IC 746 PRO. It uses the same hex address and should work with the same settings. Tnx F8CRH<br />
* IC-910H<br>Use the Icom generic setting with hex address 60h and set COM port to 4800 baud, 8 data bits, no parity, 1 stop bit. Works on all 3 bands (2m, 70 and 23 cm). Tnx F6BEE<br />
* IC-7400<br>Use the Icom generic setting with hex address 66h and set COM port to 9600 baud (also successfully tested with 1200 and 19200 baud and TRX set accordingly), 8 data bits, no parity, 2 stop bits. Tnx F8CRH<br />
<br />
==Yaesu==<br />
<br />
Note: When connecting modern Yaesu radios, additional function is supported from LUA scripts by N6TV that may be downloaded from https://bit.ly/wtscripts in file YaesuScripts.zip .<br />
<br />
* FT-100<br />
* FT-450<br />
* FT-757GX II<br />
* FT-817<br />
* FT-847<br />
* FT-857<br />
* FT-891<br />
* FT-897<br />
* FT-900<br />
* FT-920<br />
* FT-950<br />
* FT-990<br>COM port set to 4800 bauds, 8 data bits, no parity, no flow control and 2 stop bits.<br>For DTR and RTS, see FT-1000D below. Tnx F6GOX, NX5M.<br />
* FT-991<br>Use the Yaesu USB driver. See screen shots of recommended menu settings well-documented by HB9AMO at http://www.hb9amo.net/wt-ft991.php <br />
* FT-1000D<br>COM port set to 4800 bauds, 8 data bits, no parity, no flow control and 2 stop bits.<br>When using a powered CAT interface such as the Yaesu FIF-232C CAT interface box and CT-62 cable, set DTR and RTS to '''Always OFF'''.<br>When using a "passive" (not powered) interface cable such as the [http://k1nu.home.comcast.net/~k1nu/k1nu/Products/control.html K1NU CAT Control Cable], set DTR to '''Always OFF''', RTS to '''Always ON'''. Tnx F5FLN, NX5M, NQ4I.<br />
* FT-1000MP (including Mark V)<br>COM port set to 4800 bauds, 8 data bits, no parity, no flow control and 2 stop bits. Tnx FM5BH and F8CRH.<br />
* FT-2000<br />
* FTdx-1200<br />
* FTdx-3000<br />
* FTdx-5000<br />
* FTdx-9000<br />
<br />
{{wbox|Note|Sub-VFO programming from within the band map is available for the FT-1000MP, FT-2000 and FTDdx-9000 only}}.<br />
<br />
==Ten-Tec==<br />
<br />
* Jupiter<br />
* Orion (aka Orion I)<br />
* Orion II<br />
* Omni VI<br>Use the Icom generic setting, with 04h hex address, and set COM port to 9600 baud (can be modified in TRX if needed), 8 data bits, no parity, 1 stop bit. Tnx F6IFY<br />
* Omni VII<br />
<br />
<br />
{{wbox|Note|Sub-VFO programming from within the band map is available for the Orion only.}}<br />
<br />
==Elecraft==<br />
<br />
* Elecraft K2<br />
* Elecraft K3<br>Sample LUA scripts demonstrating how to control the RIT and internal DVR (voice keyer) of the Elecraft K3 from Win-Test can be downloaded from [http://www.kkn.net/~n6tv/K3scripts.zip http://www.kkn.net/~n6tv/K3scripts.zip].<br />
<br />
==Others==<br />
* FlexRadio SDR-1000<br />
* [http://dxatlas.com/omnirig/ OmniRig] - Setting radio type to OmniRig will allow the radio's COM port to be shared with other applications such as [http://winrad.org/ Winrad] and [http://www.hdsdr.de/ HDSDR].</div>N6TVhttps://docs.win-test.com/w/index.php?title=Supported_rigs&diff=4732Supported rigs2017-07-25T17:48:27Z<p>N6TV: /* Yaesu */ Added link to HB9AMO's FT-991 setup page, and N6TV LUA scripts</p>
<hr />
<div>Win-Test supports most rigs of today's amateur radio market. The radio or radios (if you use two) and their communication parameters are to be configured in the [[Menu:Options#Configure_interfaces...|Options Menu]] of Win-Test. Typically, you don't even have to guess specific baud rates or parity settings as Win-Test knows most of the default settings.<br />
<br />
==Kenwood==<br />
Virtually all Kenwood rigs are supported by Win-Test. They all use the same CAT command subset needed by Win-Test.<br />
<br />
Kenwood rigs use by default:<br />
<br />
* Speed: 4800 Bauds<br />
* Data bits: 8<br />
* Parity: None<br />
* Stop bits: 2<br />
<br />
Exception: TS-590S uses two stop bits ''only'' for 4800 baud. For all other baud rates, use only 1 stop bit.<br />
<br />
Models successfully tested: <br />
* TS-850S<br />
* TS-930S PIEXX (Tnx FM5BH)<br />
* TS-940S<br />
* TS-950S<br />
* TS-570DGE<br />
* TS-590S -- USB connection only; the serial port may not work. See [http://lists.f5mzn.org/pipermail/support/2011-July/081291.html Reflector post by RA3AUU]. USB requires installation of the [http://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx Silicon Labs Virtual COM port (VCP) driver]. For VCP installation instructions, see [http://www.kenwood.com/i/products/info/amateur/vcp_e.html this page] on the Kenwood web site).<br />
* (others are known to work, but not fully tested, e.g. TS-690, TS-450, TS-950SD, TS-2000, etc.)<br />
<br />
==Icom==<br />
<br />
Virtually, all Icom rigs are supported by Win-Test. They all use the same CAT command subset. <br />
<br />
{{wbox|Note|The VFO-B windows with ICOM is always grey [http://lists.f5mzn.org/pipermail/support/2007-February/073046.html].}}<br />
<br />
Best results for Icom radios are usually achieved by checking ''both'' the '''<tt>Don’t poll</tt>''' and the '''<tt>Use CI-V-Transceive</tt>''' options. The band map then moves very smoothly while turning the VFO. Another choice is to ''remove'' the check mark from both of these options.<br />
<br />
* IC-275<br>COM port set to 1200 baud, 8 data bits, no parity and 1 stop bit. Tnx MM0GPZ.<br>See also [[BestPractice3#Setting_up_an_Icom_IC-275H_with_the_microHAM_USB_Interface_IC|Setting up an Icom IC-275H with the microHAM USB Interface IC]].<br />
* IC-475<br />
* IC-703<br />
* IC-706<br>COM port set to 9600 baud, 8 data bits, no parity and 1 stop bit. Tnx F6IFY<br />
* IC-706 Mk II<br />
* IC-706 Mk II G<br />
* IC-718<br />
* IC-725<br />
* IC-728<br />
* IC-729<br />
* IC-735<br />
* IC-736<br />
* IC-737<br />
* IC-738<br />
* IC-746<br />
* IC-746 Pro<br />
* IC-751<br />
* IC-756<br />
* IC-756 Pro<br />
* IC-756 Pro II<br />
* IC-756 Pro III<br />
* IC-761<br />
* IC-765<br />
* IC-775 (or IC 775 DSP)<br>COM port set to 1200 baud, 8 data bits, no parity and 1 stop bit. Tnx EA3IN. (also succesfully tested up to 9600 baud. I2WIJ)<br />
* IC-781<br />
* IC-910<br />
* IC-970<br />
* IC-1275<br />
* IC-7000<br />
* IC-7100<br />
* IC-7200<br />
* IC-7300<br />
* IC-7410<br />
* IC-7600<br />
* IC-7700<br />
* IC-7800<br />
* IC-7850<br />
* IC-9100<br />
<br />
===Other Icom radios===<br />
* Icom generic: This setting can be used to connect an Icom rig not listed. You need to set the Icom rig's address (found in the rig manual) in the wt.ini file in the [Interfaces] section. Please see [[WT.INI#Generic_ICOM_radio|WT.INI]] for more details.<br />
* IC-728<br>Use the Icom generic setting with hex address 38h and set COM port to 1200 baud, 8 data bits, no parity, 1 stop bit. Tnx VK6NU<br />
* IC-746 PRO<br>In fact, the IC 7400 (below) is the European version of the IC 746 PRO. It uses the same hex address and should work with the same settings. Tnx F8CRH<br />
* IC-910H<br>Use the Icom generic setting with hex address 60h and set COM port to 4800 baud, 8 data bits, no parity, 1 stop bit. Works on all 3 bands (2m, 70 and 23 cm). Tnx F6BEE<br />
* IC-7400<br>Use the Icom generic setting with hex address 66h and set COM port to 9600 baud (also successfully tested with 1200 and 19200 baud and TRX set accordingly), 8 data bits, no parity, 2 stop bits. Tnx F8CRH<br />
<br />
==Yaesu==<br />
<br />
Note: When connecting modern Yaesu radios, additional function is supported from LUA scripts by N6TV that may be downloaded from httsp://bit.ly/wtscripts in file YaesuScripts.zip .<br />
<br />
* FT-100<br />
* FT-450<br />
* FT-757GX II<br />
* FT-817<br />
* FT-847<br />
* FT-857<br />
* FT-891<br />
* FT-897<br />
* FT-900<br />
* FT-920<br />
* FT-950<br />
* FT-990<br>COM port set to 4800 bauds, 8 data bits, no parity, no flow control and 2 stop bits.<br>For DTR and RTS, see FT-1000D below. Tnx F6GOX, NX5M.<br />
* FT-991<br>Use the Yaesu USB driver. See screen shots of recommended menu settings well-documented by HB9AMO at http://www.hb9amo.net/wt-ft991.php <br />
* FT-1000D<br>COM port set to 4800 bauds, 8 data bits, no parity, no flow control and 2 stop bits.<br>When using a powered CAT interface such as the Yaesu FIF-232C CAT interface box and CT-62 cable, set DTR and RTS to '''Always OFF'''.<br>When using a "passive" (not powered) interface cable such as the [http://k1nu.home.comcast.net/~k1nu/k1nu/Products/control.html K1NU CAT Control Cable], set DTR to '''Always OFF''', RTS to '''Always ON'''. Tnx F5FLN, NX5M, NQ4I.<br />
* FT-1000MP (including Mark V)<br>COM port set to 4800 bauds, 8 data bits, no parity, no flow control and 2 stop bits. Tnx FM5BH and F8CRH.<br />
* FT-2000<br />
* FTdx-1200<br />
* FTdx-3000<br />
* FTdx-5000<br />
* FTdx-9000<br />
<br />
{{wbox|Note|Sub-VFO programming from within the band map is available for the FT-1000MP, FT-2000 and FTDdx-9000 only}}.<br />
<br />
==Ten-Tec==<br />
<br />
* Jupiter<br />
* Orion (aka Orion I)<br />
* Orion II<br />
* Omni VI<br>Use the Icom generic setting, with 04h hex address, and set COM port to 9600 baud (can be modified in TRX if needed), 8 data bits, no parity, 1 stop bit. Tnx F6IFY<br />
* Omni VII<br />
<br />
<br />
{{wbox|Note|Sub-VFO programming from within the band map is available for the Orion only.}}<br />
<br />
==Elecraft==<br />
<br />
* Elecraft K2<br />
* Elecraft K3<br>Sample LUA scripts demonstrating how to control the RIT and internal DVR (voice keyer) of the Elecraft K3 from Win-Test can be downloaded from [http://www.kkn.net/~n6tv/K3scripts.zip http://www.kkn.net/~n6tv/K3scripts.zip].<br />
<br />
==Others==<br />
* FlexRadio SDR-1000<br />
* [http://dxatlas.com/omnirig/ OmniRig] - Setting radio type to OmniRig will allow the radio's COM port to be shared with other applications such as [http://winrad.org/ Winrad] and [http://www.hdsdr.de/ HDSDR].</div>N6TVhttps://docs.win-test.com/w/index.php?title=Message_variables&diff=4579Message variables2016-08-26T15:39:22Z<p>N6TV: /* CW / RTTY automation */ Explain how $RST works on CW vs RTTY</p>
<hr />
<div><big><big>Messages Variables</big></big><br />
<!-- Adopted to Stylesheet DL6RAI --><br />
<br />
These variables can be used in programming CW messages using the F-keys. Some of these variables do not actually create output but rather perform actions at specific points in time, like the '''<tt>$CR</tt>''' symbol.<br />
<br />
==CW / RTTY automation==<br />
* '''<tt>$CHECK</tt>''': send license year (ARRL SS only)<br />
* '''<tt>$CORRECT</tt>''': sends a call correction, if any (see [[Menu:Options#Correction|correction]])<br />
* '''<tt>$CURRENT</tt>''' (or '''<tt>$CURRENTCALL</tt>'''): Sends the callsign of the current QSO ''despite'' the presence of a $CR later in the message. The $CR (carriage return) is always executed on message keypress. See [[Menu:Windows#Partner|Windows | Partner]] for usage examples. It is also useful in ESM (Enter Sends Message) mode in lieu of $LOGGEDCALL.<br />
* '''<tt>$F1...$F7</tt>''': sends the message associated with F1 ... F7 function key<br />
* '''<tt>$FREQ''nn''</tt>''': Where ''nn'' is a band (e.g. $FREQ160, $FREQ80 etc.). Useful in a multi-op as a canned message "PSE QSY $FREQ15". Sends the frequency of the primary radio of the first networked station found on this band with the following priority : R, R+, M, and M+. In addition, in CW, if the frequency is within 100 Hz of a kHz boundary, the decimal point is omitted, e.g. 14021.09 is sent as 14021 and 14021.10 is sent as 14021R1.<br />
* '''<tt>$FREQP</tt>''': contains the frequency of the primary radio (useful for passing mults)<br />
* '''<tt>$FREQS</tt>''': contains the frequency of the secondary radio (useful for passing mults)<br />
* '''<tt>$GRIDFIELD</tt>''' (or <tt>'''$LOC4</tt>''', <tt>'''$GRID4</tt>'''): contains the 4-char QTH locator (Maidenhead square) of the entrant<br />
* '''<tt>$GRIDSQUARE</tt>''' (or <tt>'''$LOC6</tt>''', <tt>'''$GRID6</tt>'''): contains the 6-char QTH locator (Maidenhead square) of the entrant<br />
* '''<tt>$INSERT</tt>''': sends message in the ['''<tt>Ins</tt>'''] key<br />
* '''<tt>$ISLAND</tt>''': sends IOTA Reference (i.e. EU001, AF001, ...) (IOTA Contest)<br />
* '''<tt>$LOGGED</tt>''' (or '''<tt>$LOGGEDCALL</tt>'''): sends what is typed in the callsign field of the current QSO, or if blank, the previous QSO<br />
* '''<tt>$MSG1...$MSG12</tt>''': sends additional CW messages (see [[Menu:Options#Modify additional messages|Modify additional messages]])<br />
* '''<tt>$MYCALL</tt>''': sends callsign set in [[New Log#Step 2: Setup your log|contest configuration]]<br />
* '''<tt>$MYNAME</tt>''': sends operator name, set in [[New Log#Step 2: Setup your log|contest configuration]]<br />
* '''<tt>$NEXT</tt>''' (or '''<tt>$NEXTCALL</tt>'''): sends the callsign of the next QSO line when a $CR is included in the message.<br />
* '''<tt>$NEXTSERIAL</tt>''': sends next QSO serial number (current QSO serial number plus 1)<br />
* '''<tt>$PLUS</tt>''': sends message in the ['''<tt>+</tt>'''] key <br />
* '''<tt>$PREV</tt>''' (or <tt>'''$PREVCALL</tt>'''): sends the callsign on the previous QSO line.<br />
* '''<tt>$PREVSERIAL</tt>''': sends previous QSO serial number (current QSO serial number minus 1)<br />
* '''<tt>$QQSLC</tt>''': sends Quick QSL message based QSOs made (see [[Menu:Tools#Intelligent Quick QSL...|Intelligent Quick QSL]])<br />
* '''<tt>$QQSLT</tt>''': sends Quick QSL message based on time passed (see [[Menu:Tools#Intelligent Quick QSL...|Intelligent Quick QSL]])<br />
* '''<tt>$QQSLRESET</tt>''': reset the timer or the counter like if the long QSL message were just sent.<br />
* '''<tt>$QSOB4</tt>''': sends the QSOB4 message and cancels the remainder of the current message, if the current QSO is a dupe, otherwise sends nothing (see [[Menu:Options#Modify standard messages...|Modify standard messages]])<br />
* '''<tt>$RAWSERIAL</tt>''': sends the serial number of the QSO with leading zeros and without any abbreviation<br />
* '''<tt>$RST</tt>''': sends report from RST Sent field (normally '''<tt>5NN</tt>''' for CW, '''<tt>599</tt>''' for RTTY)<br />
* '''<tt>$SERIAL</tt>''': sends current QSO Serial Number, or previous serial number if the line with the cursor is blank.<br />
* '''<tt>$STATE</tt>''': sends State/Province set in [[New Log#Step 2: Setup your log|contest configuration]] (Exchange)<br />
* '''<tt>$YEAR</tt>''': sends year nr set in [[New Log#Step 2: Setup your log|contest configuration]] (i.e. EUHFC, AA)<br />
* '''<tt>$ZONE</tt>''': sends zone nr set in [[New Log#Step 2: Setup your log|contest configuration]]<br />
* '''<tt>&''xy''</tt>''': sends a [http://en.wikipedia.org/wiki/Prosigns_for_Morse_code Morse prosign] where ''xy'' represents the two characters forming the prosign, e.g. &AS, &AR, &BK, &BT, &CL, &KN, &SK, etc.<br />
* '''<tt>+</tt>''': increase speed by 4 wpm<br />
* '''<tt>-</tt>''': decrease speed by 4 wpm<br />
* '''<tt>^</tt>''': the halfspace character with 1/2 dot duration<br />
* '''<tt>~</tt>''': (tilde) at then end of a variable means "no space" will be inserted, e.g. $NEXT~? sends the next callsign followed by a question mark, with no space in between<br />
<br />
==RTTY only==<br />
* '''<tt>$13</tt>''': send carriage return character (start print on a new line)<br />
* '''<tt>$SERIE</tt>''': send the complete QTC block (WAEDC only)<br />
<br />
==Action==<br />
* '''<tt>$CR</tt>''': works like hitting ['''<tt>Enter</tt>'''] (log QSO)<br />
* '''<tt>$GRAB1</tt>''' - '''<tt>$GRAB9</tt>''': Grabs spot 1 to 9 from the [[Menu:Windows#Partner|Partner window]] and inserts it in the callsign field. <br />
* '''<tt>$GRABRT1</tt>''' - '''<tt>$GRABRT3</tt>''': Grabs realtime spot 1 to 3 from the [[Menu:Windows#Partner|Partner window]] and inserts it in the callsign field. <br />
* '''<tt>$GRABPARTNER</tt>''': grabs the first callsign from the [[Menu:Windows#Partner|Partner window]] and inserts it in the callsign field. See usage notes under [[Menu:Windows#Partner|Partner window]].<br />
* '''<tt>$GRABSPOT</tt>''': grabs spot on the current frequency<br />
* '''<tt>$GUESSEXCH</tt>''' (or '''<tt>$GUESSEXCHANGE</tt>'''): mimics a space bar hit, filling the exchange field(s) if possible, but the cursor remains in the same edit field.<br />
* '''<tt>$REPEAT</tt>''': restarts the [[Menu:Tools#Automatic_CQ_repeat|automatic repeating CQ]] sequence (if enabled), after pausing for the specified interval. Most useful at the end of the [[Menu:Options#Modify_standard_messages...|'''<tt>[Plus]</tt>''' key message]] to avoid having to press [F1] to start CQing again.<br />
* '''<tt>$RSTEXCHSENT</tt>''': Resets the "exchangeSent" flag of the active QSO (useful only for [[API#ESM_Script_.28embedded_into_Win-Test.29|ESM scripts]])<br />
* '''<tt>$SETEXCHSENT</tt>''': Sets the "exchangeSent" flag of the active QSO (useful only for [[API#ESM_Script_.28embedded_into_Win-Test.29|ESM scripts]])<br />
* '''<tt>$SPACEBAR</tt>''': works like hitting spacebar-key (move cursor to the next most-used field)<br />
* '''<tt>$TAB</tt>''': works like hitting ['''<tt>Tab</tt>'''] (move cursor to next field)<br />
<br />
==SO2R==<br />
* '''<tt>$ALTERNATECQ</tt>''' (or '''<tt>$ACQ</tt>'''): swaps primary and secondary radios and send CQ on the secondary radio<br />
* '''<tt>$CQ</tt>''': same as '''<tt>$ALTERNATECQ</tt>''' but does not swap radios<br />
* '''<tt>$LATCH</tt>''': sets latch mode<br />
* '''<tt>$MK2R=''cmd''</tt>''': send a specific MK2R command to the microHAM MK2R SO2R box. See [[Supported_Accessories#Integrated_SO2R_boxes|Integrated_SO2R_boxes]] for usage notes.<br />
* '''<tt>$R1R1</tt>''': set audio of Radio 1 to left and right ear<br />
* '''<tt>$R1R2</tt>''': set audio of Radio 1 to left and audio of Radio 2 to right ear<br />
* '''<tt>$R2R1</tt>''': set audio of Radio 2 to left and audio of Radio 1 to right ear<br />
* '''<tt>$R2R2</tt>''': set audio of Radio 2 to left and right ear<br />
* '''<tt>$RESET</tt>''': cancels any manual change made in the audio control<br />
* '''<tt>$TR1</tt>''': transmit on primary radio<br />
* '''<tt>$TR2</tt>''': transmit on secondary radio<br />
<br />
==WAEDC QTC related==<br />
* '''<tt>$CALLSIGN</tt>''': send callsign of the current QTC <br />
* '''<tt>$DONE</tt>''': if all QTC are sent: mimic the '''<tt>[+]</tt>''' key <br />
* '''<tt>$FIELD</tt>''': this variable takes the value "GROUP", "TIME", "CL" or "NR", depending on the kind of QTC field where the cursor is located<br />
* '''<tt>$GRNR</tt>''': sends group & number of the received QTC<br />
* '''<tt>$NEXT</tt>''': move focus to the next QTC line <br />
* '''<tt>$QTC</tt>''': sends group & number of the transmitted QTC <br />
* '''<tt>$QTCROW</tt>''': Row number of cursor location in the QTC window. Very useful to create a function key sending the message '''<tt>PSE RPT QTC NR $QTCROW $QTCROW</tt>''' in WAEDC RTTY to request repetition of a specific QTC. <br />
* '''<tt>$SERIAL</tt>''': send serial number of the current QTC <br />
* '''<tt>$SERIE</tt>''': send the complete QTC block (specific to RTTY) <br />
* '''<tt>$TIME</tt>''': send time of the current QTC <br />
* '''<tt>$VALID</tt>''': save everything and close the window <br />
<br />
[[Main Page|Back to Main Page]]<br />
<br />
==Custom variables==<br />
The user may define "custom" variables with any unused name. They can be used in messages and easily updated while operating. They are mostly intended for the DXPedition mode, but they work for all CW and RTTY logs.<br />
<br />
For example, one could define<br />
* '''<tt>$REGION</tt>''' as "EU", "NA", etc.<br />
* '''<tt>$UP</tt>''' as "UP" or "UP 5"<br />
<br />
See [[Menu:Options#Custom_variables...|Options | CW | Custom variables...]] for usage notes.</div>N6TVhttps://docs.win-test.com/w/index.php?title=Message_variables&diff=4578Message variables2016-08-26T15:37:53Z<p>N6TV: /* CW / RTTY automation */ Added $RAWSERIAL</p>
<hr />
<div><big><big>Messages Variables</big></big><br />
<!-- Adopted to Stylesheet DL6RAI --><br />
<br />
These variables can be used in programming CW messages using the F-keys. Some of these variables do not actually create output but rather perform actions at specific points in time, like the '''<tt>$CR</tt>''' symbol.<br />
<br />
==CW / RTTY automation==<br />
* '''<tt>$CHECK</tt>''': send license year (ARRL SS only)<br />
* '''<tt>$CORRECT</tt>''': sends a call correction, if any (see [[Menu:Options#Correction|correction]])<br />
* '''<tt>$CURRENT</tt>''' (or '''<tt>$CURRENTCALL</tt>'''): Sends the callsign of the current QSO ''despite'' the presence of a $CR later in the message. The $CR (carriage return) is always executed on message keypress. See [[Menu:Windows#Partner|Windows | Partner]] for usage examples. It is also useful in ESM (Enter Sends Message) mode in lieu of $LOGGEDCALL.<br />
* '''<tt>$F1...$F7</tt>''': sends the message associated with F1 ... F7 function key<br />
* '''<tt>$FREQ''nn''</tt>''': Where ''nn'' is a band (e.g. $FREQ160, $FREQ80 etc.). Useful in a multi-op as a canned message "PSE QSY $FREQ15". Sends the frequency of the primary radio of the first networked station found on this band with the following priority : R, R+, M, and M+. In addition, in CW, if the frequency is within 100 Hz of a kHz boundary, the decimal point is omitted, e.g. 14021.09 is sent as 14021 and 14021.10 is sent as 14021R1.<br />
* '''<tt>$FREQP</tt>''': contains the frequency of the primary radio (useful for passing mults)<br />
* '''<tt>$FREQS</tt>''': contains the frequency of the secondary radio (useful for passing mults)<br />
* '''<tt>$GRIDFIELD</tt>''' (or <tt>'''$LOC4</tt>''', <tt>'''$GRID4</tt>'''): contains the 4-char QTH locator (Maidenhead square) of the entrant<br />
* '''<tt>$GRIDSQUARE</tt>''' (or <tt>'''$LOC6</tt>''', <tt>'''$GRID6</tt>'''): contains the 6-char QTH locator (Maidenhead square) of the entrant<br />
* '''<tt>$INSERT</tt>''': sends message in the ['''<tt>Ins</tt>'''] key<br />
* '''<tt>$ISLAND</tt>''': sends IOTA Reference (i.e. EU001, AF001, ...) (IOTA Contest)<br />
* '''<tt>$LOGGED</tt>''' (or '''<tt>$LOGGEDCALL</tt>'''): sends what is typed in the callsign field of the current QSO, or if blank, the previous QSO<br />
* '''<tt>$MSG1...$MSG12</tt>''': sends additional CW messages (see [[Menu:Options#Modify additional messages|Modify additional messages]])<br />
* '''<tt>$MYCALL</tt>''': sends callsign set in [[New Log#Step 2: Setup your log|contest configuration]]<br />
* '''<tt>$MYNAME</tt>''': sends operator name, set in [[New Log#Step 2: Setup your log|contest configuration]]<br />
* '''<tt>$NEXT</tt>''' (or '''<tt>$NEXTCALL</tt>'''): sends the callsign of the next QSO line when a $CR is included in the message.<br />
* '''<tt>$NEXTSERIAL</tt>''': sends next QSO serial number (current QSO serial number plus 1)<br />
* '''<tt>$PLUS</tt>''': sends message in the ['''<tt>+</tt>'''] key <br />
* '''<tt>$PREV</tt>''' (or <tt>'''$PREVCALL</tt>'''): sends the callsign on the previous QSO line.<br />
* '''<tt>$PREVSERIAL</tt>''': sends previous QSO serial number (current QSO serial number minus 1)<br />
* '''<tt>$QQSLC</tt>''': sends Quick QSL message based QSOs made (see [[Menu:Tools#Intelligent Quick QSL...|Intelligent Quick QSL]])<br />
* '''<tt>$QQSLT</tt>''': sends Quick QSL message based on time passed (see [[Menu:Tools#Intelligent Quick QSL...|Intelligent Quick QSL]])<br />
* '''<tt>$QQSLRESET</tt>''': reset the timer or the counter like if the long QSL message were just sent.<br />
* '''<tt>$QSOB4</tt>''': sends the QSOB4 message and cancels the remainder of the current message, if the current QSO is a dupe, otherwise sends nothing (see [[Menu:Options#Modify standard messages...|Modify standard messages]])<br />
* '''<tt>$RAWSERIAL</tt>''': sends the serial number of the QSO with leading zeros and without any abbreviation<br />
* '''<tt>$RST</tt>''': sends report from RST Sent field (normally '''<tt>5NN</tt>''')<br />
* '''<tt>$SERIAL</tt>''': sends current QSO Serial Number, or previous serial number if the line with the cursor is blank.<br />
* '''<tt>$STATE</tt>''': sends State/Province set in [[New Log#Step 2: Setup your log|contest configuration]] (Exchange)<br />
* '''<tt>$YEAR</tt>''': sends year nr set in [[New Log#Step 2: Setup your log|contest configuration]] (i.e. EUHFC, AA)<br />
* '''<tt>$ZONE</tt>''': sends zone nr set in [[New Log#Step 2: Setup your log|contest configuration]]<br />
* '''<tt>&''xy''</tt>''': sends a [http://en.wikipedia.org/wiki/Prosigns_for_Morse_code Morse prosign] where ''xy'' represents the two characters forming the prosign, e.g. &AS, &AR, &BK, &BT, &CL, &KN, &SK, etc.<br />
* '''<tt>+</tt>''': increase speed by 4 wpm<br />
* '''<tt>-</tt>''': decrease speed by 4 wpm<br />
* '''<tt>^</tt>''': the halfspace character with 1/2 dot duration<br />
* '''<tt>~</tt>''': (tilde) at then end of a variable means "no space" will be inserted, e.g. $NEXT~? sends the next callsign followed by a question mark, with no space in between<br />
<br />
==RTTY only==<br />
* '''<tt>$13</tt>''': send carriage return character (start print on a new line)<br />
* '''<tt>$SERIE</tt>''': send the complete QTC block (WAEDC only)<br />
<br />
==Action==<br />
* '''<tt>$CR</tt>''': works like hitting ['''<tt>Enter</tt>'''] (log QSO)<br />
* '''<tt>$GRAB1</tt>''' - '''<tt>$GRAB9</tt>''': Grabs spot 1 to 9 from the [[Menu:Windows#Partner|Partner window]] and inserts it in the callsign field. <br />
* '''<tt>$GRABRT1</tt>''' - '''<tt>$GRABRT3</tt>''': Grabs realtime spot 1 to 3 from the [[Menu:Windows#Partner|Partner window]] and inserts it in the callsign field. <br />
* '''<tt>$GRABPARTNER</tt>''': grabs the first callsign from the [[Menu:Windows#Partner|Partner window]] and inserts it in the callsign field. See usage notes under [[Menu:Windows#Partner|Partner window]].<br />
* '''<tt>$GRABSPOT</tt>''': grabs spot on the current frequency<br />
* '''<tt>$GUESSEXCH</tt>''' (or '''<tt>$GUESSEXCHANGE</tt>'''): mimics a space bar hit, filling the exchange field(s) if possible, but the cursor remains in the same edit field.<br />
* '''<tt>$REPEAT</tt>''': restarts the [[Menu:Tools#Automatic_CQ_repeat|automatic repeating CQ]] sequence (if enabled), after pausing for the specified interval. Most useful at the end of the [[Menu:Options#Modify_standard_messages...|'''<tt>[Plus]</tt>''' key message]] to avoid having to press [F1] to start CQing again.<br />
* '''<tt>$RSTEXCHSENT</tt>''': Resets the "exchangeSent" flag of the active QSO (useful only for [[API#ESM_Script_.28embedded_into_Win-Test.29|ESM scripts]])<br />
* '''<tt>$SETEXCHSENT</tt>''': Sets the "exchangeSent" flag of the active QSO (useful only for [[API#ESM_Script_.28embedded_into_Win-Test.29|ESM scripts]])<br />
* '''<tt>$SPACEBAR</tt>''': works like hitting spacebar-key (move cursor to the next most-used field)<br />
* '''<tt>$TAB</tt>''': works like hitting ['''<tt>Tab</tt>'''] (move cursor to next field)<br />
<br />
==SO2R==<br />
* '''<tt>$ALTERNATECQ</tt>''' (or '''<tt>$ACQ</tt>'''): swaps primary and secondary radios and send CQ on the secondary radio<br />
* '''<tt>$CQ</tt>''': same as '''<tt>$ALTERNATECQ</tt>''' but does not swap radios<br />
* '''<tt>$LATCH</tt>''': sets latch mode<br />
* '''<tt>$MK2R=''cmd''</tt>''': send a specific MK2R command to the microHAM MK2R SO2R box. See [[Supported_Accessories#Integrated_SO2R_boxes|Integrated_SO2R_boxes]] for usage notes.<br />
* '''<tt>$R1R1</tt>''': set audio of Radio 1 to left and right ear<br />
* '''<tt>$R1R2</tt>''': set audio of Radio 1 to left and audio of Radio 2 to right ear<br />
* '''<tt>$R2R1</tt>''': set audio of Radio 2 to left and audio of Radio 1 to right ear<br />
* '''<tt>$R2R2</tt>''': set audio of Radio 2 to left and right ear<br />
* '''<tt>$RESET</tt>''': cancels any manual change made in the audio control<br />
* '''<tt>$TR1</tt>''': transmit on primary radio<br />
* '''<tt>$TR2</tt>''': transmit on secondary radio<br />
<br />
==WAEDC QTC related==<br />
* '''<tt>$CALLSIGN</tt>''': send callsign of the current QTC <br />
* '''<tt>$DONE</tt>''': if all QTC are sent: mimic the '''<tt>[+]</tt>''' key <br />
* '''<tt>$FIELD</tt>''': this variable takes the value "GROUP", "TIME", "CL" or "NR", depending on the kind of QTC field where the cursor is located<br />
* '''<tt>$GRNR</tt>''': sends group & number of the received QTC<br />
* '''<tt>$NEXT</tt>''': move focus to the next QTC line <br />
* '''<tt>$QTC</tt>''': sends group & number of the transmitted QTC <br />
* '''<tt>$QTCROW</tt>''': Row number of cursor location in the QTC window. Very useful to create a function key sending the message '''<tt>PSE RPT QTC NR $QTCROW $QTCROW</tt>''' in WAEDC RTTY to request repetition of a specific QTC. <br />
* '''<tt>$SERIAL</tt>''': send serial number of the current QTC <br />
* '''<tt>$SERIE</tt>''': send the complete QTC block (specific to RTTY) <br />
* '''<tt>$TIME</tt>''': send time of the current QTC <br />
* '''<tt>$VALID</tt>''': save everything and close the window <br />
<br />
[[Main Page|Back to Main Page]]<br />
<br />
==Custom variables==<br />
The user may define "custom" variables with any unused name. They can be used in messages and easily updated while operating. They are mostly intended for the DXPedition mode, but they work for all CW and RTTY logs.<br />
<br />
For example, one could define<br />
* '''<tt>$REGION</tt>''' as "EU", "NA", etc.<br />
* '''<tt>$UP</tt>''' as "UP" or "UP 5"<br />
<br />
See [[Menu:Options#Custom_variables...|Options | CW | Custom variables...]] for usage notes.</div>N6TVhttps://docs.win-test.com/w/index.php?title=Message_variables&diff=4577Message variables2016-08-26T15:34:46Z<p>N6TV: /* CW / RTTY automation */ Fix HTML syntax from previous update</p>
<hr />
<div><big><big>Messages Variables</big></big><br />
<!-- Adopted to Stylesheet DL6RAI --><br />
<br />
These variables can be used in programming CW messages using the F-keys. Some of these variables do not actually create output but rather perform actions at specific points in time, like the '''<tt>$CR</tt>''' symbol.<br />
<br />
==CW / RTTY automation==<br />
* '''<tt>$CHECK</tt>''': send license year (ARRL SS only)<br />
* '''<tt>$CORRECT</tt>''': sends a call correction, if any (see [[Menu:Options#Correction|correction]])<br />
* '''<tt>$CURRENT</tt>''' (or '''<tt>$CURRENTCALL</tt>'''): Sends the callsign of the current QSO ''despite'' the presence of a $CR later in the message. The $CR (carriage return) is always executed on message keypress. See [[Menu:Windows#Partner|Windows | Partner]] for usage examples. It is also useful in ESM (Enter Sends Message) mode in lieu of $LOGGEDCALL.<br />
* '''<tt>$F1...$F7</tt>''': sends the message associated with F1 ... F7 function key<br />
* '''<tt>$FREQ''nn''</tt>''': Where ''nn'' is a band (e.g. $FREQ160, $FREQ80 etc.). Useful in a multi-op as a canned message "PSE QSY $FREQ15". Sends the frequency of the primary radio of the first networked station found on this band with the following priority : R, R+, M, and M+. In addition, in CW, if the frequency is within 100 Hz of a kHz boundary, the decimal point is omitted, e.g. 14021.09 is sent as 14021 and 14021.10 is sent as 14021R1.<br />
* '''<tt>$FREQP</tt>''': contains the frequency of the primary radio (useful for passing mults)<br />
* '''<tt>$FREQS</tt>''': contains the frequency of the secondary radio (useful for passing mults)<br />
* '''<tt>$GRIDFIELD</tt>''' (or <tt>'''$LOC4</tt>''', <tt>'''$GRID4</tt>'''): contains the 4-char QTH locator (Maidenhead square) of the entrant<br />
* '''<tt>$GRIDSQUARE</tt>''' (or <tt>'''$LOC6</tt>''', <tt>'''$GRID6</tt>'''): contains the 6-char QTH locator (Maidenhead square) of the entrant<br />
* '''<tt>$INSERT</tt>''': sends message in the ['''<tt>Ins</tt>'''] key<br />
* '''<tt>$ISLAND</tt>''': sends IOTA Reference (i.e. EU001, AF001, ...) (IOTA Contest)<br />
* '''<tt>$LOGGED</tt>''' (or '''<tt>$LOGGEDCALL</tt>'''): sends what is typed in the callsign field of the current QSO, or if blank, the previous QSO<br />
* '''<tt>$MSG1...$MSG12</tt>''': sends additional CW messages (see [[Menu:Options#Modify additional messages|Modify additional messages]])<br />
* '''<tt>$MYCALL</tt>''': sends callsign set in [[New Log#Step 2: Setup your log|contest configuration]]<br />
* '''<tt>$MYNAME</tt>''': sends operator name, set in [[New Log#Step 2: Setup your log|contest configuration]]<br />
* '''<tt>$NEXT</tt>''' (or '''<tt>$NEXTCALL</tt>'''): sends the callsign of the next QSO line when a $CR is included in the message.<br />
* '''<tt>$NEXTSERIAL</tt>''': sends next QSO serial number (current QSO serial number plus 1)<br />
* '''<tt>$PLUS</tt>''': sends message in the ['''<tt>+</tt>'''] key <br />
* '''<tt>$PREV</tt>''' (or <tt>'''$PREVCALL</tt>'''): sends the callsign on the previous QSO line.<br />
* '''<tt>$PREVSERIAL</tt>''': sends previous QSO serial number (current QSO serial number minus 1)<br />
* '''<tt>$QQSLC</tt>''': sends Quick QSL message based QSOs made (see [[Menu:Tools#Intelligent Quick QSL...|Intelligent Quick QSL]])<br />
* '''<tt>$QQSLT</tt>''': sends Quick QSL message based on time passed (see [[Menu:Tools#Intelligent Quick QSL...|Intelligent Quick QSL]])<br />
* '''<tt>$QQSLRESET</tt>''': reset the timer or the counter like if the long QSL message were just sent.<br />
* '''<tt>$QSOB4</tt>''': sends the QSOB4 message and cancels the remainder of the current message, if the current QSO is a dupe, otherwise sends nothing (see [[Menu:Options#Modify standard messages...|Modify standard messages]])<br />
* '''<tt>$RST</tt>''': sends report from RST Sent field (normally '''<tt>5NN</tt>''')<br />
* '''<tt>$SERIAL</tt>''': sends current QSO Serial Number, or previous serial number if the line with the cursor is blank.<br />
* '''<tt>$STATE</tt>''': sends State/Province set in [[New Log#Step 2: Setup your log|contest configuration]] (Exchange)<br />
* '''<tt>$YEAR</tt>''': sends year nr set in [[New Log#Step 2: Setup your log|contest configuration]] (i.e. EUHFC, AA)<br />
* '''<tt>$ZONE</tt>''': sends zone nr set in [[New Log#Step 2: Setup your log|contest configuration]]<br />
* '''<tt>&''xy''</tt>''': sends a [http://en.wikipedia.org/wiki/Prosigns_for_Morse_code Morse prosign] where ''xy'' represents the two characters forming the prosign, e.g. &AS, &AR, &BK, &BT, &CL, &KN, &SK, etc.<br />
* '''<tt>+</tt>''': increase speed by 4 wpm<br />
* '''<tt>-</tt>''': decrease speed by 4 wpm<br />
* '''<tt>^</tt>''': the halfspace character with 1/2 dot duration<br />
* '''<tt>~</tt>''': (tilde) at then end of a variable means "no space" will be inserted, e.g. $NEXT~? sends the next callsign followed by a question mark, with no space in between<br />
<br />
==RTTY only==<br />
* '''<tt>$13</tt>''': send carriage return character (start print on a new line)<br />
* '''<tt>$SERIE</tt>''': send the complete QTC block (WAEDC only)<br />
<br />
==Action==<br />
* '''<tt>$CR</tt>''': works like hitting ['''<tt>Enter</tt>'''] (log QSO)<br />
* '''<tt>$GRAB1</tt>''' - '''<tt>$GRAB9</tt>''': Grabs spot 1 to 9 from the [[Menu:Windows#Partner|Partner window]] and inserts it in the callsign field. <br />
* '''<tt>$GRABRT1</tt>''' - '''<tt>$GRABRT3</tt>''': Grabs realtime spot 1 to 3 from the [[Menu:Windows#Partner|Partner window]] and inserts it in the callsign field. <br />
* '''<tt>$GRABPARTNER</tt>''': grabs the first callsign from the [[Menu:Windows#Partner|Partner window]] and inserts it in the callsign field. See usage notes under [[Menu:Windows#Partner|Partner window]].<br />
* '''<tt>$GRABSPOT</tt>''': grabs spot on the current frequency<br />
* '''<tt>$GUESSEXCH</tt>''' (or '''<tt>$GUESSEXCHANGE</tt>'''): mimics a space bar hit, filling the exchange field(s) if possible, but the cursor remains in the same edit field.<br />
* '''<tt>$REPEAT</tt>''': restarts the [[Menu:Tools#Automatic_CQ_repeat|automatic repeating CQ]] sequence (if enabled), after pausing for the specified interval. Most useful at the end of the [[Menu:Options#Modify_standard_messages...|'''<tt>[Plus]</tt>''' key message]] to avoid having to press [F1] to start CQing again.<br />
* '''<tt>$RSTEXCHSENT</tt>''': Resets the "exchangeSent" flag of the active QSO (useful only for [[API#ESM_Script_.28embedded_into_Win-Test.29|ESM scripts]])<br />
* '''<tt>$SETEXCHSENT</tt>''': Sets the "exchangeSent" flag of the active QSO (useful only for [[API#ESM_Script_.28embedded_into_Win-Test.29|ESM scripts]])<br />
* '''<tt>$SPACEBAR</tt>''': works like hitting spacebar-key (move cursor to the next most-used field)<br />
* '''<tt>$TAB</tt>''': works like hitting ['''<tt>Tab</tt>'''] (move cursor to next field)<br />
<br />
==SO2R==<br />
* '''<tt>$ALTERNATECQ</tt>''' (or '''<tt>$ACQ</tt>'''): swaps primary and secondary radios and send CQ on the secondary radio<br />
* '''<tt>$CQ</tt>''': same as '''<tt>$ALTERNATECQ</tt>''' but does not swap radios<br />
* '''<tt>$LATCH</tt>''': sets latch mode<br />
* '''<tt>$MK2R=''cmd''</tt>''': send a specific MK2R command to the microHAM MK2R SO2R box. See [[Supported_Accessories#Integrated_SO2R_boxes|Integrated_SO2R_boxes]] for usage notes.<br />
* '''<tt>$R1R1</tt>''': set audio of Radio 1 to left and right ear<br />
* '''<tt>$R1R2</tt>''': set audio of Radio 1 to left and audio of Radio 2 to right ear<br />
* '''<tt>$R2R1</tt>''': set audio of Radio 2 to left and audio of Radio 1 to right ear<br />
* '''<tt>$R2R2</tt>''': set audio of Radio 2 to left and right ear<br />
* '''<tt>$RESET</tt>''': cancels any manual change made in the audio control<br />
* '''<tt>$TR1</tt>''': transmit on primary radio<br />
* '''<tt>$TR2</tt>''': transmit on secondary radio<br />
<br />
==WAEDC QTC related==<br />
* '''<tt>$CALLSIGN</tt>''': send callsign of the current QTC <br />
* '''<tt>$DONE</tt>''': if all QTC are sent: mimic the '''<tt>[+]</tt>''' key <br />
* '''<tt>$FIELD</tt>''': this variable takes the value "GROUP", "TIME", "CL" or "NR", depending on the kind of QTC field where the cursor is located<br />
* '''<tt>$GRNR</tt>''': sends group & number of the received QTC<br />
* '''<tt>$NEXT</tt>''': move focus to the next QTC line <br />
* '''<tt>$QTC</tt>''': sends group & number of the transmitted QTC <br />
* '''<tt>$QTCROW</tt>''': Row number of cursor location in the QTC window. Very useful to create a function key sending the message '''<tt>PSE RPT QTC NR $QTCROW $QTCROW</tt>''' in WAEDC RTTY to request repetition of a specific QTC. <br />
* '''<tt>$SERIAL</tt>''': send serial number of the current QTC <br />
* '''<tt>$SERIE</tt>''': send the complete QTC block (specific to RTTY) <br />
* '''<tt>$TIME</tt>''': send time of the current QTC <br />
* '''<tt>$VALID</tt>''': save everything and close the window <br />
<br />
[[Main Page|Back to Main Page]]<br />
<br />
==Custom variables==<br />
The user may define "custom" variables with any unused name. They can be used in messages and easily updated while operating. They are mostly intended for the DXPedition mode, but they work for all CW and RTTY logs.<br />
<br />
For example, one could define<br />
* '''<tt>$REGION</tt>''' as "EU", "NA", etc.<br />
* '''<tt>$UP</tt>''' as "UP" or "UP 5"<br />
<br />
See [[Menu:Options#Custom_variables...|Options | CW | Custom variables...]] for usage notes.</div>N6TVhttps://docs.win-test.com/w/index.php?title=Message_variables&diff=4576Message variables2016-08-26T15:33:30Z<p>N6TV: /* CW / RTTY automation */ Added $LOC4, $GRID4, $LOC6, $GRID6 (new in WT 4.22)</p>
<hr />
<div><big><big>Messages Variables</big></big><br />
<!-- Adopted to Stylesheet DL6RAI --><br />
<br />
These variables can be used in programming CW messages using the F-keys. Some of these variables do not actually create output but rather perform actions at specific points in time, like the '''<tt>$CR</tt>''' symbol.<br />
<br />
==CW / RTTY automation==<br />
* '''<tt>$CHECK</tt>''': send license year (ARRL SS only)<br />
* '''<tt>$CORRECT</tt>''': sends a call correction, if any (see [[Menu:Options#Correction|correction]])<br />
* '''<tt>$CURRENT</tt>''' (or '''<tt>$CURRENTCALL</tt>'''): Sends the callsign of the current QSO ''despite'' the presence of a $CR later in the message. The $CR (carriage return) is always executed on message keypress. See [[Menu:Windows#Partner|Windows | Partner]] for usage examples. It is also useful in ESM (Enter Sends Message) mode in lieu of $LOGGEDCALL.<br />
* '''<tt>$F1...$F7</tt>''': sends the message associated with F1 ... F7 function key<br />
* '''<tt>$FREQ''nn''</tt>''': Where ''nn'' is a band (e.g. $FREQ160, $FREQ80 etc.). Useful in a multi-op as a canned message "PSE QSY $FREQ15". Sends the frequency of the primary radio of the first networked station found on this band with the following priority : R, R+, M, and M+. In addition, in CW, if the frequency is within 100 Hz of a kHz boundary, the decimal point is omitted, e.g. 14021.09 is sent as 14021 and 14021.10 is sent as 14021R1.<br />
* '''<tt>$FREQP</tt>''': contains the frequency of the primary radio (useful for passing mults)<br />
* '''<tt>$FREQS</tt>''': contains the frequency of the secondary radio (useful for passing mults)<br />
* '''<tt>$GRIDFIELD</tt>''' (or <tt>'''$LOC4</tt>''', '''$GRID4</tt>'''): contains the 4-char QTH locator (Maidenhead square) of the entrant<br />
* '''<tt>$GRIDSQUARE</tt>''' (or <tt>'''$LOC6</tt>''', '''$GRID6</tt>'''): contains the 6-char QTH locator (Maidenhead square) of the entrant<br />
* '''<tt>$INSERT</tt>''': sends message in the ['''<tt>Ins</tt>'''] key<br />
* '''<tt>$ISLAND</tt>''': sends IOTA Reference (i.e. EU001, AF001, ...) (IOTA Contest)<br />
* '''<tt>$LOGGED</tt>''' (or '''<tt>$LOGGEDCALL</tt>'''): sends what is typed in the callsign field of the current QSO, or if blank, the previous QSO<br />
* '''<tt>$MSG1...$MSG12</tt>''': sends additional CW messages (see [[Menu:Options#Modify additional messages|Modify additional messages]])<br />
* '''<tt>$MYCALL</tt>''': sends callsign set in [[New Log#Step 2: Setup your log|contest configuration]]<br />
* '''<tt>$MYNAME</tt>''': sends operator name, set in [[New Log#Step 2: Setup your log|contest configuration]]<br />
* '''<tt>$NEXT</tt>''' (or '''<tt>$NEXTCALL</tt>'''): sends the callsign of the next QSO line when a $CR is included in the message.<br />
* '''<tt>$NEXTSERIAL</tt>''': sends next QSO serial number (current QSO serial number plus 1)<br />
* '''<tt>$PLUS</tt>''': sends message in the ['''<tt>+</tt>'''] key <br />
* '''<tt>$PREV</tt>''' (or <tt>'''$PREVCALL</tt>'''): sends the callsign on the previous QSO line.<br />
* '''<tt>$PREVSERIAL</tt>''': sends previous QSO serial number (current QSO serial number minus 1)<br />
* '''<tt>$QQSLC</tt>''': sends Quick QSL message based QSOs made (see [[Menu:Tools#Intelligent Quick QSL...|Intelligent Quick QSL]])<br />
* '''<tt>$QQSLT</tt>''': sends Quick QSL message based on time passed (see [[Menu:Tools#Intelligent Quick QSL...|Intelligent Quick QSL]])<br />
* '''<tt>$QQSLRESET</tt>''': reset the timer or the counter like if the long QSL message were just sent.<br />
* '''<tt>$QSOB4</tt>''': sends the QSOB4 message and cancels the remainder of the current message, if the current QSO is a dupe, otherwise sends nothing (see [[Menu:Options#Modify standard messages...|Modify standard messages]])<br />
* '''<tt>$RST</tt>''': sends report from RST Sent field (normally '''<tt>5NN</tt>''')<br />
* '''<tt>$SERIAL</tt>''': sends current QSO Serial Number, or previous serial number if the line with the cursor is blank.<br />
* '''<tt>$STATE</tt>''': sends State/Province set in [[New Log#Step 2: Setup your log|contest configuration]] (Exchange)<br />
* '''<tt>$YEAR</tt>''': sends year nr set in [[New Log#Step 2: Setup your log|contest configuration]] (i.e. EUHFC, AA)<br />
* '''<tt>$ZONE</tt>''': sends zone nr set in [[New Log#Step 2: Setup your log|contest configuration]]<br />
* '''<tt>&''xy''</tt>''': sends a [http://en.wikipedia.org/wiki/Prosigns_for_Morse_code Morse prosign] where ''xy'' represents the two characters forming the prosign, e.g. &AS, &AR, &BK, &BT, &CL, &KN, &SK, etc.<br />
* '''<tt>+</tt>''': increase speed by 4 wpm<br />
* '''<tt>-</tt>''': decrease speed by 4 wpm<br />
* '''<tt>^</tt>''': the halfspace character with 1/2 dot duration<br />
* '''<tt>~</tt>''': (tilde) at then end of a variable means "no space" will be inserted, e.g. $NEXT~? sends the next callsign followed by a question mark, with no space in between<br />
<br />
==RTTY only==<br />
* '''<tt>$13</tt>''': send carriage return character (start print on a new line)<br />
* '''<tt>$SERIE</tt>''': send the complete QTC block (WAEDC only)<br />
<br />
==Action==<br />
* '''<tt>$CR</tt>''': works like hitting ['''<tt>Enter</tt>'''] (log QSO)<br />
* '''<tt>$GRAB1</tt>''' - '''<tt>$GRAB9</tt>''': Grabs spot 1 to 9 from the [[Menu:Windows#Partner|Partner window]] and inserts it in the callsign field. <br />
* '''<tt>$GRABRT1</tt>''' - '''<tt>$GRABRT3</tt>''': Grabs realtime spot 1 to 3 from the [[Menu:Windows#Partner|Partner window]] and inserts it in the callsign field. <br />
* '''<tt>$GRABPARTNER</tt>''': grabs the first callsign from the [[Menu:Windows#Partner|Partner window]] and inserts it in the callsign field. See usage notes under [[Menu:Windows#Partner|Partner window]].<br />
* '''<tt>$GRABSPOT</tt>''': grabs spot on the current frequency<br />
* '''<tt>$GUESSEXCH</tt>''' (or '''<tt>$GUESSEXCHANGE</tt>'''): mimics a space bar hit, filling the exchange field(s) if possible, but the cursor remains in the same edit field.<br />
* '''<tt>$REPEAT</tt>''': restarts the [[Menu:Tools#Automatic_CQ_repeat|automatic repeating CQ]] sequence (if enabled), after pausing for the specified interval. Most useful at the end of the [[Menu:Options#Modify_standard_messages...|'''<tt>[Plus]</tt>''' key message]] to avoid having to press [F1] to start CQing again.<br />
* '''<tt>$RSTEXCHSENT</tt>''': Resets the "exchangeSent" flag of the active QSO (useful only for [[API#ESM_Script_.28embedded_into_Win-Test.29|ESM scripts]])<br />
* '''<tt>$SETEXCHSENT</tt>''': Sets the "exchangeSent" flag of the active QSO (useful only for [[API#ESM_Script_.28embedded_into_Win-Test.29|ESM scripts]])<br />
* '''<tt>$SPACEBAR</tt>''': works like hitting spacebar-key (move cursor to the next most-used field)<br />
* '''<tt>$TAB</tt>''': works like hitting ['''<tt>Tab</tt>'''] (move cursor to next field)<br />
<br />
==SO2R==<br />
* '''<tt>$ALTERNATECQ</tt>''' (or '''<tt>$ACQ</tt>'''): swaps primary and secondary radios and send CQ on the secondary radio<br />
* '''<tt>$CQ</tt>''': same as '''<tt>$ALTERNATECQ</tt>''' but does not swap radios<br />
* '''<tt>$LATCH</tt>''': sets latch mode<br />
* '''<tt>$MK2R=''cmd''</tt>''': send a specific MK2R command to the microHAM MK2R SO2R box. See [[Supported_Accessories#Integrated_SO2R_boxes|Integrated_SO2R_boxes]] for usage notes.<br />
* '''<tt>$R1R1</tt>''': set audio of Radio 1 to left and right ear<br />
* '''<tt>$R1R2</tt>''': set audio of Radio 1 to left and audio of Radio 2 to right ear<br />
* '''<tt>$R2R1</tt>''': set audio of Radio 2 to left and audio of Radio 1 to right ear<br />
* '''<tt>$R2R2</tt>''': set audio of Radio 2 to left and right ear<br />
* '''<tt>$RESET</tt>''': cancels any manual change made in the audio control<br />
* '''<tt>$TR1</tt>''': transmit on primary radio<br />
* '''<tt>$TR2</tt>''': transmit on secondary radio<br />
<br />
==WAEDC QTC related==<br />
* '''<tt>$CALLSIGN</tt>''': send callsign of the current QTC <br />
* '''<tt>$DONE</tt>''': if all QTC are sent: mimic the '''<tt>[+]</tt>''' key <br />
* '''<tt>$FIELD</tt>''': this variable takes the value "GROUP", "TIME", "CL" or "NR", depending on the kind of QTC field where the cursor is located<br />
* '''<tt>$GRNR</tt>''': sends group & number of the received QTC<br />
* '''<tt>$NEXT</tt>''': move focus to the next QTC line <br />
* '''<tt>$QTC</tt>''': sends group & number of the transmitted QTC <br />
* '''<tt>$QTCROW</tt>''': Row number of cursor location in the QTC window. Very useful to create a function key sending the message '''<tt>PSE RPT QTC NR $QTCROW $QTCROW</tt>''' in WAEDC RTTY to request repetition of a specific QTC. <br />
* '''<tt>$SERIAL</tt>''': send serial number of the current QTC <br />
* '''<tt>$SERIE</tt>''': send the complete QTC block (specific to RTTY) <br />
* '''<tt>$TIME</tt>''': send time of the current QTC <br />
* '''<tt>$VALID</tt>''': save everything and close the window <br />
<br />
[[Main Page|Back to Main Page]]<br />
<br />
==Custom variables==<br />
The user may define "custom" variables with any unused name. They can be used in messages and easily updated while operating. They are mostly intended for the DXPedition mode, but they work for all CW and RTTY logs.<br />
<br />
For example, one could define<br />
* '''<tt>$REGION</tt>''' as "EU", "NA", etc.<br />
* '''<tt>$UP</tt>''' as "UP" or "UP 5"<br />
<br />
See [[Menu:Options#Custom_variables...|Options | CW | Custom variables...]] for usage notes.</div>N6TVhttps://docs.win-test.com/w/index.php?title=Menu:Edit&diff=4575Menu:Edit2016-08-18T02:31:34Z<p>N6TV: /* Delete QSO */ Expand and correction description of QSO deletion process, fix link to Clean Log and other typos.</p>
<hr />
<div><big><big>Menu:Edit</big></big><br />
<!-- Adopted to Stylesheet DL6RAI --><br />
<br />
==Restore QSO==<br />
Shortcut: '''<tt>Ctrl-Z</tt>'''. Allows you to restore all the original data of a QSO you are modifying.<br />
Of course, the QSO you are modifying must already be logged before you use this command. It is most useful if you accidentally change something on a prior QSO, and wish to restore it.<br />
<br />
==Initialize QSO==<br />
Shortcut: '''<tt>[F11]</tt>''' or '''<tt>Alt-W</tt>'''. Erases all the fields of the current QSO if it has not been confirmed. However, this key will not delete a QSO that has already been logged with ['''<tt>Enter</tt>''']!<br />
<br />
However, the best way to "delete" a QSO is to do it after the end of the contest, in the final log files. Otherwise, you can enter your own callsign instead (and clear it afterwards with [[Menu:File_new#Clean log|File Clean log...]]), but this may create errors in the multipliers list. A better way is to duplicate the previous QSO, on the same band. It will be one more dupe QSO, but the points and the mutipliers will be correct.<br />
<br />
==Edit Date, Time, Freq. and Op. of QSO...==<br />
Shortcut: '''<tt>Alt-F</tt>'''.<br />
Allows you to modify the date, time, frequency and operator of an already logged QSO. Note that you can only change the frequency on the same band. If you need to change bands, use '''<tt>Alt+F1</tt>''' or '''<tt>Alt+F2</tt>''' (see [[Menu:Commands#QSY|QSY]]).<br />
[[Image:EditDateTimeFrequency.png|frame|center|Editing QSO date and time and frequency]]<br clear=all><br />
'''Warning''': After a modification, Win-Test does not sort the logged QSO by time. The logging sequence by numbers is kept.<br />
<br />
If you need to move your log, or a portion of it, ahead or back in time, please refer to the Tools [[Menu:Tools#Time_shifting|time shifting]] feature in this manual.<br />
<br />
==Edit serial number==<br />
This opens the edit serial dialog box. Here you can change your sent serial number.<br />
[[Image:editserial.png|frame|center|Editing the serial number]]<br />
<br />
==Delete QSO==<br />
Permanently deletes a QSO in the log. As noted below, this command is irreversible. Note that you cannot delete QSOs unless log synchronization is disabled (see [[Menu:Options#Disable_log_synchronization_on_network|Options | Disable log synchronization on network]]).<br />
<br />
[[Image:DeleteAQSO.png|frame|center|Deleting A QSO from the log. This feature is not supported when log synchronization is enabled, such as in a multi-computer network.]]<br />
<br />
However, the best way is to [[Menu:Messages#Write_a_note_regarding_this_QSO|make a note via '''<tt>Alt-N</tt>''']], then delete the QSO after the end of the contest, in the Win-Test file or the Cabrillo/ADIF files. Another option is to enter your own callsign in the logging window, then remove it after the contest with [[Menu:File_new#Clean_log|File | Clean log...]].<br />
<br />
Yet another option is to duplicate the previous QSO. It will be one more dupe QSO, but the points and the multipliers will be correct.<br />
<br />
==Delete all QSO...==<br />
Equivalent [[Text commands#List of Text Commands|text command]]: '''<tt>CLEARLOG</tt>'''.<br><br />
See also the '''<tt>CLEARLOGNOW</tt>''' and '''<tt>COPYLOGCLEAR</tt>''' [[Text_commands#Open.2FClose.2FDatabase_Functions|text commands]], which may be more convenient if you understand what they do.<br><br />
<br />
This command deletes all the QSOs in the current opened file. Of course, as this should be rather unusual, you need to confirm the command.<br />
[[Image:DeleteAllQSO.png|frame|center|Deleting all QSOs]]<br />
You need to literally type '''<tt>OK</tt>''' (uppercase) in the box, and then press '''<tt>[Validate]</tt>''' to delete all QSOs.<br />
<br />
==Goto QSO...==<br />
Presents the dialog allowing to go directly to a QSO (if you know its number).<br />
<br />
[[Image:gotoQSO.png|frame|center|Goto QSO]]<br />
<br />
With the two labelled buttons, you can locate the cursor at the begining or at the end of the log. Same action will result by typing '''<tt>START</tt>''' (or '''<tt>FIRST</tt>''') and '''<tt>END</tt>''' (or '''<tt>LAST</tt>''') in the callsign logging field.<br />
<br />
You can also locate the cursor on the desired QSO number just by typing this number in the callsign logging field and use this menu item, or by using its shortcut ('''<tt>Ctrl-G</tt>''') for backward CT compatibility.<br />
<br />
When you have jumped to a specific QSO, Win-Test will not let you move away unless there is a valid call in the callsign field and a valid exchange in the report field. If you inadvertedly delete the callsign or report, press '''<tt>Ctrl-Z</tt>''' to undo the change.<br />
<br />
==Move in my log only==<br />
Only useful in a multi-operating environment. Checking this option will allow the operator to step through QSOs in his own log, using the '''<tt>[up arrow]</tt>''' and '''<tt>[down arrow]</tt>''' keys. This makes it much easier to correct the last QSO logged, since the cursor skips over QSOs being logged by other computers in the network.<br />
<br />
If this option is checked, you can still move to any QSO by pressing '''<tt>[Shift]-[Up arrow]</tt>''' and '''<tt>[Shift]-[down arrow]</tt>'''. On the other hand, if this option is unchecked, using these key combinations will navigate to QSOs made in your log only.<br />
<br />
[[Menus|Back to Menus]]</div>N6TVhttps://docs.win-test.com/w/index.php?title=Menu:Options&diff=4574Menu:Options2016-08-18T02:18:02Z<p>N6TV: /* Disable log synchronization on network */ Explain that NOSYNC doesn't block QSOs from other computers.</p>
<hr />
<div><big><big>Menu:Options</big></big><br />
<!-- Adopted to Stylesheet DL6RAI --><br />
<br />
==Load contest at startup==<br />
<code>Options | Load contest at startup</code><br><br />
Enables or disables the automatic loading of the last contest file in use. <br />
This command is useful to get on line again quickly if - for some reason - Win-Test <br />
crashed or you had to quit the Win-Test in the middle of the contest.<br />
<br />
If you like to switch to another file, close this file using <br />
<code>File | Close</code> and then <code>File | Open</code> menu dialog.<br />
<br />
If Win-Test is started with the '''<tt>[Ctrl]</tt>''' key down, it doesn't automatically load the previous log.<br />
<br />
When starting Win-Test from the command line, use '''<tt>-n</tt>''' or '''<tt>--noautoload</tt>''' option to prevent automactially loading the last file in use.<br />
<br />
==Automatic backup...==<br />
<code>Options | Automatic backup...</code><br><br />
This function enables or disables the automatic backup of the <tt>.wtb</tt> file to another location, e.g. network drive or removable media like an USB stick. You can choose an automatic backup interval between 1 and 120 minutes. If a backup fails, you are prompted if you wish to disable the backup.<br />
<br />
Optionally a different (time-stamped) filename will be used for every new backup file (actually a good idea for backing up to a network drive!). <br />
<br />
If the option "Always notify..." is ticked, an informal message will be displayed at the bottom of the screen after a backup run has finished. <br />
<br />
For DXpeditions it may be useful to automatically create a Logsearch File with every backup. In this case, tick the corresponding option.<br />
<br />
{{wbox|Note|Contrary to the WTB backup, the LogSearch exports are not done in a separate background thread. Thus, it is not recommended to enable this option on a running station because WT will be unavailable for logging for a while every time an export is in progress.}}<br />
<br />
[[Image:AutomaticBackup.PNG|center|frame|Setting up Automatic Backup]]<br />
<br />
Here is some additional advice:<br />
<br />
* Backups are processed in a separate thread, meaning that you will not even notice that a backup is in progress! No slowdown, no keyboard blocking etc...<br />
<br />
* Of course, it makes sense to backup to a different volume than your "working" drive. This avoids loss of everything if your hard disk fails. Do not smile... It happens, sometimes! (ARRL SSB 2002 FY5KE, IIRC!)<br />
<br />
* Once you entered the last QSO, for safety, generate your Cabrillo log(s) before exiting. A simple "MAKELOG" command opens the appropriate dialog.<br />
<br />
* In all cases, always make a copy of a file when you want to use/test/modify it. Always keep a backup, never use the original! If you have FTP access somewhere, copy the file there as soon as possible! If your computer crashes, you still will have a safe copy.<br />
<br />
Call me paranoid, but believe me, you need to loose some day a '''very''' big chunk of data to understand the importance of backups!<br />
<br />
==Disable log synchronization on network==<br />
<code>Options | Disable log synchronization on network</code>'''<br><br />
<br />
Text command shortcuts: '''<tt>NOSYNC</tt>''' | '''<tt>SYNC</tt>'''<br />
<br />
When selected, this option disables automatic background log synchronization over the network. It is only useful under certain circumstances, such as [[Multi-op/Clearing_all_logs_before_the_start|Clearing all logs before the start]] or [[Menu:Edit#Delete_QSO|deleting individual QSOs from a log]] when single-op, and using only one computer, because QSOs cannot be removed from a log when log synchronization is enabled.<br />
<br />
'''This option does not prevent QSOs logged on other computers from being added to the current log'''; it only stops the background synchronization of any "missing" QSOs, which reduces network traffic when needed, such as when using very slow legacy serial port networking.<br />
<br />
{{wbox|Note|Even when log sync is disabled via '''<tt>NOSYNC</tt>''', whenever a ''new'' QSO is made on another computer in the network, '''that QSO will still be added to all connected computers''' as soon as it is logged. The best way to keep ''all'' QSOs from other computers from appearing in a log is to use the '''Packet sharing only''' button in the [[Menu:Options#Network_Protocol_Advanced_Settings| Network Protocol Advanced Settings]] dialog.}}<br />
<br />
==CW==<br />
<code>Options | CW</code><br><br />
This menu item allows you to control different aspects of CW operation. It is enabled only when the selected operating mode is CW (otherwise it is greyed out).<br />
<br />
<br />
[[Image:CWSerialNumberAbbreviation.PNG|center|frame|CW Options submenus]]<br />
<br />
===No sound===<br />
<code>Options | CW | No sound</code><br><br />
If checked, no CW sound will be played through the internal speaker. This option is also available through the '''<tt>SOUND/NOSOUND</tt>''' text commands.<br />
<br />
====Note for some new Laptops====<br />
<br />
In some new generation Laptops, it is necessary to enable the PC Speaker in the BIOS to have it to work properly.<br />
<br />
Moreover, with some Sound systems, you have also to enable the PC Speaker in the "Volume Control".<br />
Here is how to do it:<br />
<br />
* Double click on the Speaker icon in the system tray<br />
* In the menu, select <code>Options | Properties</code>, and search for the PC Speaker Volume Control and enable it<br />
* Set the Volume slider to the appropriate sound level<br />
<br />
Unfortunately, some newer Laptops do not support the PC Speaker "beep" at all anymore... :(<br />
<br />
===Initial Speed===<br />
<code>Options | CW | Initial Speed</code><br><br />
Sets the initial CW speed for new files.<br />
<br />
===Modify standard messages...===<br />
<code>Options | CW | Modify standard messages...</code><br><br />
For quick access to this dialog, use the [[Text commands|text command]] '''<tt>MESSAGES</tt>''' or '''<tt>MSGS</tt>'''.<br><br />
The place to change the CW messages, both for Run and S&P mode. See [[Menu:Tools#Enable_Run.2FS.26P_switching|Enable Run/S&P Switching]].<br />
<br />
[[Image:CwStandardMessages.png|center|frame|Modifying CW messages; you may also edit the memories one by one using '''<tt>Shift+F1</tt>''', '''<tt>Shift+F2</tt>''' etc. ]]<br />
<br />
Please have a look at the list of [[Message_variables|message variables]] you can use in the CW memories to control different aspects of the operation.<br />
<br />
The Options tab of this window lets you redefine the $QSOB4 macro. The only variable that can be used in this field is $MYCALL, e.g. "QSO $MYCALL TEST".<br />
<br />
[[Image:CwStandardMessagesOptions.png|center|frame|CW messages options.]]<br />
<br />
Check '''Only use RUN Messages (ignore S&P Messages)''' to force Win-Test to use only one set of CW messages, regardless of operating mode.<br />
====Sprint Exchange Logic====<br />
Use '''Sprint Exchange Logic for the Insert key''' to signal to a listening station that you will take over the frequency after a QSO, by signing your call at the end of the exchange. When checked, pressing '''<tt>[Insert]</tt>''' sends the "Run Message" if the logged serial number field is blank, otherwise it sends the "Search & Pounce Message". This option only applies to the Sprint contests. It is ignored for other contests, so it may be left checked all the time.<br />
<br />
Here is example of how to set up the CW messages for the NA Sprint, with Sprint Exchange Logic enabled. Note the programming of the '''<tt>[Insert]</tt>''' message:<br />
<br />
[[Image:NA_Sprint_Messages.PNG|center|frame|Sample CW messages to be used for the NA Sprint, with Sprint Exchange Logic]]<br />
<br />
===Modify additional messages...===<br />
<code>Options | CW | Modify additional messages...</code><br><br />
The place to create or modify additional CW messages which can be accessed using '''<tt>Alt-C</tt>'''. These memories can be used for transmitting QSL information, special greetings, QSY/sked information. It also defines the macros $MSG1 to $MSG12 that may optionally be used as part of any standard CW message.<br />
<br />
[[Image:cw-additional-messages.png|center|frame|Additional CW messages that may be used occasionally like QSL info etc.]]<br />
<br />
===Modify WAE messages...===<br />
<code>Options | CW | Modify WAE messages...</code><br><br />
This function allows you to define CW message text which is available during transmit/receive of QTC traffic. The QTC<br />
window is specific to the WAE DX Contest and can be opened using '''<tt>ctrl-L</tt>''' (transmit QTCs) or <br />
'''<tt>Alt-L</tt>''' (receive QTCs). For more details of WAEDC, please see [[WAEDC]].<br />
<br />
[[Image:WaeMessagesTx.png|center|frame|Additional messages (transmit) for QTC handling in the Worked All Europe DX Contest.]]<br />
[[Image:WaeMessagesRx.png|center|frame|Additional messages (receive) for QTC handling in the Worked All Europe DX Contest.]]<br />
<br />
===Custom variables...===<br />
<code>Options | CW | Custom variables...</code><br><br />
For quick access to this dialog, use the [[Text commands|text command]] '''<tt>VARIABLES</tt>'''.<br><br />
[[Image:OptionsCWCustomVariables.PNG|center|frame|Custom message variables for DXpeditions or other purposes]]<br />
Mainly useful for DXPeditions, this feature allows you to create custom variables to be used in CW or RTTY messages.<br />
<br />
To define a new variable, double-click on the variable name or the words '''Not defined''', and follow the prompts. All variables can be used in CW or RTTY messages, (one common set of custom variables is used regardless of mode).<br />
<br />
For example, define [Plus] as<br />
'''$CORRECT TU $MYCALL $REGION$UP $CR'''<br />
then change the value of $REGION as required by typing REGION [Enter] in the callsign field of the main logging window and following the prompts.<br />
<br />
To rename a message variable, double-click on its name, and follow the prompts. To delete a message variable, rename it to an empty string.<br />
<br />
{{wbox|WARNING|Don't try to add a variable name that is already used by Win-Test or it won't work.}}<br />
<br />
===Serial number===<br />
<code>Options | CW | Serial number</code><br><br />
Equivalent [[Text_commands#CW_Functions|text commands]] are '''<tt>LZ</tt>, <tt>NOLZ</tt>, <tt>NOABBREV</tt>, <tt>SEMIABBREV</tt>, <tt>FULLABBREV</tt>''' and '''<tt>PROABBREV</tt>'''.<br><br />
<br />
'''Leading zeros''' - If checked, leading zeros for all serial numbers below 100 will be sent by Win-Test ([[Text_commands#CW_Functions|text commands]] '''<tt>LZ</tt>''' and '''<tt>NOLZ</tt>''')<br />
<br />
There are 5 possible abbreviation levels for the serial numbers:<br />
<br />
* '''Not abbreviated''' - all numbers are sent without any abbreviations or "cut numbers" ('''<tt>NOABBREV</tt>''')<br />
* '''Half abbreviated''' - only leading zeros are shortened to "T" ('''<tt>SEMIABBREV</tt>''')<br />
* '''Abbreviated''' - The 0 and the 9 are shortened to "T" and "N" ('''<tt>FULLABBREV</tt>''')<br />
* '''Pro''' - The 0, 1, 4, 5 and 9 are shortened to "T", "A", "V", "E" and "N" ('''<tt>PROABBREV</tt>''')<br />
* '''Custom''' - use the settings in the custom table. Each number can be shortened to a letter of your own choosing.<br />
<br />
'''Custom table...''' - displays the dialog shown below:<br />
[[Image:CWSerialNumberCustomTable.PNG|center|frame|Customized abbreviations for sending CW serial numbers sent by Win-Test. 0, 1, and 9 are shortened to "T", "A", and "N", but only leading zeros are abbreviated.]]<br />
This option only affects '''''serial numbers''''', not numbers within callsigns.<br />
<br />
===Correction===<br />
<code>Options | CW | Correction</code><br><br />
Equivalent to the [[Text commands#List of Text Commands|text commands]] '''<tt>CORRECT</tt>''' and '''<tt>NOCORRECT</tt>'''.<br> <br />
Controls the value of the '''<tt>$CORRECT</tt>''' [[Message_variables|message variable]]. When enabled, Win-Test automatically sends a call correction if the callsign sent ('''<tt>$LOGGEDCALL</tt>''') by the ['''<tt>Ins</tt>'''] key is changed before you press ['''<tt>+</tt>'''] to log the QSO. This is most useful when the ['''<tt>+</tt>'''] key is programmed with '''<tt>$CORRECT TU $MYCALL $CR</tt>''' or similar. '''<tt>NOCORRECT</tt>''' disables the feature.<br />
<br />
When "Smart correction" is enabled ([[Text_commands#List_of_Text_Commands|text command]]: '''<tt>SMART</tt>'''), Win-Test resends only what needs to be sent (prefix, suffix, or full call). When disabled ('''<tt>NOSMART</tt>'''), Win-Test sends the full callsign for all corrections .<br />
<br />
===Shortened spaces (CT spaces)===<br />
<code>Options | CW | Shortened spaces (CT spaces)</code><br><br />
Equivalent to the [[Text commands#List of Text Commands|text commands]] '''<tt>CTSPACE</tt>''' and '''<tt>NOCTSPACE</tt>'''.<br> <br />
The standard spacing between CW words is 7 dits length, instead of 6 (known as "CT space"). With this option you can set it back to 6 dits if you want, achieving slightly shorter spacing between words.<br />
<br />
===Auto sending...===<br />
<code>Options | CW | Auto sending...</code><br><br />
Equivalent to the [[Text_commands#List_of_Text_Commands|text commands]] '''<tt>CWAUTO</tt>''', '''<tt>NOCWAUTO</tt>'''/'''<tt>CWAUTOOFF</tt>''', '''<tt>CWAUTO3</tt>''', and '''<tt>CWAUTO4</tt>'''<br><br />
This lets Win-Test automatically send the ['''<tt>Insert</tt>'''] message as soon as some number of characters are entered in the callsign field, eliminating the need to press the ['''<tt>Ins</tt>'''] key to send an exchange.<br />
<br />
[[Image:OptionsCwAutoSending.png|frame|center|Configuring Auto sending]]<br />
<br />
When CW Auto Sending is enabled, if the cursor is in the callsign field, hitting '''<tt>[Escape]</tt>''' will disable Auto Sending for the current QSO if no CW is being transmitted. When you hit '''<tt>[Escape]</tt>''' during transmit, or when the cursor is not in the callsign field, it stops the current CW transmission, but does not disable the CW Auto Sending setting.<br />
<br />
Detail: If there is a slash character in the callsign, the triggering starts after the slash.<br />
<br />
===Remap keys in keyboard mode===<br />
<code>Options | CW | Remap keys in keyboard mode</code><br><br />
If you have remapped certain keys using the [[Menu:Tools#Redefine_keyboard_keys|Redefine keyboard keys]] dialog or the '''<tt>DEFINEKEYS</tt>''' text command, these mappings are ignored when in [[Menu:Commands#Keyboard_mode|keyboard mode]] '''<tt>[Alt-K]</tt>'''. So for example, if you have redefined the backslash key '''<tt>[\]</tt>''' to send your callsign, or the semicolon key '''<tt>[;]</tt>''' as an alternative to the plus key '''<tt>[+]</tt>''', those keys will not work the same when you are in keyboard mode. Check this option to have these remapped keys work consistently, whether you are in keyboard mode or not.<br />
<br />
==RTTY==<br />
<code>Options | RTTY</code><br><br />
This menu item allows you to setup the standard and additional messages for RTTY operation. It is enabled only when the selected operating mode is RTTY. (otherwise it is greyed out)<br />
<br />
===Modify standard messages...===<br />
<code>Options | RTTY | Modify standard messages...</code><br><br />
The place to change the RTTY messages. <br />
<br />
[[Image:OptionsRttyStandardMessages.PNG|center|frame|Modifying RTTY standard messages; you may also edit them one by one using '''<tt>Shift+F1</tt>''', '''<tt>Shift+F2</tt>''' etc. ]]<br />
<br />
Please have a look at the list of [[Message_variables|Message Variables]] you can use in the RTTY memories to control different aspects of the operation.<br />
<br />
The Options tab of this window lets you redefine the $QSOB4 macro. The only variable that can be used in this field is $MYCALL, e.g. "QSO QRZ $MYCALL".<br />
<br />
[[Image:RttyStandardMessagesOptions.PNG|center|frame|RTTY messages options.]]<br />
<br />
Check '''Only use RUN Messages (ignore S&P Messages)''' to force Win-Test to use only one set of RTTY messages, regardless of operating mode.<br />
<br />
===Modify additional messages...===<br />
<code>Options | RTTY | Modify additional messages...</code><br><br />
The place to create or modify additional RTTY messages which can be accessed using '''<tt>Alt-C</tt>'''. These memories can be used for transmitting QSL information, special greetings, QSY/sked information, ...<br />
<br />
[[Image:OptionsRttyAdditionalMessages.PNG|center|frame|Additional RTTY messages that may be used occasionally like QSL info, greetings, etc.]]<br />
<br />
[[Message_variables|Message Variables]] can also be used within these additional messages.<br />
<br />
===Modify WAE messages...===<br />
<code>Options | RTTY | Modify WAE messages...</code><br><br />
This function allows you to define RTTY message texts which are available during transmit/receive of QTC traffic. The QTC<br />
window is specific to the WAE DX Contest and can be opened using '''<tt>Ctrl-L</tt>''' (transmit QTCs) or <br />
'''<tt>Alt-L</tt>''' (receive QTCs). For more details of WAEDC, please see [[WAEDC]].<br />
<br />
[[Image:WaeMessagesTx.png|center|frame|Additional messages (transmit) for QTC handling in the Worked All Europe DX Contest.]]<br />
[[Image:WaeMessagesRx.png|center|frame|Additional messages (receive) for QTC handling in the Worked All Europe DX Contest.]]<br />
<br />
===Custom variables...===<br />
<code>Options | RTTY | Custom variables...</code><br><br />
For quick access to this dialog, use the [[Text commands|text command]] '''<tt>VARIABLES</tt>'''.<br><br />
<br />
See [[Menu:Options#Custom_variables...|Options | CW | Custom variables...]]<br />
<br />
==Configure interfaces...==<br />
<code>Options | Configure interfaces...</code><br><br />
For quick access to this dialog, use the [[Text commands|text command]] '''<tt>SETUP</tt>'''.<br><br />
All the interfaces you wish to use with Win-Test can be parametered by using this dialog box.<br />
<br />
[[Image:Configure-interfaces.png|frame|center|Interface Configuration]]<br />
<br />
===Serial Ports===<br />
The serial ports can be used for an RS-232 network (rarely used now), for a connection to a packet radio controller (also rarely used), for CW or PTT on/off keying output, for headphone audio control, for SO2R active radio control, or for an RS-232 (serial) radio, amplifier, SO2R box, or Winkey interface.<br />
<br />
If using a radio or amplifier interface, you must first specify what model you are using. Press the '''Default Settings''' button to configure all serial port settings to the standard defaults for the selected radio model or Winkey (highly recommended).<br />
<br />
If using an SO2R box, you can control it via serial commands (device type = microHAM, EZMaster, or OTRSP), or you can set the device type to "Other device" and use on/off activation of the DTR and RTS pins to control the SO2R box via "Classic Auto Control" hardware instead of via software commands.<br />
<br />
Use the serial port configuration dialog to select the appropriate settings:<br />
[[Image:com1-properties.png|frame|center|Serial port configuration]]<br />
The '''DTR''' (pin 4) and '''RTS''' (pin 7) options are:<br />
* Handshake - RS-232 hardware handshake, supported by some radios<br />
* CW - For on/off CW keying of Radio 1, Radio 2, or both, similar to LPT port CW keying. The convention is to use for DTR for CW and RTS (optionally) for PTT.<br />
* PTT - For activating PTT on Radio 1, Radio 2, or both, when a CW or internal DVK message is sent.<br />
* Always ON - Pin is always set "high" (required by some USB-to-Serial adapters and radios)<br />
* Always OFF - Pin is always set "low"<br />
* Active radio - Pin is connected to an SO2R box "Swap TX radio" line.<br />
* Stereo RX Audio - Pin is connected to an SO2R box "Stereo on/off" line.<br />
* Headphone control - Pin is connected to an SO2R box "Swap RX radio" line.<br />
<br />
The '''Active with''' option is only available when PTT or CW is selected for DTR or RTS, otherwise it is grayed out.<br />
* Radio 1 - PTT and CW is only sent when Radio 1 is active<br />
* Radio 2 - PTT and CW is only sent when Radio 2 is active<br />
* Both radios - PTT and CW is sent when either radio is active (external steering via SO2R box required)<br />
<br />
{{wbox|Note|The pin numbering applies to a standard DB9 connector.}}<br />
<br />
===Transceivers===<br />
This region of the interfaces configuration window lets you select the type of transceiver for radio 1 and 2 plus various settings like polling, polling rate (actually, delay before polling the radio again after the previous sequence) and if the ICOM specific CI-V feature is to be used or not. By the way, when you use an ICOM radio with an address different from factory settings, please see [http://docs.win-test.com/wiki/WT.INI WT.INI]<br />
<br />
===Printer Ports===<br />
A parallel port can be used to send CW and other signals from Win-Test via [[Interfaces#LPT-port_CW_keying|legacy keying interfaces]], or the microHAM MK2R/MK2R+ operating in "Classic Auto Control" mode. Press '''<tt>[Configure...]</tt>''' to display the following dialog box:<br />
<br />
[[Image:lpt1-properties.png|frame|center|Parallel port configuration showing pin 14 used for TX Radio, Pin 9 for Stereo On/Off, and Pin 4 for RX Radio, Pin 17 for CW, and Pin 16 for PTT]]<br />
<br />
Specify the address of your printer port in hex. Common values are '''<tt>378</tt>''' and '''<tt>3BC</tt>'''. To determine the address used by your printer port, open the Windows Device Manager (Start, Control Panel, System, Hardware tab, Device Manager; or Start, Run, '''<code>devmgmt.msc</code>'''). Select Ports (COM & LPT), Printer Port (LPT1), Right Click, Properties, and finally, click the Resources Tab. You will see '''<code>I/O range 0378 - 037A</code>''' or similar. Use the first address as your port address. If you do not specify the correct port address, Win-Test will appear to operate normally, but it will not key the radio at all.<br />
<br />
===CW===<br />
<tt>PTT ON Delay</tt> specifies the time delay between first PTT closure and first CW output. When using an amplifier with a slow relay, this setting allows you to close the relay line well before RF is applied, which prevents the first dot or dash sent by Win-Test from being truncated. The delay between the PTT command and the effective CW transmission is adjustable between 0 (for QSK amps) to 1000 ms.<br />
<br />
===Ethernet===<br />
The Ethernet interface is used by the Win-Test's local area network, in a multi-operating environment. If needed, you can change the broadcast address and the port number used. If you ignore the meaning of these terms, note that there should normally be no need to modify the default values given by Win-Test. See [[Networking]] for more information.<br />
<br />
===Network Protocol Advanced Settings===<br />
Under the Network Protocol Advanced Settings dialog you will find a way to restrict network traffic in very specific ways. '''CAUTION''': Modifications to the default settings must be done with extreme care. It is intended for very particular configurations and purposes, mainly used by expert users. You are on your own!<br />
<br />
[[Image:NetworkProtocolAdvancedSettings.png|frame|center|Network Protocol Advanced Settings allows you to fine-tune your network traffic]]<br />
<br />
Some pre-set typical configurations are available:<br />
<br />
* Silent time master: Can be used if the computer is used ''only'' to distribute an accurate clock. This PC will not appear in the status window of any other networked computer. Note that with this setting, no QSOs will be recorded on (or sent from) any machine with this setting.<br />
<br />
* Silent backup: Can be used if the computer is ''only'' used for backup purposes. This PC will not appear in the status window of any other networked computer. <br />
<br />
* Packet sharing only: Can be used if stations are networked with different callsigns, and do not want a common log, but do want to share a common packet stream. It can be used for several co-located single-op stations on VHF/UHF, for example.<br />
<br />
* Silent log rebuilding: Can be used if you need to rebuild from scratch a complete log from networked stations, without appearing in the status window of any other networked computer.<br />
<br />
Note that in all settings, the station will still be visible in the network via the [[Text_commands#Multi_Operating|'''<tt>INVENTORY</tt>''']] command.<br />
<br />
[x] This station is a WAN bridgehead<br />
<br />
This feature only works with the wtTunnel suite. To respect multi-op ethics, the wtTunnel package is ''only'' available for headquarters stations during the IARU HF contest. Check this box to restrict the synchronization of QSO inventories to the local network to reduce network traffic when stations are at different sites on a wide area network (WAN).<br />
<br />
See [[Networking#The_Bridgehead_Concept|The Bridgehead Concept]] for further details.<br />
<br />
===Voice Keyer===<br />
At last, if your computer has an embedded sound card, you can select and use it as a digital voice keyer by checking the appropriate box.<br />
<br />
If you want to use a third-party software to record or modify voice messages, be sure to use the following file format : WAV, PCM, 8000 Hz sampling frequency, 1 channel (mono) and 16 bits per sample.<br />
<br />
==WinKey configuration...==<br />
<code>Options | Winkey configuration...</code><br><br />
For quick access to this dialog, use the [[Text commands|text command]] '''<tt>WKSETUP</tt>'''.<br><br />
<br />
[[Image:WinkeyProperties.png|frame|center|Configuring the WinKey properties]]<br />
<br />
* '''Keying mode''':<br />
** '''Iambic A''' - Curtis A iambic timing<br />
** '''Iambic B''' - Curtis B iambic timing<br />
** '''Ultimatic''' - Non iambic mode<br />
** '''Bug (semi-automatic)''' - WinKey makes the dits and you make the dahs<br />
In either iambic mode, alternating dits and dahs are sent while both paddles are held closed. In mode B, an extra alternate dit or dah is sent after both paddles are released. In Ultimatic mode, when both paddles are pressed, the keyer will send a continuous stream of whichever paddle was last pressed.<br />
<br />
* '''Second Output (pin 5)''' (WinKey only, ignored by WinKey2 chip)<br />
** '''PTT''' - WinKey pin 5 acts as a PTT line<br />
** '''Sidetone frequency''' - WinKey pin 5 acts as a sidetone output<br />
** '''Radio 2''' - WinKey pin 5 keys a second radio<br />
* '''Sidetone Frequency''' - sets WinKey oscillator sidetone on pin 5 (ignored by WinKey2 chip)<br />
* '''Short spaces (CT spaces)''' - WinKey generates a 6-baud word space instead of a 7-baud space (1 baud = length of one dit)<br />
* '''Paddle watchdog''' - disable the key output after 128 consecutive dits or dahs. This is to guard against the paddles being accidentally keyed continuously by your cat.<br />
* '''Autospaces''' - If you pause for more than one dit time between a dit or dah, Winkey will interpret this as a letter-space and will not send the next dit or dah until a full letter-space time (3 dits) has passed<br />
* '''Swap paddles''' - reverse the dit/dah paddles (e.g. for keying with the left hand)<br />
* '''PTT'''<br />
** '''PTT Lead(ms)''' specify PTT lead (switch to transmit before CW begins)<br />
** '''PTT Tail(ms)''' specify PTT tail (keep transmitter up after CW has finished)<br />
** V2 of WinKey provides additional features:<br />
*** PTT tail control (fixed, 1.00 letter space, 1.33, 1.66, 2.00)<br />
* '''CW Message and paddle speeds'''<br />
** '''Independent''' - CW speed sent by the paddle is controlled by the WinKey speed knob, and CW speed set by Win-Test is controlled indpendently by the Win-Test keyboard commands ('''<tt>[Alt-F9]</tt>''', '''<tt>[Alt-F10]</tt>''', and '''<tt>[Alt-V]</tt>'''). In addition, both CW speeds will be displayed at the bottom of the [[Menu:Windows#Rate|Rate Window]].<br />
** '''Synchronized''' - Win-Test will keep the CW speed synchronized, whether sent by paddles or by Win-Test<br />
*** '''Only by WinKey pot''' - Only the WinKey speed knob will control CW speed; Win-Test speed commands sent via the keyboard are ignored.<br />
*** '''Only by the Win-Test commands (Alt-V/F9/F10)''' - The WinKey speed knob is ignored and CW speed changes may only be controlled by the Win-Test keyboard commands ('''<tt>[Alt-F9]</tt>''', '''<tt>[Alt-F10]</tt>''', and '''<tt>[Alt-V]</tt>''').<br />
*** '''By both (not recommended)''' - CW speed may be controlled by either the WinKey speed knob or by Win-Test keyboard commands, but this setting is not recommended as there is no way to automatically turn the WinKey speed knob to match the CW speed set by Win-Test.<br />
<br />
==EZMaster configuration...==<br />
<code>Options | EZMaster configuration...</code><br><br />
For quick access to this dialog, use the [[Text commands|text command]] '''<tt>EZSETUP</tt>'''.<br><br />
<br />
Advanced SO2R mode and setting up scenarios requires external SO2R control equipment of the last generation, communicating with Win-Test via a USB port.<br />
<br />
This menu option enables the user to configure five different option for EZMaster to work with Win-test:<br />
<br />
===CW Keyer===<br />
Internal EZMaster CW Keyer (tick Enable WinKey Box) or Win-Test keyer (do not tick box).<br />
<br />
<br />
===Radio set-up===<br />
In the image below find configuration for FT1000MP<br />
<br />
<br />
===Packet-Radio TNC===<br />
<br />
<br />
===Antenna configuration according to RX/TX===<br />
<br />
<br />
<br />
[[Image:Ezmaster.PNG|center|frame|EZMaster configuration window]]<br />
<br />
==MK/MKII/MK2R/u2R configuration...==<br />
<code>Options | MK/MKII/MK2R/u2R configuration...</code><br><br />
For quick access to this dialog, use the [[Text commands|text command]] '''<tt>MKSETUP</tt>'''.<br><br />
This option allows you to configure the microHAM devices microHAM Keyer, microHAM Keyer 2 and MK2R SO2R device.<br />
It lets you select if the microHAM protocol should be used for communication with the device.<br />
Moreover, you can specify, which pins on the ACC connected of the device will be activated, when the radio1 or radio 2 is tuned to a specific band. <br />
<br />
[[Image:MK_MKII_MK2R.PNG|center|frame|microHAM MK, MKII and MK2R configuration window]]<br />
<br />
When an attached footswitch is used, two dedicated Lua scripts named '''<tt>microhamFsOn.wts</tt>''' and '''<tt>microhamFsOff.wts</tt>''' (not case-sensitive) are called. '''<tt>wtArg</tt>''' is set the radio number of the footswitch (0 for MK/MKII - 0 or 1 for MK2R/MK2R+/u2R depending on the footswitch that generated the event).<br />
<br />
==OTRSP configuration...==<br />
<code>Options | OTRSP configuration...</code><br><br />
This option allows you to set up an Open Two Radio Switching Protocol (OTRSP) compatible <br />
device like the YCCC SO2R Box (for more information, visit http://www.k1xm.org/OTRSP).<br />
<br />
[[Image:OTSRP.PNG|center|frame|OTRSP configuration window]]<br />
<br />
If the OTRSP device has controls and if they can generate events, dedicated Lua scripts are called when events occur :<br />
<br />
* '''<tt>otrspCrOn.wts</tt>''' and '''<tt>otrspCrOff.wts</tt>''' (not case-sensitive) are called when such a control has values 1 and 0 respectively. '''<tt>wtArg</tt>''' is set to the control number (0 to 9).<br />
* '''<tt>otrspCrEvent.wts</tt>''' (not case-sensitive) is called for all states of the events. '''<tt>wtArg</tt>''' is set to (256 * cr) + state (cr = control number - 1 to 9, and state = value of the state when the event occured - 0 to 255).<br />
<br />
{{wbox|Note|If the PTT events are used, the control 0 is restricted to this usage, and doesn't fire the otrspCrOn/Off/Event.wts scripts. If the PTT events are not used, otrspCrEvent is not called when an event on this control occurs. Only the otrspCrOn/Off scripts are executed in this case.}}<br />
<br />
==RTTY configuration...==<br />
<code>Options | RTTY configuration...</code><br><br />
For quick access to this dialog, use the [[Text commands|text command]] '''<tt>RTTYSETUP</tt>'''.<br><br />
This menu entry opens the control box for [[RTTY|RTTY configuration]].<br />
<br />
[[Image:OptionsRttyConfiguration.PNG|frame|center|RTTY Configuration Box]]<br />
<br />
Please refer to the [[RTTY|RTTY chapter]] for all the details.<br />
<br />
==Frequency Offsets==<br />
This function is mainly used for a VHF/UHF/SHF setup involving a transverter. An HF radio tuned on 28 MHz is used as the user front-end which drives the transverter for 144 MHz or 432 MHz. Or a 144 MHz transceiver is used to drive a transverter to 5.7 and 10 GHz.<br />
<br />
The point is that Win-Test only sees the frequency of the front-end. For example it would find the radio tuned to 28 MHz and simply ignore its frequency read-out when set up for a VHF/UHF contest. Likewise, the radio would ignore commands to tune to 144.054 from Win-Test because it is a HF transceiver that only knows 1.8-30 MHz. This is where the frequency offset feature comes in handy. It allows you to specify a frequency (in kHz) that will be added to any frequency read from the radio and subtracted from any frequency command that goes to the radio. <br />
<br />
In other words, assume the frequency offset is set at 116000 kHz. The radio is tuned to 28054 kHz. Now Win-Test "sees" the radio at 144054 kHz, because the offset is added. Likewise, when the user clicks on a packet spot on 144088, Win-Test sends the radio to 28088 because the offset is subtracted.<br />
<br />
This way, Win-Test gives you great flexibility to enter one offset per band per radio.<br />
<br />
[[Image:OptionsFrequencyOffsets.png|center|frame|Frequency Offset allows you to use a transverter with Win-Test]]<br />
<br />
==MP3 Configuration==<br />
<code>Options | MP3 Configuration</code><br><br />
For quick access to this dialog, use the [[Text commands|text command]] '''<tt>MP3SETUP</tt>'''.<br><br />
<br />
Allows you to select the sound device used for recording and playbyck in use with the contest recorder. You must have installed a MP3 ACM Codec (e.g. LAME, Fraunhofer). The encoder is not part of the Win-Test distribution.<br />
<br />
Download LAME from http://www.free-codecs.com/LAME_ACM_Codec_download.htm. The most recent version at the time of this writing was 3.99.5. Follow instructions in the ZIP-File. With WinXP it used to work as described in http://lists.f5mzn.org/pipermail/support/2010-January/079240.html. <br />
<br />
There may already be an encoder on your system due to other software previously installed, like the Fraunhofer IIS MPEG Layer-3 Codec.<br />
<br />
The default settings (Stereo/8000 Hz sample rate, 24 kBit/s bitrate) will produce a file of about 500 MB in size for an 48h contest.<br />
<br />
[[Image:OptionsMP3Configuration.PNG|frame|center|Display options for MP3/Contest Recorder configuration.]]<br />
<br />
To make your MP3 recordings available on the Internet after the contest, see:<br />
http://lists.f5mzn.org/pipermail/support/2009-December/078951.html<br />
<br />
==Script Editor Configuration==<br />
This menu lets you configure the application to start when clicking the Edit button in the [[Menu:Tools#Scripts_Manager|Scripts Manager]]. Basically, every ASCII editor is usable, SciTE is the recommended editor as it provides syntax highlighting.<br />
<br />
[[Image:OptionsScriptEditorConfiguration.PNG|frame|center|Configure the preferred editor to manage Lua scripts from within Win-Test]]<br />
<br />
==Log==<br />
<code>Options | Log</code><br><br />
Allows you to change the display of the log entry area (the last 9 QSOs plus the current QSO entry line), including the Win-Test background color. You may select font size, colors, headings and so on.<br />
<br />
[[Image:OptionsLog.PNG|frame|center|Display options for the log entry area.]]<br />
<br />
===Fonts===<br />
Select the text font for the log entry area<br />
<br />
===Headers===<br />
Controls the display of the column titles in the log entry area. The headers may be hidden, left aligned, or centered<br />
<br />
===Hide QSO numbers===<br />
Hides the first column in the log entry area, to avoid confusion with the serial number sent, especially for multi-op entrants.<br />
<br />
===Colors...===<br />
Use this option to change the background color for the entire screen, the color of the logging text, the header text, or the warning message text. Press the '''<tt>[Factory colors]</tt>''' button to restore these to the Win-Test default colors.<br />
<br />
===Stay in field when moving up and down in the log===<br />
Select this option to the have the cursor move up and down as it would in a spreadsheet. For example, to stay in the report field when pressing the '''<tt>[Up]</tt>''' or '''<tt>[Down]</tt>''' cursor keys, instead of having the cursor jump to the beginning of the callsign field.<br />
<br />
===New Contest Files Properties===<br />
This window lets you define a directory structure and file name template for newly created contest log files. This is a nice feature to keep contest files including MP3 recordings etc. well organised.<br />
<br />
[[Image:OptionsLogNewContestFileProperties.PNG|center|frame|New Contest File Properties dialog]]<br />
<br />
The following macros may be used to specify the file name.<br />
<br />
%C = Contest name<br />
%I = Log callsign (slash substituted by hyphen)<br />
%L = Log callsign (slash substituted by underscore)<br />
%M = Mode<br />
%m = Month (2 digits)<br />
%N = Month name (long)<br />
%n = Month name (abbrev)<br />
%S = Station name<br />
%Y = Year (4 digits)<br />
%y = Year (2 digits)<br />
<br />
==DXpedition Info Field==<br />
<code>Options | DXpedition Info Field</code><br><br />
This submenu allows you to configure some options regarding the use of Win-Test on a DXpedition. It is only visible if you have selected the contest type DXpedition.<br />
<br />
[[Image:DxPeditionOptions.png|frame|center|Options available for DXpedition operation]]<br />
<br />
An info field is available to store up to 13 characters of information with the QSO, e.g. the operator's name, QTH or other information that you wish to keep visible during the QSO. The info field can be accessed with the space bar, the '''[>]''' and '''[<]''' keys or the '''[Tab]''' key. <br />
<br />
[[Image:DxPeditionInfoField.png|frame|center|The DXpedition Info Field can store up to 13 characters. If you don't use space to switch fields, you can also enter a space character like shown above.]]<br />
<br />
==Spot Warnings==<br />
When this option is enabled, the DX cluster spots are briefly displayed (as soon as they arrive), in the line under below the log entry line. You can choose to display only the spots of the current band and/or the new multipliers, as well as your own callsign (good to know when you're being spotted!). And of course you may want to hide dupes and invalid callsigns. <br />
<br />
==DX Cluster==<br />
<code>Options | DX Cluster</code><br><br />
<br />
===DX Cluster window shortcuts===<br />
[[Image:OptionsDxClusterSyntax.png|center|frame|Selecting the syntax of your DX Cluster]]<br />
This option controls the syntax of the DX-cluster node that you are using (DX Spider vs. AK1A, DXNet, etc.), and the count of spots and solar information requested by using the buttons in the [[Menu:Commands#DX-Cluster|DX cluster window]].<br />
<br />
===Start/stop wtDxTelnet automatically===<br />
When wtDxTelnet is installed in the Win-Test directory, this option allows you to start and stop this application from within Win-Test or start and stop it automatically when Win-Test is launched.<br />
<br />
[[Image:OptionsStartStopWtDxTelnet.gif|center|frame|Starting and stopping wtDxTelnet from Win-test]]<br />
<br />
==HamCAP==<br />
<code>Options | HamCAP</code><br><br />
<br />
With this menu option you can configure the way Win-Test will integrate with [http://www.dxatlas.com/HamCAP/ HamCAP] (by VE3NEA).<br><br />
You can select if you want to see immediately the HamCAP window, as soon as you call for it with the shortcut '''<tt>Ctrl-P</tt>''', or if you want it to calculate in background and you will recall the propagation forecast window later.<br />
<br />
[[Image:OptionsHamCapBackground.png|frame|center|Option In Background]]<br />
<br />
It is just a matter of taste and of how big is your monitor screen: if you have plenty of room, maybe you don't care to leave it in background (<b>In background</b> option <b>checked</b>), but in a visible part of the screen, so you don't loose the keyboard focus from the WT main window; otherwise you will see immediately HamCAP (<b>In background</b> option <b>unchecked</b>), and so you'll need to regain the focus with a mouse click.<br />
<br />
[[Image:HamCapForeground.png|frame|center|HamCAP in foreground]]<br />
<br />
Then you need to setup which HamCAP tab you want to see first.<br />
<br />
[[Image:OptionsHamCapTab.png|frame|center|Option In Background]]<br />
<br />
The most useful are the <b>Charts</b> or the <b>Map</b> tab, which are those that give the propagation information, while the others, namely Params, Settings, and Antennas, are useful in the HamCAP itself setup phase.<br />
<br />
See [[HamCAP]] in this manual for more details on the setup phase.<br />
<br />
Then you have to setup in which way HamCAP has to deal with Solar figures (SSN, SFI, A and K indexes).<br><br />
(See [[Menu:Windows#Solar_Activity | Menu Windows Solar_Activity]] in this manual).<br />
<br />
HamCAP has at least three different modes of operation:<br />
* stand-alone<br />
* in cooperation with [http://www.dxatlas.com/IonoProbe/ IonoProbe] (by VE3NEA)<br />
* feeded by a calling application (Win-Test)<br />
<br />
<br />
[[Image:OptionsHamCapSolar.png|frame|center|Option Solar indexes passing]]<br />
<br />
So, at this time, you should check one of the following options:<br />
* <b>None</b>, if you don't want, or need, Win-Test to pass any data to HamCAP, which will be working in stand-alone mode or in cooperation with IonoProbe;<br />
* <b>WWV only</b>, or <b>WCY only</b>, if you want Win-Test to pass the corresponding Solar figures, if present, to HamCAP;<br />
* <b>All</b>, and then choose <b>Priority</b>, if you want to try to use both figures and Win-Test to pass the prioritized one in case both data are present.<br />
<br><br />
<br />
<br><br />
<br />
==WAEDC==<br />
<code>Options | WAEDC</code><br><br />
Special option for the [http://www.waedc.de/ Worked All Europe DX Contest]. This menu item is only visible when WAEDC Contest is selected.<br />
<br />
For more information about Win-Test and WAEDC see [[WAEDC]].<br />
<br />
==Data files==<br />
<code>Options | Data Files</code><br><br />
<br />
Through this section you will be enabled to select four more different options in the pop-up menu as shown in the following picture.<br />
<br />
[[Image:OptionsDataFiles.png|center|frame|Selecting Options Data files section]]<br />
<br />
<br />
<br />
===Country files...===<br />
<code>Options | Data Files | Country files...</code><br><br />
Text command shortcut: <code>COUNTRYFILES</code><br />
<br />
This dialog controls which country file to use to identify multipliers. It is also used to calculate and pre-fill ITU and CQ Zones from country prefixes. There are three files to select from.<br />
<br />
[[Image:WindowsSelectCty.png|center|frame|Selecting the appropriate CTY file]]<br />
<br />
Selecting '''CTY_WT_MOD.DAT''' usually gives the most accurate results if you download the latest version. For a description of each file, see [[Other_Files|Other Files]].<br />
<br />
You can start an immediate download from the Win-Test web site by selecting a file and clicking the '''Download''' button. After pressing '''OK''', you will be prompted if you want to reload and re-score the log based on the updated country file.<br />
<br />
===Default extra data files...===<br />
<code>Options | Data Files | Default extra data files...</code><br><br />
This option will allow to select which EXTRA files WT will use to show specific information (like operator's name, IOTA references, club member names, etc.) in the Extra Information window (see [[Menu:Windows#Extra_Information | Menu:Windows Extra Information]] for more details).<br />
When selecting this option a window will pop-up where you can check the files you need. You can see an example in the following picture.<br />
<br />
[[Image:DataFilesExtra.png|center|frame|Selecting the Extra data files]]<br />
<br />
===Markers files...===<br />
<code>Options | Data Files | Markers files...</code><br><br />
This option will allow to select which Markers files WT will use to show the relevant information in the BandMap. Please refer to <br />
the description of the band map's [[Menu:Windows#Markers | context menu]] for detailed information on these files.<br />
When selecting this option a window will pop up where you can check the files you wish to display information from. <br />
You can see an example in the following picture.<br />
<br />
[[Image:DataFilesMarkers.png|center|frame|Selecting the Markers files]]<br />
<br />
===Segments files...===<br />
<code>Options | Data Files | Segments files...</code><br><br />
This option will allow to select which segments files WT will use to show the relevant information in the BandMap. Please refer to the description of the band map's [[Menu:Windows#Segments | context menu]] for detailed information on these files.<br />
When selecting this option a window will pop up where you can check the files you wish to activate. You can see an example in the following picture.<br />
<br />
[[Image:DataFilesSegment.png|center|frame|Selecting the Segments files]]<br />
<br />
==Bandplans...==<br />
<code>Options | Bandplans...</code><br><br />
A flexible and powerful band plan management allows you to specify band boundaries on a permanent basis depending on the mode of operation. We all know, that on 40 m CW, the band goes up to 7100; on RTTY, the band goes from well below 7030 to 7100 etc. etc. Since Win-Test tries to filter incoming DX spots by frequency, this is the way to have Win-Test make the correct decision to drop the spot or display it as needed DX.<br />
<br />
[[Image:Bandplans.png|center|frame|The Band Plan Manager window]]<br />
<br />
Different band plans can be saved and re-loaded at a later time. It's smart to create a band plan for SSB, another for CW, yet another one for 160 CW etc.<br />
<br />
==Windows==<br />
<code>Options | Windows</code><br><br />
<br />
[[Image:OptionsWindowsMenu.png|center|frame|Selecting how child windows are displayed]]<br />
<br />
The child windows of the application can either be included in the main Win-Test window, or float anywhere on the screen, thus allowing the Windows desktop or other running software to remain visible. If your video card and operating system support it, you can display Win-Test windows on more than one monitor.<br />
<br />
Win-Test automatically saves the current window layout in the Win-Test binary log file (.wtb) whenever you exit. So, each log file can have a different window layout depending on the contest.<br />
<br />
See [[Positioning_Windows|Positioning Windows]] for more information about how to precisely rearrange the window layout to suit your preferences. <br />
<br />
Once you have a window layout that you like, select <tt>Default layout...</tt> to save it as the default layout that will be used for new Win-Test logs. Win-Test displays the following dialog:<br />
<br />
[[Image:DefaultOpenChildWindows.png|center|frame|Changing the default window layout]]<br />
<br />
Updates to this dialog do ''not'' effect the current log's window layout; they only affect the default window layout to be used for new logs.<br />
<br />
If you press '''<tt>[Use the current layout]</tt>''', Win-Test updates the list box so that it describes the current Window layout. Generally you'll want to press this button first.<br />
<br />
The child windows are listed in the order that they will be ''drawn'', so if two windows overlap, the window listed last will appear "on top" of any windows listed earlier.<br />
<br />
Use the check boxes to indicate which child windows you want displayed by default.<br />
<br />
* '''<tt>[Uppermost]</tt>''' - moves the highlighted child window to the top of the list, so that it will be drawn first, and appear ''beneath'' any windows drawn later.<br />
* '''<tt>[Up]</tt>''' - moves the highlighted child window up one spot in the list<br />
* '''<tt>[Down]</tt>''' - moves the highlighted child window down one spot in the list<br />
* '''<tt>[Downmost]</tt>''' - moves the highlighted child window to the bottom of the list, so that it will be drawn last, and appear ''on top of'' any windows drawn earlier.<br />
* '''<tt>[Factory settings]</tt>''' - restores the default window layout to the Win-Test factory default<br />
* '''<tt>[Use the current layout]</tt>''' - updates the list to describe the child window layout being used by the current log<br />
* '''<tt>[OK]</tt>''' - saves the displayed window list as the new Win-Test default, and closes the dialog. The layout is saved in the [[WT.INI|Win-Test initialization file (wt.ini)]]. Pressing this button has ''no effect'' on the current window layout being used.<br />
* '''<tt>[Cancel]</tt>''' - cancels all changes to the default child window layout and closes the dialog.<br />
<br />
==Toolbar==<br />
<code>Options | Toolbar</code><br><br />
If this option is checked, the Icons toobar is displayed below the menu.<br />
<br />
[[Image:IconsBar.gif|frame|center|Icon toolbar]]<br />
<br />
<br />
Refer to the [[Icon_bar|Icon bar]] chapter for a detailed explanation of all the pictorial symbols.<br />
<br />
==Language==<br />
<code>Options | Language</code><br><br />
It is possible to choose the language of the Win-Test user interface. Currently supported languages are English, French, German, Italian and Spanish. <br />
<br />
[[Image:OptionsLanguageSelection.PNG|frame|center|Selecting the Language]]<br />
<br />
Win-Test has to restart when the language is switched.<br />
<br />
[[Menus|Back to Menus]]</div>N6TVhttps://docs.win-test.com/w/index.php?title=Menu:Edit&diff=4573Menu:Edit2016-08-18T02:09:01Z<p>N6TV: /* Delete all QSO... */ Add link to CLEARLOGNOW and COPYLOGCLEAR text commands</p>
<hr />
<div><big><big>Menu:Edit</big></big><br />
<!-- Adopted to Stylesheet DL6RAI --><br />
<br />
==Restore QSO==<br />
Shortcut: '''<tt>Ctrl-Z</tt>'''. Allows you to restore all the original data of a QSO you are modifying.<br />
Of course, the QSO you are modifying must already be logged before you use this command. It is most useful if you accidentally change something on a prior QSO, and wish to restore it.<br />
<br />
==Initialize QSO==<br />
Shortcut: '''<tt>[F11]</tt>''' or '''<tt>Alt-W</tt>'''. Erases all the fields of the current QSO if it has not been confirmed. However, this key will not delete a QSO that has already been logged with ['''<tt>Enter</tt>''']!<br />
<br />
However, the best way to "delete" a QSO is to do it after the end of the contest, in the final log files. Otherwise, you can enter your own callsign instead (and clear it afterwards with [[Menu:File_new#Clean log|File Clean log...]]), but this may create errors in the multipliers list. A better way is to duplicate the previous QSO, on the same band. It will be one more dupe QSO, but the points and the mutipliers will be correct.<br />
<br />
==Edit Date, Time, Freq. and Op. of QSO...==<br />
Shortcut: '''<tt>Alt-F</tt>'''.<br />
Allows you to modify the date, time, frequency and operator of an already logged QSO. Note that you can only change the frequency on the same band. If you need to change bands, use '''<tt>Alt+F1</tt>''' or '''<tt>Alt+F2</tt>''' (see [[Menu:Commands#QSY|QSY]]).<br />
[[Image:EditDateTimeFrequency.png|frame|center|Editing QSO date and time and frequency]]<br clear=all><br />
'''Warning''': After a modification, Win-Test does not sort the logged QSO by time. The logging sequence by numbers is kept.<br />
<br />
If you need to move your log, or a portion of it, ahead or back in time, please refer to the Tools [[Menu:Tools#Time_shifting|time shifting]] feature in this manual.<br />
<br />
==Edit serial number==<br />
This opens the edit serial dialog box. Here you can change your sent serial number.<br />
[[Image:editserial.png|frame|center|Editing the serial number]]<br />
<br />
==Delete QSO==<br />
Permanently deletes a QSO in the log. As Win-Test alerts, this command is irreversible.<br />
<br />
[[Image:DeleteAQSO.png|frame|center|Deleting A QSO from the log. The use of this feature is not recommended in a multi-op environment]]<br />
<br />
However, the best way to "delete" a QSO is to do it after the end of the contest, in the final log files. Otherwise, you can enter your own callsign instead (and clear it afterwards with [[Menu:File_new#File Clean log|File Clean log...]]), but this may create errors in the multipliers list. A better way is to duplicate the previous QSO. It will be one more dupe QSO, but the points and the mutlipliers will be correct.<br />
<br />
==Delete all QSO...==<br />
Equivalent [[Text commands#List of Text Commands|text command]]: '''<tt>CLEARLOG</tt>'''.<br><br />
See also the '''<tt>CLEARLOGNOW</tt>''' and '''<tt>COPYLOGCLEAR</tt>''' [[Text_commands#Open.2FClose.2FDatabase_Functions|text commands]], which may be more convenient if you understand what they do.<br><br />
<br />
This command deletes all the QSOs in the current opened file. Of course, as this should be rather unusual, you need to confirm the command.<br />
[[Image:DeleteAllQSO.png|frame|center|Deleting all QSOs]]<br />
You need to literally type '''<tt>OK</tt>''' (uppercase) in the box, and then press '''<tt>[Validate]</tt>''' to delete all QSOs.<br />
<br />
==Goto QSO...==<br />
Presents the dialog allowing to go directly to a QSO (if you know its number).<br />
<br />
[[Image:gotoQSO.png|frame|center|Goto QSO]]<br />
<br />
With the two labelled buttons, you can locate the cursor at the begining or at the end of the log. Same action will result by typing '''<tt>START</tt>''' (or '''<tt>FIRST</tt>''') and '''<tt>END</tt>''' (or '''<tt>LAST</tt>''') in the callsign logging field.<br />
<br />
You can also locate the cursor on the desired QSO number just by typing this number in the callsign logging field and use this menu item, or by using its shortcut ('''<tt>Ctrl-G</tt>''') for backward CT compatibility.<br />
<br />
When you have jumped to a specific QSO, Win-Test will not let you move away unless there is a valid call in the callsign field and a valid exchange in the report field. If you inadvertedly delete the callsign or report, press '''<tt>Ctrl-Z</tt>''' to undo the change.<br />
<br />
==Move in my log only==<br />
Only useful in a multi-operating environment. Checking this option will allow the operator to step through QSOs in his own log, using the '''<tt>[up arrow]</tt>''' and '''<tt>[down arrow]</tt>''' keys. This makes it much easier to correct the last QSO logged, since the cursor skips over QSOs being logged by other computers in the network.<br />
<br />
If this option is checked, you can still move to any QSO by pressing '''<tt>[Shift]-[Up arrow]</tt>''' and '''<tt>[Shift]-[down arrow]</tt>'''. On the other hand, if this option is unchecked, using these key combinations will navigate to QSOs made in your log only.<br />
<br />
[[Menus|Back to Menus]]</div>N6TVhttps://docs.win-test.com/w/index.php?title=FAQ:Problems_Registering_and_Running&diff=4572FAQ:Problems Registering and Running2016-07-24T00:25:32Z<p>N6TV: /* I requested a new registration key but I never received an email with the key */ Added list of blocked email service providers</p>
<hr />
<div>==How do I download, install, register and configure Win-Test on a new computer?==<br />
Click one of the following links to view or download the step-by-step illustrated '''Win-Test Installation, Registration and Configuration Guide''' (in PDF format) from http://download.win-test.com/registration/ :<br />
* [http://download.win-test.com/registration/wtreg_en.pdf wtreg_en.pdf] - English version by N6TV ([http://bit.ly/registerwt alternate server])<br />
* [http://download.win-test.com/registration/wtreg_fr.pdf wtreg_fr.pdf] - French version by F6FVY ([http://bit.ly/registerwt_f alternate version by XE1AY])<br />
* [http://download.win-test.com/registration/wtreg_es.pdf wtreg_es.pdf] - Spanish translation by LU5VV ([http://bit.ly/registerwt_ea alternate server]) <br />
* [http://download.win-test.com/registration/wtreg_it.pdf wtreg_it.pdf] - Italian translation by IK2NCJ ([http://bit.ly/registerwt_it alternate server])<br />
* [http://download.win-test.com/registration/wtreg_de.pdf wtreg_de.pdf] - German translation by DL1ELY ([http://bit.ly/registerwt_dl alternate server])<br />
* [http://download.win-test.com/registration/wtreg_pt.pdf wtreg_pt.pdf] - Portuguese translation by CU3HY ([http://bit.ly/registerwt_ct alternate server])<br />
<br />
Volunteers are needed to translate the guide to other languages. Please [http://www.qrz.com/db/n6tv contact N6TV] for the PowerPoint source file.<br />
<br />
==I selected Help | Register Software, but don't see my Computer Code==<br />
Chances are you are running the free "demo" version of Win-Test 4. This version cannot be registered. Download and install the official version from [http://download.win-test.com/v4/bin The Official Version 4 Download Site] (password required).<br />
<br />
==When I attempt to download Win-Test 4 the web site asks for a login and password. What should I use?==<br />
Your '''login''' is usually your '''callsign'''.<br />
<br />
Both your '''login''' and '''password''' are located in the "Win-Test Upgrade" or "Win-Test Purchase" email that you should have received when you purchased or upgraded to Version 4 (including free automatic upgrades). Look for an email:<br />
From: '''robot@win-test.com''' <br />
Subject: '''Win-Test V4 Free Upgrade'''<br />
-or-<br />
Subject: '''Achat de Win-Test - Win-Test purchase'''<br />
or similar.<br />
<br />
If you can't find the email with your unique web site password, you will need to send an email to F5HRY or F6FVY including your:<br />
* Account Number<br />
* Callsign<br />
* Email address used at time of purchase/upgrade<br />
* Your new email address if any<br />
<br />
==I requested a new registration key but I never received an email with the key==<br />
First, check your "Spam" folder, if any. Look for an email:<br />
From: '''robot@win-test.com''' <br />
Subject: '''Code de validation de Win-Test - Win-Test registration key'''<br />
<br />
Next, please note that registration keys are sent to the '''email address you provided when you first purchased Win-Test'''. If you no longer have access to this email address, you will need to send an email to F5HRY or F6FVY including your:<br />
* Account Number<br />
* Callsign<br />
* Old email address<br />
* New email address<br />
<br />
Due to security changes made by many email service providers (Google "DMARC policy"), registration keys sent by the Win-Test robot to '''the following email domains will be discarded automatically''', without any warning or notification:<br />
<br />
* aol.com<br />
* att.net<br />
* comcast.net<br />
* kolumbus.fi<br />
* sbcglobal.net<br />
* yahoo.com<br />
* ymail.com<br />
<br />
If your registered email address is at one of these domains, contact F5HRY to have your registered email address changed to another domain that still works, such as a Gmail account (gmail.com).<br />
<br />
==Win-Test always starts in "Demo" mode==<br />
Note: Unlike Win-Test Version 3, the [http://download.win-test.com/v4/demo/ free demo version] of Win-Test version 4, and the [http://download.win-test.com/v4/freeware/ free DXpedition version] cannot be registered or "activated"; the full version, which runs in demo mode until it registered via [[Menu:Help#Register_software| Help | Register Software]], is a different file. It must be downloaded from the [http://download.win-test.com/v4/bin password-protected download site] (see above if you don't have the password).<br />
<br />
Every PC has a unique 13-digit '''computer code''' (XXX-XXXX-XXXXXX) and every PC needs a unique 25-digit '''registration key''' (XXXXX-XXXXX-XXXXX-XXXXX-XXXXX).<br />
<br />
The registration keys for Win-Test Version 3 and Win-Test Version 4 are different. Even if you never purchased or installed Win-Test Version 4, you may have received a "free upgrade" email, especially if your purchased Win-Test Version 3 ''after'' '''June, 2008'''. If you received such an email, you are automatically going to receive only Version 4 registration keys when you request a key from the [http://www.win-test.com/rubrique.php3?id_rubrique=1870 Win-Test Registration Page]. Such keys ''do not work'' on Win-Test Version 3, though no error message is displayed. If you still require a Win-Test Version 3 registration key, you will need to request one by sending an email to F5HRY or F6FVY including your:<br />
* Account Number<br />
* Callsign<br />
* Computer Code<br />
Users who have not received a free upgrade to Version 4 and have not purchased an upgrade to Version 4 will still receive Version 3 registration keys from the web site.<br />
<br />
==My Virus scanner reports that Win-Test is a Virus!==<br />
This is probably a false alarm, especially if you downloaded and installed Win-Test from the [http://download.win-test.com Official Win-Test download site].<br />
<br />
Many virus scanners are especially prone to falsely reporting the "Artemis" or "Themida" virus in Win-Test Version 4, due to the way the executable is constructed.<br />
<br />
You can always upload '''wt.exe''' to [http://www.virustotal.com VirusTotal.com] to test it with multiple scanners. If less than 25% of the virus scanners report an issue, it is likely that Win-Test is ''not infected'', and you will need to add an "exception" to your antivirus software to allow Win-Test to run.</div>N6TVhttps://docs.win-test.com/w/index.php?title=Interfaces&diff=4571Interfaces2016-06-07T17:37:10Z<p>N6TV: /* COM-port CW keying */ Replace COM port keying circuit with improved PTT and CW schematic, with pin numbers</p>
<hr />
<div>Configuration of interfaces in Win-Test needs only be done once, rather than on a per-contest basis. This means you do not waste time remembering your interface configuration details prior to each contest!<br />
<br />
== Interface configuration ==<br />
<br />
The [[Menu:Options#Configure_interfaces...|interface configuration window]] can be opened by clicking on <code>Options->Configure Interfaces</code> menu in the main Win-Test window, or via the text command '''<tt>SETUP</tt>'''.<br />
<br />
=== Radio configuration ===<br />
At the bottom of the window there is a "Transceivers" section which includes two drop-down lists where you set your radio type ('''Radio 1''' and '''Radio 2'''). First, choose your rig make and model from the appropriate list. Please note that there is only one "Kenwood" entry in the list because all Kenwood rigs use a common protocol.<br />
<br />
On the left hand side of the window, you will see a list of COM ports (only available COM ports on your system will be selectable). After you have chosen the manufacturer and/or model of your rig, check the box corresponding to the COM port to which your radio is connected. For example: <br />
<br />
[[Image:Interfaces.png|frame|center|COM port configuration]]<br />
<br />
Upon checking the box, you will notice that the adjacent drop-down box will now be enabled. You ''must'' choose '''Radio 1''' or '''Radio 2''' from this drop-down list. You must also '''ensure that the port (baud rate) settings are correct for your radio'''.<br />
<br />
By default, the settings of 19200 8-N-1 will be configured, which is probably incorrect for your radio. Click on the adjacent '''<tt>[Configure...]</tt>''' button to display the [[Menu:Options#Serial_Ports|COM port properties dialog]]:<br />
<br />
[[Image:com1-properties.png|frame|center|COM port configuration for Radio1 / Radio2]]<br />
<br />
If you are not sure about the baud rate settings for your transceiver, press the '''<code>[default settings]</code>''' button to change all values to the known hardware defaults for the selected radio.<br />
<br />
There is also a list of known working settings for common contest radios located in the [[Supported_rigs|Supported rigs]] chapter.<br />
<br />
== Configuring other interfaces ==<br />
<br />
As you may well have noticed by this stage, a variety of other interfaces can also be enabled from the <code>Configure Interfaces</code> dialog box. It is just a simple case of ticking the relevant COM port and choosing said device from the drop-down list. Examples include TNCs, SO2R switching boxes (e.g. [[SO2R/EZMaster/Setup|EZmaster]], [[SO2R/MK2R/Setup|microHAM MK2R]], WinKey, W5XD Keyer, etc.). For everything not on the list, you can choose <code>Other interface...</code> and configure the port settings yourself - for example, COM port CW interface (see below).<br />
<br />
=== COM-port CW keying ===<br />
<br />
If you have a simple transistor-based COM port CW interface (see below), you can enable this by again choosing the corresponding COM port, and selecting <code>Other interface...</code> from the drop-down list. Clicking on the <code>Configure</code> button will display the [[Menu:Options#Serial_Ports|COM Port Properties dialog]] including a drop-down list of options for DTR (pin 4) and RTS (pin 7) on<br />
a DE9 connector (pins 20 and 4 on a DB25). Connect the emitter of the NPN transistor to signal ground, pin 5 on DE9 (pin 7 on DB25).<br />
<br />
''Be sure to select '''DTR: CW''' and '''RTS: PTT''' in the COM port Properties under Interface Configuration.''<br />
<br />
[[Image:COM_Port_CW_PTT_Circuit.png|center|frame|Simple COM port CW and PTT interface for DE-9 9-pin serial connector or USB-to-Serial adapter]]<br />
<br />
This interface was designed for K1EA's CT and is still in use today with Win-Test.<br />
<br />
=== LPT-port CW keying ===<br />
<br />
Likewise, if you have an LPT (parallel) port CW interface (see schematics below), you can enable it by checking the box next to 'LPT' in the [[Menu:Options#Configure_interfaces...|Configure interfaces dialog]]. Clicking on the <code>[Configure]</code> button in the Printer Ports section will display the [[Menu:Options#Printer_Ports|Printer Ports dialog]]. At the very bottom, you can enable CW and PTT on pin 17 and 16 respectively. ''Ensure this is checked.''<br />
<br />
{{wbox|WARNING|In order for LPT keying to function correctly under Windows XP, Vista, or 32-bit Windows 7, you will need an additional utility, '''DLPortIO.dll''' installed by Port95NT.exe, obtainable from the Win-Test website. It is a simple process and only needs to be installed/run once. Please [http://download.win-test.com/port95nt.exe click here] to download. For 64-bit Windows 7, use InpOut32.dll as described in [http://lists.f5mzn.org/pipermail/support/2011-May/081094.html this post].}}<br />
<br />
[[Image:Schema_InterfaceCW.gif|center|frame|Simple LPT port CW interface]]<br />
<br />
=== Digital Voice Keyer ===<br />
<br />
The DVK-100 voice keyer was the first computer-controlled voice memory in the contesting world in the early 90s. Later, some equipment manufacturers built voice memories into their radios like Kenwood (TS-850, TS-950 with the DRU2 and DRU3 units respectively - probably others). These devices can be controlled by Win-Test using the following LPT interface.<br />
<br />
[[Image:Schema_InterfaceDVK.gif|center|frame|Simple LPT port DVK interface]]<br />
<br />
Usually the device has 3-4 different memories which can be triggered by [<b><tt>F1</tt></b>]...[<b><tt>F4</tt></b>] on the computer keyboard.<br />
<br />
=== Sound Card ===<br />
<br />
Wav files can also be played from an internal sound card by utilizing a small interface like shown below.<br />
Messages are recorded using <b><tt>Shift-F1</tt></b>...<b><tt>Shift-F7</tt></b>.<br />
<br />
[[Image:Schema_Interface_SoundCard.gif|center|frame|Sound Card Interface]]<br />
<br />
The use of an isolation transformer is recommended both on the output side of the sound card. Of course, you can go without one but first think about the trouble you will encounter when the Line Out port of your sound card gets killed by stray RF or when someone tells you you got hum on your audio in the middle of the contest. <br />
<br />
[[Image:SoundcardInterface.gif|center|frame|Sound Card interface kindly provided by W9ZRX. This interface is in use at the K3LR M/M station.]]<br />
<br />
W9ZRX has provided this design that comes without a relay to switch Mic input between radio and sound card. Most sound cards allow routing from Mic input to Line Out so that you can control muting Line Out from within Win-Test. Make sure that the Microphone has been enabled as an Input to the Sound Card Mixer. Different Sound Cards set up slightly differently, but most seem to either show the Microphone Input to the Mixer as '''muted''', or the default Mixer Inputs do not include the Microphone until '''enabled'''.<br />
<br />
There are sound cards that do not support this option. The Writelog download site has a [http://www.writelog.com/Downloads/sbrdchk.zip sound card checker] that will help you to determine if you have this problem if it absolutely doesn't work.<br />
<br />
Another way would be to try using the Win-Test PTT output to drive a relay to allow a direct routing between your Mic and the Mic input of your TRX when the PTT output is off. This requires some additional components but better than an external mic to record the DVK messages.<br />
<br />
=== Band Data ===<br />
<br />
Win-Test supports filter and antenna switching by supplying Yaesu-standard Band data on pins 2, 7, 8 and 9 of the parallel port. These pins are equivalent to lines A, B, C and D. This feature allows you to automatically control other devices in your station, probably by using a band decoder like the one from [http://www.qth.com/topten/bdecoder.htm Top Ten Devices]. <br />
<br />
{| {{Prettytable_fixed}}<br />
! Band !! A !! B !! C !! D <br />
|-<br />
| 160 m || 0 || 0 || 0 || 1<br />
|-<br />
| 80 m || 0 || 0 || 1 || 0<br />
|-<br />
| 40 m || 0 || 0 || 1 || 1<br />
|-<br />
| 30 m || 0 || 1 || 0 || 0<br />
|-<br />
| 20 m || 0 || 1 || 0 || 1<br />
|-<br />
| 17 m || 0 || 1 || 1 || 0<br />
|-<br />
| 15 m || 0 || 1 || 1 || 1<br />
|-<br />
| 12 m || 1 || 0 || 0 || 0<br />
|-<br />
| 10 m || 1 || 0 || 0 || 1<br />
|-<br />
| 6 m || 1 || 0 || 1 || 0<br />
|-<br />
| 2 m || 1 || 0 || 1 || 1<br />
|-<br />
| 70 cm || 1 || 1 || 0 || 0<br />
|-<br />
|}<br />
<br />
=== Radio 1/Radio 2 ===<br />
<br />
LPT pin 14 is used to send Radio1/2 information to an external interface. High = Radio1, Low = Radio2.<br />
<br />
=== Headphones Control ===<br />
The signals ''Headphones Control'' (called ''RX Focus'' in the MK2R microHAM SO2R interface) is available on LPT, pin 4. This signal allows to control which radio you want to listen to in the headphones. Must be enabled in the LPT Configuration Window. Low = Radio 1, High = Radio 2.<br />
<br />
== See Also == <br />
<br />
=== From the Win-Test manual ===<br />
<br />
* [[Menu:Options#Configure_interfaces...|Configure interfaces dialog]]<br />
* [[Networking|Networking configuration for multi-ops]]<br />
* [[SO2R/EZMaster/Setup|EZMaster setup]]<br />
* [[SO2R/MK2R/Setup|microHAM MK2R setup]]<br />
<br />
=== External sources ===<br />
<br />
* [http://www.microham.com/Downloads/micro_KEYER_R_2_0_English.pdf microHAM MicroKeyer Manual]<br />
* [http://www.microham.com/Downloads/USB_Interface_II_R_1_1_English.pdf microHAM USB II Interface Manual]</div>N6TVhttps://docs.win-test.com/w/index.php?title=File:COM_Port_CW_PTT_Circuit.png&diff=4570File:COM Port CW PTT Circuit.png2016-06-07T17:31:36Z<p>N6TV: New COM port CW and PTT circuit schematic. Replaces old one that only showed CW output and didn't include pin numbers.</p>
<hr />
<div>New COM port CW and PTT circuit schematic. Replaces old one that only showed CW output and didn't include pin numbers.</div>N6TVhttps://docs.win-test.com/w/index.php?title=Keys&diff=4569Keys2016-03-11T21:54:10Z<p>N6TV: /* Message keys */ Correct messages 6 and 7; they work on phone and RTTY, not just CW.</p>
<hr />
<div><!-- Adopted to Stylesheet DL6RAI --><br />
<br />
==Editing and moving around the QSO entry line==<br />
* ['''<tt>Enter</tt>''']: Log a contact<br />
* ['''<tt>Spacebar</tt>''']: Move cursor between callsign entry and report fields<br />
* ['''<tt>Left arrow</tt>''']: Move cursor one character to the left<br />
* ['''<tt>Right arrow</tt>''']: Move cursor one character to the right<br />
* ['''<tt>Home</tt>''']: Move cursor to the beginning of the field<br />
* ['''<tt>End</tt>''']: Moves the cursor to the end of the field<br />
* ['''<tt>Backspace</tt>''']: Delete the character located left of the cursor<br />
* ['''<tt>Tab</tt>'''] : Move cursor between sent RST and received number fields<br />
* ['''<tt>></tt>''']: Move cursor to next field in the main log.<br />
* ['''<tt><</tt>''']: Move cursor to previous field in the main log.<br />
* ['''<tt>Del</tt>''']: Delete the character located under the cursor<br />
* ['''<tt>F11</tt>''']: Clear all the fields of the current QSO, and puts the cursor into the callsign logging field<br />
* '''<tt>Alt-W</tt>''': Clear QSO (like '''<tt>F11</tt>''')<br />
* '''<tt>Alt-F8</tt>''': Clear QSO (like '''<tt>F11</tt>''')<br />
* '''<tt>Alt-F</tt>''': Edit QSO date and time<br />
* '''<tt>Alt-N</tt>''': Write a note regarding this QSO<br />
* '''<tt>Alt-Up arrow</tt>''': Copy the previous QSO in the log<br />
* '''<tt>Ctrl-A</tt>''': Like ['''<tt>Home</tt>''']<br />
* '''<tt>Ctrl-B</tt>''': Like ['''<tt>Left arrow</tt>''']<br />
* '''<tt>Ctrl-D</tt>''': Like ['''<tt>Del</tt>''']<br />
* '''<tt>Ctrl-E</tt>''': Like ['''<tt>End</tt>''']<br />
* '''<tt>Ctrl-F</tt>''': Like ['''<tt>Right arrow</tt>''']<br />
* '''<tt>Ctrl-W</tt>''': Clear the current field; if report field is cleared, initialise RST<br />
* '''<tt>Ctrl-K</tt>''': Like ['''<tt>Shift-Del</tt>''']<br />
* '''<tt>Ctrl-Z</tt>''': Undo - restores edited QSO data to prior value (see [[Menu:Edit#Restore_QSO]])<br />
* '''<tt>Ctrl-Left arrow</tt>''': Like ['''<tt>Home</tt>''']<br />
* '''<tt>Ctrl-Right arrow</tt>''': Like ['''<tt>End</tt>''']<br />
* '''<tt>Shift-Backspace</tt>''': Delete all the characters left of the cursor<br />
* '''<tt>Shift-Del</tt>''': Delete all characters under and right of the cursor<br />
<br />
==Movement in the log==<br />
<br />
Warning: Any movement in the log validates the QSO where the cursor was located before the movement!<br />
<br />
* ['''<tt>Up arrow</tt>''']: Move one QSO up <br />
* ['''<tt>Down arrow</tt>''']: Move one QSO down <br />
* ['''<tt>PageUp</tt>''']: Move 10 QSOs up <br />
* ['''<tt>PageDown</tt>''']: Move 10 QSOs down <br />
* '''<tt>Ctrl-G</tt>''': Go to a specific QSO number<br />
** To skip the dialog box prompt, just enter the QSO number into the callsign field, then Press '''<tt>Ctrl-G</tt>'''. To return to the end of the log, press '''<tt>Ctrl-G</tt>''', ['''<tt>Spacebar</tt>''']<br />
* '''<tt>Ctrl-G</tt>''', ['''<tt>Home</tt>''']: Go to first QSO in log<br />
* '''<tt>Ctrl-G</tt>''', ['''<tt>End</tt>''']: Go to last QSO in log<br />
* '''<tt>Ctrl-Home</tt>''': Go to first QSO in log<br />
* '''<tt>Ctrl-End</tt>''': Go to last QSO in log<br />
* '''<tt>Ctrl-PageDown</tt>''': Go forward 24 hours<br />
* '''<tt>Ctrl-PageUp</tt>''': Go back 24 hours<br />
<br />
==Message keys==<br />
* ['''<tt>F1</tt>''']: Play message #1. Normally, this message is the CQ<br />
* ['''<tt>F2</tt>''']: Play message #2. Normally, this message is the report sent (full)<br />
* ['''<tt>F3</tt>''']: Play message #3. Normally, this message is the serial number sent<br />
* ['''<tt>F4</tt>''']: Play message #4. Normally, this message is your call<br />
* ['''<tt>F5</tt>''']: Play message #5. Normally, this message is the logged callsign<br />
* ['''<tt>F6</tt>''']: Play message #6. Normally, this message sends Call? or NR?<br />
* ['''<tt>F7</tt>''']: Play message #7. Normally, this message sends "?" or "Again?"<br />
* ['''<tt>Insert</tt>''']: Play the message defined for this key (CW/RTTY only) - normally, this message is the logged callsign the full sent report<br />
* ['''<tt>+</tt>''']: Play the message defined for this key (CW/RTTY only) - normally, this message sends a TU, then your callsign and automatically logs the QSO. See also [[Menu:Tools#Remapping_.5B.2A.5D_and_.5B.2B.5D_when_using_Notebook_or_Mini_keyboard|Remapping [+] when using a Notebook or Mini keyboard]].<br />
* ['''<tt>Esc</tt>''']: Stop the output message being sent<br />
* '''<tt>Alt-K</tt>''': Toggle Keyboard mode<br />
* '''<tt>Alt-C</tt>''': Send or modify additional messages<br />
* '''<tt>Alt-V</tt>''': Change CW speed (opens "CW-Speed" dialog box)<br />
* '''<tt>Alt-F9</tt>''': Decrease CW speed by 2 WPM<br />
* '''<tt>Alt-F10</tt>''': Increase CW speed by 2 WPM<br />
* '''<tt>Shift-F1</tt>'''...'''<tt>Shift-F7</tt>''': Record messages #1 to #7 (unless [[SO2R/Shift_binds_second_radio|Operating | Shift binds to the second radio]] is enabled)<br />
* '''<tt>Shift-Insert</tt>''': Record the message associated to the ['''<tt>Insert</tt>'''] key (unless [[SO2R/Shift_binds_second_radio|Operating | Shift binds to the second radio]] is enabled). CW/RTTY only. For Phone, the F2 message is the Insert message.<br />
* '''<tt>Shift-+</tt>''': Records the message associated to the ['''<tt>+</tt>'''] key (unless [[SO2R/Shift_binds_second_radio|Operating | Shift binds to the second radio]] is enabled). CW/RTTY only. For Phone, the F3 message is the Plus message.<br />
* '''<tt>AltGr-F1</tt>'''...'''<tt>AltGr-F7</tt>''': Record messages #1 to #7<br />
* '''<tt>AltGr-Insert</tt>''': Record the message associated to the ['''<tt>Insert</tt>'''] key<br />
* '''<tt>AltGr-+</tt>''': Records the message associated to the ['''<tt>+</tt>'''] key<br />
* '''<tt>Ctrl-Alt-F1</tt>'''...'''<tt>Ctrl-Alt-F7</tt>''': Record messages #1 to #7<br />
* '''<tt>Ctrl-Alt-Insert</tt>''': Record the message associated to the ['''<tt>Insert</tt>'''] key<br />
* '''<tt>Ctrl-Alt-+</tt>''':Records the message associated to the ['''<tt>+</tt>'''] key<br />
* '''<tt>Ctrl-Tab</tt>''': Toggle between Run and S&P mode and messages (CW/RTTY)<br />
* '''<tt>Ctrl-Shift-Tab</tt>''': Toggle between Run and S&P mode and messages on the secondary radio<br />
<br />
==Open and Close Windows==<br />
* ['''<tt>F8</tt>''']: Open/Close N + 1 Window<br />
* ['''<tt>F9</tt>''']: Open/Close Check call Window<br />
* ['''<tt>F10</tt>''']: Open/Close Check Multipliers Window<br />
* ['''<tt>F12</tt>''']: Open/Close Check Partials Window<br />
* '''<tt>Alt-A</tt>''': Open/Close DX-Cluster Announcements Window<br />
* '''<tt>Alt-B</tt>''': Open/Close Skeds Window<br />
* '''<tt>Alt-E</tt>''': Take a sked<br />
* '''<tt>Alt-I</tt>''': Open/Close Gab Window<br />
* '''<tt>Alt-M</tt>''': Open/Close Mult Window <br />
* '''<tt>Alt-O</tt>''': Open/Close DX-Cluster Monitor Window<br />
* '''<tt>Alt-R</tt>''': Open/Close Rate Window<br />
* '''<tt>Alt-S</tt>''': Open/Close Summary<br />
* '''<tt>Alt-X</tt>''': Open Extra Data Files Window<br />
* '''<tt>Alt-Z</tt>''': Open/Close Worked zones Window<br />
* '''<tt>Ctrl-F9</tt>''': Open/Close Statistics Window<br />
* '''<tt>Shift-F10</tt>''': Reverse Multiplier Check - Opens the [[Menu:Windows#Search_for_Worked_Multipliers_or_Partial_QTH_Locators|Search for Worked Multipliers]] Window<br />
<br />
==Radio Control==<br />
* ['''<tt>-</tt>''']: Split frequency - enter your receive frequency here (e.g. 7239)<br />
* ['''<tt>*</tt>''']: Switch active radio. '''This only works with the ['''<tt>*</tt>'''] key on the numeric keypad'''. See also [[Menu:Tools#Remapping_.5B.2A.5D_and_.5B.2B.5D_when_using_Notebook_or_Mini_keyboard|Remapping [*] when using a Notebook or Mini keyboard]].<br />
* '''<tt>Alt-:</tt>''' : Switch active radio<br />
* '''<tt>Alt-F1</tt>''': QSY band down (20 => 40 => ...)<br />
* '''<tt>Alt-F2</tt>''': QSY band up (20 => 15 => ...)<br />
* '''<tt>Alt-F4</tt>''': QSY back to run frequency<br />
* '''<tt>Alt-F5</tt>''': Set run frequency<br />
* '''<tt>Ctrl-S</tt>''': Swap the frequency on both radios (SO2R)<br />
* '''<tt>Ctrl-T</tt>''': Tune the transmitter (on CW)<br />
* '''<tt>Ctrl-F1</tt>''' and '''<tt>Ctrl-F2</tt>''': Switch mode (when the contest permits and mode=MIXED or ALL)<br />
<br />
==Packet==<br />
* '''<tt>Alt-A</tt>''': Open/Close DX-Cluster Announcements Window<br />
* '''<tt>Alt-O</tt>''': Open/Close DX-Cluster Monitor Window<br />
* '''<tt>Alt-T</tt>''': Talk to DX-Cluster<br />
* '''<tt>Alt-F3</tt>''': Spot<br />
<br />
==Band Map==<br />
* '''<tt>Ctrl-Enter</tt>''': Insert spot into [[Menu:Windows#Radio_1.2C_Radio_2_.28Band_Maps.29|Band Map]] <br />
* '''<tt>Ctrl-Del</tt>''': Delete spot on current frequency in the active Band Map<br />
* '''<tt>Ctrl-J</tt>''': Insert spot into Band Map<br />
* '''<tt>Ctrl-Up arrow</tt>''': Grab the first upper spot in the active Band Map (in frequency regarding the active radio)<br />
* '''<tt>Ctrl-Shift-Up arrow</tt>''': Grab the first upper spot in the active bandmap (in frequency regarding the active radio), even if it is a 0-pointer<br />
* '''<tt>Ctrl-Down arrow</tt>''': Grab the first lower spot in the active bandmap (in frequency regarding the active radio)<br />
* '''<tt>Ctrl-Shift-Down arrow</tt>''': Grab the first lower spot in the active bandmap (in frequency regarding the active radio), even if it is a 0-point station<br />
* '''<tt>Ctrl-Space</tt>''': Grab the spot on or near the current frequency<br />
* '''<tt>Ctrl-DoubleClick</tt>''' on a spot: Delete the spot without the warning window<br />
* '''<tt>Alt-DoubleClick</tt>''' on a spot: Load the sub VFO with a spot frequency (if applicable)<br />
<br />
==DX-Cluster Announcements==<br />
* '''<tt>Ctrl-DoubleClick</tt>''' on a spot: Delete the spot without the warning window<br />
* '''<tt>Alt-DoubleClick</tt>''' on a spot: Load the sub VFO with a spot frequency (if applicable)<br />
<br />
==Networking==<br />
* '''<tt>Alt-D</tt>''': Pass a station<br />
* '''<tt>Alt-G</tt>''': Send a gab<br />
* '''<tt>Alt-I</tt>''': Open/Close Gab Window<br />
* '''<tt>Alt-J</tt>''': Display status of all stations in the network<br />
<br />
==Multi Operator==<br />
* '''<tt>Alt-Y</tt>''': Toggle current QSO's station type from RUN (R1) to MULT (M) in the M/S category, or from RUN1 (R1) to RUN2 (R2) in M/2 category, and vice versa.<p>If the cursor is on the logging line rather than a previously logged QSO when you press this key, the station type is changed for all new QSOs logged on that computer, i.e. it is equivalent to entering the text commands RUN/MULT or RUN1/RUN2. See [[Menu:Commands#Station_Type|Menu: Commands | Station Type]].<br />
* '''<tt>Ctrl-F3</tt>''': Toggle current QSO (same as '''<tt>Alt-Y</tt>''')<br />
<br />
==SO2R==<br />
* <tt>'''AltGr-A'''</tt>, <tt>'''Ctrl-Alt-A'''</tt>: Listen to the primary radio with both ears<br />
* <tt>'''AltGr-T'''</tt>, <tt>'''Ctrl-Alt-T'''</tt>: Listen to the secondary radio with both ears<br />
* <tt>'''AltGr-S'''</tt>, <tt>'''Ctrl-Alt-S'''</tt>: Listen to both radios in stereo (toggle)<br />
* <tt>'''AltGr-L'''</tt>, <tt>'''Ctrl-Alt-L'''</tt>: Listen to the "other" radio with both ears during transmit (headphone "latch")<br />
* <tt>'''AltGr-R'''</tt>, <tt>'''Ctrl-Alt-R'''</tt>: Restore automatic control (advanced scenarios will control headphones, like $RESET)<br />
* <tt>'''AltGr-1'''</tt>...<tt>'''AltGr-8'''</tt>, <tt>'''Ctrl-Alt-1'''</tt>...<tt>'''Ctrl-Alt-8'''</tt>: Select one of the eight SO2R scenarios<br />
<br />
==Partner Mode==<br />
* '''<tt>Alt-Enter</tt>''': Add the call current call to the partner window<br />
* '''<tt>Alt-Space</tt>''': Grab the call in the topmost "real time" line of the partner window<br />
* '''<tt>Alt-Backpace</tt>''': Clear everything in the partner window<br />
* '''<tt>Alt-1</tt>'''...'''<tt>Alt-9</tt>''': Grab the ''n''th call from the partner window<br />
* '''<tt>Ctrl-1</tt>'''...'''<tt>Ctrl-9</tt>''': Swap the ''n''th call in partner window with callsign in the logging window<br />
* '''<tt>DoubleClick</tt>''' on a callsign: Grab the call from the partner window<br />
* '''<tt>Ctrl-DoubleClick</tt>''' on a callsign: Delete the call from the partner window<br />
<br />
==Contest Recorder==<br />
* '''<tt>AltGr-Enter</tt>''': Play QSO<br />
* '''<tt>AltGr-Up</tt>''': Previous QSO<br />
* '''<tt>AltGr-Down</tt>''': Next QSO<br />
* '''<tt>AltGr-Space</tt>''': Play/Pause<br />
* '''<tt>AltGr-PgUp</tt>''': Rewind 30s<br />
* '''<tt>AltGr-PgDown</tt>''': FastForward 30s<br />
* '''<tt>AltGr-Left</tt>''': Rewind 5s<br />
* '''<tt>AltGr-Right</tt>''': FastForward 5s<br />
<br />
Some keyboards do not have an <tt>AltGr</tt> key, so use <tt>Ctrl+Alt</tt> instead.<br />
<br />
==Special Keys==<br />
* '''<tt>Alt-L</tt>''': [[WAEDC#Receiving_QTCs|Open QTC RX window]] (to be used by EU stations)<br />
* '''<tt>Ctrl-L</tt>''': [[WAEDC#Transmitting_QTCs|Open QTC TX window]] (to be used by DX stations)<br />
<br />
[[Main Page|Back to Main Page]]</div>N6TVhttps://docs.win-test.com/w/index.php?title=Keys&diff=4568Keys2016-03-11T21:48:00Z<p>N6TV: /* Message keys */ Indicate alternatives from programming messages when Shift binds to secondary radio is enabled</p>
<hr />
<div><!-- Adopted to Stylesheet DL6RAI --><br />
<br />
==Editing and moving around the QSO entry line==<br />
* ['''<tt>Enter</tt>''']: Log a contact<br />
* ['''<tt>Spacebar</tt>''']: Move cursor between callsign entry and report fields<br />
* ['''<tt>Left arrow</tt>''']: Move cursor one character to the left<br />
* ['''<tt>Right arrow</tt>''']: Move cursor one character to the right<br />
* ['''<tt>Home</tt>''']: Move cursor to the beginning of the field<br />
* ['''<tt>End</tt>''']: Moves the cursor to the end of the field<br />
* ['''<tt>Backspace</tt>''']: Delete the character located left of the cursor<br />
* ['''<tt>Tab</tt>'''] : Move cursor between sent RST and received number fields<br />
* ['''<tt>></tt>''']: Move cursor to next field in the main log.<br />
* ['''<tt><</tt>''']: Move cursor to previous field in the main log.<br />
* ['''<tt>Del</tt>''']: Delete the character located under the cursor<br />
* ['''<tt>F11</tt>''']: Clear all the fields of the current QSO, and puts the cursor into the callsign logging field<br />
* '''<tt>Alt-W</tt>''': Clear QSO (like '''<tt>F11</tt>''')<br />
* '''<tt>Alt-F8</tt>''': Clear QSO (like '''<tt>F11</tt>''')<br />
* '''<tt>Alt-F</tt>''': Edit QSO date and time<br />
* '''<tt>Alt-N</tt>''': Write a note regarding this QSO<br />
* '''<tt>Alt-Up arrow</tt>''': Copy the previous QSO in the log<br />
* '''<tt>Ctrl-A</tt>''': Like ['''<tt>Home</tt>''']<br />
* '''<tt>Ctrl-B</tt>''': Like ['''<tt>Left arrow</tt>''']<br />
* '''<tt>Ctrl-D</tt>''': Like ['''<tt>Del</tt>''']<br />
* '''<tt>Ctrl-E</tt>''': Like ['''<tt>End</tt>''']<br />
* '''<tt>Ctrl-F</tt>''': Like ['''<tt>Right arrow</tt>''']<br />
* '''<tt>Ctrl-W</tt>''': Clear the current field; if report field is cleared, initialise RST<br />
* '''<tt>Ctrl-K</tt>''': Like ['''<tt>Shift-Del</tt>''']<br />
* '''<tt>Ctrl-Z</tt>''': Undo - restores edited QSO data to prior value (see [[Menu:Edit#Restore_QSO]])<br />
* '''<tt>Ctrl-Left arrow</tt>''': Like ['''<tt>Home</tt>''']<br />
* '''<tt>Ctrl-Right arrow</tt>''': Like ['''<tt>End</tt>''']<br />
* '''<tt>Shift-Backspace</tt>''': Delete all the characters left of the cursor<br />
* '''<tt>Shift-Del</tt>''': Delete all characters under and right of the cursor<br />
<br />
==Movement in the log==<br />
<br />
Warning: Any movement in the log validates the QSO where the cursor was located before the movement!<br />
<br />
* ['''<tt>Up arrow</tt>''']: Move one QSO up <br />
* ['''<tt>Down arrow</tt>''']: Move one QSO down <br />
* ['''<tt>PageUp</tt>''']: Move 10 QSOs up <br />
* ['''<tt>PageDown</tt>''']: Move 10 QSOs down <br />
* '''<tt>Ctrl-G</tt>''': Go to a specific QSO number<br />
** To skip the dialog box prompt, just enter the QSO number into the callsign field, then Press '''<tt>Ctrl-G</tt>'''. To return to the end of the log, press '''<tt>Ctrl-G</tt>''', ['''<tt>Spacebar</tt>''']<br />
* '''<tt>Ctrl-G</tt>''', ['''<tt>Home</tt>''']: Go to first QSO in log<br />
* '''<tt>Ctrl-G</tt>''', ['''<tt>End</tt>''']: Go to last QSO in log<br />
* '''<tt>Ctrl-Home</tt>''': Go to first QSO in log<br />
* '''<tt>Ctrl-End</tt>''': Go to last QSO in log<br />
* '''<tt>Ctrl-PageDown</tt>''': Go forward 24 hours<br />
* '''<tt>Ctrl-PageUp</tt>''': Go back 24 hours<br />
<br />
==Message keys==<br />
* ['''<tt>F1</tt>''']: Play message #1. Normally, this message is the CQ<br />
* ['''<tt>F2</tt>''']: Play message #2. Normally, this message is the report sent (full)<br />
* ['''<tt>F3</tt>''']: Play message #3. Normally, this message is the serial number sent<br />
* ['''<tt>F4</tt>''']: Play message #4. Normally, this message is your call<br />
* ['''<tt>F5</tt>''']: Play message #5. Normally, this message is the logged callsign<br />
* ['''<tt>F6</tt>''']: Play message #6 (CW only)<br />
* ['''<tt>F7</tt>''']: Play message #7 (CW only)<br />
* ['''<tt>Insert</tt>''']: Play the message defined for this key (CW/RTTY only) - normally, this message is the logged callsign the full sent report<br />
* ['''<tt>+</tt>''']: Play the message defined for this key (CW/RTTY only) - normally, this message sends a TU, then your callsign and automatically logs the QSO. See also [[Menu:Tools#Remapping_.5B.2A.5D_and_.5B.2B.5D_when_using_Notebook_or_Mini_keyboard|Remapping [+] when using a Notebook or Mini keyboard]].<br />
* ['''<tt>Esc</tt>''']: Stop the output message being sent<br />
* '''<tt>Alt-K</tt>''': Toggle Keyboard mode<br />
* '''<tt>Alt-C</tt>''': Send or modify additional messages<br />
* '''<tt>Alt-V</tt>''': Change CW speed (opens "CW-Speed" dialog box)<br />
* '''<tt>Alt-F9</tt>''': Decrease CW speed by 2 WPM<br />
* '''<tt>Alt-F10</tt>''': Increase CW speed by 2 WPM<br />
* '''<tt>Shift-F1</tt>'''...'''<tt>Shift-F7</tt>''': Record messages #1 to #7 (unless [[SO2R/Shift_binds_second_radio|Operating | Shift binds to the second radio]] is enabled)<br />
* '''<tt>Shift-Insert</tt>''': Record the message associated to the ['''<tt>Insert</tt>'''] key (unless [[SO2R/Shift_binds_second_radio|Operating | Shift binds to the second radio]] is enabled). CW/RTTY only. For Phone, the F2 message is the Insert message.<br />
* '''<tt>Shift-+</tt>''': Records the message associated to the ['''<tt>+</tt>'''] key (unless [[SO2R/Shift_binds_second_radio|Operating | Shift binds to the second radio]] is enabled). CW/RTTY only. For Phone, the F3 message is the Plus message.<br />
* '''<tt>AltGr-F1</tt>'''...'''<tt>AltGr-F7</tt>''': Record messages #1 to #7<br />
* '''<tt>AltGr-Insert</tt>''': Record the message associated to the ['''<tt>Insert</tt>'''] key<br />
* '''<tt>AltGr-+</tt>''': Records the message associated to the ['''<tt>+</tt>'''] key<br />
* '''<tt>Ctrl-Alt-F1</tt>'''...'''<tt>Ctrl-Alt-F7</tt>''': Record messages #1 to #7<br />
* '''<tt>Ctrl-Alt-Insert</tt>''': Record the message associated to the ['''<tt>Insert</tt>'''] key<br />
* '''<tt>Ctrl-Alt-+</tt>''':Records the message associated to the ['''<tt>+</tt>'''] key<br />
* '''<tt>Ctrl-Tab</tt>''': Toggle between Run and S&P mode and messages (CW/RTTY)<br />
* '''<tt>Ctrl-Shift-Tab</tt>''': Toggle between Run and S&P mode and messages on the secondary radio<br />
<br />
==Open and Close Windows==<br />
* ['''<tt>F8</tt>''']: Open/Close N + 1 Window<br />
* ['''<tt>F9</tt>''']: Open/Close Check call Window<br />
* ['''<tt>F10</tt>''']: Open/Close Check Multipliers Window<br />
* ['''<tt>F12</tt>''']: Open/Close Check Partials Window<br />
* '''<tt>Alt-A</tt>''': Open/Close DX-Cluster Announcements Window<br />
* '''<tt>Alt-B</tt>''': Open/Close Skeds Window<br />
* '''<tt>Alt-E</tt>''': Take a sked<br />
* '''<tt>Alt-I</tt>''': Open/Close Gab Window<br />
* '''<tt>Alt-M</tt>''': Open/Close Mult Window <br />
* '''<tt>Alt-O</tt>''': Open/Close DX-Cluster Monitor Window<br />
* '''<tt>Alt-R</tt>''': Open/Close Rate Window<br />
* '''<tt>Alt-S</tt>''': Open/Close Summary<br />
* '''<tt>Alt-X</tt>''': Open Extra Data Files Window<br />
* '''<tt>Alt-Z</tt>''': Open/Close Worked zones Window<br />
* '''<tt>Ctrl-F9</tt>''': Open/Close Statistics Window<br />
* '''<tt>Shift-F10</tt>''': Reverse Multiplier Check - Opens the [[Menu:Windows#Search_for_Worked_Multipliers_or_Partial_QTH_Locators|Search for Worked Multipliers]] Window<br />
<br />
==Radio Control==<br />
* ['''<tt>-</tt>''']: Split frequency - enter your receive frequency here (e.g. 7239)<br />
* ['''<tt>*</tt>''']: Switch active radio. '''This only works with the ['''<tt>*</tt>'''] key on the numeric keypad'''. See also [[Menu:Tools#Remapping_.5B.2A.5D_and_.5B.2B.5D_when_using_Notebook_or_Mini_keyboard|Remapping [*] when using a Notebook or Mini keyboard]].<br />
* '''<tt>Alt-:</tt>''' : Switch active radio<br />
* '''<tt>Alt-F1</tt>''': QSY band down (20 => 40 => ...)<br />
* '''<tt>Alt-F2</tt>''': QSY band up (20 => 15 => ...)<br />
* '''<tt>Alt-F4</tt>''': QSY back to run frequency<br />
* '''<tt>Alt-F5</tt>''': Set run frequency<br />
* '''<tt>Ctrl-S</tt>''': Swap the frequency on both radios (SO2R)<br />
* '''<tt>Ctrl-T</tt>''': Tune the transmitter (on CW)<br />
* '''<tt>Ctrl-F1</tt>''' and '''<tt>Ctrl-F2</tt>''': Switch mode (when the contest permits and mode=MIXED or ALL)<br />
<br />
==Packet==<br />
* '''<tt>Alt-A</tt>''': Open/Close DX-Cluster Announcements Window<br />
* '''<tt>Alt-O</tt>''': Open/Close DX-Cluster Monitor Window<br />
* '''<tt>Alt-T</tt>''': Talk to DX-Cluster<br />
* '''<tt>Alt-F3</tt>''': Spot<br />
<br />
==Band Map==<br />
* '''<tt>Ctrl-Enter</tt>''': Insert spot into [[Menu:Windows#Radio_1.2C_Radio_2_.28Band_Maps.29|Band Map]] <br />
* '''<tt>Ctrl-Del</tt>''': Delete spot on current frequency in the active Band Map<br />
* '''<tt>Ctrl-J</tt>''': Insert spot into Band Map<br />
* '''<tt>Ctrl-Up arrow</tt>''': Grab the first upper spot in the active Band Map (in frequency regarding the active radio)<br />
* '''<tt>Ctrl-Shift-Up arrow</tt>''': Grab the first upper spot in the active bandmap (in frequency regarding the active radio), even if it is a 0-pointer<br />
* '''<tt>Ctrl-Down arrow</tt>''': Grab the first lower spot in the active bandmap (in frequency regarding the active radio)<br />
* '''<tt>Ctrl-Shift-Down arrow</tt>''': Grab the first lower spot in the active bandmap (in frequency regarding the active radio), even if it is a 0-point station<br />
* '''<tt>Ctrl-Space</tt>''': Grab the spot on or near the current frequency<br />
* '''<tt>Ctrl-DoubleClick</tt>''' on a spot: Delete the spot without the warning window<br />
* '''<tt>Alt-DoubleClick</tt>''' on a spot: Load the sub VFO with a spot frequency (if applicable)<br />
<br />
==DX-Cluster Announcements==<br />
* '''<tt>Ctrl-DoubleClick</tt>''' on a spot: Delete the spot without the warning window<br />
* '''<tt>Alt-DoubleClick</tt>''' on a spot: Load the sub VFO with a spot frequency (if applicable)<br />
<br />
==Networking==<br />
* '''<tt>Alt-D</tt>''': Pass a station<br />
* '''<tt>Alt-G</tt>''': Send a gab<br />
* '''<tt>Alt-I</tt>''': Open/Close Gab Window<br />
* '''<tt>Alt-J</tt>''': Display status of all stations in the network<br />
<br />
==Multi Operator==<br />
* '''<tt>Alt-Y</tt>''': Toggle current QSO's station type from RUN (R1) to MULT (M) in the M/S category, or from RUN1 (R1) to RUN2 (R2) in M/2 category, and vice versa.<p>If the cursor is on the logging line rather than a previously logged QSO when you press this key, the station type is changed for all new QSOs logged on that computer, i.e. it is equivalent to entering the text commands RUN/MULT or RUN1/RUN2. See [[Menu:Commands#Station_Type|Menu: Commands | Station Type]].<br />
* '''<tt>Ctrl-F3</tt>''': Toggle current QSO (same as '''<tt>Alt-Y</tt>''')<br />
<br />
==SO2R==<br />
* <tt>'''AltGr-A'''</tt>, <tt>'''Ctrl-Alt-A'''</tt>: Listen to the primary radio with both ears<br />
* <tt>'''AltGr-T'''</tt>, <tt>'''Ctrl-Alt-T'''</tt>: Listen to the secondary radio with both ears<br />
* <tt>'''AltGr-S'''</tt>, <tt>'''Ctrl-Alt-S'''</tt>: Listen to both radios in stereo (toggle)<br />
* <tt>'''AltGr-L'''</tt>, <tt>'''Ctrl-Alt-L'''</tt>: Listen to the "other" radio with both ears during transmit (headphone "latch")<br />
* <tt>'''AltGr-R'''</tt>, <tt>'''Ctrl-Alt-R'''</tt>: Restore automatic control (advanced scenarios will control headphones, like $RESET)<br />
* <tt>'''AltGr-1'''</tt>...<tt>'''AltGr-8'''</tt>, <tt>'''Ctrl-Alt-1'''</tt>...<tt>'''Ctrl-Alt-8'''</tt>: Select one of the eight SO2R scenarios<br />
<br />
==Partner Mode==<br />
* '''<tt>Alt-Enter</tt>''': Add the call current call to the partner window<br />
* '''<tt>Alt-Space</tt>''': Grab the call in the topmost "real time" line of the partner window<br />
* '''<tt>Alt-Backpace</tt>''': Clear everything in the partner window<br />
* '''<tt>Alt-1</tt>'''...'''<tt>Alt-9</tt>''': Grab the ''n''th call from the partner window<br />
* '''<tt>Ctrl-1</tt>'''...'''<tt>Ctrl-9</tt>''': Swap the ''n''th call in partner window with callsign in the logging window<br />
* '''<tt>DoubleClick</tt>''' on a callsign: Grab the call from the partner window<br />
* '''<tt>Ctrl-DoubleClick</tt>''' on a callsign: Delete the call from the partner window<br />
<br />
==Contest Recorder==<br />
* '''<tt>AltGr-Enter</tt>''': Play QSO<br />
* '''<tt>AltGr-Up</tt>''': Previous QSO<br />
* '''<tt>AltGr-Down</tt>''': Next QSO<br />
* '''<tt>AltGr-Space</tt>''': Play/Pause<br />
* '''<tt>AltGr-PgUp</tt>''': Rewind 30s<br />
* '''<tt>AltGr-PgDown</tt>''': FastForward 30s<br />
* '''<tt>AltGr-Left</tt>''': Rewind 5s<br />
* '''<tt>AltGr-Right</tt>''': FastForward 5s<br />
<br />
Some keyboards do not have an <tt>AltGr</tt> key, so use <tt>Ctrl+Alt</tt> instead.<br />
<br />
==Special Keys==<br />
* '''<tt>Alt-L</tt>''': [[WAEDC#Receiving_QTCs|Open QTC RX window]] (to be used by EU stations)<br />
* '''<tt>Ctrl-L</tt>''': [[WAEDC#Transmitting_QTCs|Open QTC TX window]] (to be used by DX stations)<br />
<br />
[[Main Page|Back to Main Page]]</div>N6TVhttps://docs.win-test.com/w/index.php?title=Menu:File_new&diff=4567Menu:File new2016-02-25T22:29:56Z<p>N6TV: /* Contest Configuration */ Indicate how to rename as station profile via shift+click</p>
<hr />
<div><big><big>Menu:File (without a file opened)</big></big><br />
<!-- Adopted to Stylesheet DL6RAI --><br />
<br />
==New==<br />
You may use <tt>File | New...</tt> to create a new log file.<br />
<br />
{{wbox|Note|Since Win-Test stores most CW/RTTY messages and window positions in each log file, it is usually more convenient to copy an old Win-Test log file of the same contest type, rather to use the method described below. When you create a brand new log file with Win-Test, it resets all CW/RTTY messages and Window positions to Win-Test defaults, and these may not represent your personal preferences.}}<br />
<br />
Win-Test first shows the contest configuration screen, which is described in detail in the [[#Contest_Configuration|Contest Configuration]] section below.<br />
<br />
[[Image:Contest_configuration.png|center|frame|Contest Configuration screen]]<br />
<br />
After selecting a contest type and clicking the '''OK''' button, Win-Test automatically generates a new file name based on the type, mode, year, callsign, etc. Win-Test then displays the following dialog box, which you may use to change the generated name and subdirectory. The default extension for Win-Test log files is .wt4, which should not be changed. (Win-Test 3 used .wtb as the file extension, which stood for "Win-Test binary".)<br />
<br />
[[Image:FileNew.png|center|frame|Dialog allowing you to customize the name and location of your log file]]<br />
<br />
{{wbox|Note|For a multi-op setup, do ''not'' put log files on a shared network drive. Each computer must use its own local log file, stored on its own local hard disk drive. Log data will be automatically shared and synchronized between computers (when enabled) across the local network by Win-Test.}}<br />
<br />
To change the default location and naming convention, click the '''Advanced...''' button and refer to the legend displayed at the bottom of the dialog, as shown below:<br />
<br />
[[Image:NewContestFileProperties.png|center|frame|Use this dialog to change the default naming convention and location of your Win-Test log files]]<br />
<br />
By default, Win-Test creates a new sub-directory for every contest type. If you wish to have all of your logs stored in the ''same'' directory, leave the '''Sub-dir. name''' field blank, as shown above.<br />
<br />
==Contest Configuration==<br />
After selecting '''New''', '''Open''', or entering the '''REOPEN''' text command when a log is already open, the contest parameters are shown in the following dialog box:<br />
[[Image:Contest_configuration.png|center|frame|Contest configuration parameters]]<br />
<br />
===Station Parameters===<br />
<br />
* '''Callsign:''' The one used during the contest. Do not specify the departement (REF contest), or the zone number in this field ! On the other hand, the potential /P, /M or /MM must be specified.<br />
* '''Locator:''' Mandatory for a VHF contest. Optional but useful for an HF contest (this will allow to get accurate beam headings or sunrises/sunsets). To determine your locator, go to [http://f6fvy.free.fr/qthLocator/fullScreen.php http://f6fvy.free.fr/qthLocator/fullScreen.php], find your location on the interactive map, and click on it to display your grid square number.<br />
* '''Exchange:''' Type your zone, your state, your department... according to the contest you will run. For example, for a CQWW DX contest, specify your WAZ zone. Let this box empty if the sent report is a serial number (for the WPX, for example). If there is a domestic and a DX side in the contest, specify DX if it is your case. Press the button with the "?" symbol to get more information.<br />
* '''DXCC prefix:''' Standard prefix of your DXCC country. This information is used only for live score reporting, so you may leave that open.<br />
* '''WAZ zone:''' Your WAZ zone. This information is used only for live score reporting, so you may leave that open.<br />
* '''ITU zone:''' Your ITU zone. This information is used only for live score reporting, so you may leave that open.<br />
* '''State/Province/Other:''' Your state, province or other regional designator. This information is used only for live score reporting, so you may leave that open.<br />
* '''Name:''' Name of the callsign's owner.<br />
* '''Address:''' You have 3 free lines to give the address of the station. Keep the last one to specify your zip code and town, as well as your country for an international contest. <br />
* '''Profiles:''' You can save up to five different station profiles. Profiles are a set of station information (Callsign, Name, Address, etc.) that can be reused when necessary; they allow quick Win-Test setup for operators that frequently change their contest call, or go to DXpeditions, or operate on a multi-op team. Profiles are saved in specific sections in the <tt>wt.ini</tt> file.<br />
** '''Load:''' click the button to load the previously-saved station profile<br />
** '''Save as:''' click the button to create a Station profile. To ''rename'' or reuse a station profile, '''<code>[Shift]+click</code>''' on the button and follow the prompts.<br />
<br />
===Contest Parameters===<br />
<br />
* '''Contest:''' The contest to run. Multipliers, dupe checking, points scoring etc... will depend on this choice. Please be careful! Regarding VHF contests, Win-Test supports 2 "generic" contests: "European VHF" and "European VHF (gridsquare counting as multiplier)". These 2 contests will be compatible with the vast majority of the minor contests having the same scoring system.<br />
* '''Category:''' Choose the category in which you will participate. Check in the rules that the corresponding category really exists in the specified contest! Win-Test does not check for the existence of a specific category against the current contest rules.<br />
* '''Overlay:''' Some contests rules show overlays (like Rookie). Check in the rules that the corresponding overlay really exists in the specified contest!<br />
* '''Mode:''' Choose the mode in which you will participate. Selecting '''<tt>MIXED</tt>''' will allow you to switch between SSB and CW. If you also wish to have digital modes, select '''<tt>ALL</tt>'''. Check the rules if the corresponding mode really exists in the specified contest!<br />
* '''Band plan:''' Select a contest-specific band plan or leave the Default one. For more details, please see [[Menu:Options#Bandplans...|Options | Bandplans...]]<br />
* '''Power:''' Your effective power, compulsory for the ARRL DX, on the DX side. Use only numbers, figures like '''<tt>5</tt>''' or '''<tt>100</tt>''', but do not specify watts! If you are allowed to transmit more than 1 kW, specify '''<tt>KW</tt>'''.<br />
* '''Class:''' Choose the power class.<br />
* '''Operators:''' Put the operators' callsigns here. For strict compatibility with the Cabrillo format, please leave a blank space between each listed callsign.<br />
<br />
===Network Parameters===<br />
The following parameters make sense only in a networked Win-Test environment.<br />
* '''Station name:''' All computers in the network must have different names. Use descriptive names to easily recognize a computer in the status window.<br />
* '''Enable time distribution in network:''' In order to synchronize the timestamps of all logged QSOs, ''one and only one'' computer should be defined as '''time master''' by checking this box.<br />
<br />
==Open==<br />
<br />
Opens a log file in the Win-Test format (.wt4 for Win-Test version 4, .wtb for Win-Test 3).<br />
<br />
There is no need to close the file already in use. The new file will take its place.<br />
<br />
[[Image:FileOpen.png|center|frame|Opening a Win-Test binary log file]]<br />
<br />
After choosing the file, the contest configuration dialog appears:<br />
<br />
[[Image:Contest_configuration.png|center|frame|Contest configuration screen]]<br />
<br />
You can then modify these parameters, if needed, before starting to log contacts.<br />
See the [[#Contest_Configuration|Contest Configuration]] section above for more information.<br />
<br />
A progress bar is then displayed as the log file is loaded, as well as information about data base files associated with the contest.<br />
===Corrupted Files===<br />
<br />
Should your file have been corrputed by any means, Win-Test will automatically open up a dialog to fix the error. <br />
<br />
[[Image:TryFixFile.gif|center|frame|Fix Errors Dialog. Make sure you know what you're doing]]<br />
<br />
<br />
The original log will be saved under the original name with an '''<tt>_err</tt>''' suffix before the .wt4 extension.<br />
<br />
The fix will most probably delete the QSO records in question to allow for a clean log. Make sure you know what you're doing and be sure to have a backup of the original! Fixing the file is only possible in some cases. For example, when you inadvertedly opened a v3 Win-Test file with Win-Test version 2, you are at a loss (see [http://www.f5mzn.org/pipermail/support/2006-November/072424.html http://www.f5mzn.org/pipermail/support/2006-November/072424.html]).<br />
<br />
==Import==<br />
<br />
Allows to import logs from Editest or Cabrillo format to Win-Test format.<br />
<br />
Furthermore, after importing the log file, you can immediatly load this file in Win-Test, by checking the appropriate box.<br />
<br />
[[Image:file-import-editest.png|center|frame|Editest Import]] [[Image:file-import-cabrillo.png|center|frame|Cabrillo Import]]<br />
<br />
Of course, the original file is not modified. <br />
<br />
==Export==<br />
<br />
Provides a way to export a Win-Test version 4 (.wt4) log into an Win-Test version 3 (.wtb) file format. The former Editest format is no longer supported for export.<br />
<br />
[[Image:ExportFileTo.png|center|frame|Export to Win-Test version 3 format]]<br />
<br />
The original .WT4 file is not modified.<br />
<br />
==Merge Logs==<br />
<br />
Merging is the process of manually bringing two or more (partly) separate log files together. <br><br />
<br />
Useful in a multi-operator Win-Test LAN, this menu allows to merge the logs issued from different computers. You can thus gather all the QSO in an unique file (named "master"), which has to be the first added to the list. The original file will be automatically saved before any modification (.bak).<br />
<br />
Since Win-Test version 3, with networking and log synchronization, this should no longer be necessary.<br />
A valid scenario, however, could be a DXpedition, where several computers run independently, without a network backbone and a complete log has to be created on a day-by-day basis and distributed to all stations for completeness and redundancy or uploaded as an on-line-log.<br />
<br />
<center><br />
{|<br />
|[[Image:MergeFileStart.gif|center|frame|Start up the merge dialog; this menu item is visible only when no WT file is open]]<br />
|[[Image:MergeFileSelect.PNG|center|frame|Now select the files to be merged]]<br />
|}<br />
</center><br />
<br />
<br />
Merging Logs is done in six steps:<br />
<br />
# Close the current log<br />
# Collect all log fiels to be merged on your computer<br />
# Go to '''<tt>File | Merge logs...</tt>'''<br />
# Select all the log files you would like to merge <br />
# Select the file that should become the master file<br />
# Press OK to start merging<br />
<br />
Win-Test will read QSO data from all the files and incorporate them into the designated master log file, removing any duplicate contacts. Optionally, you may chose to load the master log file after the merge process has finished.<br />
<br />
This menu is only visible if no file is opened. If a log is opened, just close it by the <code>File | Close</code> menu or the '''<tt>CLOSE</tt>''' text command.<br />
<br />
{{wbox|Note|If you have changed a QSO in a partial file and the unchanged QSO is still contained in another log that is being merged, you will end up with both the changed and the unchanged QSO in the final log.}}<br />
<br />
{{wbox|Note|Win-Test will not allow merging logs from different contests.}}<br />
<br />
[[Image:MergeUnableDifferentRules.gif|center|frame|Files from different contests cannot be merged]]<br />
<br />
==Clean log==<br />
<br />
===Cleaning===<br />
<br />
This function removes QSOs logged with your own callsign. It can also remove duplicate QSOs.<br />
<br />
The recommended way to remove QSOs during a contest is to overwrite them with your own callsign. Later, after the contest, you can delete these QSOs from the log. Win-Test allows you to do that very easily via a menu item.<br />
<br />
'''First, close the log''' via '''<tt>File | Close</tt>''' or the '''<tt>CLOSE</tt>''' command. <br />
The Clean Log item is only visible, in the File menu, when the log is closed.<br />
<br />
Then from the menu choose '''<tt>File | Clean log</tt>'''.<br />
<br />
<center><br />
{|<br />
|[[Image:FileCleanLog.gif|frame|center|The Clean Log menu item]]<br />
|[[Image:FileCleanLogOptions.gif|frame|center|The Clean Log dialog]]<br />
|}<br />
</center><br />
<br />
When you select Clean Log, Win-Test prompts you to select the log file you want to clean.<br />
Next the Clean Log dialog prompts you choose the actions you want to perform:<br />
* to delete QSOs with yourself (good)<br />
* to delete all duplicate QSOs (bad idea) <br />
* to remove any "/QRP" extensions (generally OK).<br />
<br />
Please refer also to the [[Multi-op/Deleting_QSO|Multi-op/Deleting_QSO]] chapter.<br />
<br />
'''Warning:'''<br />
Contest sponsors advise against deleting duplicate QSOs from your log. In fact, if the other station did not correctly get your callsign during the first QSO, this QSO will be lost! The log checking software used by sponsors never penalizes a log for dupes, so it is OK to leave them in your log.<br />
<br />
===Time Shift===<br />
<br />
This feature allow to move your log, or a portion of it, ahead or back in time.<br />
It is comparable to the CT_TIME.EXE utility supplied with CT, back in the old days, and it has been extended in fuctionality. <br />
<br />
For complete details please refer to [[Menu:Tools#Time_shifting| Menu:Tools Time shifting]] in this manual.<br />
<br />
===Resolving 10-Minute-Rule Violations===<br />
<br />
This is a typical Multi-OP item. Please see [[Multi-op/Issues/Non_Multipliers|Multi-op/Issues/Non_Multipliers]] for more information about this topic.<br />
<br />
==Quit==<br />
Closes the current file and quits Win-Test back to the Windows environment.<br />
<br />
<br />
<br />
[[Menus|Back to Menus]]</div>N6TVhttps://docs.win-test.com/w/index.php?title=FAQ:Rotator_Control_and_wtRotators&diff=4566FAQ:Rotator Control and wtRotators2016-02-23T05:30:10Z<p>N6TV: /* How do I control a Green Heron RT-21 control box with wtRotators? */ Remove statement about using real serial rather than USB-to-Serial. Suggest wtRotators v1.4.2 or later.</p>
<hr />
<div>==How do I control my rotators with Win-Test?==<br />
Win-Test provides a separate program called '''wtRotators''' to connect to rotator control boxes. wtRotators shares the rotator controller with one or more copies of Win-Test via local TCP/IP broadcast messages. A third party program called [http://www.qsl.net/yo3dmu/index_Page346.htm PstRotatorAz] offered by YO3DMU may also be used with Win-Test instead of wtRotators.<br />
<br />
Both Win-Test ''and'' wtRotators/PstRotatorsAz have to be configured to use the same '''broadcast address''' and '''port number''', or else Win-Test and the rotator control software will not be able to communicate.<br />
<br />
* '''If you are using a single computer''' for both logging and rotator control (e.g. single-op), follow the procedure for [[Rotators#Configuring_wtRotators_.28single_PC.2C_no_network.29|Configuring wtRotators (single PC, no network)]]. It explains how to use the "loopback" address so that all communication between Win-Test and wtRotators stays inside the computer, instead of going over the LAN.<br />
<br />
* '''If you are using multiple networked computers''', and want to control rotators from more than one PC, (e.g. multi-single, multi-multi), follow the procedure for [[Rotators#Configuring_wtRotators_.28multi-op_environment.29|Configuring wtRotators (multi-op environment)]]. You only need to run wtRotators on the PC that is physically connected to the control box, not all of them.<br />
<br />
In both environments, it is essential to '''configure the ''same'' broadcast address and port number in both programs.'''<br />
<br />
Win-Test will automatically calculate beam headings and rotate the appropriate antenna as long as this information is properly defined to wtRotators. See [[Rotators#Add_your_rotators|Add your rotators]].<br />
<br />
==Can I make wtRotators start automatically when I start Win-Test?==<br />
Yes. In '''Win-Test''', select [[Menu:Windows#Rotators|Windows | Rotators]] then right click and select '''Local wtRotators | Start/stop automatically'''.<br />
==How do I control a Green Heron RT-21 control box with wtRotators?==<br />
Select '''Hy-Gain DCU-1''' as the rotator type.<br />
<br />
Serial ports numbered COM10 and above are supported by wtRotators version 1.4.2 or later. Earlier versions only work with COM1 to COM9. If using the USB Interface, use the Windows Device Manager to determine the virtual serial port assigned to your control box.</div>N6TVhttps://docs.win-test.com/w/index.php?title=Check_Partial_and_Np1_Files&diff=4565Check Partial and Np1 Files2016-02-22T23:07:36Z<p>N6TV: /* Files names list */ Fix file name for CQ WW 160M</p>
<hr />
<div>The [[Menu:Windows#Check_Partials|Check Partials Window]] displays callsigns whenever 2 or 3 characters are entered in the callsign field, based on the contents of certain files.<br />
==Check Partial and N+1 Files==<br />
<br />
Pre version 3.3.5, Win-Test used a native database format for Check Partials and N+1 checking, called the<br />
DTB database file format which was mostly associated with a specific contest.<br />
<br />
With that version, both the SCP and the DTA formats are additionally supported by Win-Test.<br />
<br />
<ul><br />
<li> Win-Test accepts SCP plain text files. SCP stands for Super Check Partial. The structure of the file is simple, one callsign per line, no ordering required. SCP is the preferred format for Win-Test.<br />
<br />
<li> Secondly CT compatible binary DTA files (MASTER.DTA) are supported by Win-Test. These files are usually available before the major contest. <br />
<ul><br />
<li> [http://www.supercheckpartial.com http://www.supercheckpartial.com] this is the main reference site for SCP and DTA files. Fully updated.<br />
<li> [http://www.qsl.net/k1tr/master.htm http://www.qsl.net/k1tr/master.htm] this site maintain a MASTER.DTA file for North American VHF/UHF Contests<br />
<li> [http://www.datomonline.com/suppfiles.html http://www.datomonline.com/suppfiles.html] this site was used by NA users (actually outdated!)<br><br />
<p> </p><br />
</ul><br />
<br />
<li> Finally, DTB files are supported for backward compatibility.<br />
</ul><br />
<br />
Win-Test now accepts specialized Check Partial files, separated by band and by mode for any given contest. <br />
This should improve log accuracy and QSO rate. To get more details on how to name these files so that they can be found by Win-Test in the right situation, see [[Check_Partial_and_Np1_Files#Naming_Convention|Naming Convention]] below, or read [http://download.win-test.com/files/checkPartial/%23_READ_ME_%23.TXT http://download.win-test.com/files/checkPartial/READ_ME.TXT].<br />
<br />
{{wbox|Note|If a contest-specific check partial file or database (.dtb) file is present in the Win-Test directory shown below, it will be used as the default file for partial and N+1 checks ''instead of'' '''MASTER.SCP'''. To override this, use the file name '''DEFAULT.SCP''' or '''DEFAULT.DTA''' instead of '''MASTER.SCP''' or '''MASTER.DTA'''.}}<br />
===Location===<br />
These files must be located in the appropriate directory:<br />
<br />
For Win-Test version 4, save check partial files in:<br />
* Windows XP: <tt>'''C:\Documents and Settings\All Users\Application Data\Win-Test\databases\'''</tt><br />
* Windows Vista or Windows 7: <tt>'''C:\ProgramData\Win-Test\databases\'''</tt><br />
{{wbox|Note|When renaming or saving '''MASTER.SCP''', '''DEFAULT.SCP''' etc. make sure that the file name is not '''MASTER.SCP.SCP''', or '''DEFAULT.SCP.txt''', which will prevent these files from loading. See instructions below explaining how to make the full file name visible in Windows.}}<br />
<br />
For Win-Test version 3:<br />
* <tt>'''C:\Program Files\Win-Test\'''</tt> (or the Win-Test installation directory)<br />
<br />
====Viewing hidden files and folders====<br />
By default, Windows hides some of these directories, making them invisible. You can view them via [[Menu:File_open#Explore|File | Explore | /databases directory]], or even better, make all hidden folders visible, and make all file extensions (.SCP, .DTA, etc.) visible too.<br />
<br />
To display hidden files and folders and extensions:<br />
=====Windows XP=====<br />
# Open '''Folder Options''' in the Windows '''Control Panel'''. <br />
## Click '''Start''', and then click '''Control Panel'''.<br />
## Double-click '''Folder Options'''.<br />
# On the '''View''' tab, under '''Hidden files and folders''', click '''Show hidden files and folders'''.<br />
# ''Remove'' the check mark next to '''Hide extensions for known file types'''.<br />
# Click '''OK'''.<br />
<br />
=====Windows Vista and Windows 7=====<br />
# Open Folder Options by clicking the '''Start''' button, clicking '''Control Panel''', clicking '''Appearance and Personalization''', and then clicking '''Folder Options'''.<br />
# Click the '''View''' tab.<br />
# Under '''Advanced settings''', click '''Show hidden files, folders, and drives'''.<br />
# ''Remove'' the check mark next to '''Hide extensions for known file types'''.<br />
# Click '''OK'''.<br />
<br />
===Naming Convention===<br />
Win-Test allows the usage of 3 different formats :<br />
<br />
* <b>SCP</b> files : Plain textual - One capitalized callsign per line. No ordering required.<br />
* <b>DTA</b> files : Binary CT format - You can use MEdit (http://dxatlas.com/MEdit/Files/MEdit.zip) to work on these files<br />
* <b>DTB</b> files : Binary WT format - Kept for backward compatibility.<br />
<br />
Note that the "compact" DTA format offered by MEdit is accepted by WT.<br />
<br />
The preferred format is SCP.<br />
<br />
From version 3.3.0, WT allows one file per band, mode and contest.<br />
<br />
This means that one can build specialized files for a specific contest, and even for one band and/or mode in that contest.<br />
<br />
The naming convention of the check partial files are (where * stands for SCP or DTA or DTB) :<br />
<br />
* <tt>fileName_band_mode.*</tt><br />
* <tt>fileName_mode.*</tt><br />
* <tt>fileName_band.*</tt><br />
* <tt>fileName.*</tt><br />
<br />
===Search order===<br />
The first matching file is used for check partial searches<br />
<br />
# <tt>DEFAULT.*</tt><br />
# <tt>fileName_band_mode.*</tt><br />
# <tt>fileName_mode.*</tt><br />
# <tt>fileName_band.*</tt><br />
# <tt>fileName.*</tt><br />
# <tt>MASTER.*</tt><br />
# <tt>HF.*</tt> or <tt>VHF.*</tt><br />
<br />
If more than one type of file exists with the same name, the search order is based on the file extension:<br />
# <tt>*.DTA</tt><br />
# <tt>*.SCP</tt><br />
# <tt>*.DTB</tt><br />
<br />
So if both MASTER.DTA and MASTER.SCP exist, but no other files, MASTER.DTA will be used.<br />
<br />
If Win-Test does not find a specialized file for the current contest, it will use the MASTER.* files, or if that is not found, the HF.* and VHF.* files.<br />
<br />
To see which file is actually being used, right click on the [[Menu:Windows#Check_Partials|Check Partials Window]] and select '''Used files list...''':<br />
<br />
[[Image:Check Partial Files List.PNG|frame|center|Right click on Check Partials window and select Used files list... to determine which file is being used for super check]]<br />
<br />
===Files names list===<br />
<br />
9KCC15 : 9K CC contest<br />
AGCW_HNY : AGCW Happy New Year contest<br />
AA_DX : All Asian contest - DX side<br />
AA_AA : All Asian contest - Asian side<br />
ARI_DX : ARI contest - DX side<br />
ARI_I : ARI contest - Italian side<br />
ARI_SEZIONI : ARI Sezioni contest<br />
ARRL_10_DX : ARRL 10m contest - DX side<br />
ARRL_10_USVE : ARRL 10m contest - K/VE side<br />
ARRL_160_DX : ARRL 160m contest - DX side<br />
ARRL_160_USVE : ARRL 160m contest - K/VE side<br />
ARRL_DX_DX : ARRL DX contest - DX side<br />
ARRL_DX_USVE : ARRL DX contest - K/VE side<br />
ARRL_FD : ARRL Field Day<br />
ARRL_SS : ARRL SweepStakes<br />
BALTIC : Baltic contest<br />
CIS : CIS contest<br />
CQM : CQ-M contest<br />
CQWW_160M : CQWW DX 160m contest<br />
CQWW : CQWW DX contest<br />
WPX : CQWW WPX contest<br />
CROATIAN : Croatian contest<br />
DARC_10 : DARC 10m contest<br />
DARC_XMAS : DARC X-Mas contest<br />
EU_HF : EU HF Championship<br />
EU_SPRINT : EU Sprint<br />
FOC_MARATHON : FOC Marathon<br />
GACW : GACW DX contest<br />
HADX : HA DX contest<br />
HELVETIA_DX : Helvatia contest (DX side)<br />
HELVETIA_HB : Helvetia contest (HB side)<br />
IARU_FD_R1 : IARU Field Day Rgn 1<br />
IARU_HF : IARU HF championships<br />
IOTA : IOTA contest<br />
JIDX_DX : JIDX contest (DX side)<br />
JIDX_JA : JIDX contest (JA side)<br />
KCJ : KCJ contest<br />
KCJ_160 : KCJ Top band contest<br />
KOS : King Of Spain contest<br />
LZ_DX : LZ DX contest<br />
LOTW : LOTW contest<br />
NAQP : North America QSO Party<br />
NRAU_BALTIC : NRAU Baltic contest<br />
OC_DX_DX : Oceania DX contest (DX side)<br />
OC_DX_OC : Oceania DX contest (Oceania side)<br />
OKOM_DX_DX : OK/OM DX contest (DX side)<br />
OKOM_DX_OKOM : OK/OM DX contest (OK/OM side)<br />
PACC_DX : PACC contest (DX side)<br />
PACC_PA : PACC contest (PA side)<br />
TX_QP : TX QSO Party<br />
RAC : RAC Canaday Day and RAC Canada Winter contests<br />
RDAC_DX : RDA contest (DX side)<br />
RDAC_UA : RDA contest (Russian side)<br />
RDXC : Russian DX contest<br />
REF_HF_DX : REF HF (DX side)<br />
REF_HF_F : REF HF (F side)<br />
REF_160_DX : REF 160m (DX side)<br />
REF_160_F : REF 160m (F side)<br />
RSGB_1510_DX : RSGB 15/10 (DX side)<br />
RSGB_1510_UK : RSGB 15/10 (UK side)<br />
RSGB_160_DX : RSGB 160m (DX side)<br />
RSGB_160_UK : RSGB 160m (UK side)<br />
RSGB_80_CC : RSGB 80 CC contest<br />
RSGB_AFS : RSGB AFS<br />
RSGB_CMW : RSGB Commonwealth<br />
R_160_DX : Russian 160 (DX side)<br />
R_160_UA : Russian 160 (UA side)<br />
SAC_DX : SAC (DX side)<br />
SAC_SC : SAC (Scandinavian side)<br />
SP_DX_DX : SP DX contest (DX side)<br />
SP_DX_SP : SP DX contest (SP side)<br />
STEW_PERRY : Stew Perry Challenge<br />
TOEC : TOE contest<br />
UBA_DX : UBA DX contest<br />
UBA_SPRING_DX : UBA Spring (DX side)<br />
UBA_SPRING_ON : UBA Spring (ON side)<br />
UFT_HF : UFT HF contest<br />
UK_DX : Ukranian DX contest<br />
WAE_DX : WAE contest (DX side)<br />
WAE_EU : WAE contest (EU side)<br />
WAG_DX : WAG (DX side)<br />
WAG_DL : WAG (DL side)<br />
YO_DX_DX : YO DX contest (DX side)<br />
YO_DX_YO : YO DX contest (YO side)<br />
YU_DX : YU DX contest <br />
<br />
For example, if you want to use a specific ARRL DX (DX side) for 80m you must name it :<br />
<br />
ARRL_DX_DX_80.* (where * stands for SCP or DTA or DTB)<br />
<br />
<br />
[[Main Page|Back to Main Page]]</div>N6TVhttps://docs.win-test.com/w/index.php?title=Menu:Windows&diff=4564Menu:Windows2016-02-19T07:13:32Z<p>N6TV: /* Rotators */ Explain in more detail how to use the Rotators window.</p>
<hr />
<div><big><big>Menu:Windows</big></big><br />
<!-- Adopted to Stylesheet DL6RAI --><br />
<br />
Most of the windows have a context or "pop-up" menu which can be opened by right-clicking on the window.<br />
<br />
All windows can be moved by "dragging" the title bar with the mouse pointer. Simply hold down the left mouse button while the cursor is over the title bar, and drag the window with the mouse. Another option is to hold down the '''<tt>Ctrl</tt>''' key and the left mouse button while the mouse pointer is positioned anywhere within a window (except for the RTTY reception windows), then drag.<br />
<br />
{{wbox|Tip|Hold down the '''<tt>Shift</tt>''' key while dragging or resizing a window to "snap" it into position, right next to the edge of an adjacent window.}}<br />
<br />
==Log Entry (Main window)==<br />
[[Image:LogEntryWindow.PNG|frame|center|The Win-Test main logging window.]]<br />
<br />
Use the Win-Test main window or "Log Entry" window to enter all QSOs made on the primary radio. The window displays the last nine QSOs in the log, plus a tenth line for entering the next QSO. The title bar displays the current log file name, the station name entered in the [[New_Log#Step_2:_Setup_your_log|Contest Configuration window]] (e.g. "[Shack]"), and the current operator's callsign (for multi-ops that use the '''<tt>OPON</tt>''' or '''<tt>LOGIN</tt>''' [[Text_commands#Multi_Operating|text commands]]). By default, the Win-Test main window serves as a background for all other windows, but you may also choose to have every window "float" independently (see [[Menu:Options#Windows]]). <br />
<br />
When you close the log entry window, Win-Test terminates.<br />
<br />
Any QSO may be edited simply by typing over anything that needs correction. Use the '''<tt>[Up arrow]</tt>''' and '''<tt>[Down arrow]</tt>''' keys to edit previous QSOs. To restore the original QSO data, press '''<tt>Ctrl-Z</tt>''' before moving the cursor from that line. You can also delete a QSO (if single-op), though it is usually better to just enter a duplicate QSO -- see [[Menu:Edit#Delete_QSO]] for more information.<br />
<br />
When the cursor is positioned in the callsign field, data is entered in "insert mode", that is, typing does not replace characters, it only inserts them. In all other fields, data is entered in "overtype mode". See [[FAQ:User_Interface#Can_I_use_.22Insert_Mode.22_in_a_serial_number_or_exchange_field.3F|this entry in the FAQ]] for the rationale.<br />
<br />
The '''<tt>[Spacebar]</tt>''' key is used to quickly move the cursor back and forth between the callsign field and the received exchange field, skipping over the RST columns.<br />
<br />
{{wbox|Tip|Enter a "?" character in the middle of a callsign or exchange as a placeholder for missing information, e.g. <code>F?MZN</code>. Then when you press '''<tt>[Spacebar]</tt>''', the cursor will jump directly to the "?" character, and you can overtype it with the missing data (even in the callsign field).}}<br />
<br />
The '''<tt>[Backspace]</tt>''', '''<tt>[Del]</tt>''', '''<tt>[Left arrow]</tt>''', '''<tt>[Right arrow]</tt>''', '''<tt>[Home]</tt>''', '''<tt>[End]</tt>''', '''<tt>[Ctrl][Left arrow]</tt>''' and '''<tt>[Ctrl][Right arrow]</tt>'''keys operate conventionally, within a single field; they do not move the cursor outside of the current field. <br />
<br />
The '''<tt>[Tab]</tt>''' key may be used to position the cursor under the RST sent column as well as callsign and exchange. The '''<tt>[>]</tt>''' and '''<tt>[<]</tt>''' keys work similarly, but they also allow you to move the cursor to the QSO time field for direct editing. You can also change the time, date, frequency, serial number sent and other fields of a QSO by positioning the cursor on any line and pressing '''<tt>[Alt-F]</tt>''' to display the [[Menu:Edit|Edit QSO pop-up menu]].<br />
<br />
You may scroll back through the entire log by pressing the '''<tt>[PageUp]</tt>''' and '''<tt>[PageDown]</tt>''' keys.<br />
<br />
{{wbox|Tip|Press '''<tt>Ctrl-[PageUp]</tt>''' to scroll back in the log by 24 hours.}}<br />
<br />
Enter a '''QSO number''' on the last line and press '''<tt>[Ctrl-g]</tt>''' to "Go to" that QSO number in the log. Press '''<tt>[Ctrl-g] [Enter]</tt>''' to return to the bottom of the log.<br />
<br />
Enter a callsign, prefix or '''beam heading''' (0 to 360°) on the last line and press '''<tt>[Ctrl]+[F12]</tt>''' to rotate to that heading. Press '''<tt>[Alt]+[F12]</tt>''' for long (or "alternate") path. For more information, see [[Rotators#Testing_the_configuration|Rotators]].<br />
<br />
Many other keys may be used in this window to assist with rapid data entry. For example, '''<tt>[F11]</tt>''' clears the entire QSO, whereas '''<tt>Ctrl-W</tt>''' clears only the current field. See [[Keys#Editing_and_moving_around_the_QSO_entry_line|Keys - Editing and moving around the QSO entry line]].<br />
<br />
The font size, background color, and header line attributes of this window may be adjusted by right clicking and selecting the '''Log''' option (see [[Menu:Options#Log]]). The yellow header text can be centered, left-justified, or completely hidden.<br />
<br />
The columns vary from contest to contest. In the CQ World-Wide example above,<br />
<br />
* '''QSO''' - raw QSO number. Can be hidden using [[Menu:Options#Hide_QSO_numbers|Hide QSO numbers]] (recommended for Multi-Multi contests with a sent serial number)<br />
* '''Bd''' - band. Can be changed with '''<tt>[Alt-F1]</tt>''', '''<tt>[Alt-F2]</tt>''', or '''<tt>[Alt-F]</tt>'''<br />
* '''Time''' - QSO time (UTC). Can be changed by moving the cursor with the '''<tt>[<]</tt>''' key, or '''<tt>[Alt-F]</tt>'''<br />
* '''Callsign''' - Callsign of station worked.<br />
{{wbox|Tip|Enter Win-Test [[Text_commands#List_of_Text_Commands|text commands]] (menu shortcuts) in the callsign field.}}<br />
* '''Sen/Rcvd''' - Sent and received exchanges<br />
* '''Mult''' - multipliers and other information:<br />
** '''C''' - Country multiplier<br />
** '''Z''' - Zone multiplier<br />
** '''DUPE''' - Duplicate contact<br />
** '''????''' - Multiplier in received exchange field not recognized (e.g. unrecognized state or section abbreviation, zone number out of range)<br />
** '''////''' - Unrecognized country prefix<br />
** '''!!!!''' - Multiplier violation (non-mult worked by a Mult station in a Multi-single, band change violation, etc.)<br />
** <i>other</i> - Prefix, country, state, grid, etc. multiplier<br />
* '''Pt''' - QSO points<br />
* '''Stn''' - Station identifier (can be changed by pressing '''<tt>Alt-Y</tt>''' - see [[Keys#Multi_Operator]])<br />
**'''R1/R2''' - Run 1 or Run 2 (multi-two), or Radio 1 / Radio 2 (SO2R).<br />
**'''R/M''' - Run or Mult (Multi-single)<br />
**'''+''' (suffix) - Indicates QSO data entered by a support or [[Menu:Windows#Partner|partner station]]<br />
<br />
Finally, a red information line at the bottom of the window displays additional information, such as<br />
* '''* New zone *'''<br />
* '''* New country *'''<br />
* '''* Dupe with #1963 at 23:59Z 2008-11-30 (25) * '''<br />
* '''* Spotted by F5MZN * '''<br />
* Brief one-line packet cluster announcements of new multipliers<br />
<br />
==Worked Gridsquares==<br />
<code>Windows | Worked Gridsquares</code> or '''<tt>Alt-L</tt>'''<br />
<br><br />
Opens (or closes) the gridsquares window. The gridsquares worked are in grey, the red spots are the stations worked and the green spots are the stations spotted. The current gridsquare is displayed in red color to give an indication of direction. This works even with only four of the six characters entered.<br />
<br />
[[Image:WindowsGridSquareMap1.gif|center|frame|Gridsquares Map]]<br />
<br />
If the [[Menu:Windows#DX-Cluster_Announcements|DX-Cluster Announcements]] window is opened and the gridsquare of a spot is known, passing the mouse over this spot will blink its location in this window.<br />
<br />
Right click on the map to display the pop-up window:<br />
<br />
[[Image:GridSquareMapPopUp.PNG|center|frame|Gridsquare map pop-up window displayed by right-clicking on the map]]<br />
<br />
* '''Copy the map''' copies the image to the Windows clipboard<br />
* '''Actualize Information''' controls when the map will be updated:<br />
** Pressing the spacebar <br />
** Automatically<br />
* '''Colorize worked gridsquares''' marks worked grid squares in gray<br />
* '''Show QSO''' marks QSOs with a red dot<br />
* '''Display the spots''' marks spotted stations with a green dot<br />
* '''Show gridsquares''' draws the squares and the grid square lines<br />
* '''Show fields only''' turns grid square outlines off<br />
* '''Show caption''' displays the major grid square names (first two letters)<br />
* '''Center map here''' lets you move the center of the map interactively. <br />
<br />
{{wbox|Note|This option is available only if you have '''not''' selected "Always center on the operating QTH" in the Properties dialog (see below).}}<br />
<br />
* '''Properties...''' allows you to modify several display parameters:<br />
<br />
[[Image:GridSquareMapProperties.PNG|center|frame|Gridsquares Map Properties]]<br />
<br />
The larger the scale, the bigger the map.<br />
<br />
==Worked Zones==<br />
<code>Windows | Worked Zones</code> or '''<tt>Alt-Z</tt>'''<br />
<br><br />
Opens (or closes) the worked zones window. The title of this menu item will fit to the chosen contest.<br />
The window displays the worked multipliers (in blue) or not (in white) on the current band, and possibly the current mode.<br />
<br />
Some examples:<br />
<br />
[[Image:WindowsZone1.gif|center|frame|Worked departements window (French REF HF contest)]]<br />
<br />
[[Image:WindowsZone3.gif|center|frame|Worked states and provinces window (International ARRL DX contest)]]<br />
<br />
Furthermore, with a right click on this window (if the contest is multi-bands and/or multi-modes) you can display the distribution of these multipliers by band (and/or mode).<br />
<br />
<br />
[[Image:WindowsZone2.gif|center|frame|WAZ zones worked window by band (CQWW DX contest)]]<br />
<br />
At last, the same contextual menu allows you to copy all the datas of this window into the clipboard as an image or a text, and directly paste it as a text file or an Excel (TM) or OpenOffice spreadsheet.<br />
<br />
==Worked DXCC==<br />
<code>Windows | Worked DXCC</code> or '''<tt>Alt-M</tt>'''<br />
<br><br />
Opens (or closes) the worked DXCC window. The title of this menu item will change with the contest chosen.<br />
<br />
[[Image:WindowsMult.gif|center|frame|Worked DXCC countries window]]<br />
<br />
If one DXCC country has been worked on a band (possibly a mode), this band will be displayed in blue, otherwise it remains in white. This window is resizable.<br />
<br />
A right click on this window allows to display the countries alphabetically sorted (within the same continent), or sorted by number of band/mode worked. More, to easily search for missing countries, the countries worked on all bands can be hidden (clean sweeps).<br />
<br />
You can easily move to the next (or previous) bookmark - displayed on a yellow background by default - by holding the '''<tt>Shift</tt>''' key down, while rolling your mouse wheel.<br />
<br />
Last, all the data included in this window can be copied as a text file, and pasted in text or directly in an Excel (TM) or OpenOffice spreadsheet, for a later analysis.<br />
<br />
==Check Callsign==<br />
<code>Windows | Check Callsign</code> or ['''<tt>F9</tt>''']<br />
<br><br />
Opens (or closes) the worked callsign window. This window displays a checkmark if and on which bands a specific callsign has been logged before. Depending on the type of the contest, the display may show more than one column to display the different possible modes.<br />
<br />
[[Image:WindowsCheckCallsign.gif|center|frame|The Check Callsign Window]]<br />
<br />
Moving the mouse cursor over the checkmark will bring up additional information about this QSO. And a double-click on it will move the cursor to this QSO.<br />
<br />
==Check Multipliers==<br />
<code>Windows | Check Multipliers</code> or ['''<tt>F10</tt>''']<br />
<br><br />
<br />
Opens (or closes) the checking multipliers window.<br />
<br />
[[Image:WindowsCheckCountry.PNG|center|frame|Check Multipliers window for the CQ World-Wide DX contest]]<br />
<br />
To use this window, enter a callsign or country prefix in the data entry area of the main logging window. The dark blue line indicates the current band. The other lines indicate whether this multiplier has been worked or not on other bands (and in other modes if the contest rules permit). If the callsign entered has been worked on other bands, Win-Test displays those QSOs. Otherwise, the callsign of the first station worked in that multiplier on that band is displayed, if any. For the CQ World-Wide DX contest, display priority is: same callsign, same country and same zone. An uppercase "Z" in the last column indicates that the zone and country have been worked on the indicated band. A lowercase "z" means the zone has been worked, but not the country. And of course a blank line indicates that both the zone and country are needed. See also the [[Menu:Windows#Search_for_Worked_Multipliers_or_Partial_QTH_Locators|Search for Worked Multipliers]] window.<br />
<br />
Additional information about the multiplier is displayed at the bottom:<br />
<br />
* The official country prefix and country name<br />
* A small icon indicating if it is local day, night, or sunrise/sunset time in that country<br />
* The current local time in that country (suffixed by a lowercase "l")<br />
* The short (Az) and long path (Lp) beam headings (azimuths) to this multiplier (based on the station locator entered in the [[New_Log#Step_2:_Setup_your_logcontest|Contest configuration screen]])<br />
* The sunrise (SR) and sunset (SS) time in this country, expressed as UTC (suffixed by a lowercase "z"). These times are computed from the geographical coordinates given taken from the CTY* file or your QTH locator, if specified in the setup dialog.<br />
* Graphical indication of the sun status on both sides of the QSO (may be disabled via the context menu)<br />
** Two yellow bars represent the sun over 24 hours of the day. The top bar displays the situation at the DX location, while the bottom bar represents your own location.<br />
** A pink cursor denotes current time. <br />
** Dotted lines represent local noon or local midnight. <br />
<br />
A double click on a line will move the cursor to the specified QSO. Press '''<tt>[Ctrl-End]</tt>''' or '''<tt>[Ctrl-G]</tt>''', '''<tt>[Enter]</tt>''' to return the cursor to the blank line at the end of the data entry area.<br />
<br />
Finally, using the context menu (right click on the window), you can change '''Actualize information''' to '''Automatically''' (recommended) or to '''Pressing the space bar''' to indicate when you want the check multiplier screen to be updated. "Automatically" updates the screen after each keystroke. Any modification in the received exchange field (e.g. zone) also updates this check multiplier window.<br />
<br />
==Search for Worked Multipliers or Partial QTH Locators==<br />
<code>Windows | Search for Worked Multipliers</code><br><br />
Keyboard shortcut: '''<tt>Shift+F10</tt>'''<br />
<br><br />
<br />
Lists all the callsigns logged in a specified multiplier (Zone, State, ARRL Section, Grid Square Locator, etc.).<br />
<br />
To quickly list everyone you have logged in a particular multiplier, sorted by band, enter the multiplier in the ''callsign'' field and press '''<tt>Shift+F10</tt>'''. The [[Menu:Windows#Check_Partials|Check Partial Window]] will be displayed in a different format, as shown below.<br />
<br />
[[Image:WindowsCheckMult1.gif|center|frame|Looking for a departement during the REF HF Contest]]<br />
<br />
[[Image:WindowsCheckMult2.gif|center|frame|Looking for a WAZ zone during the CQWW DX (Zone 40)]]<br />
<br />
[[Image:WindowsCheckMult3.gif|center|frame|Looking for an US state during the ARRL DX Contest (here: District of Columbia, DC)]]<br />
<br />
Any further typing in the callsign field restores the [[Menu:Windows#Check_Partials|Check Partial Window]] to its normal appearance. You can also use '''<tt>[Ctrl-W]</tt>''', '''<tt>[Alt-W]</tt>''', or '''<tt>[F11]</tt>''' to erase the multiplier from the callsign field.<br />
<br />
{{wbox|Note|This search only works for contests where the multiplier is logged as part of the exchange, so it doesn't work for the CQ WPX contest or the ARRL DX Contest (when operating from the U.S. and Canada).}}<br />
<br />
For VHF/UHF/SHF... contests, this function is dedicated to partial QTH locator search. Enter the partial QTH locator either in the callsign or in the locator field and then press '''<tt>Shift-F10</tt>'''.<br />
<br />
[[Image:WindowsCheckPartialQTHLocator.PNG|center|frame|Searching callsigns by QTH locator]]<br />
<br />
==Check Partials==<br />
<code>Windows | Check Partials</code> or ['''<tt>F12</tt>''']<br />
<br><br />
<br />
Opens (or closes) the Check Partials window. The master file used is normally MASTER.SCP or DEFAULT.SCP or ''contest''.DTB, as described under [[Check_Partial_and_Np1_Files|Check Partial and Np1 Files]].<br />
<br />
[[Image:WindowsCheckPartial.gif|center|frame|Checking partials. Partial callsign entered: A2Q]]<br />
<br />
If this window is open, and at least 3 characters are entered in the callsign logging field, Win-Test looks in the master database for the callsigns including the 3-character string.<br />
<br />
For example, in this upper screen-shot, the partial callsign entered is "A2Q". All the callsigns found by Win-Test show this string.<br />
<br />
The white callsigns are those not worked yet. The green callsigns are stations worked on another band, but not the current band. The red callsigns are the dupes (callsigns already worked on the current band).<br />
<br />
[[Image:WindowsCheckPartialOptions.gif|center|frame|Available context menu options in the Check Partial window]]<br />
<br />
Double clicking on a callsign copies it into the callsign logging field.<br />
<br />
Right click in the window to brings up a context menu where you can choose if Win-Test is to use the master database or just your log. Another option is (in some contests) if you want to see the expected report in that window (from ''contest''.DTB).<br />
<br />
For slow contests, it might make sense to start the check partial search after the second letter is entered into the callsign field, rather than the third. <br />
<br />
Another option allows you limit the number of callsigns displayed to fit the available space in the window.<br />
<br />
Finally, the option '''Used files list''' will display the master file that Win-Test has loaded to feed the Check Partials window:<br />
<br />
[[Image:Check Partial Files List.PNG|center|frame|Used files list selected from Check Partial window pop-up menu]].<br />
<br />
See [[Check_Partial_and_Np1_Files|Check Partial and Np1 Files]] for more info about naming super check files, search order, and how to update them.<br />
<br />
In HF contests such as CQ World-Wide, you can enter a zone number in the '''callsign''' field and press '''<tt>Shift+F10</tt>''' to display a list of prefixes in that zone, and a list of stations worked in that zone.<br />
<br />
[[Image:WindowsCheckPartialShiftF10.png|center|frame|Check partial window after entering 37 in the callsign field and pressing Shift+F10 to view countries in that zone. 5H3EE is in zone 37 and has been worked on 20m.]]<br />
<br />
In VHF/UHF contests, pressing '''<tt>Shift+F10</tt>''' on a partial QTH locator changes the Check Partials Window to the Partial QTH Locator Search Window. This feature is helpful to identify stations in a VHF/UHF contest when you copy only the QTH locator.<br />
<br />
[[Image:WindowsCheckPartialResult.png|center|frame|Check Partial QTH Locator window]]<br />
<br />
You may enter the partial QTH locator either in the callsign or in the QTH locator fields. A minimum of four characters has to be present in order to check the locator.<br />
<br />
==Check N + 1==<br />
<code>Windows | Check N + 1</code> or ['''<tt>F8</tt>''']<br />
<br><br />
<br />
Opens (or closes) the N + 1 window. The master file used is normally MASTER.SCP or DEFAULT.SCP or ''contest''.DTB, as described under [[Check_Partial_and_Np1_Files|Check Partial and Np1 Files]].<br />
<br />
If this window is open, and at least 3 characters are entered in the callsign logging field, Win-Test looks in the master database for the callsigns differing from the partial callsign by one character.<br />
<br />
This command also detects 2-character swap (dyslexia), as well as one missing character.<br />
<br />
[[Image:WindowsNp1_1.gif|center|frame|N + 1 window (Partial call entered: W5TQ)]]<br />
<br />
If the callsign is not included in the master database, and has not been worked yet, it is considered a UNIQUE. Otherwise, it is displayed in the first position.<br />
<br />
[[Image:WindowsNp1_2.gif|center|frame|N + 1 window (Partial call entered: K3OK)]]<br />
<br />
The white callsigns are the stations not yet worked. The green ones are those worked on another band, but not the current band. The red callsigns are dupes.<br />
<br />
[[Image:WindowsNp1_3.gif|center|frame|Available context menu options in the N+1 window]]<br />
<br />
Double clicking on a callsign copies it into the callsign logging field.<br />
<br />
A right click in the window brings up a context menu where you can choose to use the master database or just your log. A second option (in some contests) is if you want to see the expected report in that window (from ''contest''.DTB). You may also wish to limit the number of callsigns displayed to the available space in the N+1 window. Finally, the option "Used files list" will display the master file that Win-Test has loaded to feed the Check Partials window.<br />
<br />
==Partner==<br />
<code>Windows | Partner</code><br />
<br><br />
Opens (or closes) the partner window.<br />
<br />
[[Image:PartnerWindow.gif|right|frame|Partner window with two entries. You can now pull W6XR into the callsign field by pressing '''<tt>Alt-1</tt>''']] <br><p>This feature is especially useful in a Multi-OP environment when facing large pile-ups and/or weak signals or when you are training a new operator.</p><br />
<br />
Situation: You get several callers coming back to your CQ. You pull out one callsign - but sometimes you are able to copy another callsign or at least parts of it. If you could remember this second call after the first QSO, you'd be able to call the second station right away (without QRZ) and save time.<br />
<br />
Improvement: Set up a second operator (OP2), a second computer and a second pair of headphones, sometimes a second receiver. Both OPs now open up the Partner window on their computer. The running operator OP1 continues like before: He works the first callsign. In the mean time, the OP2 supports OP1 to copy the callsign - or alternatively - he can add callsigns he copied from the pile-up by entering the callsign on the QSO entry field and then pressing '''<tt>Alt-Enter</tt>'''.<br />
<br />
This callsign will now be displayed on all computers in the network that are set at the same band and mode. OP1 will see the new callsign after his first QSO and calls that station right away. <br />
<br />
The Partner window can hold up to 9 callsigns, and theses calls can be pulled into the callsign field with '''<tt>Alt-1</tt>''', '''<tt>Alt-2</tt>'''...'''<tt>Alt-9</tt>'''. Usually this is done by OP1 to log that callsign, while OP2 uses this function to remove the call from the partner window. Once the QSO is logged, that callsign will disappear from both partner windows.<br />
<br />
You can also swap the callsign field with one of the entries by pressing '''<tt>Ctrl-1</tt>''', '''<tt>Ctrl-2</tt>'''...'''<tt>Ctrl-9</tt>'''.<br />
<br />
Using message variables on CW and RTTY you can now enter a QSO (with correction or not), grab another callsign from the Partner window, and send the new report in one keystroke, by using:<br />
'''$CORRECT TU $CR NOW $GRABPARTNER $NEXT $F2''' (sends call if corrected before the TU)<br />
for the '''<tt>[Plus]</tt>''' key, or<br />
'''$CURRENT TU $CR NOW $GRABPARTNER $NEXT $F2''' (resends full call before the TU)<br />
assuming '''<tt>$F2</tt>''' contains the report.<br />
<br />
If you want to manually grab a callsign from the Partner window you can use:<br />
'''$PREV TU NOW $LOGGED $F2'''<br />
Then<br />
# Use the '''<tt>[Enter]</tt>''' key to silently enter the current QSO<br />
# Grab the next callsign from the Partner windownd (via double-click or Alt-''n'')<br />
# Send the message above<br />
<br />
[[Image:WindowsPartnerWindowRealtimefeature.PNG|left|frame|Partner Window in Real Time Mode]]<br />
<br><p>When a QSO is logged locally or via the network it is checked against the contents of the partner window, and - if found - removed from the partner window as it is now obsolete.</p><br />
<br />
If automatic exchange guessing is enabled, a callsign grabbed from the partner window will have the exchange window filled in and will update the check partials and N+1 windows.<br />
<br />
Finally, the entire Partner window content can be cleared by using the appropriate context menu item or by pressing '''<tt>Alt-Backspace</tt>'''. Individual entries can be removed via '''<tt>Ctrl-Doubleclick</tt>'''.<br />
<br />
Up to three support partners can be engaged. If you do not want the partner to be limited by band and mode, use the "No band/mode filtering" option in the context menu of the partner window. <br />
<br />
A '''real-time''' mode is available in the partner window's context menu. This allows the main operator to have a real-time view on what the partner(s) is(are) typing (character by character) so he(she) does not have to wait until they press '''<tt>Alt-Enter</tt>''' in this time-critical situation. For this to work, the supporting partner has to change his station type to "Support" (see section [[Menu:Commands#Station_Type]]), indicated by '''<tt>R+</tt>''' on the QSO entry line.<br />
<br />
In the context menu of the partner window there are two settings that can be done, when more then one partner (up to 3) is engaged:<br />
* as support, must be selected to which slot this partner will send its real-time characters<br />
* as runner, must be selected how many slot are being displayed at the partner window top<br />
<br />
The runner will then grab a real-time slot with '''<tt>Alt-Space</tt>''', or in all cases, he can also double-click on any callsign of this window.<br />
<br />
==Status==<br />
<code>Windows | Status</code> or '''<tt>Alt-J</tt>'''<br />
<br><br />
Opens (or closes) the status window.<br />
<br />
[[Image:StatusWindow.gif|center|frame|Status Window]]<br />
<br />
This window indicates the status of each station connected to the network. From left to right, are displayed :<br />
<br />
* Station name<br />
* Current band and mode<br />
* Station type<br />
* QSY frequency of the current band and mode<br />
* Radio 1 frequency<br />
* Radio 2 frequency<br />
* Time left before a possible QSY, according to the 10 minutes M/S rule, or "OK" if the station is allowed to make a QSY on another band. Note that this column only appears if the contest specifies this particular rule.<br />
<br />
Your own station is displayed in a deep blue background. The active radio of each station has its frequency in red characters.<br />
The list may be by band and station names when it gets cluttered in a very large network by using the appropriate function in the context menu.<br />
<br />
A double left click on a station name will display the chat dialog with this station name as default destination.<br />
<br />
Opening the context menu with a right mouseclick will allow you to turn on network traffic logging. This might be useful for basic network troubleshooting. This log file uses the .ntk (stands for NeTworK) file extension.<br />
<br />
At last, a double left click on any frequency displayed will tune the current radio to that frequency.<br />
<br />
==Skeds==<br />
<code>Windows | Skeds</code> or '''<tt>Alt-B</tt>'''<br />
<br><br />
Opens (or closes) the skeds window.<br />
<br />
[[Image:WindowsSked.gif|center|frame|Skeds Window]]<br />
<br />
Skeds (Alt-E) and passed stations (Alt-D) are displayed in this window. See [[Multi-op/Passing]].<br />
<br />
* A grey background means that the sked is over for more than 10 minutes.<br />
* A yellow background means that the sked is planned within less than 10 minutes maximum (a "hot sked"). If the window was not open, it will pop-up to remind the operator of the hot sked. The pop-up will be suppressed, however, if Win-Test is running minimized.<br />
* A green background means that the sked is planned in more than 10 minutes.<br />
<br />
A - (minus) sign before the hour means that the sked is over for more than 24 hours. A + (plus) sign before the hour means that the sked is planned in more than 24 hours.<br />
<br />
A right click allows to sort the skeds window by time or by band. You can also hide the older skeds, and modify or cancel a sked. In a multi operating configuration, the sked data are sent across the network.<br />
<br />
At last, note that a double left click will tune the current radio on the sked frequency and capture the callsign of the scheduled station in the callsign logging field. You will thus just need to press ['''<tt>Return</tt>'''] after completing the QSO!<br />
<br />
==Solar Activity==<br />
<code>Windows | Solar Activity</code><br />
<br><br />
<br />
This option displays solar activity data that has been received from the DX cluster connection. You can chose between SSN, SFI, K and A indexes. It is an interesting tool to discover trends in propagation during a contest.<br />
<br />
<center><br />
{|<br />
|[[Image:WindowsSolarActivityWWV.png|center|frame|Solar Activity Window (WWV data)]]<br />
|[[Image:WindowsSolarActivityWCY.png|center|frame|Solar Activity Window (from DK0WCY)]]<br />
|}<br />
</center><br />
<br />
As there are two sources on the DX cluster for this kind of information, you may chose between WWV and WCY.<br />
This information can also be applied - in conjunction with HamCap - for specific propagation forecasts.<br />
See [[Menu:Options#HamCAP | Menu Options HamCAP]] in this manual.<br />
<br />
Click on the triangles to open or close a chart. You may open or close all charts at once by holding the ['''<tt>Shift</tt>'''] key down while clicking on one of the triangles.<br />
<br />
==QSY Wizard==<br />
<code>Windows | QSY Wizard</code><br />
<br />
The QSY Wizard can only be used if [[HamCAP]] is installed and running. You must also have [[Menu:Options#HamCAP| Options | HamCAP | Tab]] set to '''Charts'''.<br />
<br />
After working a DX, pressing '''<tt>Ctrl-P</tt>''' will bring up the HamCAP window with a propagation prediction to this DX. Then, the QSY Wizard will display the bands on which to which a QSY or sked may be useful:<br />
<center><br />
{|<br />
|[[Image:WindowsQsyWizard.png|center|frame|QSY Wizard]]<br />
|[[Image:HamCAPprediction.png|center|frame|HamCAP prediction to CN2R]]<br />
|}<br />
</center><br />
In the above example CN2R has been worked on 20m. After pressing '''<tt>Ctrl-P</tt>''' the wizard tells us that a QSY may be promising to 15, 40, 80 and 160m. For 10m, however, the wizard recommends a sked at 18:30 UT instead. This is the peak time predicted by HamCap for this path but MUF will be only be 20.1 MHz (the mouse cursor was over the 18:30/28MHz yellow square while creating this screenshot).<br />
<br />
==Extra Information==<br />
This window displays data included in .XDT (eXtra DaTa) files. These files are textual and have a very basic syntax. These files are suitable for name lists (your favorite contest friends or club members, whose names you never get to remember in the middle of the contest) or information about a station's capabilities on other VHF/UHF/SHF bands so that you will want to ask for a sked.<br />
<br />
[[Image:WindowsExtraDataFiles.png|center|frame|The Extra Data Files Window can be used to display additional useful information during the contest.]]<br />
<br />
===XDT Files===<br />
The first column is the callsign of the station for which information is to be displayed. The rest of the line carries the information to display. There can be only one line per callsign. Lines have to be formatted in MS-DOS mode, i.e. CR/LF at the end.<br />
<br />
You can set up to 10 default extra data files by the menu function '''<code>Options | Data files | Default data files</code>'''. These files will be opened with every log. They must be located in the WT installation directory. Refer to [[Menu:Options#Default_extra_data_files... | Menu: Options Default extra data files...]] for detailed information.<br />
<br />
You can also add '''log-specific''' extra data files by using the '''<tt>Extra files...</tt>''' item in the context menu of this window (right-click to open the contextual menu). A new window will open-up where you can click the ADD button to browse the computer resources to locate and select the file you need (see picture).<br />
<br />
[[Image:LogSpecificExtraDataFiles.png|center|frame|Click the ADD button to locate and select the file you need]]<br />
<br />
There is no limitation to the location and the number of these log-specific files. The added file names and paths will then be save in a file with '''<tt>.xdl</tt>''' extension among all the other contest specific files (.LOG, .SUM, .pkt, .gab, .wtb, etc.).<br />
<br />
<br />
If you modify an '''<tt>.XDT</tt>''' file while it is in use, you must reload it by using the '''<tt>Reload files</tt>''' item in the context menu.<br />
<br />
{{wbox|Note|This function is designed to work with no more than a few thousand callsigns only. Don't try it with millions of lines or a Callbook file!}}<br />
<br />
===Directives===<br />
Directives are special statements in the data file beginning with a hash sign and a space.<br />
<br />
The <code># TITLE</code> directive is used to display a title in the window, like this:<br />
<pre><br />
# TITLE Operator Names<br />
CT1BOH Jose<br />
DJ1YFK Fab<br />
DL4NER Werner<br />
DL6RAI Ben<br />
F5HRY Herve<br />
F5MZN Olivier<br />
F6FVY Larry<br />
M0CLW Simon<br />
M3PHP Peter<br />
</pre><br />
<br />
The <code># VARIABLE</code> directive allows you to send the extra information in a CW message by using a variable name. The variable name '''must''' begin with the $ character.<br />
<br />
Example: The following line will substitute the $OPNAME string in the CW messages with the extra info included in this file, if the sent callsign has matching data.<br />
<br />
<pre><br />
# VARIABLE $OPNAME <br />
</pre><br />
<br />
<br />
{{wbox|Note|The variable subsitution only works with the internal CW keyer.}}<br />
<br />
==Summary==<br />
<code>Windows | Summary</code> or '''<tt>Alt-S</tt>'''<br />
<br><br />
Opens (or closes) the scoring summary window.<br />
<br />
[[Image:WindowsSummary.gif|center|frame|Summary]]<br />
<br />
The displayed number of QSO does not include the dupes. Thus, the QSO column displays only the QSO that have generated points.<br />
<br />
A right click allows to copy the scoring summary data in the clipboard as an image or as a text file (in WT language or in English, depending on the contest).<br />
<br />
[[Image:LiveScoreBroadcasting.gif|center|frame|Enabling Live Score Broadcasting through the context menu]]<br />
<br />
The context menu also allows you to configure and enable live score reporting by using a specific UDP broadcast protocol [http://download.win-test.com/utils/SummaryBroadcastingSpecs.txt]. Please note that additional third-party software is<br />
needed to post your score to one of the live scoreboards on the internet.<br />
<br />
For testing purposes, there is an option to create a live score broadcast "now"; typically, it will be broadcasted automatically once every five minutes or however you set up the periodicity. Live score broadcasting in a multi operator environment is limited to the station that is the network time master. For further information about live scores, please see [http://www.w1ve.com/livescores] and [http://www.5b4wn.com/main/index.php?m=10].<br />
<br />
==Rate==<br />
<code>Windows | Rate</code> or '''<tt>Alt-R</tt>'''<br />
<br><br />
Opens (or closes) the rate window.<br />
<br />
[[Image:WindowsRate.PNG|center|frame|Rate Window]]<br />
<br />
This window is divided in different parts:<br />
<br />
The upper part displays the rate of the last hour, of the last 10 QSO, and of the last 100 QSO. It also displays a moving graph of the rate, computed on the last 15 minutes before the current QSO. The lower portion of that window displays additional rate information in text format.<br />
<br />
===Graphs===<br />
The graph is calculated on the last 15 minutes (default). Each bar, thus representing one minute on the air, calculates the moving average rate on the last X minutes, this time being selectable between 5 to 30 minutes. A short period will be selected for a contest with high rates (international HF, such as CQWW or WPX), and a longer one for a contest with slower rates (such as a national HF, or a VHF).<br />
<br />
Below is a display that shows instant continent distribution of previous QSOs. It uses the same timing parameters as the instant rates above.<br />
<br />
The QSO Timer Alarm progress bar appears below that. This bar gives a clear visual indication of the time elapsed since your last QSO. Right click and select '''Off-time timer alarm''' to set the full scale range of the progress bar. In the screen shot above, it is the red bar showing over 100H elapsed since the last QSO, but normally it is a green progress bar that advances from left to right. It begins as 100% green and slowly more of it turns red until it reaches full scale, when the bar becomes 100% red. The default scale is 5 minutes, but it is configurable between 1 and 120 minutes.<br />
<br />
===Text Information===<br />
The next part displays information about Time ON and Time OFF. For new logs, the off-time calculation is based on the contest rules. You can still use a custom setting to check your operating efficiency. Right click and select '''Off-time calculation threshold'''. If the contest rule is unknown, 15 minutes will be used as a default threshold. <br />
<br />
The next part shows information about band changes.<br />
<br />
The central part gives general information about the point statistics of the contest, e.g. time by mult, QSO counts, Mult worth, etc. <br />
<br />
The bottom part indicates the current mode and, in CW, the current speed, as well as the status of the automated CQ repeat mode.<br />
Some indicators that may appear there include:<br />
* '''CW''' - Operating mode is set to CW (press '''<tt>Ctrl-F1</tt>''' or '''<tt>Ctrl-F2</tt>''' to change)<br />
* '''SSB''' - Operating mode is set to Phone<br />
* '''RTTY''' - Operating mode is set to RTTY<br />
* '''34 WPM''' - CW speed in Words Per Minute (adjust with '''<tt>Alt-F9</tt>''', '''<tt>Alt-F10</tt>''', and '''<tt>Alt-V</tt>''')<br />
* '''34/32 WPM''' - Independent CW speed between Win-Test and WinKey pot (WinKey speed displayed on right)<br />
* '''S''' - Operator is listening in Stereo mode (operator pressed '''<tt>AltGr-S</tt>''' or '''<tt>Ctrl-Alt-S</tt>''', press '''<tt>AltGr-A</tt>''' or '''<tt>Ctrl-Alt-A</tt>''' to remove)<br />
* '''T''' - Operator is listening to the Secondary Radio (operator pressed '''<tt>AltGr-T</tt>''' or '''<tt>Ctrl-Alt-T</tt>''', press '''<tt>AltGr-A</tt>''' or '''<tt>Ctrl-Alt-A</tt>''' to remove)<br />
* '''REPEAT''' - Automatic repeating CQ feature is active and '''<tt>[F1]</tt>''' has been pressed. See [[Menu:Tools#Automatic_CQ_repeat|Automatic CQ Repeat]].<br />
<br />
===Context Menu===<br />
A right click allows you to choose on what bands and modes these calculations have to be done:<br />
<br />
* All : No filtering is done<br />
* Current : Filters only QSO done in the mode and band of the current radio<br />
* According to QSO : Filters only QSO done in the mode and band of the current QSO<br />
<br />
You can also choose to display the calculations as :<br />
<br />
* QSO / h : Only based on the number of QSO<br />
* Points / QSO : Averages the points of the QSO<br />
* Points QSO / h : Without the multipliers<br />
* Points / h : Including the multipliers<br />
<br />
Thresholds are defined and can be modified on the following properties:<br />
<br />
* Instant moving graph window -how many minutes of history are taken into account<br />
* Off Time Alarm - after how many minutes the color of the green bar will turn red<br />
* Off-time calculation - after how much time of no QSO, time is counted towards off-time (may be contest specific)<br />
* Last band change method - which event triggers the timer after a band change<br />
<br />
Moreover, the contents of the rate window can be customized by selecting one or more of the following, which are listed under the '''Display''' menu item of the context menu:<br />
<br />
* Instant rate moving graph<br />
* Instant continents distribution<br />
* Off-time timer<br />
* Time ON / Time OFF<br />
* Band Changes<br />
* Band Changes elapsed times<br />
* QSO/Mult ratio<br />
* Distances Data<br />
<br />
Finally, right click and select the '''Copy''' menu item to copy this window, as an image, to the Windows clipboard.<br />
<br />
{{wbox|Note|The available menu items in the context menu may vary depending on where you right click in the window.}}<br />
<br />
==Statistics==<br />
<code>Windows | Statistics</code> or '''<tt>[Ctrl-F9]</tt>'''<br />
<br><br />
Opens (or closes) the Statistics window, a rate sheet.<br />
<br />
[[Image:WindowsRateSheet.gif|center|frame|Statistics Window showing total QSOs made on all bands and modes, per hour]]<br />
<br />
The size of this window can be changed by dragging the edges. The window displays the number of QSOs, hour by hour, for the entire contest period.<br />
<br />
The time span is fixed depending on the contest type. For the shorter contests, the display spans 24 hours; for the major contests, it spans the full 48 hours. For DXpeditions, it is configurable from 1 to 15 days via the [Days...] button in the [[New_Log#Step_2:_Setup_your_log|Contest Configuration window]].<br />
<br />
Switching to the '''Targets''' tab in the statistics window, you may compare your current score to a pre-loaded estimate, which may be derived from a previous contest operation or generated by hand. Positive offsets with respect to the target file are shown in green color, negative offsets in red color. <br />
<br />
[[Image:Targets.PNG|center|frame|Cumulative (overall) Multiplier tracking vs. target]]<br />
<br />
You may also display hour-by-hour comparisons with the targets.<br />
<br />
[[Image:StatisticsHourlyQSOTargets.PNG|center|frame|Hour by hour QSO tracking vs. target]]<br />
<br />
Please see [[Menu:Tools#Load_an_objective_file|Menu | Tools | Load a targets file...]] for further information on exporting and loading target files.<br />
<br />
Switching to the '''Continents''' tab displays continental QSO statistics.<br />
<br />
[[Image:StatisticsContinents.PNG|center|frame|Continental QSO statistics]]<br />
<br />
A right click allows to set different display options:<br />
<br />
{| align="center"<br />
|[[Image:StatisticsPopUpMenuDisplayedData.PNG|center|frame|Pop-up menu showing displayed data options]]<br />
|[[Image:StatisticsPopUpMenu.PNG|center|frame|Pop-up menu showing band options]]<br />
|}<br />
<br />
Displayed Data<br />
<br />
* Select which kind of data to display: QSOs, Multipliers, QSO Points, etc.<br />
<br />
<br />
Band<br />
<br />
* All (total): Single color display, all bands combined<br />
* All (detailed): Multicolor display, one color per band<br />
* Current: Displays statistics for the current band<br />
* According to QSO: Displays statistics for the band of the currently selected QSO<br />
<br />
Mode<br />
<br />
* All (total): Single color display, all modes combined<br />
* All (detailed): Multicolor display, one color per mode<br />
* Current: Displays statistics for the current mode<br />
* According to QSO: Displays statistics for the mode of the currently selected QSO<br />
<br />
Display<br />
<br />
* By time: Displays an hour by hour comparison<br />
* Overall: Displays a cumulative (overall total) comparison<br />
<br />
Another option allows you to load a targets file for comparison, or export a targets file based on the current log.<br />
<br />
Finally, it is possible to copy any of the Statistics windows as image or text to the Windows clipboard. Then you can copy the data into to a text document or even into an Excel&reg; or OpenOffice spreadsheet.<br />
<br />
==Gab==<br />
<code>Windows | Gab</code> or '''<tt>Alt-I</tt>'''<br />
<br><br />
Opens (or closes) the gab window.<br />
<br />
[[Image:WindowsGab.gif|center|frame|Gab Window]]<br />
<br />
All the gab chat is displayed in this window. With a right click, you can choose to display (or not) the time when the message was sent, including (or not) the seconds. Moreover, this window can be copied as an image.<br />
<br />
In the context menu, the option "Taskbar flashing" can be selected to make the Windows Task Bar flash every time a gab is received.<br />
<br />
All the gab chat is recorded in the <tt>.gab</tt> file of the current contest.<br />
<br />
A double-click in a station name in this window will open the chat dialog, with this station name as default destination.<br />
<br />
==World Map==<br />
<code>Windows | World Map</code><br />
<br><br />
Opens (or closes) the map window<br />
<br />
[[Image:WindowsMap.gif|center|frame|World Map]]<br />
<br />
The dimensions of this worldmap window can be modified. With a right click, you can display (or not) the grey-line. Moreover, you can increase or decrease the format (zoom).<br />
<br />
An additional option allows you to display only the greyline terminator plus a little symbol for the sun which makes reading the information a little easier at times.<br />
<br />
[[Image:WorldMapWithLightTerminator.gif|center|frame|World Map with light terminator]]<br />
<br />
==Radio 1, Radio 2 (Band Maps)==<br />
<code>Windows | Radio 1</code> or <code>Windows | Radio 2</code><br />
<br><br />
Opens (or closes) the radio window.<br />
[[Image:WindowsRadio.gif|right|frame|Radio window (band map)]]<br />
These resizable windows are also called Band Maps.<br />
<br />
The frequencies of the 2 VFOs are displayed. The active VFO has a yellow background.<br />
<br />
If Win-Test has a DX cluster connection, the bandmaps are automatically fed from the DX cluster data stream, from logging contacts, and by manually adding information using '''<tt>Ctrl-Enter</tt>''' instead of '''<tt>[Enter]</tt>'''.<br />
The green callsigns are the new multipliers, the black ones are the new callsigns (not worked so far), and the dupes are in grey and slanted font.<br />
<br />
A double click on a callsign will automatically put the radio on the spot frequency and capture the callsign in the logging field. You just need to complete the QSO and press '''<tt>[Enter]</tt>'''! Press '''<tt>[Alt-F4]</tt>''' to return to your run frequency.<br />
<br />
An '''<tt>[Alt]</tt>'''-double click on a callsign will load the spot frequency into the Sub VFO (VFO B), if your radio supports it.<br />
<br />
While in split mode during 40m and 80m SSB operation, when adding a spot to the band map, Win-Test remembers both the RX and the TX VFO frequencies, and will store this information so that when you select the spot, both VFOs will be set correctly, and you'll be ready to call (unless the QSX frequency has changed in the mean time).<br />
<br />
Moving the mouse pointer over a spot in the band map will bring up additional information, such as the age of the spot the callsign of the spotter, and any comments. Double-clicking the spot with the '''<tt>[Ctrl]</tt>''' key removes the spot from the band map (without confirmation).<br />
<br />
[[Keys#Band_Map|Other key combinations]] can be used to operate with the Band Map.<br />
<br />
===Band Maps Context menu===<br />
<br />
A right click on this window brings up its context menu. <br />
<br />
* The top option in this Context Menu allows you to program the Sub VFO (if your radio supports it) with this spot. <br />
* The '''Propagation''' submenu item allows you to gather propagation information via [[HamCAP]] (if installed)<br />
* The next two entries '''Modify...''' and '''Delete''' allow you to change or remove spots in the band map. Note that you can quickly remove a spot by double-clicking it with the '''<tt>[Ctrl]</tt>''' key pressed.<br />
* Additionally, you can change the scale of the band map display from 1:1 up to 30:1. The scale can also be set through the mouse wheel.<br />
* More options are hidden in the sub menus [[#Extended_information|Display Options]] and [[#Band_Map_properties|Properties...]] where one can set a lot of minor details of the band map.<br />
[[Image:WindowsBandMapContextMenu.PNG|center|frame|Band Map Context Menu]] <br><br />
*<code>29S 11N</code> at the bottom indicates there are 29 spots total, 11 new calls (not yet worked).<br />
* The List tab of the band map has a context menu with several sorting options:<br />
[[Image:WindowsBandMapListViewContextMenuSort.png|center|frame|Band Map List View Context Menu - sorting options]] <br><br />
* The List tab of the band map has a display option that lets you hide dupes and display additional information:<br />
[[Image:WindowsBandMapListViewContextMenuDisplay.png|center|frame|Band Map List View Context Menu - hiding dupes]] <br><br />
<br />
====Special cursors====<br />
Special indicators for the last CQ frequency or the QSY frequency (set with the PASSFREQ text command, or with the <code>Commands | QSY frequency</code> menu option) can also be activated (see picture). <br />
<br />
[[Image:WindowsBandMapCqCursor.png|center|frame|Band Map with CQ cursor]] <br><br />
<br />
To enable them, tag the CQ cursor and/or the QSY cursor items in the Display Options submenu of the context menu itself.<br />
<br />
====Extended information====<br />
The Display Options menu also allows you to select if the expected exchange will be displayed in the band map and other minor details, like day/sunrise/sunset/night symbols, time and sender, comments etc.<br />
<br />
====Markers====<br />
The Display Options menu allows you to enable the displaying of markers. These can be useful for beacons and other known stations on the bands.<br />
<br />
[[Image:WindowsBandmapMarker.png|center|frame|Band Map with a marker file for 10 m beacons loaded ]]<br />
<br />
Markers are defined by text files with a '''.mkr''' extension located in the Win-Test directory. WT can use and display up to 10 files simultaneously; they can be selected in the <tt>Options | Data files | Markers files</tt> menu. <br />
For detailed information, please see [[Menu:Options#Markers_files... | Menu: Options Data files Markers files]].<br />
<br />
Marker display settings can be different for each radio. The syntax of the marker files is very basic and they are easy to create with a simple text editor like Notepad.<br />
<br />
A marker is defined by its frequency (in kHz), a label (one word) and an optional tooltip (30 chars max.) that will flash when the mouse cursor is positioned on the marker for a few seconds. If you include a four or six character gridsquare locator, WT will display heading and distance to this gridsquare in the tooltip window.<br />
<br />
Example:<br />
<br />
28205 DL0IGI Hohenpeissenberg JN57MT<br />
28257 DK0TEN Sipplinger Berg JN47NT<br />
28277.5 DF0AAB Kiel JO54GH<br />
<br />
Two DIRECTIVES (or KEYWORDS) define the background and foreground color:<br />
<br />
* # BACKGROUND color => Sets the background color of the following markers in the file. If no color is specified, the default color is green.<br />
* # TEXT color => Sets the text color of the following markers in the file. If no color is specified, the default color is black.<br />
<br />
The known colors are: White, Black, Red, Green, Blue, Yellow, Magenta, Cyan. The case of the color is irrelevant, so "green" and "Green" are identical.<br />
<br />
Example :<br />
<br />
# BACKGROUND white<br />
# TEXT green<br />
#<br />
14100 Bcn NCDXF Beacon<br />
<br />
This will display a white marker with a green text "Bcn". The associated tooltip will be "NCDXF Beacon". As usual, you can double-click on a marker to set the current radio on the frequency of the marker. A sample file '''NcdxfBeacons.mkr''' is located in the WT repository at: http://download.win-test.com/files/markers/. It displays markers for each NCDXF beacon. <br />
<br />
You may build your own marker files (VHF beacons etc.) and share it with the WT community if you want.<br />
<br />
====Segments====<br />
WT can display band allocations for different license types in the bandmap tab of the radio windows. This allows you to select a run frequency which is in right band segment for US-Advanced or US-Novice amateurs for example.<br />
<br />
Band segments are defined by text files with a '''.seg''' extension located in the Win-Test directory. WT can use and display up to 10 files simultaneously; they can be selected in the <tt>Options | Data files | Segments files</tt> menu.<br />
Please find more detailed information in [[Menu:Options#Segments_files... | Menu: Options Data files Segments files]].<br />
<br />
Due to space constraints - you can't have more than 5 segments displayed per band for any given frequency.<br />
<br />
The segments display settings can be different for each radio.<br />
<br />
<center><br />
{|<br />
|[[Image:BandMapMarkerSegment.png|center|frame|Band Map with marker and segments]]<br />
|[[Image:WindowsBandmapSegments.png|center|frame|Band Map with US band allocation]]<br />
|}<br />
</center><br />
<br />
<br />
The syntax of the segments files is very basic, and the files are easily created with a simple text editor like Notepad. A segment is defined by specifying its lowest and its highest frequency (in kHz). The two frequencies may be linked by an hyphen for easier reading. An optional tooltip text (30 chars max.) can be given to explain the meaning of the color segment. By placing the mouse cursor over a colored line in the band map display, the tooltip will display.<br />
<br />
The BandMap segment color is indicated by the DIRECTIVE (keyword) COLOR like given below. The known colors are: White, Black, Red, Green, Blue, Yellow, Magenta, Cyan. The case of the color name is irrelevant. If no color is specified, the segments will be displayed in yellow.<br />
<br />
Example:<br />
<br />
# COLOR Red<br />
14000-14150 Extra CW<br />
14150-14350 Extra SSB<br />
# COLOR Yellow<br />
14025-14150 Advanced CW<br />
14175-14350 Advanced SSB<br />
# COLOR Magenta<br />
14025-14150 General CW<br />
14225-14350 General SSB<br />
<br />
This will display the US band allocation in the 20-m-band.<br />
<br />
The segments order, and potential overlaps in the file are irrelevant. WT will take care to display them in an optimized way.<br />
<br />
Two sample files are located in the WT repository at http://download.win-test.com/files/segments/<br />
<br />
* '''UsSegmentsDetailled.seg''' displays all band segments for every US licence type.<br />
* '''UsSegments.seg''' displays all band segments in which all US licencees are potentially active.<br />
<br />
You may create your own band segments files for other countries, regions, etc. and share them with the WT community if you want.<br />
<br />
====Band Map properties====<br />
Selecting '''Properties...''' in the context menu of the Radio 1 or Radio 2 band map windows displays the Bandmaps Properties window:<br />
<br />
[[Image:BandMapProperties.png|center|frame|Bandmap properties window]]<br />
<br />
Here you can define the lifetime of two kinds of spots, control the behavior of the logging window when you press '''<tt>[Ctrl-Enter]</tt>''' to create an operator-entered spot, control the automatic entry of data in the logging window when you grab a spot in the bandmap (via double click), select random 100 Hz TX frequency offsets to improve the chances of calling a spot on a clearer frequency (recommended), and the spot bandwidth for each mode (CW, SSB, RTTY) which is used to determine when two spots are on the same frequency. The spot bandwidth can be set between 0 Hz and 5000 Hz, in 100 Hz steps. The lifetime of spots in the band map can be changed from the default (60 minutes) to any other value below 100 minutes.<br />
<br />
Search & Pounce Options allow you to add spots to the band map without having to press '''<tt>[Ctrl-Enter]</tt>'''. Simply enter the callsign and turn the VFO by the specified frequency change threshold to automatically populate the band map.<br />
<br />
{{wbox|Note|To automatically populate the Band Map, you must be in S&P mode. Search & Pounce is not activated by default. Select [[Menu:Tools#Enable_Run.2FS.26P_switching|Tools | Data entry | Enable Run/S&P switching]] (text command shortcut: '''<tt>RUNSP [Enter]</tt>'''), and then press '''<tt>[Ctrl-tab]</tt>''' once to toggle from Run to S&P mode. The [[Menu:Windows#Clock|clock window]] indicates the current mode.}}<br />
<br />
==Secondary Radio==<br />
<code>Windows | Secondary Radio</code><br />
<br><br />
Opens (or closes) the Secondary Radio window.<br />
<br />
[[Image:secondary_window.PNG|center|frame|Secondary Radio Window]]<br />
<br />
This window controls the "other" radio that is currently not in use during SO2R operation, not necessarily radio 2.<br />
For more information, please see [[SO2R/Second_radio_window]].<br />
<br />
==RTTY (radio1, radio2)==<br />
<code>Windows | RTTY (radio 1)<br><br />
Windows | RTTY (radio 2)<br />
</code><br />
<br><br />
Opens (or closes) the RTTY Transit/Receive windows.<br />
<br />
[[Image:RttyWindow.PNG|frame|center|RTTY TX/RX Window]]<br />
<br />
For more information, see [[RTTY#Receive.2Ftransmit_window|RTTY Receive/Transmit window]] in the [[RTTY]] chapter.<br />
<br />
==Rotators==<br />
<code>Windows | Rotators</code><br />
<br><br />
Opens (or closes) the Rotators window, which displays the true beam heading (after adding any programmed offsets) of all the antennas available on the current operating band or bands (two bands if using two radios).<br />
<br />
[[Image:WindowsRotatorsConnected.PNG|frame|center|Rotators window with true heading of four antennas on current operating bands]]<br />
<br />
The three tabs at the bottom may be used to select what is displayed:<br />
<br />
* '''Antennas''' - Display the true beam heading (by antenna name) of all named antennas defined for the current operating band or bands. Any defined antenna offsets are used to calculate the displayed heading. Arrow buttons can be used to rotate one antenna at a time.<br />
* '''Stacks''' - Display the true beam heading of any wtRotator "Stacks" (or "Groups") on the current band. The buttons may be used to rotate the entire stack at once to the same heading, even if each antenna has a separate rotator. The heading of the first rotator added to a stack or group determines which heading is shown for the stack (even if another antenna in the stack is currently pointing in a different direction).<br />
* '''Rotators''' - Display ''all'' connected rotators (by rotator name), regardless of band, and the heading of each, as displayed on the control box. Any antenna offsets are ignored.<br />
<br />
Click on the arrow buttons to rotate the current antenna, stack, or rotator as follows:<br />
* <code>[<<]</code> - Rotate 45° counter-clockwise<br />
* <code>[<]</code> - Rotate 15° counter-clockwise<br />
* <code>[>]</code> - Rotate 15° clockwise<br />
* <code>[>>]</code> - Rotate 45° clockwise <br />
You may also enter a callsign, DXCC prefix, or beam heading in the Win-Test logging Window, and press '''<code>[Ctrl]-F12</code>''' to rotate all antennas defined on the current band to desired heading (assuming your Grid Square or "Locator" is properly defined in the Contest Configuration screen).<br />
<br />
''Right click'' on the dark blue area of the Rotators window to display the pop-up menu.<br />
<br />
[[Image:WindowsRotators.PNG|frame|center|Rotators window with pop-up menus]]<br />
<br />
Use the pop-menu to sort the list, change font size, or start or stop the companion program, '''wtRotators''', on the local PC. wtRotators is a program that communicates with one more more rotators, similar to the way that wtDxTelnet communicates with one or more packet clusters. In can be located on the current computer or a separate computer on the LAN, whichever computer is physically connected to a rotator's serial port. <br />
<br />
Select the '''Start/stop automatically''' option to have Win-Test automatically start and stop the wtRotators program on the local computer whenever you open or close Win-Test.<br />
<br />
See the [[Rotators]] main topic for more information about configuring and using wtRotators with Win-Test.<br />
<br />
==DX-Cluster Monitor==<br />
<code>Windows | DX-Cluster monitor</code> or '''<tt>Alt-O</tt>'''<br />
<br><br />
Opens (or closes) the DX Cluster monitoring window.<br />
<br />
[[Image:WindowsPacket.gif|center|frame|DX Cluster monitoring window]]<br />
<br />
The contents of this window are logged to to the '''.pkt''' file. Logging can optionally be disabled to save disk space or to prevent malware scanners from slowing down the system -- in particular, when a lot of spots is being received (e.g. via RBN). To disable logging, right-click in the window and uncheck "Stream logging".<br />
<br />
The window is scrollable so that you can step back through history, back - even to the beginning of the file. The scrolled window will not update when new spots arrive. However, there is a little hint in the title bar like '''[+1138 lines]'''. In order to see all spots which have arrived in the mean time you have to move the scrollbar back to the end of the window.<br />
<br />
For more information regarding the setup of DX Cluster connections, please see<br />
[http://docs.win-test.com/wiki/Menu:Commands#DX-Cluster Commands | DX Cluster]<br />
<br />
==DX-Cluster Announcements==<br />
<code>Windows | DX-Cluster Announcements</code> or '''<tt>Alt-A</tt>'''<br />
<br><br />
Opens (or closes) the DX cluster announcements window.<br />
<br />
[[Image:WindowsDxClusterAnn.gif|center|frame|DX Cluster Announcements Window]]<br />
<br />
This window gathers all the spots coming from the DX cluster. New multipliers are green, other stations (but not dupes) are black.<br />
<br />
With a right click, you can choose to display only new multipliers, only spots entered by the operator and/or selected bands:<br />
<br />
[[Image:DXClusterAnnouncementsBands.PNG|center|frame|Band selection pop-up menu for the DX Cluster Announcements window]]<br />
<br />
All spots are logged to the corresponding '''.dxc''' file in the log directory. Logging can be disabled to save disk space or prevent malware scanners from slowing down the system - in particular, when a lot of spots is being received (e.g. via RBN). Manually entered spots are still being logged to the '''.dxc''' file.<br />
<br />
The displayed information is selectable (local time as a sun symbol, time spotted, spot comments, beam heading, and the callsign of the spot sender):<br />
<br />
[[Image:DXClusterAnnouncementsDisplayOptions.PNG|center|frame|Display options for the DX Cluster Announcements window]]<br />
<br />
A double click on a selected line will automatically switch the active radio to the spot frequency, and will grab the call and enter it in the callsign logging field. You just need to complete the QSO and press ['''<tt>Return</tt>'''].<br />
<br />
QSX information (like QSX 7239) is parsed from the comment field of the spot and handled correctly, so that when you click on such a spot, the transceiver will switch to split mode, put VFO A on the RX frequency and VFO B on the TX frequency. QSX is indicated by an asterisk (*) character on the spotted callsign. Cross-band QSX frequencies are being ignored.<br />
<br />
Additional shortcuts:<br />
* '''<tt>[Ctrl] + Dbl click</tt>''' on a spot removes the spot from the Announcements window (without confirmation).<br />
* '''<tt>[Alt] + Dbl click</tt>''' on a spot loads the spot frequency in the sub VFO of the active radio (if your radio supports it) <br />
<br />
For more information regarding the setup of DX Cluster connections, please see<br />
[http://docs.win-test.com/wiki/Menu:Commands#DX-Cluster Commands | DX Cluster]<br />
<br />
==Clock==<br />
<code>Windows | Clock</code><br />
<br><br />
Opens (or closes) the clock window.<br />
<br />
[[Image:clocks.png|center|frame|Clock window samples]]<br />
<br />
To set time in Win-Test, you don't need to change the computer time. You just need to adjust the computer clock in the local time, within the right time zone. Win-Test will compute the UTC time from this information. <br />
<br />
The color of the time display changes in minutes 59 and 00, to prepare an operator changeover in a multi-op environment.<br />
<br />
This window also displays sunrise and sunset times (SR and SS) according to your location. To catch your eye, the color of these times will change when you are within 30 minutes of sunrise or sunset times.<br />
<br />
This window also displays your Locator (which is needed if you want that WT exactly compute SR/SS times as well as Bearings and distance to the correspondent) and the Win-Test operating mode, RUN or S/P, according to your operating needs. For details on this feature see also [[Menu:Tools#Data_entry | Menu:Tools Data_entry]].<br />
<br />
Just as a side note, WinXP allows you to synchronize your computer's clock time through the Internet. Please see more details on Microsoft's support pages ([http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/windows_date_it_overview.mspx overview] and <br />
[http://technet2.microsoft.com/windowsserver/en/library/b43a025f-cce2-4c82-b3ea-3b95d482db3a1033.mspx details]).<br />
<br />
The font type and size, as well as the background and all the usual window colors can be changed through the context menu using a right mouse click on that window.<br />
<br />
==Contest Recorder==<br />
<code>Windows | Contest Recorder</code><br />
<br><br />
Opens (or closes) the Contest Recorder window.<br />
<br />
Before recording, right click and select [[Menu:Options#MP3_Configuration|MP3 Configuration]] to set the recording parameters.<br />
<br />
A right-click on the Recorder window gives help to the keyboard shortcuts. <br />
Use <code>right-click | Files Information</code> to see information about recorded files, or to delete recorded files.<br />
<br />
[[Image:ContestRecorder.PNG|center|frame|Contest Recorder window]]<br />
<br />
==SSB bargraph==<br />
<code>Windows | SSB bargraph</code><br />
<br><br />
Opens (or closes) the SSB bargraph window<br />
<br />
[[Image:WindowsVuMeter.gif|center|frame|SSB bargraph window]]<br />
<br />
This bargraph displays the audio level of the Win-Test's digital voice player (if used, of course). The appropriate level is the yellow part of this bargraph.<br />
<br />
==Close all Windows==<br />
<code>Windows | Close all windows</code><br />
<br><br />
Closes all windows except the log entry area in the left lower area.<br />
<br />
[[Menus|Back to Menus]]</div>N6TVhttps://docs.win-test.com/w/index.php?title=File:WindowsRotatorsConnected.PNG&diff=4563File:WindowsRotatorsConnected.PNG2016-02-19T06:32:35Z<p>N6TV: The Rotators window with 4 rotators visible on the two current operating bands</p>
<hr />
<div>The Rotators window with 4 rotators visible on the two current operating bands</div>N6TVhttps://docs.win-test.com/w/index.php?title=Rotators&diff=4562Rotators2016-02-19T06:25:10Z<p>N6TV: /* Configuring wtRotators (single PC, no network) */ Explain how to enter rotator offsets with a better example. Describe controller window.</p>
<hr />
<div>Automated rotators may be controlled by an external application provided as part of the Win-Test package called '''wtRotators'''. This program (wtRotators) communicates directly with the rotator hardware via serial ports, '''not''' Win-Test. Win-Test just sends broadcast messages to wtRotators.<br />
==Configuring wtRotators (single-op environment)==<br />
The reasoning behind using a separate program for controlling rotators was to be able to have only one PC per rotator controller in a multi-op environment, rather than having to switch rotator control between different PCs. But, in a single PC environment, no network is required.<br />
<br />
Configuration of wtRotators is straightforward, very similar to configuring wtDxTelnet. It only needs to be done once. This section explains how to setup wtRotators and Win-Test for use in a single-op environment, with both wtRotators and Win-Test running on the same computer. There are further instructions below describing what has to be done in a multi-op environment. <br />
<br />
===Configuring Win-Test for wtRotators===<br />
First, open the [[Menu:Options#Configure_interfaces...|Configure Interfaces window]] in Win-Test via <code>Options | Configure interfaces...</code>, or just type the text command '''<tt>SETUP</tt>''' and press '''<tt>[Enter]</tt>'''. Check the box labeled '''Enable ethernet network''' and ensure that it looks like the following:<br />
<br />
[[Image:network_singleop.png|center]]<br />
<br />
When running both programs on a single PC, use the "loopback" broadcast IP address, '''127.255.255.255'''. No Ethernet connection is required when specifying this special address; it is internal to the machine and always present.<br />
<br />
Press '''<tt>[OK]</tt>'''. This is the only change of configuration you'll have to make in Win-Test itself. You can also open the rotators window via [[Menu:Windows#Rotators| Windows | Rotators]].<br />
<br />
===Configuring wtRotators (single PC, no network)=== <br />
Start wtRotators (in Windows, <code>Start | Programs | Win-Test | wtRotators</code>, or use the pop-up menu in the [[Menu:Windows#Rotators|Win-Test Rotators Window]]. From the wtRotators menu, select '''<code>Options | Win-Test Network Properties</code>'''.<br />
<br />
[[Image:WtRotatorsOptions.png|center]]<br />
<br />
Edit all the values so that they look exactly like this:<br />
<br />
[[Image:WtRotatorsNetworkPropertiesSingleOp.PNG|center]]<br />
<br />
These options may well be greyed out by default, in which case be sure to ''uncheck'' the box labeled '''Disable communication with Win-Test''', and then you will be able to edit everything. Use the same loopback broadcast address and port number that you specified in Win-Test, as shown above.<br />
<br />
Press '''<tt>[OK]</tt>'''. You may then see a security alert from Windows about wtRotators:<br />
<br />
[[Image:WtRotatorsWindowsSecurityAlert.png|center]]<br />
<br />
This is normal. '''Press [Unblock]''' and you should never see it again.<br />
<br />
Note that wtRotators must always be running in the background if you want automated control of your rotators via Win-Test. Like wtDxTelnet, wtRotators can be started and stopped automatically. See [[Menu:Windows#Rotators| Windows | Rotators]].<br />
<br />
====Add your rotators====<br />
From the wtRotators menu, choose '''<tt>Controllers | Add</tt>'''.<br />
<br />
[[Image:WtRotatorsControllersAdd.png|center]]<br />
<br />
Select a rotator type from the list. If you are using a [http://www.greenheronengineering.com/proddetail.php?prod=RT-21 Green Heron RT-21] control box, select '''Hy-Gain DCU-1'''.<br />
<br />
Next, enter all the values applicable to the antennas turned by that rotator, for example:<br />
<br />
[[Image:WtRotatorsAddRotator.png|center]]<br />
<br />
A quick description of the various settings here. Most of the fields in this window have a "tool tip"; just hover the mouse pointer over the field to display quick pop-up help text about the field.<br />
* '''Com Port''' - Select '''<tt>COM1</tt>''', '''<tt>COM2</tt>''', etc., whatever serial port is connected to the specified rotator. Baud rate and other settings are determined automatically by the previously-selected rotator type. To disable rotator control, select '''None'''.<br />
* '''Rotator Name''' - The rotator name you choose will appear in the wtRotators messages window, and at the top of the small controller window.<br />
* '''Affected Group''' - Select a group name or select '''None'''. The default group names are '''Group #1''' to '''Group #18''', but you can edit these group names via '''<tt>Controllers | Configure Groups</tt>'''. You can put several antennas into a group to turn them all at once. This is useful for stacked antennas which are on separate rotors. In WT, you can then turn the "stack" (all rotors will be turned to the target azimuth), or you can turn them independently (for example, both antennas beamed to two different directions).<br />
* '''Show controller''' - When this box is checked, wtRotators will launch a small "controller window" (on the PC with the rotator) that displays the same beam heading as displayed by the rotator control box. Arrow buttons at the bottom may be used to manually turn the rotator counter-clockwise <code>[<]</code> or clockwise <code>[>]</code>. It also has a pop-up menu for quickly selecting beam headings from 0 to 330° in 30° increments or any specific heading (''right click'' to view the pop-up).<br />
[[Image:WtRotatorsControllerWindow.png|center]]<br />
* '''Rotation limits''' - Click to display pop-up window where you can enter the range of values supported by this rotator. Any heading outside the range will be translated to the nearest limit. [Q: How does one specify that 170 to 190° are "out of range"? --Ed.]<br />
[[Image:WtRotatorsRotationLimits.png|center]]<br />
* '''Antenna Name''' - Choose any name for your antennas. Each antenna must have a unique name.<br />
* '''Band''' - Operating band. Win-Test turns the proper rotator based on the operating band of the active radio. For multiband antennas, create several entries as shown above. Omitted bands will be ignored by this instance of wtRotators.<br />
* '''Offset''' - Offset to add if the antenna is skewed from the rotator indication. Click to enter a value between 0 and 360°. For example, if you have a rotary dipole in line with the booms of your Yagis, use 90° as shown in the example. If your antenna is actually pointing at 20° when the rotator indicates 0°, enter 20. Be sure to check '''Enable Offset''' as shown. For "negative" offsets, like "-25°", use the equivalent value, 335°.<br />
[[Image:WtRotatorsOffset.PNG|center]]<br />
* '''Heading Range''' - Click to specify a range of beam heading values supported by this antenna. If the antenna is to be used for all directions, leave this column blank by unchecking '''Enable a Beaming Range for that Antenna'''. [Q: How to specify a range that excludes 170 to 190°? --Ed.]<br />
[[Image:WtRotatorsHeadingRange.png|center]]<br />
* '''Bidirect''' - Check this box when using a bi-directional antenna, such as a dipole. Win-Test will automatically move the rotator to the nearest usable beam heading.<br />
<br />
Press '''<tt>[OK]</tt>''' to save all changes, or '''<tt>[Cancel]</tt>''' to start over.<br />
<br />
===Testing the configuration===<br />
Once you have setup both Win-Test and wtRotators, it is time to verify that you can control the rotator from within Win-Test.<br />
<br />
In Win-Test, enter either a '''callsign''' or a '''beam heading''' (0 to 360°) on the last line of the [[Menu:Windows#Log_Entry_.28Main_window.29|log entry window]], and press '''<tt>[Ctrl]+[F12]</tt>''' to rotate to that heading. When entering a callsign or prefix, use '''<tt>[Alt]+[F12]</tt>''' for long (or "alternate") path. You can also move the cursor up to a previous QSO and press either key to rotate to the heading for that callsign. Callsign prefixes within your own country cannot be used to rotate the beam.<br />
<br />
You should immediately see a message in the wtRotators window such as the following:<br />
[[Image:WtRotatorsStatusMessages.png|center]]<br />
and the rotator should turn to the indicated heading.<br />
<br />
'''If you see no messages in the wtRotators window''', it means no antenna was named and defined for that band, or it means Win-Test and wtRotators are not communicating properly. Verify that both are using the same broadcast IP address and port number, and that "Disable communications with Win-Test" is ''not'' checked, and that your firewall is not blocking the port.<br />
<br />
===Editing the rotator configuration===<br />
From the wtRotators menu, choose '''<tt>Controllers | Edit</tt>''' or '''<tt>Controllers | Delete</tt>'''.<br />
<br />
===Adding additional rotators===<br />
From the wtRotators menu, choose '''<tt>Controllers | Add</tt>''' and repeat the procedure described above for each rotator that you want to support.<br />
<br />
===Initializing rotator communications===<br />
wtRotators automatically re-initializes communications with the rotator when any change is made. If the rotator is temporarily disconnected or powered off, or if wtRotators is no longer turning the rotator even though all the normal messages are displayed, from the wtRotators menu, select '''<tt>Controllers | Initialize</tt>''' and wtRotators will reopen the specified COM port and attempt to re-establish communications with the rotator controller.<br />
<br />
==Configuring wtRotators (multi-op environment)==<br />
The above guide covers setting up Win-Test and wtRotators in a single-op environment and thankfully the only difference between the two configurations is the networking set-up in wtRotators. <br />
<br />
=== Obtaining your network broadcast address === <br />
In order to configure wtRotators correctly, you need to know the IP broadcast address you have set in Win-Test for the network. Simply open the [[Menu:Options#Configure_interfaces...|Configure Interfaces window]] in Win-Test via <code>Options | Configure interfaces...</code>, or just type the text command '''<tt>SETUP</tt>''' and press '''<tt>[Enter]</tt>'''. Press the '''<tt>[By default]</tt>''' button to have Win-Test automatically calculate the broadcast address based on your PC's current IP address. <br />
<br />
The broadcast address is found as follows:<br />
[[Image:Networking_multiop.png|center]]<br />
So, in this above example, the broadcast address is '''<tt>192.168.0.255</tt>'''. Use this same broadcast address and port number in wtRotators, in wtDxTelnet, and in all networked PCs. Just press the '''<tt>[Default]</tt>''' button in wtRotators, and it will calculate the same broadcast value as Win-Test, no need to write anything down.<br />
<br />
[[Image:WtRotatorsNetworkPropertiesMultiOp.png|center]]<br />
<br />
===Configuring wtRotators (multiple PCs in a network)=== <br />
The advantage of wtRotators in a multi-op environment is that you only require ''one'' connection to a rotator control box, all networked PCs will be able to control that rotator, based on operating band.<br />
<br />
Follow the steps above, for configuring wtRotators in a single-op environment, but the network properties will be different. Go to the '''<tt>Options|Win-Test Network Properties</tt>''' menu in wtRotators.<br />
[[Image:WtRotatorsOptions.png|center]]<br />
Use the following details:<br />
[[Image:WtRotatorsNetworkPropertiesMultiOp.png|center]]<br />
* '''Broadcast IP address''' - It is ''very'' important that you get the address absolutely correct for the rotator data to be propagated across the network. It '''must''' match the broadcast address which you have specified in Win-Test's network properties in the previous step. Using the example above, in this instance, the broadcast IP address would be '''<tt>192.168.0.255</tt>'''. Just press the '''<tt>[Default]</tt>''' button shown above, and wtRotators will calculate the same default broadcast address as Win-Test's '''<tt>[By default]</tt>''' button.<br />
* '''Port number''' - Can usually be left as-is. Again, it must match what has been specified in Win-Test. The same port number can be used for both wtDxtelnet and wtRotators. The default port number is 9871. Use 9871 unless you have already changed the port number (and thus you should know what you're doing and thus you should know the port number).<br />
* '''Application ID''' - Can also be left as '''<tt>ROTATOR</tt>'''. <br />
<br />
Click '''<tt>[OK]</tt>''', and you have successfully configured both Win-Test and wtRotators. You should now [[#Testing_the_configuration|test the configuration]] as described above.<br />
<br />
===Add your rotators===<br />
[[Rotators#Add_your_rotators|Add your rotators]] as described above. Keep in mind that any rotator can be turned by any operator, so take care to limit the bands and beam headings covered by each rotator.<br />
<br />
==See Also== <br />
<br />
===In the manual=== <br />
<br />
* [[Networking|Setting up networking in a multi-op environment]]<br />
* [[Menu:Windows#Rotators| Windows | Rotators]]</div>N6TVhttps://docs.win-test.com/w/index.php?title=File:WtRotatorsControllerWindow.png&diff=4561File:WtRotatorsControllerWindow.png2016-02-19T06:14:59Z<p>N6TV: N6TV uploaded a new version of File:WtRotatorsControllerWindow.png</p>
<hr />
<div>The wtRotators Controller window</div>N6TVhttps://docs.win-test.com/w/index.php?title=Rotators&diff=4560Rotators2016-02-16T00:06:53Z<p>N6TV: /* Testing the configuration */ Explained what happens if you don't see a message.</p>
<hr />
<div>Automated rotators may be controlled by an external application provided as part of the Win-Test package called '''wtRotators'''. This program (wtRotators) communicates directly with the rotator hardware via serial ports, '''not''' Win-Test. Win-Test just sends broadcast messages to wtRotators.<br />
==Configuring wtRotators (single-op environment)==<br />
The reasoning behind using a separate program for controlling rotators was to be able to have only one PC per rotator controller in a multi-op environment, rather than having to switch rotator control between different PCs. But, in a single PC environment, no network is required.<br />
<br />
Configuration of wtRotators is straightforward, very similar to configuring wtDxTelnet. It only needs to be done once. This section explains how to setup wtRotators and Win-Test for use in a single-op environment, with both wtRotators and Win-Test running on the same computer. There are further instructions below describing what has to be done in a multi-op environment. <br />
<br />
===Configuring Win-Test for wtRotators===<br />
First, open the [[Menu:Options#Configure_interfaces...|Configure Interfaces window]] in Win-Test via <code>Options | Configure interfaces...</code>, or just type the text command '''<tt>SETUP</tt>''' and press '''<tt>[Enter]</tt>'''. Check the box labeled '''Enable ethernet network''' and ensure that it looks like the following:<br />
<br />
[[Image:network_singleop.png|center]]<br />
<br />
When running both programs on a single PC, use the "loopback" broadcast IP address, '''127.255.255.255'''. No Ethernet connection is required when specifying this special address; it is internal to the machine and always present.<br />
<br />
Press '''<tt>[OK]</tt>'''. This is the only change of configuration you'll have to make in Win-Test itself. You can also open the rotators window via [[Menu:Windows#Rotators| Windows | Rotators]].<br />
<br />
===Configuring wtRotators (single PC, no network)=== <br />
Start wtRotators (in Windows, <code>Start | Programs | Win-Test | wtRotators</code>, or use the pop-up menu in the [[Menu:Windows#Rotators|Win-Test Rotators Window]]. From the wtRotators menu, select '''<code>Options | Win-Test Network Properties</code>'''.<br />
<br />
[[Image:WtRotatorsOptions.png|center]]<br />
<br />
Edit all the values so that they look exactly like this:<br />
<br />
[[Image:WtRotatorsNetworkPropertiesSingleOp.PNG|center]]<br />
<br />
These options may well be greyed out by default, in which case be sure to ''uncheck'' the box labeled '''Disable communication with Win-Test''', and then you will be able to edit everything. Use the same loopback broadcast address and port number that you specified in Win-Test, as shown above.<br />
<br />
Press '''<tt>[OK]</tt>'''. You may then see a security alert from Windows about wtRotators:<br />
<br />
[[Image:WtRotatorsWindowsSecurityAlert.png|center]]<br />
<br />
This is normal. '''Press [Unblock]''' and you should never see it again.<br />
<br />
Note that wtRotators must always be running in the background if you want automated control of your rotators via Win-Test. Like wtDxTelnet, wtRotators can be started and stopped automatically. See [[Menu:Windows#Rotators| Windows | Rotators]].<br />
<br />
====Add your rotators====<br />
From the wtRotators menu, choose '''<tt>Controllers | Add</tt>'''.<br />
<br />
[[Image:WtRotatorsControllersAdd.png|center]]<br />
<br />
Select a rotator type from the list. If you are using a [http://www.greenheronengineering.com/proddetail.php?prod=RT-21 Green Heron RT-21] control box, select '''Hy-Gain DCU-1'''.<br />
<br />
Next, enter all the values applicable to the antennas turned by that rotator, for example:<br />
<br />
[[Image:WtRotatorsAddRotator.png|center]]<br />
<br />
A quick description of the various settings here. Most of the fields in this window have a "tool tip"; just hover the mouse pointer over the field to display quick pop-up help text about the field.<br />
* '''Com Port''' - Select '''<tt>COM1</tt>''', '''<tt>COM2</tt>''', etc., whatever serial port is connected to the specified rotator. Baud rate and other settings are determined automatically by the previously-selected rotator type. To disable rotator control, select '''None'''.<br />
* '''Rotator Name''' - The rotator name you choose will appear in the wtRotators messages window, and at the top of the small controller window.<br />
* '''Affected Group''' - Select a group name or select '''None'''. The default group names are '''Group #1''' to '''Group #18''', but you can edit these group names via '''<tt>Controllers | Configure Groups</tt>'''. You can put several antennas into a group to turn them all at once. This is useful for stacked antennas which are on separate rotors. In WT, you can then turn the "stack" (all rotors will be turned to the target azimuth), or you can turn them independently (for example, both antennas beamed to two different directions).<br />
* '''Show controller''' - When this box is checked, wtRotators will launch a small "controller window" with buttons that may be used to manually turn the rotator. It also has a pop-up menu for quickly selecting beam headings from 0 to 330° in 30° increments or any specific heading (''right click'' to view the pop-up).<br />
[[Image:WtRotatorsControllerWindow.png|center]]<br />
* '''Rotation limits''' - Click to display pop-up window where you can enter the range of values supported by this rotator. Any heading outside the range will be translated to the nearest limit. [Q: How does one specify that 170 to 190° are "out of range"? --Ed.]<br />
[[Image:WtRotatorsRotationLimits.png|center]]<br />
* '''Antenna Name''' - Choose any name for your antennas. Each antenna must have a unique name.<br />
* '''Band''' - Operating band. Win-Test turns the proper rotator based on the operating band of the active radio. For multiband antennas, create several entries as shown above. Omitted bands will be ignored by this instance of wtRotators.<br />
* '''Offset''' - Offset to apply to the read angle if the antenna is skewed from the rotator indication. Click to enter a value between 0 and 360°. For example, if you have a rotary dipole in line with the booms of your Yagis, use 90° as shown in the example. Be sure to check '''Enable Offset''' as shown. For "negative" offsets, like "-25°", use the equivalent value, 335°.<br />
[[Image:WtRotatorsOffset.PNG|center]]<br />
* '''Heading Range''' - Click to specify a range of beam heading values supported by this antenna. If the antenna is to be used for all directions, leave this column blank by unchecking '''Enable a Beaming Range for that Antenna'''. [Q: How to specify a range that excludes 170 to 190°? --Ed.]<br />
[[Image:WtRotatorsHeadingRange.png|center]]<br />
* '''Bidirect''' - Check this box when using a bi-directional antenna, such as a dipole. Win-Test will automatically move the rotator to the nearest usable beam heading.<br />
<br />
Press '''<tt>[OK]</tt>''' to save all changes, or '''<tt>[Cancel]</tt>''' to start over.<br />
<br />
===Testing the configuration===<br />
Once you have setup both Win-Test and wtRotators, it is time to verify that you can control the rotator from within Win-Test.<br />
<br />
In Win-Test, enter either a '''callsign''' or a '''beam heading''' (0 to 360°) on the last line of the [[Menu:Windows#Log_Entry_.28Main_window.29|log entry window]], and press '''<tt>[Ctrl]+[F12]</tt>''' to rotate to that heading. When entering a callsign or prefix, use '''<tt>[Alt]+[F12]</tt>''' for long (or "alternate") path. You can also move the cursor up to a previous QSO and press either key to rotate to the heading for that callsign. Callsign prefixes within your own country cannot be used to rotate the beam.<br />
<br />
You should immediately see a message in the wtRotators window such as the following:<br />
[[Image:WtRotatorsStatusMessages.png|center]]<br />
and the rotator should turn to the indicated heading.<br />
<br />
'''If you see no messages in the wtRotators window''', it means no antenna was named and defined for that band, or it means Win-Test and wtRotators are not communicating properly. Verify that both are using the same broadcast IP address and port number, and that "Disable communications with Win-Test" is ''not'' checked, and that your firewall is not blocking the port.<br />
<br />
===Editing the rotator configuration===<br />
From the wtRotators menu, choose '''<tt>Controllers | Edit</tt>''' or '''<tt>Controllers | Delete</tt>'''.<br />
<br />
===Adding additional rotators===<br />
From the wtRotators menu, choose '''<tt>Controllers | Add</tt>''' and repeat the procedure described above for each rotator that you want to support.<br />
<br />
===Initializing rotator communications===<br />
wtRotators automatically re-initializes communications with the rotator when any change is made. If the rotator is temporarily disconnected or powered off, or if wtRotators is no longer turning the rotator even though all the normal messages are displayed, from the wtRotators menu, select '''<tt>Controllers | Initialize</tt>''' and wtRotators will reopen the specified COM port and attempt to re-establish communications with the rotator controller.<br />
<br />
==Configuring wtRotators (multi-op environment)==<br />
The above guide covers setting up Win-Test and wtRotators in a single-op environment and thankfully the only difference between the two configurations is the networking set-up in wtRotators. <br />
<br />
=== Obtaining your network broadcast address === <br />
In order to configure wtRotators correctly, you need to know the IP broadcast address you have set in Win-Test for the network. Simply open the [[Menu:Options#Configure_interfaces...|Configure Interfaces window]] in Win-Test via <code>Options | Configure interfaces...</code>, or just type the text command '''<tt>SETUP</tt>''' and press '''<tt>[Enter]</tt>'''. Press the '''<tt>[By default]</tt>''' button to have Win-Test automatically calculate the broadcast address based on your PC's current IP address. <br />
<br />
The broadcast address is found as follows:<br />
[[Image:Networking_multiop.png|center]]<br />
So, in this above example, the broadcast address is '''<tt>192.168.0.255</tt>'''. Use this same broadcast address and port number in wtRotators, in wtDxTelnet, and in all networked PCs. Just press the '''<tt>[Default]</tt>''' button in wtRotators, and it will calculate the same broadcast value as Win-Test, no need to write anything down.<br />
<br />
[[Image:WtRotatorsNetworkPropertiesMultiOp.png|center]]<br />
<br />
===Configuring wtRotators (multiple PCs in a network)=== <br />
The advantage of wtRotators in a multi-op environment is that you only require ''one'' connection to a rotator control box, all networked PCs will be able to control that rotator, based on operating band.<br />
<br />
Follow the steps above, for configuring wtRotators in a single-op environment, but the network properties will be different. Go to the '''<tt>Options|Win-Test Network Properties</tt>''' menu in wtRotators.<br />
[[Image:WtRotatorsOptions.png|center]]<br />
Use the following details:<br />
[[Image:WtRotatorsNetworkPropertiesMultiOp.png|center]]<br />
* '''Broadcast IP address''' - It is ''very'' important that you get the address absolutely correct for the rotator data to be propagated across the network. It '''must''' match the broadcast address which you have specified in Win-Test's network properties in the previous step. Using the example above, in this instance, the broadcast IP address would be '''<tt>192.168.0.255</tt>'''. Just press the '''<tt>[Default]</tt>''' button shown above, and wtRotators will calculate the same default broadcast address as Win-Test's '''<tt>[By default]</tt>''' button.<br />
* '''Port number''' - Can usually be left as-is. Again, it must match what has been specified in Win-Test. The same port number can be used for both wtDxtelnet and wtRotators. The default port number is 9871. Use 9871 unless you have already changed the port number (and thus you should know what you're doing and thus you should know the port number).<br />
* '''Application ID''' - Can also be left as '''<tt>ROTATOR</tt>'''. <br />
<br />
Click '''<tt>[OK]</tt>''', and you have successfully configured both Win-Test and wtRotators. You should now [[#Testing_the_configuration|test the configuration]] as described above.<br />
<br />
===Add your rotators===<br />
[[Rotators#Add_your_rotators|Add your rotators]] as described above. Keep in mind that any rotator can be turned by any operator, so take care to limit the bands and beam headings covered by each rotator.<br />
<br />
==See Also== <br />
<br />
===In the manual=== <br />
<br />
* [[Networking|Setting up networking in a multi-op environment]]<br />
* [[Menu:Windows#Rotators| Windows | Rotators]]</div>N6TVhttps://docs.win-test.com/w/index.php?title=Rotators&diff=4559Rotators2016-02-16T00:05:33Z<p>N6TV: /* Configuring wtRotators (single PC, no network) */ Explained what happens with omitted bands.</p>
<hr />
<div>Automated rotators may be controlled by an external application provided as part of the Win-Test package called '''wtRotators'''. This program (wtRotators) communicates directly with the rotator hardware via serial ports, '''not''' Win-Test. Win-Test just sends broadcast messages to wtRotators.<br />
==Configuring wtRotators (single-op environment)==<br />
The reasoning behind using a separate program for controlling rotators was to be able to have only one PC per rotator controller in a multi-op environment, rather than having to switch rotator control between different PCs. But, in a single PC environment, no network is required.<br />
<br />
Configuration of wtRotators is straightforward, very similar to configuring wtDxTelnet. It only needs to be done once. This section explains how to setup wtRotators and Win-Test for use in a single-op environment, with both wtRotators and Win-Test running on the same computer. There are further instructions below describing what has to be done in a multi-op environment. <br />
<br />
===Configuring Win-Test for wtRotators===<br />
First, open the [[Menu:Options#Configure_interfaces...|Configure Interfaces window]] in Win-Test via <code>Options | Configure interfaces...</code>, or just type the text command '''<tt>SETUP</tt>''' and press '''<tt>[Enter]</tt>'''. Check the box labeled '''Enable ethernet network''' and ensure that it looks like the following:<br />
<br />
[[Image:network_singleop.png|center]]<br />
<br />
When running both programs on a single PC, use the "loopback" broadcast IP address, '''127.255.255.255'''. No Ethernet connection is required when specifying this special address; it is internal to the machine and always present.<br />
<br />
Press '''<tt>[OK]</tt>'''. This is the only change of configuration you'll have to make in Win-Test itself. You can also open the rotators window via [[Menu:Windows#Rotators| Windows | Rotators]].<br />
<br />
===Configuring wtRotators (single PC, no network)=== <br />
Start wtRotators (in Windows, <code>Start | Programs | Win-Test | wtRotators</code>, or use the pop-up menu in the [[Menu:Windows#Rotators|Win-Test Rotators Window]]. From the wtRotators menu, select '''<code>Options | Win-Test Network Properties</code>'''.<br />
<br />
[[Image:WtRotatorsOptions.png|center]]<br />
<br />
Edit all the values so that they look exactly like this:<br />
<br />
[[Image:WtRotatorsNetworkPropertiesSingleOp.PNG|center]]<br />
<br />
These options may well be greyed out by default, in which case be sure to ''uncheck'' the box labeled '''Disable communication with Win-Test''', and then you will be able to edit everything. Use the same loopback broadcast address and port number that you specified in Win-Test, as shown above.<br />
<br />
Press '''<tt>[OK]</tt>'''. You may then see a security alert from Windows about wtRotators:<br />
<br />
[[Image:WtRotatorsWindowsSecurityAlert.png|center]]<br />
<br />
This is normal. '''Press [Unblock]''' and you should never see it again.<br />
<br />
Note that wtRotators must always be running in the background if you want automated control of your rotators via Win-Test. Like wtDxTelnet, wtRotators can be started and stopped automatically. See [[Menu:Windows#Rotators| Windows | Rotators]].<br />
<br />
====Add your rotators====<br />
From the wtRotators menu, choose '''<tt>Controllers | Add</tt>'''.<br />
<br />
[[Image:WtRotatorsControllersAdd.png|center]]<br />
<br />
Select a rotator type from the list. If you are using a [http://www.greenheronengineering.com/proddetail.php?prod=RT-21 Green Heron RT-21] control box, select '''Hy-Gain DCU-1'''.<br />
<br />
Next, enter all the values applicable to the antennas turned by that rotator, for example:<br />
<br />
[[Image:WtRotatorsAddRotator.png|center]]<br />
<br />
A quick description of the various settings here. Most of the fields in this window have a "tool tip"; just hover the mouse pointer over the field to display quick pop-up help text about the field.<br />
* '''Com Port''' - Select '''<tt>COM1</tt>''', '''<tt>COM2</tt>''', etc., whatever serial port is connected to the specified rotator. Baud rate and other settings are determined automatically by the previously-selected rotator type. To disable rotator control, select '''None'''.<br />
* '''Rotator Name''' - The rotator name you choose will appear in the wtRotators messages window, and at the top of the small controller window.<br />
* '''Affected Group''' - Select a group name or select '''None'''. The default group names are '''Group #1''' to '''Group #18''', but you can edit these group names via '''<tt>Controllers | Configure Groups</tt>'''. You can put several antennas into a group to turn them all at once. This is useful for stacked antennas which are on separate rotors. In WT, you can then turn the "stack" (all rotors will be turned to the target azimuth), or you can turn them independently (for example, both antennas beamed to two different directions).<br />
* '''Show controller''' - When this box is checked, wtRotators will launch a small "controller window" with buttons that may be used to manually turn the rotator. It also has a pop-up menu for quickly selecting beam headings from 0 to 330° in 30° increments or any specific heading (''right click'' to view the pop-up).<br />
[[Image:WtRotatorsControllerWindow.png|center]]<br />
* '''Rotation limits''' - Click to display pop-up window where you can enter the range of values supported by this rotator. Any heading outside the range will be translated to the nearest limit. [Q: How does one specify that 170 to 190° are "out of range"? --Ed.]<br />
[[Image:WtRotatorsRotationLimits.png|center]]<br />
* '''Antenna Name''' - Choose any name for your antennas. Each antenna must have a unique name.<br />
* '''Band''' - Operating band. Win-Test turns the proper rotator based on the operating band of the active radio. For multiband antennas, create several entries as shown above. Omitted bands will be ignored by this instance of wtRotators.<br />
* '''Offset''' - Offset to apply to the read angle if the antenna is skewed from the rotator indication. Click to enter a value between 0 and 360°. For example, if you have a rotary dipole in line with the booms of your Yagis, use 90° as shown in the example. Be sure to check '''Enable Offset''' as shown. For "negative" offsets, like "-25°", use the equivalent value, 335°.<br />
[[Image:WtRotatorsOffset.PNG|center]]<br />
* '''Heading Range''' - Click to specify a range of beam heading values supported by this antenna. If the antenna is to be used for all directions, leave this column blank by unchecking '''Enable a Beaming Range for that Antenna'''. [Q: How to specify a range that excludes 170 to 190°? --Ed.]<br />
[[Image:WtRotatorsHeadingRange.png|center]]<br />
* '''Bidirect''' - Check this box when using a bi-directional antenna, such as a dipole. Win-Test will automatically move the rotator to the nearest usable beam heading.<br />
<br />
Press '''<tt>[OK]</tt>''' to save all changes, or '''<tt>[Cancel]</tt>''' to start over.<br />
<br />
===Testing the configuration===<br />
Once you have setup both Win-Test and wtRotators, it is time to verify that you can control the rotator from within Win-Test.<br />
<br />
In Win-Test, enter either a '''callsign''' or a '''beam heading''' (0 to 360°) on the last line of the [[Menu:Windows#Log_Entry_.28Main_window.29|log entry window]], and press '''<tt>[Ctrl]+[F12]</tt>''' to rotate to that heading. When entering a callsign or prefix, use '''<tt>[Alt]+[F12]</tt>''' for long (or "alternate") path. You can also move the cursor up to a previous QSO and press either key to rotate to the heading for that callsign. Callsign prefixes within your own country cannot be used to rotate the beam.<br />
<br />
You should immediately see a message in the wtRotators window such as the following:<br />
[[Image:WtRotatorsStatusMessages.png|center]]<br />
and the rotator should turn to the indicated heading.<br />
<br />
'''If you see no messages in the wtRotators window''', it means Win-Test and wtRotators are not communicating properly. Verify that both are using the same broadcast IP address and port number, and that "Disable communications with Win-Test" is ''not'' checked, and that your firewall is not blocking the port.<br />
<br />
===Editing the rotator configuration===<br />
From the wtRotators menu, choose '''<tt>Controllers | Edit</tt>''' or '''<tt>Controllers | Delete</tt>'''.<br />
<br />
===Adding additional rotators===<br />
From the wtRotators menu, choose '''<tt>Controllers | Add</tt>''' and repeat the procedure described above for each rotator that you want to support.<br />
<br />
===Initializing rotator communications===<br />
wtRotators automatically re-initializes communications with the rotator when any change is made. If the rotator is temporarily disconnected or powered off, or if wtRotators is no longer turning the rotator even though all the normal messages are displayed, from the wtRotators menu, select '''<tt>Controllers | Initialize</tt>''' and wtRotators will reopen the specified COM port and attempt to re-establish communications with the rotator controller.<br />
<br />
==Configuring wtRotators (multi-op environment)==<br />
The above guide covers setting up Win-Test and wtRotators in a single-op environment and thankfully the only difference between the two configurations is the networking set-up in wtRotators. <br />
<br />
=== Obtaining your network broadcast address === <br />
In order to configure wtRotators correctly, you need to know the IP broadcast address you have set in Win-Test for the network. Simply open the [[Menu:Options#Configure_interfaces...|Configure Interfaces window]] in Win-Test via <code>Options | Configure interfaces...</code>, or just type the text command '''<tt>SETUP</tt>''' and press '''<tt>[Enter]</tt>'''. Press the '''<tt>[By default]</tt>''' button to have Win-Test automatically calculate the broadcast address based on your PC's current IP address. <br />
<br />
The broadcast address is found as follows:<br />
[[Image:Networking_multiop.png|center]]<br />
So, in this above example, the broadcast address is '''<tt>192.168.0.255</tt>'''. Use this same broadcast address and port number in wtRotators, in wtDxTelnet, and in all networked PCs. Just press the '''<tt>[Default]</tt>''' button in wtRotators, and it will calculate the same broadcast value as Win-Test, no need to write anything down.<br />
<br />
[[Image:WtRotatorsNetworkPropertiesMultiOp.png|center]]<br />
<br />
===Configuring wtRotators (multiple PCs in a network)=== <br />
The advantage of wtRotators in a multi-op environment is that you only require ''one'' connection to a rotator control box, all networked PCs will be able to control that rotator, based on operating band.<br />
<br />
Follow the steps above, for configuring wtRotators in a single-op environment, but the network properties will be different. Go to the '''<tt>Options|Win-Test Network Properties</tt>''' menu in wtRotators.<br />
[[Image:WtRotatorsOptions.png|center]]<br />
Use the following details:<br />
[[Image:WtRotatorsNetworkPropertiesMultiOp.png|center]]<br />
* '''Broadcast IP address''' - It is ''very'' important that you get the address absolutely correct for the rotator data to be propagated across the network. It '''must''' match the broadcast address which you have specified in Win-Test's network properties in the previous step. Using the example above, in this instance, the broadcast IP address would be '''<tt>192.168.0.255</tt>'''. Just press the '''<tt>[Default]</tt>''' button shown above, and wtRotators will calculate the same default broadcast address as Win-Test's '''<tt>[By default]</tt>''' button.<br />
* '''Port number''' - Can usually be left as-is. Again, it must match what has been specified in Win-Test. The same port number can be used for both wtDxtelnet and wtRotators. The default port number is 9871. Use 9871 unless you have already changed the port number (and thus you should know what you're doing and thus you should know the port number).<br />
* '''Application ID''' - Can also be left as '''<tt>ROTATOR</tt>'''. <br />
<br />
Click '''<tt>[OK]</tt>''', and you have successfully configured both Win-Test and wtRotators. You should now [[#Testing_the_configuration|test the configuration]] as described above.<br />
<br />
===Add your rotators===<br />
[[Rotators#Add_your_rotators|Add your rotators]] as described above. Keep in mind that any rotator can be turned by any operator, so take care to limit the bands and beam headings covered by each rotator.<br />
<br />
==See Also== <br />
<br />
===In the manual=== <br />
<br />
* [[Networking|Setting up networking in a multi-op environment]]<br />
* [[Menu:Windows#Rotators| Windows | Rotators]]</div>N6TVhttps://docs.win-test.com/w/index.php?title=Message_variables&diff=4558Message variables2015-10-19T16:06:35Z<p>N6TV: /* Action */ Added $GRAB1-$GRAB9, $GRABRT1-$GRABRT3</p>
<hr />
<div><big><big>Messages Variables</big></big><br />
<!-- Adopted to Stylesheet DL6RAI --><br />
<br />
These variables can be used in programming CW messages using the F-keys. Some of these variables do not actually create output but rather perform actions at specific points in time, like the '''<tt>$CR</tt>''' symbol.<br />
<br />
==CW / RTTY automation==<br />
* '''<tt>$CHECK</tt>''': send license year (ARRL SS only)<br />
* '''<tt>$CORRECT</tt>''': sends a call correction, if any (see [[Menu:Options#Correction|correction]])<br />
* '''<tt>$CURRENT</tt>''' (or '''<tt>$CURRENTCALL</tt>'''): Sends the callsign of the current QSO ''despite'' the presence of a $CR later in the message. The $CR (carriage return) is always executed on message keypress. See [[Menu:Windows#Partner|Windows | Partner]] for usage examples. It is also useful in ESM (Enter Sends Message) mode in lieu of $LOGGEDCALL.<br />
* '''<tt>$F1...$F7</tt>''': sends the message associated with F1 ... F7 function key<br />
* '''<tt>$FREQ''nn''</tt>''': Where ''nn'' is a band (e.g. $FREQ160, $FREQ80 etc.). Useful in a multi-op as a canned message "PSE QSY $FREQ15". Sends the frequency of the primary radio of the first networked station found on this band with the following priority : R, R+, M, and M+. In addition, in CW, if the frequency is within 100 Hz of a kHz boundary, the decimal point is omitted, e.g. 14021.09 is sent as 14021 and 14021.10 is sent as 14021R1.<br />
* '''<tt>$FREQP</tt>''': contains the frequency of the primary radio (useful for passing mults)<br />
* '''<tt>$FREQS</tt>''': contains the frequency of the secondary radio (useful for passing mults)<br />
* '''<tt>$GRIDFIELD</tt>''': contains the 4-char QTH locator (Maidenhead square) of the entrant<br />
* '''<tt>$GRIDSQUARE</tt>''': contains the 6-char QTH locator (Maidenhead square) of the entrant<br />
* '''<tt>$INSERT</tt>''': sends message in the ['''<tt>Ins</tt>'''] key<br />
* '''<tt>$ISLAND</tt>''': sends IOTA Reference (i.e. EU001, AF001, ...) (IOTA Contest)<br />
* '''<tt>$LOGGED</tt>''' (or '''<tt>$LOGGEDCALL</tt>'''): sends what is typed in the callsign field of the current QSO, or if blank, the previous QSO<br />
* '''<tt>$MSG1...$MSG12</tt>''': sends additional CW messages (see [[Menu:Options#Modify additional messages|Modify additional messages]])<br />
* '''<tt>$MYCALL</tt>''': sends callsign set in [[New Log#Step 2: Setup your log|contest configuration]]<br />
* '''<tt>$MYNAME</tt>''': sends operator name, set in [[New Log#Step 2: Setup your log|contest configuration]]<br />
* '''<tt>$NEXT</tt>''' (or '''<tt>$NEXTCALL</tt>'''): sends the callsign of the next QSO line when a $CR is included in the message.<br />
* '''<tt>$NEXTSERIAL</tt>''': sends next QSO serial number (current QSO serial number plus 1)<br />
* '''<tt>$PLUS</tt>''': sends message in the ['''<tt>+</tt>'''] key <br />
* '''<tt>$PREV</tt>''' (or <tt>'''$PREVCALL</tt>'''): sends the callsign on the previous QSO line.<br />
* '''<tt>$PREVSERIAL</tt>''': sends previous QSO serial number (current QSO serial number minus 1)<br />
* '''<tt>$QQSLC</tt>''': sends Quick QSL message based QSOs made (see [[Menu:Tools#Intelligent Quick QSL...|Intelligent Quick QSL]])<br />
* '''<tt>$QQSLT</tt>''': sends Quick QSL message based on time passed (see [[Menu:Tools#Intelligent Quick QSL...|Intelligent Quick QSL]])<br />
* '''<tt>$QQSLRESET</tt>''': reset the timer or the counter like if the long QSL message were just sent.<br />
* '''<tt>$QSOB4</tt>''': sends the QSOB4 message and cancels the remainder of the current message, if the current QSO is a dupe, otherwise sends nothing (see [[Menu:Options#Modify standard messages...|Modify standard messages]])<br />
* '''<tt>$RST</tt>''': sends report from RST Sent field (normally '''<tt>5NN</tt>''')<br />
* '''<tt>$SERIAL</tt>''': sends current QSO Serial Number, or previous serial number if the line with the cursor is blank.<br />
* '''<tt>$STATE</tt>''': sends State/Province set in [[New Log#Step 2: Setup your log|contest configuration]] (Exchange)<br />
* '''<tt>$YEAR</tt>''': sends year nr set in [[New Log#Step 2: Setup your log|contest configuration]] (i.e. EUHFC, AA)<br />
* '''<tt>$ZONE</tt>''': sends zone nr set in [[New Log#Step 2: Setup your log|contest configuration]]<br />
* '''<tt>&''xy''</tt>''': sends a [http://en.wikipedia.org/wiki/Prosigns_for_Morse_code Morse prosign] where ''xy'' represents the two characters forming the prosign, e.g. &AS, &AR, &BK, &BT, &CL, &KN, &SK, etc.<br />
* '''<tt>+</tt>''': increase speed by 4 wpm<br />
* '''<tt>-</tt>''': decrease speed by 4 wpm<br />
* '''<tt>^</tt>''': the halfspace character with 1/2 dot duration<br />
* '''<tt>~</tt>''': (tilde) at then end of a variable means "no space" will be inserted, e.g. $NEXT~? sends the next callsign followed by a question mark, with no space in between<br />
<br />
==RTTY only==<br />
* '''<tt>$13</tt>''': send carriage return character (start print on a new line)<br />
* '''<tt>$SERIE</tt>''': send the complete QTC block (WAEDC only)<br />
<br />
==Action==<br />
* '''<tt>$CR</tt>''': works like hitting ['''<tt>Enter</tt>'''] (log QSO)<br />
* '''<tt>$GRAB1</tt>''' - '''<tt>$GRAB9</tt>''': Grabs spot 1 to 9 from the [[Menu:Windows#Partner|Partner window]] and inserts it in the callsign field. <br />
* '''<tt>$GRABRT1</tt>''' - '''<tt>$GRABRT3</tt>''': Grabs realtime spot 1 to 3 from the [[Menu:Windows#Partner|Partner window]] and inserts it in the callsign field. <br />
* '''<tt>$GRABPARTNER</tt>''': grabs the first callsign from the [[Menu:Windows#Partner|Partner window]] and inserts it in the callsign field. See usage notes under [[Menu:Windows#Partner|Partner window]].<br />
* '''<tt>$GRABSPOT</tt>''': grabs spot on the current frequency<br />
* '''<tt>$GUESSEXCH</tt>''' (or '''<tt>$GUESSEXCHANGE</tt>'''): mimics a space bar hit, filling the exchange field(s) if possible, but the cursor remains in the same edit field.<br />
* '''<tt>$REPEAT</tt>''': restarts the [[Menu:Tools#Automatic_CQ_repeat|automatic repeating CQ]] sequence (if enabled), after pausing for the specified interval. Most useful at the end of the [[Menu:Options#Modify_standard_messages...|'''<tt>[Plus]</tt>''' key message]] to avoid having to press [F1] to start CQing again.<br />
* '''<tt>$RSTEXCHSENT</tt>''': Resets the "exchangeSent" flag of the active QSO (useful only for [[API#ESM_Script_.28embedded_into_Win-Test.29|ESM scripts]])<br />
* '''<tt>$SETEXCHSENT</tt>''': Sets the "exchangeSent" flag of the active QSO (useful only for [[API#ESM_Script_.28embedded_into_Win-Test.29|ESM scripts]])<br />
* '''<tt>$SPACEBAR</tt>''': works like hitting spacebar-key (move cursor to the next most-used field)<br />
* '''<tt>$TAB</tt>''': works like hitting ['''<tt>Tab</tt>'''] (move cursor to next field)<br />
<br />
==SO2R==<br />
* '''<tt>$ALTERNATECQ</tt>''' (or '''<tt>$ACQ</tt>'''): swaps primary and secondary radios and send CQ on the secondary radio<br />
* '''<tt>$CQ</tt>''': same as '''<tt>$ALTERNATECQ</tt>''' but does not swap radios<br />
* '''<tt>$LATCH</tt>''': sets latch mode<br />
* '''<tt>$MK2R=''cmd''</tt>''': send a specific MK2R command to the microHAM MK2R SO2R box. See [[Supported_Accessories#Integrated_SO2R_boxes|Integrated_SO2R_boxes]] for usage notes.<br />
* '''<tt>$R1R1</tt>''': set audio of Radio 1 to left and right ear<br />
* '''<tt>$R1R2</tt>''': set audio of Radio 1 to left and audio of Radio 2 to right ear<br />
* '''<tt>$R2R1</tt>''': set audio of Radio 2 to left and audio of Radio 1 to right ear<br />
* '''<tt>$R2R2</tt>''': set audio of Radio 2 to left and right ear<br />
* '''<tt>$RESET</tt>''': cancels any manual change made in the audio control<br />
* '''<tt>$TR1</tt>''': transmit on primary radio<br />
* '''<tt>$TR2</tt>''': transmit on secondary radio<br />
<br />
==WAEDC QTC related==<br />
* '''<tt>$CALLSIGN</tt>''': send callsign of the current QTC <br />
* '''<tt>$DONE</tt>''': if all QTC are sent: mimic the '''<tt>[+]</tt>''' key <br />
* '''<tt>$FIELD</tt>''': this variable takes the value "GROUP", "TIME", "CL" or "NR", depending on the kind of QTC field where the cursor is located<br />
* '''<tt>$GRNR</tt>''': sends group & number of the received QTC<br />
* '''<tt>$NEXT</tt>''': move focus to the next QTC line <br />
* '''<tt>$QTC</tt>''': sends group & number of the transmitted QTC <br />
* '''<tt>$QTCROW</tt>''': Row number of cursor location in the QTC window. Very useful to create a function key sending the message '''<tt>PSE RPT QTC NR $QTCROW $QTCROW</tt>''' in WAEDC RTTY to request repetition of a specific QTC. <br />
* '''<tt>$SERIAL</tt>''': send serial number of the current QTC <br />
* '''<tt>$SERIE</tt>''': send the complete QTC block (specific to RTTY) <br />
* '''<tt>$TIME</tt>''': send time of the current QTC <br />
* '''<tt>$VALID</tt>''': save everything and close the window <br />
<br />
[[Main Page|Back to Main Page]]<br />
<br />
==Custom variables==<br />
The user may define "custom" variables with any unused name. They can be used in messages and easily updated while operating. They are mostly intended for the DXPedition mode, but they work for all CW and RTTY logs.<br />
<br />
For example, one could define<br />
* '''<tt>$REGION</tt>''' as "EU", "NA", etc.<br />
* '''<tt>$UP</tt>''' as "UP" or "UP 5"<br />
<br />
See [[Menu:Options#Custom_variables...|Options | CW | Custom variables...]] for usage notes.</div>N6TVhttps://docs.win-test.com/w/index.php?title=Interfaces&diff=4552Interfaces2015-09-07T21:41:54Z<p>N6TV: /* COM-port CW keying */ Indicated ground pin for serial port keying.</p>
<hr />
<div>Configuration of interfaces in Win-Test needs only be done once, rather than on a per-contest basis. This means you do not waste time remembering your interface configuration details prior to each contest!<br />
<br />
== Interface configuration ==<br />
<br />
The [[Menu:Options#Configure_interfaces...|interface configuration window]] can be opened by clicking on <code>Options->Configure Interfaces</code> menu in the main Win-Test window, or via the text command '''<tt>SETUP</tt>'''.<br />
<br />
=== Radio configuration ===<br />
At the bottom of the window there is a "Transceivers" section which includes two drop-down lists where you set your radio type ('''Radio 1''' and '''Radio 2'''). First, choose your rig make and model from the appropriate list. Please note that there is only one "Kenwood" entry in the list because all Kenwood rigs use a common protocol.<br />
<br />
On the left hand side of the window, you will see a list of COM ports (only available COM ports on your system will be selectable). After you have chosen the manufacturer and/or model of your rig, check the box corresponding to the COM port to which your radio is connected. For example: <br />
<br />
[[Image:Interfaces.png|frame|center|COM port configuration]]<br />
<br />
Upon checking the box, you will notice that the adjacent drop-down box will now be enabled. You ''must'' choose '''Radio 1''' or '''Radio 2''' from this drop-down list. You must also '''ensure that the port (baud rate) settings are correct for your radio'''.<br />
<br />
By default, the settings of 19200 8-N-1 will be configured, which is probably incorrect for your radio. Click on the adjacent '''<tt>[Configure...]</tt>''' button to display the [[Menu:Options#Serial_Ports|COM port properties dialog]]:<br />
<br />
[[Image:com1-properties.png|frame|center|COM port configuration for Radio1 / Radio2]]<br />
<br />
If you are not sure about the baud rate settings for your transceiver, press the '''<code>[default settings]</code>''' button to change all values to the known hardware defaults for the selected radio.<br />
<br />
There is also a list of known working settings for common contest radios located in the [[Supported_rigs|Supported rigs]] chapter.<br />
<br />
== Configuring other interfaces ==<br />
<br />
As you may well have noticed by this stage, a variety of other interfaces can also be enabled from the <code>Configure Interfaces</code> dialog box. It is just a simple case of ticking the relevant COM port and choosing said device from the drop-down list. Examples include TNCs, SO2R switching boxes (e.g. [[SO2R/EZMaster/Setup|EZmaster]], [[SO2R/MK2R/Setup|microHAM MK2R]], WinKey, W5XD Keyer, etc.). For everything not on the list, you can choose <code>Other interface...</code> and configure the port settings yourself - for example, COM port CW interface (see below).<br />
<br />
=== COM-port CW keying ===<br />
<br />
If you have a simple transistor-based COM port CW interface (see below), you can enable this by again choosing the corresponding COM port, and selecting <code>Other interface...</code> from the drop-down list. Clicking on the <code>Configure</code> button will display the [[Menu:Options#Serial_Ports|COM Port Properties dialog]] including a drop-down list of options for DTR (pin 4) and RTS (pin 7) on<br />
a DB9 connector (pins 20 and 4 on a DB25). Connect the emitter of the NPN transistor to signal ground, pin 5 on DB9 (pin 7 on DB25).<br />
<br />
''Be sure to select '''DTR: CW''' from the drop-down list.''<br />
<br />
[[Image:Schema_COM_InterfaceCW.gif|center|frame|Simple COM port CW interface]]<br />
<br />
This interface was designed for K1EA's CT and is still in use today with Win-Test.<br />
<br />
=== LPT-port CW keying ===<br />
<br />
Likewise, if you have an LPT (parallel) port CW interface (see schematics below), you can enable it by checking the box next to 'LPT' in the [[Menu:Options#Configure_interfaces...|Configure interfaces dialog]]. Clicking on the <code>[Configure]</code> button in the Printer Ports section will display the [[Menu:Options#Printer_Ports|Printer Ports dialog]]. At the very bottom, you can enable CW and PTT on pin 17 and 16 respectively. ''Ensure this is checked.''<br />
<br />
{{wbox|WARNING|In order for LPT keying to function correctly under Windows XP, Vista, or 32-bit Windows 7, you will need an additional utility, '''DLPortIO.dll''' installed by Port95NT.exe, obtainable from the Win-Test website. It is a simple process and only needs to be installed/run once. Please [http://download.win-test.com/port95nt.exe click here] to download. For 64-bit Windows 7, use InpOut32.dll as described in [http://lists.f5mzn.org/pipermail/support/2011-May/081094.html this post].}}<br />
<br />
[[Image:Schema_InterfaceCW.gif|center|frame|Simple LPT port CW interface]]<br />
<br />
=== Digital Voice Keyer ===<br />
<br />
The DVK-100 voice keyer was the first computer-controlled voice memory in the contesting world in the early 90s. Later, some equipment manufacturers built voice memories into their radios like Kenwood (TS-850, TS-950 with the DRU2 and DRU3 units respectively - probably others). These devices can be controlled by Win-Test using the following LPT interface.<br />
<br />
[[Image:Schema_InterfaceDVK.gif|center|frame|Simple LPT port DVK interface]]<br />
<br />
Usually the device has 3-4 different memories which can be triggered by [<b><tt>F1</tt></b>]...[<b><tt>F4</tt></b>] on the computer keyboard.<br />
<br />
=== Sound Card ===<br />
<br />
Wav files can also be played from an internal sound card by utilizing a small interface like shown below.<br />
Messages are recorded using <b><tt>Shift-F1</tt></b>...<b><tt>Shift-F7</tt></b>.<br />
<br />
[[Image:Schema_Interface_SoundCard.gif|center|frame|Sound Card Interface]]<br />
<br />
The use of an isolation transformer is recommended both on the output side of the sound card. Of course, you can go without one but first think about the trouble you will encounter when the Line Out port of your sound card gets killed by stray RF or when someone tells you you got hum on your audio in the middle of the contest. <br />
<br />
[[Image:SoundcardInterface.gif|center|frame|Sound Card interface kindly provided by W9ZRX. This interface is in use at the K3LR M/M station.]]<br />
<br />
W9ZRX has provided this design that comes without a relay to switch Mic input between radio and sound card. Most sound cards allow routing from Mic input to Line Out so that you can control muting Line Out from within Win-Test. Make sure that the Microphone has been enabled as an Input to the Sound Card Mixer. Different Sound Cards set up slightly differently, but most seem to either show the Microphone Input to the Mixer as '''muted''', or the default Mixer Inputs do not include the Microphone until '''enabled'''.<br />
<br />
There are sound cards that do not support this option. The Writelog download site has a [http://www.writelog.com/Downloads/sbrdchk.zip sound card checker] that will help you to determine if you have this problem if it absolutely doesn't work.<br />
<br />
Another way would be to try using the Win-Test PTT output to drive a relay to allow a direct routing between your Mic and the Mic input of your TRX when the PTT output is off. This requires some additional components but better than an external mic to record the DVK messages.<br />
<br />
=== Band Data ===<br />
<br />
Win-Test supports filter and antenna switching by supplying Yaesu-standard Band data on pins 2, 7, 8 and 9 of the parallel port. These pins are equivalent to lines A, B, C and D. This feature allows you to automatically control other devices in your station, probably by using a band decoder like the one from [http://www.qth.com/topten/bdecoder.htm Top Ten Devices]. <br />
<br />
{| {{Prettytable_fixed}}<br />
! Band !! A !! B !! C !! D <br />
|-<br />
| 160 m || 0 || 0 || 0 || 1<br />
|-<br />
| 80 m || 0 || 0 || 1 || 0<br />
|-<br />
| 40 m || 0 || 0 || 1 || 1<br />
|-<br />
| 30 m || 0 || 1 || 0 || 0<br />
|-<br />
| 20 m || 0 || 1 || 0 || 1<br />
|-<br />
| 17 m || 0 || 1 || 1 || 0<br />
|-<br />
| 15 m || 0 || 1 || 1 || 1<br />
|-<br />
| 12 m || 1 || 0 || 0 || 0<br />
|-<br />
| 10 m || 1 || 0 || 0 || 1<br />
|-<br />
| 6 m || 1 || 0 || 1 || 0<br />
|-<br />
| 2 m || 1 || 0 || 1 || 1<br />
|-<br />
| 70 cm || 1 || 1 || 0 || 0<br />
|-<br />
|}<br />
<br />
=== Radio 1/Radio 2 ===<br />
<br />
LPT pin 14 is used to send Radio1/2 information to an external interface. High = Radio1, Low = Radio2.<br />
<br />
=== Headphones Control ===<br />
The signals ''Headphones Control'' (called ''RX Focus'' in the MK2R microHAM SO2R interface) is available on LPT, pin 4. This signal allows to control which radio you want to listen to in the headphones. Must be enabled in the LPT Configuration Window. Low = Radio 1, High = Radio 2.<br />
<br />
== See Also == <br />
<br />
=== From the Win-Test manual ===<br />
<br />
* [[Menu:Options#Configure_interfaces...|Configure interfaces dialog]]<br />
* [[Networking|Networking configuration for multi-ops]]<br />
* [[SO2R/EZMaster/Setup|EZMaster setup]]<br />
* [[SO2R/MK2R/Setup|microHAM MK2R setup]]<br />
<br />
=== External sources ===<br />
<br />
* [http://www.microham.com/Downloads/micro_KEYER_R_2_0_English.pdf microHAM MicroKeyer Manual]<br />
* [http://www.microham.com/Downloads/USB_Interface_II_R_1_1_English.pdf microHAM USB II Interface Manual]</div>N6TVhttps://docs.win-test.com/w/index.php?title=API&diff=4536API2015-03-18T00:24:44Z<p>N6TV: /* Win-Test API Variables */ change wtScript to wtRootScript</p>
<hr />
<div>===List of Win-Test API Functions===<br />
Compiled from information found on the WT reflector on October 7, 2009 ([http://lists.f5mzn.org/pipermail/support/2009-October/078505.html],<br />
[http://lists.f5mzn.org/pipermail/support/2009-October/078510.html]).<br />
<br />
'''The most current API documentation from the Win-Test developers may be found at [http://download.win-test.com/v4/lua/LuaApiDoc.txt http://download.win-test.com/v4/lua/LuaApiDoc.txt].<br />
'''<br />
====Class wtApp====<br />
{| border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#F9F9F9; font-size:95%; empty-cells:show;"<br />
|-<br />
| '''<tt>wtApp:AlertBox(Text)</tt>'''<br />
| Opens a standard Windows alert box with the specified text and an [OK] button.<br />
|-<br />
| '''<tt>wtApp:CallScript(strScript [, arg])</tt>'''<br />
| Call a wts script (no extension required in strScript). Can return a number only (or nothing). Optional argument's value can be accessed via wtArg in the called script.<br />
|-<br />
| '''<tt>wtApp:GetAppPath()</tt>'''<br />
| Win-Test installation directory path<br />
|-<br />
| '''<tt>wtApp:GetKeyState()</tt>'''<br />
| Returns the modifers keys status when the function is called.<br />
|-<br />
| '''<tt>wtApp:GetCfgPath()</tt>'''<br />
| \cfg directory path<br />
|-<br />
| '''<tt>wtApp:GetCtyPath()</tt>'''<br />
| \countryFiles directory path<br />
|-<br />
| '''<tt>wtApp:GetDatabasePath()</tt>'''<br />
| \databases directory path<br />
|-<br />
| '''<tt>wtApp:GetExtraPath()</tt>'''<br />
| \extras directory path<br />
|-<br />
| '''<tt>wtApp:GetIniFileName()</tt>'''<br />
| Return the name of the current .ini file, including the ".ini" extension. Usually returns "wt.ini" unless overidden via the -i command line argument.<br />
|-<br />
| '''<tt>wtApp:GetLogFileName()</tt>'''<br />
| Return the name of the current log file, including the ".wt4" extension<br />
|-<br />
| '''<tt>wtApp:GetLogPath()</tt>'''<br />
| Current log directory path<br />
|-<br />
| '''<tt>wtApp:GetOpPath()</tt>'''<br />
| \ops directory path<br />
|-<br />
| '''<tt>wtApp:GetScriptPath()</tt>'''<br />
| \scripts directory path<br />
|-<br />
| '''<tt>wtApp:InputInteger(Prompt, Title, Default)</tt>'''<br />
| If Prompt is empty, it defaults to "Enter an integer". If Title is empty, it defaults to "Win-Test script". If a default value is specified, the pop-up window is pre-filled with the specified integer value.<br />
|-<br />
| '''<tt>wtApp:InputNumber(Prompt, Title, Default)</tt>'''<br />
| If Prompt is empty, it defaults to "Enter a number". If Title is empty, it defaults to "Win-Test script". If a default value is specified, the pop-up window is pre-filled with the specified number value. In LUA, a "number" data type may or may not contain a decimal point.<br />
|-<br />
| '''<tt>wtApp:InputText(Prompt, Title, Default)</tt>'''<br />
| If Prompt is empty, it defaults to "Enter a text". If Title is empty, it defaults to "Win-Test script". If a default value is specified, the pop-up window is pre-filled with the specified text.<br />
|-<br />
| '''<tt>wtApp:InputUpperText(Prompt, Title, Default)</tt>'''<br />
| Same as wtApp:InputText, but all text is converted to uppercase.<br />
|-<br />
| '''<tt>wtApp:IsCapsLock()</tt>'''<br />
| Returns '''true''' if the '''[Caps Lock]''' key is enabled and the secondary radio window is highlighted, otherwise returns '''false'''.<br />
|-<br />
| '''<tt>wtApp:IsPostKeyProcess()</tt>'''<br />
| Returns '''true''' if the current script is being executed after the assigned key has been processed by WT, otherwise returns '''false'''.<br />
|-<br />
| '''<tt>wtApp:MessageBox(Text, Type, Title)</tt>'''<br />
| Display a Message box with the specified text, using the specified type and message box title (shown in the title bar of the message box window). See also wtApp:AlertBox(). Type 0 is an ordinary message box with an [OK] button, type 1 has both an [OK] and a [Cancel] button. The return code indicates the button pressed by the user (which may be ignored). Return code 1 means the [OK] button was pressed, return code 2 means the [Cancel] button was pressed.<br />
<br />
See the [http://msdn.microsoft.com/en-us/library/ms645505%28VS.85%29.aspx Microsoft Windows MessageBox API documentation] for more details about supported message box types and return codes.<br />
|-<br />
| '''<tt>wtApp:ResetCapsLock()</tt>'''<br />
| Disables the '''[Caps Lock]''' key. Normally used to change focus to the primary radio window when [[Menu:Operating#Caps_Lock_binds_to_the_secondary_radio|Caps Lock binds to the secondary radio]] is enabled<br />
|-<br />
| '''<tt>wtApp:SendAltKey(Key)</tt>'''<br />
| Key is a letter, a number, or a function key ("F1".."F12" + "Insert" + "Plus" + "Esc")<br />
|-<br />
| '''<tt>wtApp:SendCtrlKey(Key)</tt>'''<br />
| Key is a letter, a number, or a function key ("F1".."F12" + "Insert" + "Plus" + "Esc")<br />
|-<br />
| '''<tt>wtApp:SendFKey(Key [, ModifierKeys])</tt>'''<br />
| Send Functions keys (and Insert and Plus). Key is one of "F1".."F12" + "Insert" + "Plus" + "Esc". ModifierKeys (optional) indicates the modifier keys (Ctrl = 4, Alt = 2, Shift = 1, None = 0 - can be combined via addition, e.g., 6 = Ctrl+Alt). If this argument is missing or -1, the current modifier keys are used.<br />
|-<br />
| '''<tt>wtApp:SendKey(Key [, ModifiersKeys])</tt>'''<br />
| Send key or string. Key is a single character or a string. ModifiersKeys (optional) indicates the modifiers keys (Ctrl = 4, Alt = 2, Shift = 1, None = 0 - can be combined via addition, e.g., 6 = Ctrl+Alt). If this argument is missing or -1, the current modifiers keys are used.<br />
|-<br />
| '''<tt>wtApp:SendKeyCode(Code [, ModifierKeys])</tt>'''<br />
| Send a key by its ASCII code. Keycode is an ASCII code. ModifierKeys (optional) indicates the modifier keys (Ctrl = 4, Alt = 2, Shift = 1, None = 0 - can be combined via addition, e.g., 6 = Ctrl+Alt). If this argument is missing or -1, the current modifier keys are used.<br />
<br />
For Windows virtual key codes, add 256 to the key code, e.g. use <tt>wtApp:SendKeyCode(265, WT_KEY_CTRL)</tt> to simulate pressing <tt>[Ctrl]+[TAB]</tt>. Refer to the [http://msdn.microsoft.com/en-us/library/windows/desktop/dd375731(v=vs.85).aspx Microsoft Virtual Key Code documentation] to obtain code values for VK_TAB (256+9=265), VK_RETURN (256+13=269), VK_LEFT (256+37=293), etc.<br />
|-<br />
| '''<tt>wtApp:SetCapsLock()</tt>'''<br />
| Enables the '''[Caps Lock]''' key. Normally used to change focus to the secondary radio window when [[Menu:Operating#Caps_Lock_binds_to_the_secondary_radio|Caps Lock binds to the secondary radio]] is enabled<br />
|-<br />
| '''<tt>wtApp:SetWindowColor(ChildWndId, nRed, nGreen, nBlue, nColorIndex)</tt>'''<br />
| Set the nColorIndex color of the child window designated by its windowID (see [[API#Child_window_IDs|Child window IDs]]). If ChildWndId is < 0, it applies to the main window. If nColorIndex is omitted (or set to 0), it applies to the background color All colors must be <= 255.<br />
|-<br />
| '''<tt>wtApp:ShowWindow(ChildWndId)</tt>'''<br />
| Show the child window designated by its windowID (see [[API#Child_window_IDs|Child window IDs]])<br />
|-<br />
| '''<tt>wtApp:Sleep(Time)</tt>'''<br />
| Time expressed in milliseconds.<br />
|-<br />
| '''<tt>wtApp:TextCommand(Text)</tt>'''<br />
| Send WT text command to application<br />
|-<br />
| '''<tt>wtApp:ToggleCapsLock()</tt>'''<br />
| Toggles the '''[Caps Lock]''' key. Normally used to swap the current focus from the primary or secondary radio window when [[Menu:Operating#Caps_Lock_binds_to_the_secondary_radio|Caps Lock binds to the secondary radio]] is enabled<br />
|-<br />
| '''<tt>wtApp:ToggleWindow(ChildWndId)</tt>'''<br />
| Toggle the child window designated by its windowID (see [[API#Child_window_IDs|Child window IDs]])<br />
|-<br />
| '''<tt>wtApp:WizzWindow(ChildWndId)</tt>'''<br />
| "Wizz" (shake or vibrate) the child window designated by its windowID (see [[API#Child_window_IDs|Child window IDs]]). Can be used to draw attention to a particular window. <br />
|-<br />
|}<br />
<br />
====Class wtContest====<br />
{| border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#F9F9F9; font-size:95%; empty-cells:show;"<br />
|-<br />
| '''<tt>wtContest:IsExchangeRequired()</tt>'''<br />
| Return a boolean. True if the current contest requires an exchange (associated with RST)<br />
|-<br />
| '''<tt>wtContest:GetContestId()</tt>'''<br />
| Return the current contestID (see [[API#Supported_contest_IDs|Supported contest IDs]])<br />
|-<br />
|}<br />
<br />
====Class wtGab====<br />
{| border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#F9F9F9; font-size:95%; empty-cells:show;"<br />
|-<br />
| '''<tt>wtGab:Send(strText[, strToStation])</tt>'''<br />
| Sends a gab strText to strToStation. If strToStation is omitted, the text is sent to the whole network.<br />
|-<br />
|}<br />
<br />
====Class wtKeyer====<br />
<br />
{| border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#F9F9F9; font-size:95%; empty-cells:show;"<br />
|-<br />
| '''<tt>wtKeyer:GetCwSpeed()</tt>'''<br />
| Return the CW speed in wpm (return 0 in case of error).<br />
|-<br />
| '''<tt>wtKeyer:GrabHighlightedCallsign()</tt>'''<br />
| Works only in RTTY mode and grabs the currently highlighted callsign from the RX window. <br />
|-<br />
| '''<tt>wtKeyer:Insert(strMessage)</tt>'''<br />
| Works for the CW and RTTY keyers. When used in a synchronous script, it provides a way to "fill-in" or "insert" data into the CW/RTTY message stream. It is recommended to be used only in synchronous mode to ensure that the characters are inserted in the right place. WARNING: strMessage can only contain text data (no variables or script calls). It is ''not'' interpreted by the CW/RTTY parser (except for +/- speed bursts). <br />
|-<br />
| '''<tt>wtKeyer:Play(Message)</tt>'''<br />
| Message is a plain string to be played, a saved message ('''<tt>$F1</tt>''' etc.) or a variable ('''<tt>$xxx</tt>''')<br />
|-<br />
| '''<tt>wtKeyer:PlayAdditionalMsg(AdditionalMsgIndex)</tt>'''<br />
| Play the additional CW/RTTY messages (Alt-C set)<br />
|-<br />
| '''<tt>wtKeyer:SetCwSpeed(Speed)</tt>'''<br />
| Set CW speed in wpm.<br />
|-<br />
| '''<tt>wtKeyer:Stop()</tt>'''<br />
| Stop the current message<br />
|-<br />
|}<br />
<br />
====Class wtMicroham====<br />
{| border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#F9F9F9; font-size:95%; empty-cells:show;"<br />
|-<br />
| '''<tt>wtMicroham:GetDeviceId()</tt>'''<br />
| Return the ID of the microHAM attached device (see [[API#microHAM_Device_IDs|microHAM Device IDs]]).<br />
|-<br />
| '''<tt>wtMicroham:GetFirmwareVersion()</tt>'''<br />
| Return the firmware version string of the microHAM attached device.<br />
|-<br />
| '''<tt>wtMicroham:Send(strCommand)</tt>'''<br />
| Send a command string to the microHAM attached device. The trailing <CR> character is optional, and is appended if needed.<br />
|-<br />
|}<br />
<br />
====Class wtOp====<br />
{| border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#F9F9F9; font-size:95%; empty-cells:show;"<br />
|-<br />
| '''<tt>wtOp:GetCallsign()</tt>'''<br />
| Return the current op callsign<br />
|-<br />
| '''<tt>wtOp:GetNick()</tt>'''<br />
| Return the current op nick<br />
|-<br />
|}<br />
<br />
====Class wtOtrsp====<br />
{| border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#F9F9F9; font-size:95%; empty-cells:show;"<br />
|-<br />
| '''<tt>wtOtrsp:GetDeviceName()</tt>'''<br />
| Returns the name of the OTRSP attached device.<br />
|-<br />
| '''<tt>wtOtrsp:GetFirmwareVersion()</tt>'''<br />
| Returns the firmware version of the OTRSP attached device. NOTE: Some devices do not support this API, and return an empty string.<br />
|-<br />
| '''<tt>wtOtrsp:Send(strCommand)</tt>'''<br />
| Sends a command string to the OTRSP attached device. The trailing <CR> character is optional, and is appended if needed.<br />
|-<br />
|}<br />
<br />
====Class wtQso====<br />
<br />
{| border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#F9F9F9; font-size:95%; empty-cells:show;"<br />
|-<br />
| '''<tt>wtQso:IsCallsignEmpty()</tt>'''<br />
| Return a boolean : True if the callsign field of the active QSO is empty<br />
|-<br />
| '''<tt>wtQso:IsCallsignIncomplete()</tt>'''<br />
| Return a boolean : True if the callsign field of the active QSO contains a "?"<br />
|-<br />
| '''<tt>wtQso:IsExchangeEmpty()</tt>'''<br />
| Return a boolean : True if the exchange field of the active QSO is empty<br />
|-<br />
| '''<tt>wtQso:IsExchangeSent()</tt>'''<br />
| Return a boolean : True if the exchangeSent flag of the active QSO is set<br />
|-<br />
| '''<tt>wtQso:SetExchangeSent()</tt>'''<br />
| Set the exchangeSent flag of the active QSO (see '''<tt>wtQso:IsExchangeSent()</tt>''') - Similar to the use of '''<tt>$SETEXCHSENT</tt>'''<br />
|-<br />
| '''<tt>wtQso:ResetExchangeSent()</tt>'''<br />
| Reset the exchangeSent flag of the active QSO (see '''<tt>wtQso:IsExchangeSent()</tt>''') - Similar to the use of '''<tt>$RSTEXCHSENT</tt>'''<br />
|-<br />
| '''<tt>wtQso:ClearStatus()</tt>'''<br />
| Clear the status flags of the active QSO<br />
|-<br />
| '''<tt>wtQso:GetData()</tt>'''<br />
| Returns a LUA table object with fields of the current QSO. The current available keys are "time", "band", "mode", "freq", "callsign", "rstSent", "serialSent", "rstReceived", "exchReceived", "miscInfoReceived", "miscInfo2Received", e.g. qsoData = wtQso:GetData(), then qsoData["time"] returns "17:03" or similar.<br />
|-<br />
| '''<tt>wtQso:GetModeId()</tt>'''<br />
| Return the mode ID of the active QSO (see [[API#Supported_mode_IDs|Supported mode IDs]]).<br />
|-<br />
| '''<tt>wtQso:IsCallsignRepeated()</tt>'''<br />
| Return a boolean. True if the callsign hasn't changed since the last Enter<br />
|-<br />
| '''<tt>wtQso:IsOperatingModeRun()</tt>'''<br />
| Return a boolean. True if the operating mode of the active QSO is RUN (and False if S&P)<br />
|-<br />
| '''<tt>wtQso:IsModePhone()</tt>'''<br />
| Return a boolean. True if the mode of the active QSO is Phone (SSB and FM), and False otherwise<br />
|-<br />
| '''<tt>wtQso:IsQsoApproved()</tt>'''<br />
| Return a boolean. True if all requested fields of the active QSO are filled (contest dependent)<br />
|-<br />
| '''<tt>wtQso:IsDupe()</tt>'''<br />
| Return a boolean. True if the current callsign is a dupe<br />
|-<br />
| '''<tt>wtQso:IsCurrentFieldCallsign()</tt>'''<br />
| Return a boolean : True if the current field is the callsign field<br />
|-<br />
| '''<tt>wtQso:IsCurrentFieldExchange()</tt>'''<br />
| Return a boolean : True if the current field is an exchange field<br />
|-<br />
| '''<tt>wtQso:IsCurrentFieldOther()</tt>'''<br />
| Return a boolean : True if the current field is not the callsign field or an exchange field<br />
|-<br />
| '''<tt>wtQso:IsCurrentFieldEmpty()</tt>'''<br />
| Return a boolean : True if the current field is empty (except RST for the exchange field)<br />
|-<br />
| '''<tt>wtQso:IsCurrentFieldPrimaryRadio()</tt>'''<br />
| Return a boolean : True if the current field is in the primary radio (main log)<br />
|-<br />
| '''<tt>wtQso:IsCurrentFieldSecondryRadio()</tt>'''<br />
| Return a boolean : True if the current field is in the secondary radio<br />
|-<br />
|}<br />
<br />
====Class wtRadio*====<br />
<br />
The following generic functions can by applied to:<br />
'''<tt>wtRadio</tt>''' (the active one),<br />
'''<tt>wtRadioInactive</tt>''' (the non-active one),<br />
'''<tt>wtRadioPrimary</tt>''' (the one that is in the main log wnd)<br />
'''<tt>wtRadioSecondary</tt>''' (the one that is in the secondary log wnd)<br />
'''<tt>wtRadio1</tt>''' and '''<tt>wtRadio2</tt>'''.<br />
<br />
WARNING: Some functions may not work because of the CAT protocol or radio hardware limitations.<br />
<br />
{| border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#F9F9F9; font-size:95%; empty-cells:show;"<br />
|-<br />
| '''<tt>wtRadio*:GetFreq()</tt>'''<br />
| Return freq of the active VFO of the designated radio freq is expressed in kHz<br />
|-<br />
| '''<tt>wtRadio*:GetFreq(NVfo)</tt>'''<br />
| Return freq of the designated VFO (0 => VFO A, 1 => VFO B) of the designated radio freq is expressed in kHz<br />
|-<br />
| '''<tt>wtRadio*:GetFreqInactiveVfo()</tt>'''<br />
| Return freq of the inactive VFO of the designated radio freq is expressed in kHz<br />
|-<br />
| '''<tt>wtRadio*:GetTypeId()</tt>'''<br />
| Return type of radio (see [[API#Radio_Types|Radio Types]])<br />
|-<br />
| '''<tt>wtRadio*:GetManufacturerId()</tt>'''<br />
| Return manufacturer of radio (see [[API#Radio_Manufacturer_Constants|Radio Manufacturer Constants]])<br />
|-<br />
| '''<tt>wtRadio*:SetFreq(freq)</tt>'''<br />
| Set freq of the active VFO of the designated radio freq is expressed in kHz<br />
|-<br />
| '''<tt>wtRadio*:SetFreq(freq, nVfo)</tt>'''<br />
| Set freq of the designated VFO (0 => VFO A, 1 => VFO B) of the designated radio freq is expressed in kHz<br />
|-<br />
| '''<tt>wtRadio*:SetFreqInactiveVfo(freq)</tt>'''<br />
| Set freq of the inactive VFO of the designated radio freq is expressed in kHz<br />
|-<br />
| '''<tt>wtRadio*:SetFreqSubVfo(freq)</tt>'''<br />
| Set freq of the sub VFO of the designated radio freq is expressed in kHz<br />
|-<br />
| '''<tt>wtRadio*:SetSplit(freq)</tt>'''<br />
| Set split ON and the split frequency on the designated radio freq is expressed in kHz<br />
|-<br />
| '''<tt>wtRadio*:ResetSplit()</tt>'''<br />
| Reset split on the designated radio<br />
|-<br />
| '''<tt>wtRadio*:IsSplit()</tt>'''<br />
| Return false or true whether the split is set or not on the designated radio<br />
|-<br />
| '''<tt>wtRadio*:GetRadioId()</tt>'''<br />
| Return the radioID (0 => RADIO_1, 1 => RADIO_2) of the designated radio<br />
|-<br />
| '''<tt>wtRadio*:Send(catString)</tt>'''<br />
| Send the ASCII catString to the designated radio<br />
|-<br />
| '''<tt>wtRadio*:SendHex(hexString)</tt>'''<br />
| Send the hexString to the designated radio. The hexString must contain only 0-9 and A-F characters and must have an even length. Ex "02DFA8" etc.<br />
|-<br />
|}<br />
<br />
====Class wtStatus====<br />
{| border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#F9F9F9; font-size:95%; empty-cells:show;"<br />
|-<br />
| '''<tt>wtStatus:GetList()</tt>'''<br />
| Returns a table with names of the stations in the network<br />
|-<br />
| '''<tt>wtStatus:GetStatus(strStation)</tt>'''<br />
| returns a table with fields of the status of a given station. Returns nil if this station doesn't exist. The table keys are "band" "mode" "currentRadio" "radio1Freq" "radio2Freq" "radio1IsManual" "radio2IsManual" "passFreq" "type" and "qsyStatusId".<br />
|-<br />
| '''<tt>wtStatus:GetFreq(strBand[, strMode])</tt>'''<br />
| returns the "best" pass freq for a given band and mode. To determine this frequency, it uses the same algorithm as the $FREQnn variable<br />
|-<br />
|}<br />
<br />
===Win-Test API Variables===<br />
* '''<tt>wtArg</tt>''': get the optional argument set in the Script Manager or in a '''#SCRIPT(argument)''' call. '''<tt>wtArgument</tt>''' is also provided for backward compatibility. Both variables are local to the script called.<br />
* '''<tt>wtCurrentScript</tt>''': contains the script name currently executed, without extension<br />
* '''<tt>wtRootScript</tt>''': contains the name of the top-most called script, without extension<br />
<br />
===Win-Test API Constants===<br />
'''The most current list of Win-Test API Constants may be found at [http://download.win-test.com/v4/lua/constants.wts http://download.win-test.com/v4/lua/constants.wts].'''<br />
<br />
Constants are not guaranteed to remain constant in Lua, that is, a program can update these variables. Any constant could be accidentally reassigned to refer to some other object or value. Unfortunately, there is no easy way to generate code that prevents this. You will just have to be careful. Avoid creating variable names starting with WT_.<br />
<br />
====Child window IDs====<br />
<pre><br />
WT_WND_SUMMARY = 0;<br />
WT_WND_GRIDSQUAREMAP = 1;<br />
WT_WND_CHECKPARTIAL = 2;<br />
WT_WND_RATESHEET = 3;<br />
WT_WND_CLOCK = 4;<br />
WT_WND_VUMETER = 5;<br />
WT_WND_RATE = 6;<br />
WT_WND_GAB = 7;<br />
WT_WND_MAP = 8;<br />
WT_WND_CHECKCOUNTRY = 9;<br />
WT_WND_ZONE = 10;<br />
WT_WND_MULT = 11;<br />
WT_WND_NP1 = 12;<br />
WT_WND_RADIO1 = 13;<br />
WT_WND_RADIO2 = 14;<br />
WT_WND_PACKETCLUSTER = 15;<br />
WT_WND_DXCLUSTERANN = 16;<br />
WT_WND_SOLAR = 17;<br />
WT_WND_PARTNER = 18;<br />
WT_WND_STATUS = 19;<br />
WT_WND_SKED = 20;<br />
WT_WND_CHECKCALL = 21;<br />
WT_WND_SECONDARYRADIO = 22;<br />
WT_WND_RTTY1 = 23;<br />
WT_WND_RTTY2 = 24;<br />
WT_WND_QSYWIZARD = 25;<br />
WT_WND_EXTRAINFO = 26;<br />
WT_WND_ZONE2 = 27;<br />
WT_WND_ROTATORS = 28;<br />
WT_WND_CONTESTRECORDER = 29;<br />
</pre><br />
<br />
====Supported contest IDs====<br />
<pre><br />
WT_CONTEST_IARU_VHF = 1;<br />
WT_CONTEST_IARU_UHF = 2;<br />
WT_CONTEST_IARU_CW = 3;<br />
WT_CONTEST_IARU_HF = 4;<br />
WT_CONTEST_IARU_R1_50MHZ = 5;<br />
WT_CONTEST_REF_THF = 10;<br />
WT_CONTEST_REF_DDFM_50MHZ = 11;<br />
WT_CONTEST_THF_EU = 20;<br />
WT_CONTEST_THF_EU_50_70 = 21;<br />
WT_CONTEST_THF_EU_GRIDSQUARE = 30;<br />
WT_CONTEST_THF_EU_GRIDSQUARE_50_70 = 31;<br />
WT_CONTEST_THF_EU_GRIDSQUARE_NO_DIST = 32;<br />
WT_CONTEST_THF_EU_GRIDSQUARE_NO_DIST_50_70 = 33;<br />
WT_CONTEST_REF_HF = 100;<br />
WT_CONTEST_ARRL_DX = 101;<br />
WT_CONTEST_ARRL_10 = 102;<br />
WT_CONTEST_ARRL_160 = 103;<br />
WT_CONTEST_ARRL_SWEEPSTAKES = 104;<br />
WT_CONTEST_ARRL_FD = 105;<br />
WT_CONTEST_ARRL_RU = 106;<br />
WT_CONTEST_ARRL_UHF_AUG = 130;<br />
WT_CONTEST_ARRL_VHF_JAN = 131;<br />
WT_CONTEST_ARRL_VHF_JUN = 132;<br />
WT_CONTEST_ARRL_VHF_SEP = 133;<br />
WT_CONTEST_REF_160 = 150;<br />
WT_CONTEST_CQWW_DX = 200;<br />
WT_CONTEST_CQWW_WPX = 201;<br />
WT_CONTEST_CQWW_160 = 202;<br />
WT_CONTEST_CQWW_VHF = 250;<br />
WT_CONTEST_RDXC = 300;<br />
WT_CONTEST_RDAC = 301;<br />
WT_CONTEST_CIS = 302;<br />
WT_CONTEST_R_160 = 303;<br />
WT_CONTEST_RRTC = 304;<br />
WT_CONTEST_RAEM = 305;<br />
WT_CONTEST_DXPEDITION_HF = 400;<br />
WT_CONTEST_DXPEDITION_VHF = 410;<br />
WT_CONTEST_ALL_ASIAN = 500;<br />
WT_CONTEST_SPDXC = 600;<br />
WT_CONTEST_JIDX = 700;<br />
WT_CONTEST_KCJ = 701;<br />
WT_CONTEST_KCJ_TOPBAND = 702;<br />
WT_CONTEST_YUDXC = 800;<br />
WT_CONTEST_CQM = 900;<br />
WT_CONTEST_ARI = 1000;<br />
WT_CONTEST_ARI_SEZIONI = 1001;<br />
WT_CONTEST_ARI_40_80 = 1002;<br />
WT_CONTEST_BALTIC = 1100;<br />
WT_CONTEST_KING_OF_SPAIN = 1200;<br />
WT_CONTEST_IOTA = 1300;<br />
WT_CONTEST_RSGB_160 = 1301;<br />
WT_CONTEST_RSGB_80_CC = 1302;<br />
WT_CONTEST_RSGB_CMW = 1303;<br />
WT_CONTEST_RSGB_15_10 = 1304;<br />
WT_CONTEST_RSGB_AFS = 1305;<br />
WT_CONTEST_WAEDC = 1400;<br />
WT_CONTEST_WAG = 1401;<br />
WT_CONTEST_DARC_XMAS = 1402;<br />
WT_CONTEST_DARC_10 = 1403;<br />
WT_CONTEST_YODXC = 1500;<br />
WT_CONTEST_EU_HF = 1600;<br />
WT_CONTEST_SCC = 1601;<br />
WT_CONTEST_OCDXC = 1700;<br />
WT_CONTEST_TOECC = 1800;<br />
WT_CONTEST_SAC = 1900;<br />
WT_CONTEST_NRAU_BALTIC = 1901;<br />
WT_CONTEST_NAC = 1902;<br />
WT_CONTEST_SARTG = 1903;<br />
WT_CONTEST_QP_TX = 2000;<br />
WT_CONTEST_EU_SPRINT = 2100;<br />
WT_CONTEST_UKDXC = 2200;<br />
WT_CONTEST_OKOMDXC = 2300;<br />
WT_CONTEST_STEW_PERRY = 2400;<br />
WT_CONTEST_GACW_DX = 2401;<br />
WT_CONTEST_NINE_KCC_15 = 2402;<br />
WT_CONTEST_FOC_MARATHON = 2403;<br />
WT_CONTEST_LOTW = 2404;<br />
WT_CONTEST_AP_SPRINT = 2405;<br />
WT_CONTEST_JARTS = 2406;<br />
WT_CONTEST_MARCONI_HF = 2407;<br />
WT_CONTEST_LZDX = 2500;<br />
WT_CONTEST_CROATIAN_CW = 2600;<br />
WT_CONTEST_UBADX = 2700;<br />
WT_CONTEST_UBA_SPRING_80M = 2701;<br />
WT_CONTEST_UBA_SPRING_6M = 2702;<br />
WT_CONTEST_UBA_SPRING_2M = 2703;<br />
WT_CONTEST_ON_80M = 2704;<br />
WT_CONTEST_ON_6M = 2705;<br />
WT_CONTEST_ON_2M = 2706;<br />
WT_CONTEST_RAC_DAY = 2800;<br />
WT_CONTEST_RAC_WINTER = 2801;<br />
WT_CONTEST_PACC = 2900;<br />
WT_CONTEST_HELVETIA = 3000;<br />
WT_CONTEST_HELVETIA_VHF = 3001;<br />
WT_CONTEST_IARU_FD_R1_GENERIC = 3100;<br />
WT_CONTEST_IARU_FD_R1_DARC = 3101;<br />
WT_CONTEST_IARU_FD_R1_RSGB = 3102;<br />
WT_CONTEST_UFT_HF = 3200;<br />
WT_CONTEST_AGCW_HNY = 3300;<br />
WT_CONTEST_HA_DX = 3400;<br />
WT_CONTEST_NAQP = 3500;<br />
WT_CONTEST_NA_SPRINT = 3501;<br />
WT_CONTEST_NCCC_SPRINT = 3600;<br />
WT_CONTEST_CQIR = 3700;<br />
</pre><br />
<br />
====Supported mode IDs====<br />
<pre><br />
WT_MODE_CW = 0;<br />
WT_MODE_SSB = 1;<br />
WT_MODE_RTTY = 2;<br />
WT_MODE_FM = 3;<br />
WT_MODE_PSK = 4;<br />
WT_MODE_PKT = 5;<br />
WT_MODE_HELL = 6;<br />
WT_MODE_SAT = 7;<br />
</pre><br />
<br />
====Status key IDs====<br />
<pre><br />
WT_KEY_NONE = 0;<br />
WT_KEY_SHIFT = 1;<br />
WT_KEY_ALT = 2;<br />
WT_KEY_CTRL = 4;<br />
</pre><br />
<br />
====Radio Constants====<br />
<pre><br />
WT_RADIO_MAX = 2;<br />
<br />
WT_RADIO_VFOA = 0;<br />
WT_RADIO_VFOB = 1;<br />
<br />
WT_RADIO_1 = 0;<br />
WT_RADIO_2 = 1;<br />
</pre><br />
<br />
====Radio Manufacturer Constants====<br />
<pre><br />
WT_RADIO_MANUFACTURER_UNKNOWN = 0;<br />
WT_RADIO_MANUFACTURER_ICOM = 1;<br />
WT_RADIO_MANUFACTURER_YAESU = 2;<br />
WT_RADIO_MANUFACTURER_KENWOOD = 3;<br />
WT_RADIO_MANUFACTURER_TENTEC = 4;<br />
WT_RADIO_MANUFACTURER_ELECRAFT = 5;<br />
WT_RADIO_MANUFACTURER_FLEXRADIO = 6;<br />
</pre><br />
<br />
====Radio Types====<br />
<pre><br />
WT_RADIO_UNKNOWN = -1;<br />
WT_RADIO_NONE = 0;<br />
WT_RADIO_KENWOOD = 1;<br />
WT_RADIO_IC703 = 1703;<br />
WT_RADIO_IC706 = 1706;<br />
WT_RADIO_IC706MkII = 17061;<br />
WT_RADIO_IC706MkIIG = 17062;<br />
WT_RADIO_IC718 = 1718;<br />
WT_RADIO_IC725 = 1725;<br />
WT_RADIO_IC728 = 1728;<br />
WT_RADIO_IC729 = 1729;<br />
WT_RADIO_IC735 = 1735;<br />
WT_RADIO_IC736 = 1736;<br />
WT_RADIO_IC738 = 1738;<br />
WT_RADIO_IC737 = 1737;<br />
WT_RADIO_IC746 = 1746;<br />
WT_RADIO_IC746Pro = 17761;<br />
WT_RADIO_IC751 = 1751;<br />
WT_RADIO_IC756 = 1756;<br />
WT_RADIO_IC756Pro = 17561;<br />
WT_RADIO_IC756ProII = 17562;<br />
WT_RADIO_IC756ProIII = 17563;<br />
WT_RADIO_IC761 = 1761;<br />
WT_RADIO_IC765 = 1765;<br />
WT_RADIO_IC775 = 1775;<br />
WT_RADIO_IC781 = 1781;<br />
WT_RADIO_IC275 = 1275;<br />
WT_RADIO_IC475 = 1475;<br />
WT_RADIO_IC1275 = 11275;<br />
WT_RADIO_IC910 = 1910;<br />
WT_RADIO_IC7000 = 17000;<br />
WT_RADIO_IC7600 = 17600;<br />
WT_RADIO_IC7700 = 17700;<br />
WT_RADIO_IC7800 = 17800;<br />
WT_RADIO_ICGENERIC = 1000;<br />
WT_RADIO_FT1000MP = 2110;<br />
WT_RADIO_FT1000 = 2100;<br />
WT_RADIO_FT2000 = 2200;<br />
WT_RADIO_FT990 = 2099;<br />
WT_RADIO_FT920 = 2092;<br />
WT_RADIO_FT100 = 2010;<br />
WT_RADIO_FT847 = 20847;<br />
WT_RADIO_FT900 = 2090;<br />
WT_RADIO_FT897 = 20897;<br />
WT_RADIO_FT817 = 20817;<br />
WT_RADIO_FT857 = 20857;<br />
WT_RADIO_FT757GXII = 207572;<br />
WT_RADIO_FTDX9000 = 2900;<br />
WT_RADIO_FT450 = 2450;<br />
WT_RADIO_FT950 = 2950;<br />
WT_RADIO_ORION = 3000;<br />
WT_RADIO_OMNI6 = 3001;<br />
WT_RADIO_JUPITER = 3002;<br />
WT_RADIO_OMNI7 = 3003;<br />
WT_RADIO_ORION_II = 3004;<br />
WT_RADIO_SDR1000 = 4000;<br />
WT_RADIO_K2 = 5000;<br />
WT_RADIO_K3 = 5001;<br />
WT_RADIO_OMNIRIG = 6000;<br />
</pre><br />
<br />
====microHAM Device IDs====<br />
<pre><br />
WT_MICROHAM_NONE = 0;<br />
WT_MICROHAM_MK = 1;<br />
WT_MICROHAM_MKII = 2;<br />
WT_MICROHAM_MK2R = 10;<br />
WT_MICROHAM_MK2R_PLUS = 11;<br />
WT_MICROHAM_MICRO_2R = 12;<br />
</pre><br />
<br />
===Advanced Programming Examples===<br />
====ESM Script (embedded into Win-Test)====<br />
For convenience, you can find below the current ESM (Enter Sends Message) embedded script. Note that the real returned values are somewhat different from the ones described above, because of the nature of this script (embedded), but it is a good source of inspiration for your own masterpiece. As Lua is an interpreted language, the good news is that you can edit your script while WT is running. No need to exit WT, enter modifications, and start WT again. Just edit esm.wts while WT is running, save it, and try it immediately!<br />
<br />
The script assumes the following messages have been programmed into the [[Menu:Options#Modify_standard_messages...|Standard CW messages]] dialog:<br />
<br />
----<br />
'''F1''' => CQ<br><br />
'''F2''' => RST + Exchange<br><br />
'''F3''' => TU<br><br />
'''F4''' => $MYCALL<br><br />
'''F5''' => $LOGGED<br><br />
'''F7''' => ? or Again (Phone)<br><br />
'''INSERT''' => Sends exchange (CW and RTTY)<br><br />
'''PLUS''' => TU and Log the QSO<br><br />
----<br />
<br />
Here is the source code for '''esm.wts'''. To change the behavior, save it in the Win-Test scripts directory (File | Explore | /scripts directory), then edit it.<br />
<br />
<code><br />
-- v1.2 All variables in messages replaced by keypresses<br />
-- v1.1 Dupes taken into account in the S&P mode<br />
-- v1.0 Initial version<br />
<br />
-- Send functions<br />
<br />
function sendCq()<br />
wtQso:ResetExchangeSent();<br />
wtApp:SendFKey("F1"); -- Always use the function key<br />
end;<br />
<br />
function sendExchangeRun()<br />
wtApp:SendFKey(wtQso:IsModePhone() and "F2" or "INSERT"); -- Ternary Operator<br />
wtQso:SetExchangeSent();<br />
end;<br />
<br />
function sendExchangeAgain()<br />
if (wtQso:IsModePhone()) then<br />
wtApp:SendFKey("F2");<br />
else<br />
wtApp:SendFKey("F5"); -- $LOGGED<br />
wtApp:SendFKey("F7"); -- ?<br />
end;<br />
end;<br />
<br />
function sendTu()<br />
wtApp:SendFKey("PLUS");<br />
wtQso:ClearStatus();<br />
end;<br />
<br />
function sendQuestionMark()<br />
wtQso:ResetExchangeSent();<br />
wtApp:SendFKey("F7"); -- Again ?<br />
end;<br />
<br />
function sendMyCall()<br />
wtApp:SendFKey("F4"); -- My call<br />
end;<br />
<br />
function sendExchangeSAndP()<br />
wtApp:SendFKey("F2");<br />
wtQso:SetExchangeSent();<br />
end;<br />
<br />
<br />
-- ESM core code<br />
<br />
-- Return 0 (or return nothing) if we want the CR<br />
-- to be processed also by WT (ie log QSO) and -1 if not.<br />
<br />
if (wtQso:IsOperatingModeRun()) then -- Run<br />
if (wtContest:IsExchangeRequired()) then -- Usual contests<br />
if (wtQso:IsExchangeEmpty() or not wtQso:IsQsoApproved()) then<br />
if (wtQso:IsCallsignEmpty()) then<br />
sendCq();<br />
else<br />
if (wtQso:IsCallsignRepeated()) then<br />
sendExchangeAgain();<br />
else<br />
sendExchangeRun();<br />
end;<br />
end;<br />
else<br />
if (wtQso:IsExchangeSent()) then<br />
sendTu()<br />
else<br />
sendExchangeRun();<br />
end;<br />
end;<br />
else -- DXPed etc.<br />
if (not wtQso:IsQsoApproved()) then<br />
if (wtQso:IsCallsignEmpty()) then<br />
sendCq();<br />
else<br />
if (wtQso:IsCallsignRepeated()) then<br />
sendExchangeAgain();<br />
else<br />
sendExchangeRun();<br />
end;<br />
end;<br />
else<br />
if (wtQso:IsExchangeSent()) then<br />
sendTu();<br />
else<br />
sendExchangeRun();<br />
end;<br />
end;<br />
end;<br />
else -- S&P : The automatic exchange fill (if enabled) is disabled by WT<br />
if ( (wtQso:IsExchangeEmpty() and wtContest:IsExchangeRequired())<br />
or not wtQso:IsQsoApproved() ) then<br />
if (wtQso:IsCallsignEmpty()) then<br />
sendQuestionMark();<br />
else<br />
if (not wtQso:IsDupe()) then -- Call only if not dupe<br />
sendMyCall();<br />
end;<br />
end;<br />
else<br />
if (wtQso:IsExchangeSent()) then<br />
wtQso:ClearStatus();<br />
return 0; -- Log it silently<br />
else<br />
if (not wtQso:IsDupe()) then -- Sent exchange only if not dupe<br />
sendExchangeSAndP();<br />
end;<br />
end;<br />
end;<br />
end;<br />
<br />
return -1; -- This script overrides the Win-Test CR process<br />
</code><br />
<br />
====Alternative ESM Script (provided by F5VIH/SV3SJ)====<br />
<br />
At the top of the script you will find a variable setting:<br />
<br />
shortcq = false;<br />
<br />
Setting it to true, it will convert the CQ calling and the TU part of the QSO in short forms (a la 5b4agn) and the exact contents of the messages are defined in the two lines that follow the shortcq setting. I have also added the possibility to have an exchange filled in and no call (in that case the script sends CL?)<br />
<br />
I must say I am very impressed by the functionality that WT opens to the users with lua scripts. I would really like to see more API calls made available and WT functions using scripts (programmable keys, even SO2R, etc).<br />
<br />
In the mean time if you have suggestions to improve the script let me know. I can easily inlcude them.<br />
<br />
<pre><br />
----------------------------------- <br />
-- Wintest ESM - Nick, F5VIH/SV3SJ<br />
-- Set "shortCQ to true or false<br />
-----------------------------------<br />
<br />
shortcq = false;<br />
shortCQ = "$MYCALL";<br />
shortTU = "$CORRECT ++TU-- $CR";<br />
<br />
-- Send functions<br />
<br />
function sendCq()<br />
wtQso:ResetExchangeSent();<br />
if (wtQso:IsModePhone()) then<br />
wtApp:SendFKey("F1");<br />
else<br />
if (shortcq) then<br />
wtKeyer:Play(shortCQ);<br />
else<br />
wtApp:SendFKey("F1"); -- Always use the function key<br />
end;<br />
end;<br />
end;<br />
function sendExchangeRun()<br />
if (wtQso:IsModePhone()) then<br />
wtApp:SendFKey("F2");<br />
wtKeyer:Play("$CR");<br />
else<br />
wtKeyer:Play("$INSERT");<br />
end;<br />
wtQso:SetExchangeSent();<br />
end;<br />
<br />
function sendExchangeAgain()<br />
if (wtQso:IsModePhone()) then<br />
wtApp:SendFKey("F2");<br />
else<br />
wtKeyer:Play("$F5 $F7"); -- $LOGGED ?<br />
end;<br />
end;<br />
<br />
function sendTu()<br />
if (wtQso:IsModePhone()) then<br />
if (shortcq) then<br />
wtKeyer:Play("$CR");<br />
wtApp:SendFKey("F5");<br />
else<br />
wtApp:SendFKey("PLUS");<br />
end;<br />
else<br />
if (shortcq) then<br />
wtKeyer:Play(shortTU);<br />
else<br />
wtKeyer:Play("$PLUS");<br />
end;<br />
end;<br />
wtQso:ClearStatus();<br />
end;<br />
<br />
function sendQuestionMark()<br />
wtQso:ResetExchangeSent();<br />
if (wtQso:IsModePhone()) then<br />
wtApp:SendFKey("F7"); -- Again ?<br />
else<br />
wtKeyer:Play("$F7");<br />
end;<br />
end;<br />
<br />
function sendMyCall()<br />
if (wtQso:IsModePhone()) then<br />
wtApp:SendFKey("F4"); -- My call<br />
else<br />
wtKeyer:Play("$F4");<br />
end;<br />
end;<br />
<br />
function sendExchangeSAndP() -- Sends appropriate exchange when in S&P mode<br />
if (wtQso:IsModePhone()) then<br />
wtApp:SendFKey("F2"); -- 5NN EXCHANGE<br />
else<br />
wtKeyer:Play("$F2");<br />
end;<br />
wtQso:SetExchangeSent();<br />
end;<br />
<br />
function sendAskForCall()<br />
if (wtQso:IsModePhone()) then<br />
wtApp:SendFKey("F7"); -- AGN<br />
else<br />
wtKeyer:Play("CL?");<br />
end;<br />
end;<br />
<br />
function askForNumber()<br />
if (wtQso:IsModePhone()) then<br />
wtApp:SendFKey("F6"); -- NR AGN<br />
else<br />
wtKeyer:Play("$F6");<br />
end;<br />
end;<br />
<br />
function askWithPartialCall()<br />
if (wtQso:IsModePhone()) then<br />
wtApp:SendFKey("F7"); -- AGN<br />
else<br />
wtKeyer:Play("$F5 ?");<br />
end;<br />
end;<br />
<br />
-- ESM core code<br />
<br />
-- Return 0 (or return nothing) if we want the CR<br />
-- to be processed also by WT (ie log QSO) and -1 if not.<br />
<br />
if (wtQso:IsOperatingModeRun()) then -- Run Mode<br />
if (wtContest:IsExchangeRequired()) then -- Usual contests requiring an exchange<br />
if (wtQso:IsCallsignEmpty()) then<br />
if (wtQso:IsExchangeEmpty()) then<br />
sendCq();<br />
else -- we ve got an exchange but not a call, ask for the call<br />
sendAskForCall();<br />
end;<br />
else -- call is not empty<br />
if (wtQso:IsExchangeSent()) then -- we have sent the exchage<br />
if (not wtQso:IsQsoApproved()) then<br />
if (wtQso:IsCurrentFieldCallsign() and not wtQso:IsExchangeEmpty()) then<br />
askWithPartialCall();<br />
end;<br />
if (wtQso:IsCurrentFieldCallsign() and wtQso:IsExchangeEmpty()) then<br />
wtQso:ResetExchangeSent();<br />
sendExchangeRun();<br />
if (wtQso:IsCurrentFieldCallsign()) then wtKeyer:Play("$SPACEBAR") end;<br />
end;<br />
if (wtQso:IsCurrentFieldExchange() and wtQso:IsExchangeEmpty()) then<br />
askForNumber();<br />
end;<br />
else -- qso has valid call and exchange<br />
if (wtQso:IsCurrentFieldExchange()) then<br />
sendTu();<br />
else -- current field is not exchange (should be callsign)<br />
if (wtQso:IsCurrentFieldCallsign()) then<br />
wtQso:ResetExchangeSent();<br />
sendExchangeRun();<br />
if (wtQso:IsCurrentFieldCallsign()) then wtKeyer:Play("$SPACEBAR") end;<br />
end;<br />
end;<br />
end;<br />
<br />
else -- have not sent exchange and we are in the call field<br />
sendExchangeRun();<br />
if (wtQso:IsCurrentFieldCallsign()) then wtKeyer:Play("$SPACEBAR") end;<br />
end;<br />
end;<br />
<br />
else -- The contest doesnt require an exchange to be received e.g. DXPed etc.<br />
if (not wtQso:IsQsoApproved()) then<br />
if (wtQso:IsCallsignEmpty()) then<br />
sendCq();<br />
else<br />
if (wtQso:IsCallsignRepeated()) then<br />
sendExchangeAgain();<br />
else<br />
sendExchangeRun();<br />
end;<br />
end;<br />
else<br />
if (wtQso:IsExchangeSent()) then<br />
sendTu();<br />
else<br />
sendExchangeRun();<br />
end;<br />
end;<br />
end;<br />
<br />
else -- S&P : The automatic exchange fill (if enabled) is disabled by WT<br />
if ( (wtQso:IsExchangeEmpty() and wtContest:IsExchangeRequired()) or not wtQso:IsQsoApproved() ) then<br />
if (wtQso:IsCallsignEmpty()) then<br />
sendQuestionMark();<br />
else<br />
if (not wtQso:IsDupe()) then -- Call only if not dupe<br />
sendMyCall();<br />
end;<br />
end;<br />
else<br />
if (wtQso:IsExchangeSent()) then<br />
wtQso:ClearStatus();<br />
wtKeyer:Play("$CR");<br />
return -1; -- Log it silently<br />
else<br />
if (not wtQso:IsDupe()) then -- Sent exchange only if not dupe<br />
sendExchangeSAndP();<br />
end;<br />
end;<br />
end;<br />
end;<br />
<br />
return -1; -- This script overrides the Win-Test CR process<br />
</pre><br />
<br />
====Grab next call from partner window====<br />
The following script was kindly provided by Hank Lonberg, KR7X. It remaps the '''<tt>[~]</tt>''' key to grab the next callsign from the partner window and send an exchange.<br />
<br />
<pre><br />
wtKeyer:Play("$CORRECT TU $CR NOW $GRABPARTNER $NEXT $GUESSEXCH $F2 $13");<br />
</pre><br />
<br />
====Re-map [Ä] key with /P for Field Day====<br />
Practical in Field Day where a lot of stations are signing "/P" - especially with a German keyboard layout. <br />
<br />
<pre><br />
-- add /P to a callsign for Field Day operations<br />
wtApp:SendKeyCode(47);<br />
wtApp:SendKeyCode(112);<br />
</pre><br />
<br />
====Change background of Main Window depening on RUN/S&P Mode====<br />
The idea to this script was provided by GW3NJW. Name this script '''<tt>RunSPSwitch.wts</tt>''' and have it assigned to '''<tt>Ctrl-Tab</tt>'''<br />
<br />
<pre><br />
if (wtApp:IsPostKeyProcess()) then<br />
if (wtQso:IsOperatingModeRun()) then<br />
wtApp:SetWindowColor(-1, 0, 165, 165);<br />
else<br />
wtApp:SetWindowColor(-1, 128,128,128);<br />
end;<br />
else<br />
return 1; -- Triggers a post key process call<br />
end;<br />
</pre></div>N6TVhttps://docs.win-test.com/w/index.php?title=FAQ:Problems_Registering_and_Running&diff=4535FAQ:Problems Registering and Running2015-03-11T20:56:03Z<p>N6TV: /* Win-Test still comes up in "Demo" mode */ Correct punctuation.</p>
<hr />
<div>==How do I download, install, register and configure Win-Test on a new computer?==<br />
Click one of the following links to view or download the step-by-step illustrated '''Win-Test Installation, Registration and Configuration Guide''' (in PDF format) from http://download.win-test.com/registration/ :<br />
* [http://download.win-test.com/registration/wtreg_en.pdf wtreg_en.pdf] - English version by N6TV ([http://bit.ly/registerwt alternate server])<br />
* [http://download.win-test.com/registration/wtreg_fr.pdf wtreg_fr.pdf] - French version by F6FVY ([http://bit.ly/registerwt_f alternate version by XE1AY])<br />
* [http://download.win-test.com/registration/wtreg_es.pdf wtreg_es.pdf] - Spanish translation by LU5VV ([http://bit.ly/registerwt_ea alternate server]) <br />
* [http://download.win-test.com/registration/wtreg_it.pdf wtreg_it.pdf] - Italian translation by IK2NCJ ([http://bit.ly/registerwt_it alternate server])<br />
* [http://download.win-test.com/registration/wtreg_de.pdf wtreg_de.pdf] - German translation by DL1ELY ([http://bit.ly/registerwt_dl alternate server])<br />
* [http://download.win-test.com/registration/wtreg_pt.pdf wtreg_pt.pdf] - Portuguese translation by CU3HY ([http://bit.ly/registerwt_ct alternate server])<br />
<br />
Volunteers are needed to translate the guide to other languages. Please [http://www.qrz.com/db/n6tv contact N6TV] for the PowerPoint source file.<br />
<br />
==I selected Help | Register Software, but don't see my Computer Code==<br />
Chances are you are running the free "demo" version of Win-Test 4. This version cannot be registered. Download and install the official version from [http://download.win-test.com/v4/bin The Official Version 4 Download Site] (password required).<br />
<br />
==When I attempt to download Win-Test 4 the web site asks for a login and password. What should I use?==<br />
Your '''login''' is usually your '''callsign'''.<br />
<br />
Both your '''login''' and '''password''' are located in the "Win-Test Upgrade" or "Win-Test Purchase" email that you should have received when you purchased or upgraded to Version 4 (including free automatic upgrades). Look for an email:<br />
From: '''robot@win-test.com''' <br />
Subject: '''Win-Test V4 Free Upgrade'''<br />
-or-<br />
Subject: '''Achat de Win-Test - Win-Test purchase'''<br />
or similar.<br />
<br />
If you can't find the email with your unique web site password, you will need to send an email to F5HRY or F6FVY including your:<br />
* Account Number<br />
* Callsign<br />
* Email address used at time of purchase/upgrade<br />
* Your new email address if any<br />
<br />
==I requested a new registration key but I never received an email with the key==<br />
First, check your "Spam" folder, if any. Look for an email:<br />
From: '''robot@win-test.com''' <br />
Subject: '''Code de validation de Win-Test - Win-Test registration key'''<br />
<br />
Next, please note that registration keys are sent to the '''email address you provided when you first purchased Win-Test'''. If you no longer have access to this email address, you will need to send an email to F5HRY or F6FVY including your:<br />
* Account Number<br />
* Callsign<br />
* Old email address<br />
* New email address<br />
<br />
==Win-Test always starts in "Demo" mode==<br />
Note: Unlike Win-Test Version 3, the [http://download.win-test.com/v4/demo/ free demo version] of Win-Test version 4, and the [http://download.win-test.com/v4/freeware/ free DXpedition version] cannot be registered or "activated"; the full version, which runs in demo mode until it registered via [[Menu:Help#Register_software| Help | Register Software]], is a different file. It must be downloaded from the [http://download.win-test.com/v4/bin password-protected download site] (see above if you don't have the password).<br />
<br />
Every PC has a unique 13-digit '''computer code''' (XXX-XXXX-XXXXXX) and every PC needs a unique 25-digit '''registration key''' (XXXXX-XXXXX-XXXXX-XXXXX-XXXXX).<br />
<br />
The registration keys for Win-Test Version 3 and Win-Test Version 4 are different. Even if you never purchased or installed Win-Test Version 4, you may have received a "free upgrade" email, especially if your purchased Win-Test Version 3 ''after'' '''June, 2008'''. If you received such an email, you are automatically going to receive only Version 4 registration keys when you request a key from the [http://www.win-test.com/rubrique.php3?id_rubrique=1870 Win-Test Registration Page]. Such keys ''do not work'' on Win-Test Version 3, though no error message is displayed. If you still require a Win-Test Version 3 registration key, you will need to request one by sending an email to F5HRY or F6FVY including your:<br />
* Account Number<br />
* Callsign<br />
* Computer Code<br />
Users who have not received a free upgrade to Version 4 and have not purchased an upgrade to Version 4 will still receive Version 3 registration keys from the web site.<br />
<br />
==My Virus scanner reports that Win-Test is a Virus!==<br />
This is probably a false alarm, especially if you downloaded and installed Win-Test from the [http://download.win-test.com Official Win-Test download site].<br />
<br />
Many virus scanners are especially prone to falsely reporting the "Artemis" or "Themida" virus in Win-Test Version 4, due to the way the executable is constructed.<br />
<br />
You can always upload '''wt.exe''' to [http://www.virustotal.com VirusTotal.com] to test it with multiple scanners. If less than 25% of the virus scanners report an issue, it is likely that Win-Test is ''not infected'', and you will need to add an "exception" to your antivirus software to allow Win-Test to run.</div>N6TVhttps://docs.win-test.com/w/index.php?title=Menu:Help&diff=4534Menu:Help2015-03-11T20:55:13Z<p>N6TV: /* Register software */ Added link to FAQ page and registration guides</p>
<hr />
<div>==Register software==<br />
<code>Help | Register Software...</code><br><br />
Please refer to the detailed Installation Guides in the [[FAQ:Problems_Registering_and_Running#How_do_I_download.2C_install.2C_register_and_configure_Win-Test_on_a_new_computer.3F|FAQ page]] for step-by-step instructions on how to use this dialog.<br />
<br />
Even with the trial or "demo" version, you can fully use Win-Test. There is only a time restriction that randomly shuts down Win-Test, and exported logs (Cabrillo, Reg1Test) are limited to 50 QSOs.<br />
<br />
To register Win-Test, after having purchased a licence, you just need to visit the Win-Test web pages and request a key code, by entering your customer account number and your system's Computer Code which is displayed in this dialog box.<br />
<br />
[[Image:HelpRegisterSoftware.gif|center|frame|Win-Test Registration Window]]<br />
<br />
A license key will be sent to you via email from the license robot. Just copy this key into the correct field and press OK. The limitations will then be disabled and when Win-Test starts up, you will no longer have to press keys 1, 2 or 3.<br />
<br />
==Use online documentation==<br />
<code>Help | Use online manual</code><br><br />
If this option is checked, Win-Test tries to access the reference manual on the web, instead of using the local copy that has been distributed with the installation file.<br />
<br />
==Reference manual==<br />
<code>Help | Reference Manual</code> or '''<tt>Alt-H</tt>'''<br />
<br><br />
Starts a browser and displays the reference manual.<br />
<br />
Sometimes, the documentation provided with newer releases of Win-Test are slightly outdated.<br />
To use the most current version of the manual, either select the "online" version as shown<br />
above or retrieve a copy of the static manual from http://docs.win-test.com/pdf/static/manual.zip<br />
and unpack it in the Win-Test/docs/en directory (rename or remove the original en-directory first).<br />
This will provide you with the most up-to-date documentaion.<br />
<br />
==Display text command tips for menu items==<br />
<code>Help | Display text commands tips for menu items</code><br />
<br><br />
This option lets you enable tool tips (small yellow pop-up help text) for menu items. This option is enabled by default. These tool tips display keyboard shortcuts or [[Text_commands|text commands]] for the functions selected. Text commands let you peform menu functions without having to use the mouse.<br />
<br />
==Win-Test Home Page==<br />
<code>Help | Win-Test Home Page</code><br />
<br><br />
Starts up the system Web browser and directs it to go directly to the Win-Test Home Page http://www.win-test.com.<br />
<br />
==Documentation Wiki Home Page==<br />
<code>Help | Documentation Wiki Home Page</code><br />
<br><br />
Starts up the system Web browser and directs it to go directly to the Win-Test Documentation Website (Wiki) http://docs.win-test.com.<br />
<br />
<br />
==About==<br />
<code>Help | About</code> <br><br />
Displays the Win-Test version used, and allows a direct access to the Win-Test web pages at [http://www.win-test.com www.win-test.com].<br />
<br />
[[Image:HelpAbout.PNG|center|frame|About Win-Test]]<br />
<br />
[[Menus|Back to Menus]]</div>N6TVhttps://docs.win-test.com/w/index.php?title=FAQ:Problems_Registering_and_Running&diff=4533FAQ:Problems Registering and Running2015-03-11T20:48:20Z<p>N6TV: /* I entered my registration key but Win-Test still comes up in "Demo" mode */ Clarify that full version can also run in demo mode</p>
<hr />
<div>==How do I download, install, register and configure Win-Test on a new computer?==<br />
Click one of the following links to view or download the step-by-step illustrated '''Win-Test Installation, Registration and Configuration Guide''' (in PDF format) from http://download.win-test.com/registration/ :<br />
* [http://download.win-test.com/registration/wtreg_en.pdf wtreg_en.pdf] - English version by N6TV ([http://bit.ly/registerwt alternate server])<br />
* [http://download.win-test.com/registration/wtreg_fr.pdf wtreg_fr.pdf] - French version by F6FVY ([http://bit.ly/registerwt_f alternate version by XE1AY])<br />
* [http://download.win-test.com/registration/wtreg_es.pdf wtreg_es.pdf] - Spanish translation by LU5VV ([http://bit.ly/registerwt_ea alternate server]) <br />
* [http://download.win-test.com/registration/wtreg_it.pdf wtreg_it.pdf] - Italian translation by IK2NCJ ([http://bit.ly/registerwt_it alternate server])<br />
* [http://download.win-test.com/registration/wtreg_de.pdf wtreg_de.pdf] - German translation by DL1ELY ([http://bit.ly/registerwt_dl alternate server])<br />
* [http://download.win-test.com/registration/wtreg_pt.pdf wtreg_pt.pdf] - Portuguese translation by CU3HY ([http://bit.ly/registerwt_ct alternate server])<br />
<br />
Volunteers are needed to translate the guide to other languages. Please [http://www.qrz.com/db/n6tv contact N6TV] for the PowerPoint source file.<br />
<br />
==I selected Help | Register Software, but don't see my Computer Code==<br />
Chances are you are running the free "demo" version of Win-Test 4. This version cannot be registered. Download and install the official version from [http://download.win-test.com/v4/bin The Official Version 4 Download Site] (password required).<br />
<br />
==When I attempt to download Win-Test 4 the web site asks for a login and password. What should I use?==<br />
Your '''login''' is usually your '''callsign'''.<br />
<br />
Both your '''login''' and '''password''' are located in the "Win-Test Upgrade" or "Win-Test Purchase" email that you should have received when you purchased or upgraded to Version 4 (including free automatic upgrades). Look for an email:<br />
From: '''robot@win-test.com''' <br />
Subject: '''Win-Test V4 Free Upgrade'''<br />
-or-<br />
Subject: '''Achat de Win-Test - Win-Test purchase'''<br />
or similar.<br />
<br />
If you can't find the email with your unique web site password, you will need to send an email to F5HRY or F6FVY including your:<br />
* Account Number<br />
* Callsign<br />
* Email address used at time of purchase/upgrade<br />
* Your new email address if any<br />
<br />
==I requested a new registration key but I never received an email with the key==<br />
First, check your "Spam" folder, if any. Look for an email:<br />
From: '''robot@win-test.com''' <br />
Subject: '''Code de validation de Win-Test - Win-Test registration key'''<br />
<br />
Next, please note that registration keys are sent to the '''email address you provided when you first purchased Win-Test'''. If you no longer have access to this email address, you will need to send an email to F5HRY or F6FVY including your:<br />
* Account Number<br />
* Callsign<br />
* Old email address<br />
* New email address<br />
<br />
==Win-Test still comes up in "Demo" mode==<br />
Note: Unlike Win-Test Version 3, the [http://download.win-test.com/v4/demo/ free demo version] of Win-Test version 4, and the [http://download.win-test.com/v4/freeware/ free DXpedition version] cannot be registered or "activated"; the full version, which runs in demo mode until registered, is a different file. It must be downloaded from the [http://download.win-test.com/v4/bin password-protected download site] (see above if you don't have the password).<br />
<br />
Every PC has a unique 13-digit '''computer code''' (XXX-XXXX-XXXXXX) and every PC needs a unique 25-digit '''registration key''' (XXXXX-XXXXX-XXXXX-XXXXX-XXXXX).<br />
<br />
The registration keys for Win-Test Version 3 and Win-Test Version 4 are different. Even if you never purchased or installed Win-Test Version 4, you may have received a "free upgrade" email, especially if your purchased Win-Test Version 3 ''after'' '''June, 2008'''. If you received such an email, you are automatically going to receive only Version 4 registration keys when you request a key from the [http://www.win-test.com/rubrique.php3?id_rubrique=1870 Win-Test Registration Page]. Such keys ''do not work'' on Win-Test Version 3, though no error message is displayed. If you still require a Win-Test Version 3 registration key, you will need to request one by sending an email to F5HRY or F6FVY including your:<br />
* Account Number<br />
* Callsign<br />
* Computer Code<br />
Users who have not received a free upgrade to Version 4 and have not purchased an upgrade to Version 4 will still receive Version 3 registration keys from the web site.<br />
<br />
==My Virus scanner reports that Win-Test is a Virus!==<br />
This is probably a false alarm, especially if you downloaded and installed Win-Test from the [http://download.win-test.com Official Win-Test download site].<br />
<br />
Many virus scanners are especially prone to falsely reporting the "Artemis" or "Themida" virus in Win-Test Version 4, due to the way the executable is constructed.<br />
<br />
You can always upload '''wt.exe''' to [http://www.virustotal.com VirusTotal.com] to test it with multiple scanners. If less than 25% of the virus scanners report an issue, it is likely that Win-Test is ''not infected'', and you will need to add an "exception" to your antivirus software to allow Win-Test to run.</div>N6TVhttps://docs.win-test.com/w/index.php?title=FAQ:Problems_Registering_and_Running&diff=4532FAQ:Problems Registering and Running2015-03-11T20:46:07Z<p>N6TV: /* I entered my registration key but Win-Test still comes up in "Demo" mode */ Added links explaining demo mode problems.</p>
<hr />
<div>==How do I download, install, register and configure Win-Test on a new computer?==<br />
Click one of the following links to view or download the step-by-step illustrated '''Win-Test Installation, Registration and Configuration Guide''' (in PDF format) from http://download.win-test.com/registration/ :<br />
* [http://download.win-test.com/registration/wtreg_en.pdf wtreg_en.pdf] - English version by N6TV ([http://bit.ly/registerwt alternate server])<br />
* [http://download.win-test.com/registration/wtreg_fr.pdf wtreg_fr.pdf] - French version by F6FVY ([http://bit.ly/registerwt_f alternate version by XE1AY])<br />
* [http://download.win-test.com/registration/wtreg_es.pdf wtreg_es.pdf] - Spanish translation by LU5VV ([http://bit.ly/registerwt_ea alternate server]) <br />
* [http://download.win-test.com/registration/wtreg_it.pdf wtreg_it.pdf] - Italian translation by IK2NCJ ([http://bit.ly/registerwt_it alternate server])<br />
* [http://download.win-test.com/registration/wtreg_de.pdf wtreg_de.pdf] - German translation by DL1ELY ([http://bit.ly/registerwt_dl alternate server])<br />
* [http://download.win-test.com/registration/wtreg_pt.pdf wtreg_pt.pdf] - Portuguese translation by CU3HY ([http://bit.ly/registerwt_ct alternate server])<br />
<br />
Volunteers are needed to translate the guide to other languages. Please [http://www.qrz.com/db/n6tv contact N6TV] for the PowerPoint source file.<br />
<br />
==I selected Help | Register Software, but don't see my Computer Code==<br />
Chances are you are running the free "demo" version of Win-Test 4. This version cannot be registered. Download and install the official version from [http://download.win-test.com/v4/bin The Official Version 4 Download Site] (password required).<br />
<br />
==When I attempt to download Win-Test 4 the web site asks for a login and password. What should I use?==<br />
Your '''login''' is usually your '''callsign'''.<br />
<br />
Both your '''login''' and '''password''' are located in the "Win-Test Upgrade" or "Win-Test Purchase" email that you should have received when you purchased or upgraded to Version 4 (including free automatic upgrades). Look for an email:<br />
From: '''robot@win-test.com''' <br />
Subject: '''Win-Test V4 Free Upgrade'''<br />
-or-<br />
Subject: '''Achat de Win-Test - Win-Test purchase'''<br />
or similar.<br />
<br />
If you can't find the email with your unique web site password, you will need to send an email to F5HRY or F6FVY including your:<br />
* Account Number<br />
* Callsign<br />
* Email address used at time of purchase/upgrade<br />
* Your new email address if any<br />
<br />
==I requested a new registration key but I never received an email with the key==<br />
First, check your "Spam" folder, if any. Look for an email:<br />
From: '''robot@win-test.com''' <br />
Subject: '''Code de validation de Win-Test - Win-Test registration key'''<br />
<br />
Next, please note that registration keys are sent to the '''email address you provided when you first purchased Win-Test'''. If you no longer have access to this email address, you will need to send an email to F5HRY or F6FVY including your:<br />
* Account Number<br />
* Callsign<br />
* Old email address<br />
* New email address<br />
<br />
==I entered my registration key but Win-Test still comes up in "Demo" mode==<br />
Note: Unlike Win-Test Version 3, the [http://download.win-test.com/v4/demo/ free demo version] of Win-Test version 4, and the [http://download.win-test.com/v4/freeware/ free DXpedition version] cannot be registered or "activated"; the full version which can be registered is a different file that must be downloaded from the [http://download.win-test.com/v4/bin password-protected download site] (see above if you don't have the password).<br />
<br />
Every PC has a unique 13-digit '''computer code''' (XXX-XXXX-XXXXXX) and every PC needs a unique 25-digit '''registration key''' (XXXXX-XXXXX-XXXXX-XXXXX-XXXXX).<br />
<br />
The registration keys for Win-Test Version 3 and Win-Test Version 4 are different. Even if you never purchased or installed Win-Test Version 4, you may have received a "free upgrade" email, especially if your purchased Win-Test Version 3 ''after'' '''June, 2008'''. If you received such an email, you are automatically going to receive only Version 4 registration keys when you request a key from the [http://www.win-test.com/rubrique.php3?id_rubrique=1870 Win-Test Registration Page]. Such keys ''do not work'' on Win-Test Version 3, though no error message is displayed. If you still require a Win-Test Version 3 registration key, you will need to request one by sending an email to F5HRY or F6FVY including your:<br />
* Account Number<br />
* Callsign<br />
* Computer Code<br />
Users who have not received a free upgrade to Version 4 and have not purchased an upgrade to Version 4 will still receive Version 3 registration keys from the web site.<br />
<br />
==My Virus scanner reports that Win-Test is a Virus!==<br />
This is probably a false alarm, especially if you downloaded and installed Win-Test from the [http://download.win-test.com Official Win-Test download site].<br />
<br />
Many virus scanners are especially prone to falsely reporting the "Artemis" or "Themida" virus in Win-Test Version 4, due to the way the executable is constructed.<br />
<br />
You can always upload '''wt.exe''' to [http://www.virustotal.com VirusTotal.com] to test it with multiple scanners. If less than 25% of the virus scanners report an issue, it is likely that Win-Test is ''not infected'', and you will need to add an "exception" to your antivirus software to allow Win-Test to run.</div>N6TVhttps://docs.win-test.com/w/index.php?title=Menu:Windows&diff=4531Menu:Windows2015-03-10T23:57:44Z<p>N6TV: /* DX-Cluster Announcements */ Change VFO a to VFO A</p>
<hr />
<div><big><big>Menu:Windows</big></big><br />
<!-- Adopted to Stylesheet DL6RAI --><br />
<br />
Most of the windows have a context or "pop-up" menu which can be opened by right-clicking on the window.<br />
<br />
All windows can be moved by "dragging" the title bar with the mouse pointer. Simply hold down the left mouse button while the cursor is over the title bar, and drag the window with the mouse. Another option is to hold down the '''<tt>Ctrl</tt>''' key and the left mouse button while the mouse pointer is positioned anywhere within a window (except for the RTTY reception windows), then drag.<br />
<br />
{{wbox|Tip|Hold down the '''<tt>Shift</tt>''' key while dragging or resizing a window to "snap" it into position, right next to the edge of an adjacent window.}}<br />
<br />
==Log Entry (Main window)==<br />
[[Image:LogEntryWindow.PNG|frame|center|The Win-Test main logging window.]]<br />
<br />
Use the Win-Test main window or "Log Entry" window to enter all QSOs made on the primary radio. The window displays the last nine QSOs in the log, plus a tenth line for entering the next QSO. The title bar displays the current log file name, the station name entered in the [[New_Log#Step_2:_Setup_your_log|Contest Configuration window]] (e.g. "[Shack]"), and the current operator's callsign (for multi-ops that use the '''<tt>OPON</tt>''' or '''<tt>LOGIN</tt>''' [[Text_commands#Multi_Operating|text commands]]). By default, the Win-Test main window serves as a background for all other windows, but you may also choose to have every window "float" independently (see [[Menu:Options#Windows]]). <br />
<br />
When you close the log entry window, Win-Test terminates.<br />
<br />
Any QSO may be edited simply by typing over anything that needs correction. Use the '''<tt>[Up arrow]</tt>''' and '''<tt>[Down arrow]</tt>''' keys to edit previous QSOs. To restore the original QSO data, press '''<tt>Ctrl-Z</tt>''' before moving the cursor from that line. You can also delete a QSO (if single-op), though it is usually better to just enter a duplicate QSO -- see [[Menu:Edit#Delete_QSO]] for more information.<br />
<br />
When the cursor is positioned in the callsign field, data is entered in "insert mode", that is, typing does not replace characters, it only inserts them. In all other fields, data is entered in "overtype mode". See [[FAQ:User_Interface#Can_I_use_.22Insert_Mode.22_in_a_serial_number_or_exchange_field.3F|this entry in the FAQ]] for the rationale.<br />
<br />
The '''<tt>[Spacebar]</tt>''' key is used to quickly move the cursor back and forth between the callsign field and the received exchange field, skipping over the RST columns.<br />
<br />
{{wbox|Tip|Enter a "?" character in the middle of a callsign or exchange as a placeholder for missing information, e.g. <code>F?MZN</code>. Then when you press '''<tt>[Spacebar]</tt>''', the cursor will jump directly to the "?" character, and you can overtype it with the missing data (even in the callsign field).}}<br />
<br />
The '''<tt>[Backspace]</tt>''', '''<tt>[Del]</tt>''', '''<tt>[Left arrow]</tt>''', '''<tt>[Right arrow]</tt>''', '''<tt>[Home]</tt>''', '''<tt>[End]</tt>''', '''<tt>[Ctrl][Left arrow]</tt>''' and '''<tt>[Ctrl][Right arrow]</tt>'''keys operate conventionally, within a single field; they do not move the cursor outside of the current field. <br />
<br />
The '''<tt>[Tab]</tt>''' key may be used to position the cursor under the RST sent column as well as callsign and exchange. The '''<tt>[>]</tt>''' and '''<tt>[<]</tt>''' keys work similarly, but they also allow you to move the cursor to the QSO time field for direct editing. You can also change the time, date, frequency, serial number sent and other fields of a QSO by positioning the cursor on any line and pressing '''<tt>[Alt-F]</tt>''' to display the [[Menu:Edit|Edit QSO pop-up menu]].<br />
<br />
You may scroll back through the entire log by pressing the '''<tt>[PageUp]</tt>''' and '''<tt>[PageDown]</tt>''' keys.<br />
<br />
{{wbox|Tip|Press '''<tt>Ctrl-[PageUp]</tt>''' to scroll back in the log by 24 hours.}}<br />
<br />
Enter a '''QSO number''' on the last line and press '''<tt>[Ctrl-g]</tt>''' to "Go to" that QSO number in the log. Press '''<tt>[Ctrl-g] [Enter]</tt>''' to return to the bottom of the log.<br />
<br />
Enter a callsign, prefix or '''beam heading''' (0 to 360°) on the last line and press '''<tt>[Ctrl]+[F12]</tt>''' to rotate to that heading. Press '''<tt>[Alt]+[F12]</tt>''' for long (or "alternate") path. For more information, see [[Rotators#Testing_the_configuration|Rotators]].<br />
<br />
Many other keys may be used in this window to assist with rapid data entry. For example, '''<tt>[F11]</tt>''' clears the entire QSO, whereas '''<tt>Ctrl-W</tt>''' clears only the current field. See [[Keys#Editing_and_moving_around_the_QSO_entry_line|Keys - Editing and moving around the QSO entry line]].<br />
<br />
The font size, background color, and header line attributes of this window may be adjusted by right clicking and selecting the '''Log''' option (see [[Menu:Options#Log]]). The yellow header text can be centered, left-justified, or completely hidden.<br />
<br />
The columns vary from contest to contest. In the CQ World-Wide example above,<br />
<br />
* '''QSO''' - raw QSO number. Can be hidden using [[Menu:Options#Hide_QSO_numbers|Hide QSO numbers]] (recommended for Multi-Multi contests with a sent serial number)<br />
* '''Bd''' - band. Can be changed with '''<tt>[Alt-F1]</tt>''', '''<tt>[Alt-F2]</tt>''', or '''<tt>[Alt-F]</tt>'''<br />
* '''Time''' - QSO time (UTC). Can be changed by moving the cursor with the '''<tt>[<]</tt>''' key, or '''<tt>[Alt-F]</tt>'''<br />
* '''Callsign''' - Callsign of station worked.<br />
{{wbox|Tip|Enter Win-Test [[Text_commands#List_of_Text_Commands|text commands]] (menu shortcuts) in the callsign field.}}<br />
* '''Sen/Rcvd''' - Sent and received exchanges<br />
* '''Mult''' - multipliers and other information:<br />
** '''C''' - Country multiplier<br />
** '''Z''' - Zone multiplier<br />
** '''DUPE''' - Duplicate contact<br />
** '''????''' - Multiplier in received exchange field not recognized (e.g. unrecognized state or section abbreviation, zone number out of range)<br />
** '''////''' - Unrecognized country prefix<br />
** '''!!!!''' - Multiplier violation (non-mult worked by a Mult station in a Multi-single, band change violation, etc.)<br />
** <i>other</i> - Prefix, country, state, grid, etc. multiplier<br />
* '''Pt''' - QSO points<br />
* '''Stn''' - Station identifier (can be changed by pressing '''<tt>Alt-Y</tt>''' - see [[Keys#Multi_Operator]])<br />
**'''R1/R2''' - Run 1 or Run 2 (multi-two), or Radio 1 / Radio 2 (SO2R).<br />
**'''R/M''' - Run or Mult (Multi-single)<br />
**'''+''' (suffix) - Indicates QSO data entered by a support or [[Menu:Windows#Partner|partner station]]<br />
<br />
Finally, a red information line at the bottom of the window displays additional information, such as<br />
* '''* New zone *'''<br />
* '''* New country *'''<br />
* '''* Dupe with #1963 at 23:59Z 2008-11-30 (25) * '''<br />
* '''* Spotted by F5MZN * '''<br />
* Brief one-line packet cluster announcements of new multipliers<br />
<br />
==Worked Gridsquares==<br />
<code>Windows | Worked Gridsquares</code> or '''<tt>Alt-L</tt>'''<br />
<br><br />
Opens (or closes) the gridsquares window. The gridsquares worked are in grey, the red spots are the stations worked and the green spots are the stations spotted. The current gridsquare is displayed in red color to give an indication of direction. This works even with only four of the six characters entered.<br />
<br />
[[Image:WindowsGridSquareMap1.gif|center|frame|Gridsquares Map]]<br />
<br />
If the [[Menu:Windows#DX-Cluster_Announcements|DX-Cluster Announcements]] window is opened and the gridsquare of a spot is known, passing the mouse over this spot will blink its location in this window.<br />
<br />
Right click on the map to display the pop-up window:<br />
<br />
[[Image:GridSquareMapPopUp.PNG|center|frame|Gridsquare map pop-up window displayed by right-clicking on the map]]<br />
<br />
* '''Copy the map''' copies the image to the Windows clipboard<br />
* '''Actualize Information''' controls when the map will be updated:<br />
** Pressing the spacebar <br />
** Automatically<br />
* '''Colorize worked gridsquares''' marks worked grid squares in gray<br />
* '''Show QSO''' marks QSOs with a red dot<br />
* '''Display the spots''' marks spotted stations with a green dot<br />
* '''Show gridsquares''' draws the squares and the grid square lines<br />
* '''Show fields only''' turns grid square outlines off<br />
* '''Show caption''' displays the major grid square names (first two letters)<br />
* '''Center map here''' lets you move the center of the map interactively. <br />
<br />
{{wbox|Note|This option is available only if you have '''not''' selected "Always center on the operating QTH" in the Properties dialog (see below).}}<br />
<br />
* '''Properties...''' allows you to modify several display parameters:<br />
<br />
[[Image:GridSquareMapProperties.PNG|center|frame|Gridsquares Map Properties]]<br />
<br />
The larger the scale, the bigger the map.<br />
<br />
==Worked Zones==<br />
<code>Windows | Worked Zones</code> or '''<tt>Alt-Z</tt>'''<br />
<br><br />
Opens (or closes) the worked zones window. The title of this menu item will fit to the chosen contest.<br />
The window displays the worked multipliers (in blue) or not (in white) on the current band, and possibly the current mode.<br />
<br />
Some examples:<br />
<br />
[[Image:WindowsZone1.gif|center|frame|Worked departements window (French REF HF contest)]]<br />
<br />
[[Image:WindowsZone3.gif|center|frame|Worked states and provinces window (International ARRL DX contest)]]<br />
<br />
Furthermore, with a right click on this window (if the contest is multi-bands and/or multi-modes) you can display the distribution of these multipliers by band (and/or mode).<br />
<br />
<br />
[[Image:WindowsZone2.gif|center|frame|WAZ zones worked window by band (CQWW DX contest)]]<br />
<br />
At last, the same contextual menu allows you to copy all the datas of this window into the clipboard as an image or a text, and directly paste it as a text file or an Excel (TM) or OpenOffice spreadsheet.<br />
<br />
==Worked DXCC==<br />
<code>Windows | Worked DXCC</code> or '''<tt>Alt-M</tt>'''<br />
<br><br />
Opens (or closes) the worked DXCC window. The title of this menu item will change with the contest chosen.<br />
<br />
[[Image:WindowsMult.gif|center|frame|Worked DXCC countries window]]<br />
<br />
If one DXCC country has been worked on a band (possibly a mode), this band will be displayed in blue, otherwise it remains in white. This window is resizable.<br />
<br />
A right click on this window allows to display the countries alphabetically sorted (within the same continent), or sorted by number of band/mode worked. More, to easily search for missing countries, the countries worked on all bands can be hidden (clean sweeps).<br />
<br />
You can easily move to the next (or previous) bookmark - displayed on a yellow background by default - by holding the '''<tt>Shift</tt>''' key down, while rolling your mouse wheel.<br />
<br />
Last, all the data included in this window can be copied as a text file, and pasted in text or directly in an Excel (TM) or OpenOffice spreadsheet, for a later analysis.<br />
<br />
==Check Callsign==<br />
<code>Windows | Check Callsign</code> or ['''<tt>F9</tt>''']<br />
<br><br />
Opens (or closes) the worked callsign window. This window displays a checkmark if and on which bands a specific callsign has been logged before. Depending on the type of the contest, the display may show more than one column to display the different possible modes.<br />
<br />
[[Image:WindowsCheckCallsign.gif|center|frame|The Check Callsign Window]]<br />
<br />
Moving the mouse cursor over the checkmark will bring up additional information about this QSO. And a double-click on it will move the cursor to this QSO.<br />
<br />
==Check Multipliers==<br />
<code>Windows | Check Multipliers</code> or ['''<tt>F10</tt>''']<br />
<br><br />
<br />
Opens (or closes) the checking multipliers window.<br />
<br />
[[Image:WindowsCheckCountry.PNG|center|frame|Check Multipliers window for the CQ World-Wide DX contest]]<br />
<br />
To use this window, enter a callsign or country prefix in the data entry area of the main logging window. The dark blue line indicates the current band. The other lines indicate whether this multiplier has been worked or not on other bands (and in other modes if the contest rules permit). If the callsign entered has been worked on other bands, Win-Test displays those QSOs. Otherwise, the callsign of the first station worked in that multiplier on that band is displayed, if any. For the CQ World-Wide DX contest, display priority is: same callsign, same country and same zone. An uppercase "Z" in the last column indicates that the zone and country have been worked on the indicated band. A lowercase "z" means the zone has been worked, but not the country. And of course a blank line indicates that both the zone and country are needed. See also the [[Menu:Windows#Search_for_Worked_Multipliers_or_Partial_QTH_Locators|Search for Worked Multipliers]] window.<br />
<br />
Additional information about the multiplier is displayed at the bottom:<br />
<br />
* The official country prefix and country name<br />
* A small icon indicating if it is local day, night, or sunrise/sunset time in that country<br />
* The current local time in that country (suffixed by a lowercase "l")<br />
* The short (Az) and long path (Lp) beam headings (azimuths) to this multiplier (based on the station locator entered in the [[New_Log#Step_2:_Setup_your_logcontest|Contest configuration screen]])<br />
* The sunrise (SR) and sunset (SS) time in this country, expressed as UTC (suffixed by a lowercase "z"). These times are computed from the geographical coordinates given taken from the CTY* file or your QTH locator, if specified in the setup dialog.<br />
* Graphical indication of the sun status on both sides of the QSO (may be disabled via the context menu)<br />
** Two yellow bars represent the sun over 24 hours of the day. The top bar displays the situation at the DX location, while the bottom bar represents your own location.<br />
** A pink cursor denotes current time. <br />
** Dotted lines represent local noon or local midnight. <br />
<br />
A double click on a line will move the cursor to the specified QSO. Press '''<tt>[Ctrl-End]</tt>''' or '''<tt>[Ctrl-G]</tt>''', '''<tt>[Enter]</tt>''' to return the cursor to the blank line at the end of the data entry area.<br />
<br />
Finally, using the context menu (right click on the window), you can change '''Actualize information''' to '''Automatically''' (recommended) or to '''Pressing the space bar''' to indicate when you want the check multiplier screen to be updated. "Automatically" updates the screen after each keystroke. Any modification in the received exchange field (e.g. zone) also updates this check multiplier window.<br />
<br />
==Search for Worked Multipliers or Partial QTH Locators==<br />
<code>Windows | Search for Worked Multipliers</code><br><br />
Keyboard shortcut: '''<tt>Shift+F10</tt>'''<br />
<br><br />
<br />
Lists all the callsigns logged in a specified multiplier (Zone, State, ARRL Section, Grid Square Locator, etc.).<br />
<br />
To quickly list everyone you have logged in a particular multiplier, sorted by band, enter the multiplier in the ''callsign'' field and press '''<tt>Shift+F10</tt>'''. The [[Menu:Windows#Check_Partials|Check Partial Window]] will be displayed in a different format, as shown below.<br />
<br />
[[Image:WindowsCheckMult1.gif|center|frame|Looking for a departement during the REF HF Contest]]<br />
<br />
[[Image:WindowsCheckMult2.gif|center|frame|Looking for a WAZ zone during the CQWW DX (Zone 40)]]<br />
<br />
[[Image:WindowsCheckMult3.gif|center|frame|Looking for an US state during the ARRL DX Contest (here: District of Columbia, DC)]]<br />
<br />
Any further typing in the callsign field restores the [[Menu:Windows#Check_Partials|Check Partial Window]] to its normal appearance. You can also use '''<tt>[Ctrl-W]</tt>''', '''<tt>[Alt-W]</tt>''', or '''<tt>[F11]</tt>''' to erase the multiplier from the callsign field.<br />
<br />
{{wbox|Note|This search only works for contests where the multiplier is logged as part of the exchange, so it doesn't work for the CQ WPX contest or the ARRL DX Contest (when operating from the U.S. and Canada).}}<br />
<br />
For VHF/UHF/SHF... contests, this function is dedicated to partial QTH locator search. Enter the partial QTH locator either in the callsign or in the locator field and then press '''<tt>Shift-F10</tt>'''.<br />
<br />
[[Image:WindowsCheckPartialQTHLocator.PNG|center|frame|Searching callsigns by QTH locator]]<br />
<br />
==Check Partials==<br />
<code>Windows | Check Partials</code> or ['''<tt>F12</tt>''']<br />
<br><br />
<br />
Opens (or closes) the Check Partials window. The master file used is normally MASTER.SCP or DEFAULT.SCP or ''contest''.DTB, as described under [[Check_Partial_and_Np1_Files|Check Partial and Np1 Files]].<br />
<br />
[[Image:WindowsCheckPartial.gif|center|frame|Checking partials. Partial callsign entered: A2Q]]<br />
<br />
If this window is open, and at least 3 characters are entered in the callsign logging field, Win-Test looks in the master database for the callsigns including the 3-character string.<br />
<br />
For example, in this upper screen-shot, the partial callsign entered is "A2Q". All the callsigns found by Win-Test show this string.<br />
<br />
The white callsigns are those not worked yet. The green callsigns are stations worked on another band, but not the current band. The red callsigns are the dupes (callsigns already worked on the current band).<br />
<br />
[[Image:WindowsCheckPartialOptions.gif|center|frame|Available context menu options in the Check Partial window]]<br />
<br />
Double clicking on a callsign copies it into the callsign logging field.<br />
<br />
Right click in the window to brings up a context menu where you can choose if Win-Test is to use the master database or just your log. Another option is (in some contests) if you want to see the expected report in that window (from ''contest''.DTB).<br />
<br />
For slow contests, it might make sense to start the check partial search after the second letter is entered into the callsign field, rather than the third. <br />
<br />
Another option allows you limit the number of callsigns displayed to fit the available space in the window.<br />
<br />
Finally, the option '''Used files list''' will display the master file that Win-Test has loaded to feed the Check Partials window:<br />
<br />
[[Image:Check Partial Files List.PNG|center|frame|Used files list selected from Check Partial window pop-up menu]].<br />
<br />
See [[Check_Partial_and_Np1_Files|Check Partial and Np1 Files]] for more info about naming super check files, search order, and how to update them.<br />
<br />
In HF contests such as CQ World-Wide, you can enter a zone number in the '''callsign''' field and press '''<tt>Shift+F10</tt>''' to display a list of prefixes in that zone, and a list of stations worked in that zone.<br />
<br />
[[Image:WindowsCheckPartialShiftF10.png|center|frame|Check partial window after entering 37 in the callsign field and pressing Shift+F10 to view countries in that zone. 5H3EE is in zone 37 and has been worked on 20m.]]<br />
<br />
In VHF/UHF contests, pressing '''<tt>Shift+F10</tt>''' on a partial QTH locator changes the Check Partials Window to the Partial QTH Locator Search Window. This feature is helpful to identify stations in a VHF/UHF contest when you copy only the QTH locator.<br />
<br />
[[Image:WindowsCheckPartialResult.png|center|frame|Check Partial QTH Locator window]]<br />
<br />
You may enter the partial QTH locator either in the callsign or in the QTH locator fields. A minimum of four characters has to be present in order to check the locator.<br />
<br />
==Check N + 1==<br />
<code>Windows | Check N + 1</code> or ['''<tt>F8</tt>''']<br />
<br><br />
<br />
Opens (or closes) the N + 1 window. The master file used is normally MASTER.SCP or DEFAULT.SCP or ''contest''.DTB, as described under [[Check_Partial_and_Np1_Files|Check Partial and Np1 Files]].<br />
<br />
If this window is open, and at least 3 characters are entered in the callsign logging field, Win-Test looks in the master database for the callsigns differing from the partial callsign by one character.<br />
<br />
This command also detects 2-character swap (dyslexia), as well as one missing character.<br />
<br />
[[Image:WindowsNp1_1.gif|center|frame|N + 1 window (Partial call entered: W5TQ)]]<br />
<br />
If the callsign is not included in the master database, and has not been worked yet, it is considered a UNIQUE. Otherwise, it is displayed in the first position.<br />
<br />
[[Image:WindowsNp1_2.gif|center|frame|N + 1 window (Partial call entered: K3OK)]]<br />
<br />
The white callsigns are the stations not yet worked. The green ones are those worked on another band, but not the current band. The red callsigns are dupes.<br />
<br />
[[Image:WindowsNp1_3.gif|center|frame|Available context menu options in the N+1 window]]<br />
<br />
Double clicking on a callsign copies it into the callsign logging field.<br />
<br />
A right click in the window brings up a context menu where you can choose to use the master database or just your log. A second option (in some contests) is if you want to see the expected report in that window (from ''contest''.DTB). You may also wish to limit the number of callsigns displayed to the available space in the N+1 window. Finally, the option "Used files list" will display the master file that Win-Test has loaded to feed the Check Partials window.<br />
<br />
==Partner==<br />
<code>Windows | Partner</code><br />
<br><br />
Opens (or closes) the partner window.<br />
<br />
[[Image:PartnerWindow.gif|right|frame|Partner window with two entries. You can now pull W6XR into the callsign field by pressing '''<tt>Alt-1</tt>''']] <br><p>This feature is especially useful in a Multi-OP environment when facing large pile-ups and/or weak signals or when you are training a new operator.</p><br />
<br />
Situation: You get several callers coming back to your CQ. You pull out one callsign - but sometimes you are able to copy another callsign or at least parts of it. If you could remember this second call after the first QSO, you'd be able to call the second station right away (without QRZ) and save time.<br />
<br />
Improvement: Set up a second operator (OP2), a second computer and a second pair of headphones, sometimes a second receiver. Both OPs now open up the Partner window on their computer. The running operator OP1 continues like before: He works the first callsign. In the mean time, the OP2 supports OP1 to copy the callsign - or alternatively - he can add callsigns he copied from the pile-up by entering the callsign on the QSO entry field and then pressing '''<tt>Alt-Enter</tt>'''.<br />
<br />
This callsign will now be displayed on all computers in the network that are set at the same band and mode. OP1 will see the new callsign after his first QSO and calls that station right away. <br />
<br />
The Partner window can hold up to 9 callsigns, and theses calls can be pulled into the callsign field with '''<tt>Alt-1</tt>''', '''<tt>Alt-2</tt>'''...'''<tt>Alt-9</tt>'''. Usually this is done by OP1 to log that callsign, while OP2 uses this function to remove the call from the partner window. Once the QSO is logged, that callsign will disappear from both partner windows.<br />
<br />
You can also swap the callsign field with one of the entries by pressing '''<tt>Ctrl-1</tt>''', '''<tt>Ctrl-2</tt>'''...'''<tt>Ctrl-9</tt>'''.<br />
<br />
Using message variables on CW and RTTY you can now enter a QSO (with correction or not), grab another callsign from the Partner window, and send the new report in one keystroke, by using:<br />
'''$CORRECT TU $CR NOW $GRABPARTNER $NEXT $F2''' (sends call if corrected before the TU)<br />
for the '''<tt>[Plus]</tt>''' key, or<br />
'''$CURRENT TU $CR NOW $GRABPARTNER $NEXT $F2''' (resends full call before the TU)<br />
assuming '''<tt>$F2</tt>''' contains the report.<br />
<br />
If you want to manually grab a callsign from the Partner window you can use:<br />
'''$PREV TU NOW $LOGGED $F2'''<br />
Then<br />
# Use the '''<tt>[Enter]</tt>''' key to silently enter the current QSO<br />
# Grab the next callsign from the Partner windownd (via double-click or Alt-''n'')<br />
# Send the message above<br />
<br />
[[Image:WindowsPartnerWindowRealtimefeature.PNG|left|frame|Partner Window in Real Time Mode]]<br />
<br><p>When a QSO is logged locally or via the network it is checked against the contents of the partner window, and - if found - removed from the partner window as it is now obsolete.</p><br />
<br />
If automatic exchange guessing is enabled, a callsign grabbed from the partner window will have the exchange window filled in and will update the check partials and N+1 windows.<br />
<br />
Finally, the entire Partner window content can be cleared by using the appropriate context menu item or by pressing '''<tt>Alt-Backspace</tt>'''. Individual entries can be removed via '''<tt>Ctrl-Doubleclick</tt>'''.<br />
<br />
Up to three support partners can be engaged. If you do not want the partner to be limited by band and mode, use the "No band/mode filtering" option in the context menu of the partner window. <br />
<br />
A '''real-time''' mode is available in the partner window's context menu. This allows the main operator to have a real-time view on what the partner(s) is(are) typing (character by character) so he(she) does not have to wait until they press '''<tt>Alt-Enter</tt>''' in this time-critical situation. For this to work, the supporting partner has to change his station type to "Support" (see section [[Menu:Commands#Station_Type]]), indicated by '''<tt>R+</tt>''' on the QSO entry line.<br />
<br />
In the context menu of the partner window there are two settings that can be done, when more then one partner (up to 3) is engaged:<br />
* as support, must be selected to which slot this partner will send its real-time characters<br />
* as runner, must be selected how many slot are being displayed at the partner window top<br />
<br />
The runner will then grab a real-time slot with '''<tt>Alt-Space</tt>''', or in all cases, he can also double-click on any callsign of this window.<br />
<br />
==Status==<br />
<code>Windows | Status</code> or '''<tt>Alt-J</tt>'''<br />
<br><br />
Opens (or closes) the status window.<br />
<br />
[[Image:StatusWindow.gif|center|frame|Status Window]]<br />
<br />
This window indicates the status of each station connected to the network. From left to right, are displayed :<br />
<br />
* Station name<br />
* Current band and mode<br />
* Station type<br />
* QSY frequency of the current band and mode<br />
* Radio 1 frequency<br />
* Radio 2 frequency<br />
* Time left before a possible QSY, according to the 10 minutes M/S rule, or "OK" if the station is allowed to make a QSY on another band. Note that this column only appears if the contest specifies this particular rule.<br />
<br />
Your own station is displayed in a deep blue background. The active radio of each station has its frequency in red characters.<br />
The list may be by band and station names when it gets cluttered in a very large network by using the appropriate function in the context menu.<br />
<br />
A double left click on a station name will display the chat dialog with this station name as default destination.<br />
<br />
Opening the context menu with a right mouseclick will allow you to turn on network traffic logging. This might be useful for basic network troubleshooting. This log file uses the .ntk (stands for NeTworK) file extension.<br />
<br />
At last, a double left click on any frequency displayed will tune the current radio to that frequency.<br />
<br />
==Skeds==<br />
<code>Windows | Skeds</code> or '''<tt>Alt-B</tt>'''<br />
<br><br />
Opens (or closes) the skeds window.<br />
<br />
[[Image:WindowsSked.gif|center|frame|Skeds Window]]<br />
<br />
Skeds (Alt-E) and passed stations (Alt-D) are displayed in this window. See [[Multi-op/Passing]].<br />
<br />
* A grey background means that the sked is over for more than 10 minutes.<br />
* A yellow background means that the sked is planned within less than 10 minutes maximum (a "hot sked"). If the window was not open, it will pop-up to remind the operator of the hot sked. The pop-up will be suppressed, however, if Win-Test is running minimized.<br />
* A green background means that the sked is planned in more than 10 minutes.<br />
<br />
A - (minus) sign before the hour means that the sked is over for more than 24 hours. A + (plus) sign before the hour means that the sked is planned in more than 24 hours.<br />
<br />
A right click allows to sort the skeds window by time or by band. You can also hide the older skeds, and modify or cancel a sked. In a multi operating configuration, the sked data are sent across the network.<br />
<br />
At last, note that a double left click will tune the current radio on the sked frequency and capture the callsign of the scheduled station in the callsign logging field. You will thus just need to press ['''<tt>Return</tt>'''] after completing the QSO!<br />
<br />
==Solar Activity==<br />
<code>Windows | Solar Activity</code><br />
<br><br />
<br />
This option displays solar activity data that has been received from the DX cluster connection. You can chose between SSN, SFI, K and A indexes. It is an interesting tool to discover trends in propagation during a contest.<br />
<br />
<center><br />
{|<br />
|[[Image:WindowsSolarActivityWWV.png|center|frame|Solar Activity Window (WWV data)]]<br />
|[[Image:WindowsSolarActivityWCY.png|center|frame|Solar Activity Window (from DK0WCY)]]<br />
|}<br />
</center><br />
<br />
As there are two sources on the DX cluster for this kind of information, you may chose between WWV and WCY.<br />
This information can also be applied - in conjunction with HamCap - for specific propagation forecasts.<br />
See [[Menu:Options#HamCAP | Menu Options HamCAP]] in this manual.<br />
<br />
Click on the triangles to open or close a chart. You may open or close all charts at once by holding the ['''<tt>Shift</tt>'''] key down while clicking on one of the triangles.<br />
<br />
==QSY Wizard==<br />
<code>Windows | QSY Wizard</code><br />
<br />
The QSY Wizard can only be used if [[HamCAP]] is installed and running. You must also have [[Menu:Options#HamCAP| Options | HamCAP | Tab]] set to '''Charts'''.<br />
<br />
After working a DX, pressing '''<tt>Ctrl-P</tt>''' will bring up the HamCAP window with a propagation prediction to this DX. Then, the QSY Wizard will display the bands on which to which a QSY or sked may be useful:<br />
<center><br />
{|<br />
|[[Image:WindowsQsyWizard.png|center|frame|QSY Wizard]]<br />
|[[Image:HamCAPprediction.png|center|frame|HamCAP prediction to CN2R]]<br />
|}<br />
</center><br />
In the above example CN2R has been worked on 20m. After pressing '''<tt>Ctrl-P</tt>''' the wizard tells us that a QSY may be promising to 15, 40, 80 and 160m. For 10m, however, the wizard recommends a sked at 18:30 UT instead. This is the peak time predicted by HamCap for this path but MUF will be only be 20.1 MHz (the mouse cursor was over the 18:30/28MHz yellow square while creating this screenshot).<br />
<br />
==Extra Information==<br />
This window displays data included in .XDT (eXtra DaTa) files. These files are textual and have a very basic syntax. These files are suitable for name lists (your favorite contest friends or club members, whose names you never get to remember in the middle of the contest) or information about a station's capabilities on other VHF/UHF/SHF bands so that you will want to ask for a sked.<br />
<br />
[[Image:WindowsExtraDataFiles.png|center|frame|The Extra Data Files Window can be used to display additional useful information during the contest.]]<br />
<br />
===XDT Files===<br />
The first column is the callsign of the station for which information is to be displayed. The rest of the line carries the information to display. There can be only one line per callsign. Lines have to be formatted in MS-DOS mode, i.e. CR/LF at the end.<br />
<br />
You can set up to 10 default extra data files by the menu function '''<code>Options | Data files | Default data files</code>'''. These files will be opened with every log. They must be located in the WT installation directory. Refer to [[Menu:Options#Default_extra_data_files... | Menu: Options Default extra data files...]] for detailed information.<br />
<br />
You can also add '''log-specific''' extra data files by using the '''<tt>Extra files...</tt>''' item in the context menu of this window (right-click to open the contextual menu). A new window will open-up where you can click the ADD button to browse the computer resources to locate and select the file you need (see picture).<br />
<br />
[[Image:LogSpecificExtraDataFiles.png|center|frame|Click the ADD button to locate and select the file you need]]<br />
<br />
There is no limitation to the location and the number of these log-specific files. The added file names and paths will then be save in a file with '''<tt>.xdl</tt>''' extension among all the other contest specific files (.LOG, .SUM, .pkt, .gab, .wtb, etc.).<br />
<br />
<br />
If you modify an '''<tt>.XDT</tt>''' file while it is in use, you must reload it by using the '''<tt>Reload files</tt>''' item in the context menu.<br />
<br />
{{wbox|Note|This function is designed to work with no more than a few thousand callsigns only. Don't try it with millions of lines or a Callbook file!}}<br />
<br />
===Directives===<br />
Directives are special statements in the data file beginning with a hash sign and a space.<br />
<br />
The <code># TITLE</code> directive is used to display a title in the window, like this:<br />
<pre><br />
# TITLE Operator Names<br />
CT1BOH Jose<br />
DJ1YFK Fab<br />
DL4NER Werner<br />
DL6RAI Ben<br />
F5HRY Herve<br />
F5MZN Olivier<br />
F6FVY Larry<br />
M0CLW Simon<br />
M3PHP Peter<br />
</pre><br />
<br />
The <code># VARIABLE</code> directive allows you to send the extra information in a CW message by using a variable name. The variable name '''must''' begin with the $ character.<br />
<br />
Example: The following line will substitute the $OPNAME string in the CW messages with the extra info included in this file, if the sent callsign has matching data.<br />
<br />
<pre><br />
# VARIABLE $OPNAME <br />
</pre><br />
<br />
<br />
{{wbox|Note|The variable subsitution only works with the internal CW keyer.}}<br />
<br />
==Summary==<br />
<code>Windows | Summary</code> or '''<tt>Alt-S</tt>'''<br />
<br><br />
Opens (or closes) the scoring summary window.<br />
<br />
[[Image:WindowsSummary.gif|center|frame|Summary]]<br />
<br />
The displayed number of QSO does not include the dupes. Thus, the QSO column displays only the QSO that have generated points.<br />
<br />
A right click allows to copy the scoring summary data in the clipboard as an image or as a text file (in WT language or in English, depending on the contest).<br />
<br />
[[Image:LiveScoreBroadcasting.gif|center|frame|Enabling Live Score Broadcasting through the context menu]]<br />
<br />
The context menu also allows you to configure and enable live score reporting by using a specific UDP broadcast protocol [http://download.win-test.com/utils/SummaryBroadcastingSpecs.txt]. Please note that additional third-party software is<br />
needed to post your score to one of the live scoreboards on the internet.<br />
<br />
For testing purposes, there is an option to create a live score broadcast "now"; typically, it will be broadcasted automatically once every five minutes or however you set up the periodicity. Live score broadcasting in a multi operator environment is limited to the station that is the network time master. For further information about live scores, please see [http://www.w1ve.com/livescores] and [http://www.5b4wn.com/main/index.php?m=10].<br />
<br />
==Rate==<br />
<code>Windows | Rate</code> or '''<tt>Alt-R</tt>'''<br />
<br><br />
Opens (or closes) the rate window.<br />
<br />
[[Image:WindowsRate.PNG|center|frame|Rate Window]]<br />
<br />
This window is divided in different parts:<br />
<br />
The upper part displays the rate of the last hour, of the last 10 QSO, and of the last 100 QSO. It also displays a moving graph of the rate, computed on the last 15 minutes before the current QSO. The lower portion of that window displays additional rate information in text format.<br />
<br />
===Graphs===<br />
The graph is calculated on the last 15 minutes (default). Each bar, thus representing one minute on the air, calculates the moving average rate on the last X minutes, this time being selectable between 5 to 30 minutes. A short period will be selected for a contest with high rates (international HF, such as CQWW or WPX), and a longer one for a contest with slower rates (such as a national HF, or a VHF).<br />
<br />
Below is a display that shows instant continent distribution of previous QSOs. It uses the same timing parameters as the instant rates above.<br />
<br />
The QSO Timer Alarm progress bar appears below that. This bar gives a clear visual indication of the time elapsed since your last QSO. Right click and select '''Off-time timer alarm''' to set the full scale range of the progress bar. In the screen shot above, it is the red bar showing over 100H elapsed since the last QSO, but normally it is a green progress bar that advances from left to right. It begins as 100% green and slowly more of it turns red until it reaches full scale, when the bar becomes 100% red. The default scale is 5 minutes, but it is configurable between 1 and 120 minutes.<br />
<br />
===Text Information===<br />
The next part displays information about Time ON and Time OFF. For new logs, the off-time calculation is based on the contest rules. You can still use a custom setting to check your operating efficiency. Right click and select '''Off-time calculation threshold'''. If the contest rule is unknown, 15 minutes will be used as a default threshold. <br />
<br />
The next part shows information about band changes.<br />
<br />
The central part gives general information about the point statistics of the contest, e.g. time by mult, QSO counts, Mult worth, etc. <br />
<br />
The bottom part indicates the current mode and, in CW, the current speed, as well as the status of the automated CQ repeat mode.<br />
Some indicators that may appear there include:<br />
* '''CW''' - Operating mode is set to CW (press '''<tt>Ctrl-F1</tt>''' or '''<tt>Ctrl-F2</tt>''' to change)<br />
* '''SSB''' - Operating mode is set to Phone<br />
* '''RTTY''' - Operating mode is set to RTTY<br />
* '''34 WPM''' - CW speed in Words Per Minute (adjust with '''<tt>Alt-F9</tt>''', '''<tt>Alt-F10</tt>''', and '''<tt>Alt-V</tt>''')<br />
* '''34/32 WPM''' - Independent CW speed between Win-Test and WinKey pot (WinKey speed displayed on right)<br />
* '''S''' - Operator is listening in Stereo mode (operator pressed '''<tt>AltGr-S</tt>''' or '''<tt>Ctrl-Alt-S</tt>''', press '''<tt>AltGr-A</tt>''' or '''<tt>Ctrl-Alt-A</tt>''' to remove)<br />
* '''T''' - Operator is listening to the Secondary Radio (operator pressed '''<tt>AltGr-T</tt>''' or '''<tt>Ctrl-Alt-T</tt>''', press '''<tt>AltGr-A</tt>''' or '''<tt>Ctrl-Alt-A</tt>''' to remove)<br />
* '''REPEAT''' - Automatic repeating CQ feature is active and '''<tt>[F1]</tt>''' has been pressed. See [[Menu:Tools#Automatic_CQ_repeat|Automatic CQ Repeat]].<br />
<br />
===Context Menu===<br />
A right click allows you to choose on what bands and modes these calculations have to be done:<br />
<br />
* All : No filtering is done<br />
* Current : Filters only QSO done in the mode and band of the current radio<br />
* According to QSO : Filters only QSO done in the mode and band of the current QSO<br />
<br />
You can also choose to display the calculations as :<br />
<br />
* QSO / h : Only based on the number of QSO<br />
* Points / QSO : Averages the points of the QSO<br />
* Points QSO / h : Without the multipliers<br />
* Points / h : Including the multipliers<br />
<br />
Thresholds are defined and can be modified on the following properties:<br />
<br />
* Instant moving graph window -how many minutes of history are taken into account<br />
* Off Time Alarm - after how many minutes the color of the green bar will turn red<br />
* Off-time calculation - after how much time of no QSO, time is counted towards off-time (may be contest specific)<br />
* Last band change method - which event triggers the timer after a band change<br />
<br />
Moreover, the contents of the rate window can be customized by selecting one or more of the following, which are listed under the '''Display''' menu item of the context menu:<br />
<br />
* Instant rate moving graph<br />
* Instant continents distribution<br />
* Off-time timer<br />
* Time ON / Time OFF<br />
* Band Changes<br />
* Band Changes elapsed times<br />
* QSO/Mult ratio<br />
* Distances Data<br />
<br />
Finally, right click and select the '''Copy''' menu item to copy this window, as an image, to the Windows clipboard.<br />
<br />
{{wbox|Note|The available menu items in the context menu may vary depending on where you right click in the window.}}<br />
<br />
==Statistics==<br />
<code>Windows | Statistics</code> or '''<tt>[Ctrl-F9]</tt>'''<br />
<br><br />
Opens (or closes) the Statistics window, a rate sheet.<br />
<br />
[[Image:WindowsRateSheet.gif|center|frame|Statistics Window showing total QSOs made on all bands and modes, per hour]]<br />
<br />
The size of this window can be changed by dragging the edges. The window displays the number of QSOs, hour by hour, for the entire contest period.<br />
<br />
The time span is fixed depending on the contest type. For the shorter contests, the display spans 24 hours; for the major contests, it spans the full 48 hours. For DXpeditions, it is configurable from 1 to 15 days via the [Days...] button in the [[New_Log#Step_2:_Setup_your_log|Contest Configuration window]].<br />
<br />
Switching to the '''Targets''' tab in the statistics window, you may compare your current score to a pre-loaded estimate, which may be derived from a previous contest operation or generated by hand. Positive offsets with respect to the target file are shown in green color, negative offsets in red color. <br />
<br />
[[Image:Targets.PNG|center|frame|Cumulative (overall) Multiplier tracking vs. target]]<br />
<br />
You may also display hour-by-hour comparisons with the targets.<br />
<br />
[[Image:StatisticsHourlyQSOTargets.PNG|center|frame|Hour by hour QSO tracking vs. target]]<br />
<br />
Please see [[Menu:Tools#Load_an_objective_file|Menu | Tools | Load a targets file...]] for further information on exporting and loading target files.<br />
<br />
Switching to the '''Continents''' tab displays continental QSO statistics.<br />
<br />
[[Image:StatisticsContinents.PNG|center|frame|Continental QSO statistics]]<br />
<br />
A right click allows to set different display options:<br />
<br />
{| align="center"<br />
|[[Image:StatisticsPopUpMenuDisplayedData.PNG|center|frame|Pop-up menu showing displayed data options]]<br />
|[[Image:StatisticsPopUpMenu.PNG|center|frame|Pop-up menu showing band options]]<br />
|}<br />
<br />
Displayed Data<br />
<br />
* Select which kind of data to display: QSOs, Multipliers, QSO Points, etc.<br />
<br />
<br />
Band<br />
<br />
* All (total): Single color display, all bands combined<br />
* All (detailed): Multicolor display, one color per band<br />
* Current: Displays statistics for the current band<br />
* According to QSO: Displays statistics for the band of the currently selected QSO<br />
<br />
Mode<br />
<br />
* All (total): Single color display, all modes combined<br />
* All (detailed): Multicolor display, one color per mode<br />
* Current: Displays statistics for the current mode<br />
* According to QSO: Displays statistics for the mode of the currently selected QSO<br />
<br />
Display<br />
<br />
* By time: Displays an hour by hour comparison<br />
* Overall: Displays a cumulative (overall total) comparison<br />
<br />
Another option allows you to load a targets file for comparison, or export a targets file based on the current log.<br />
<br />
Finally, it is possible to copy any of the Statistics windows as image or text to the Windows clipboard. Then you can copy the data into to a text document or even into an Excel&reg; or OpenOffice spreadsheet.<br />
<br />
==Gab==<br />
<code>Windows | Gab</code> or '''<tt>Alt-I</tt>'''<br />
<br><br />
Opens (or closes) the gab window.<br />
<br />
[[Image:WindowsGab.gif|center|frame|Gab Window]]<br />
<br />
All the gab chat is displayed in this window. With a right click, you can choose to display (or not) the time when the message was sent, including (or not) the seconds. Moreover, this window can be copied as an image.<br />
<br />
In the context menu, the option "Taskbar flashing" can be selected to make the Windows Task Bar flash every time a gab is received.<br />
<br />
All the gab chat is recorded in the <tt>.gab</tt> file of the current contest.<br />
<br />
A double-click in a station name in this window will open the chat dialog, with this station name as default destination.<br />
<br />
==World Map==<br />
<code>Windows | World Map</code><br />
<br><br />
Opens (or closes) the map window<br />
<br />
[[Image:WindowsMap.gif|center|frame|World Map]]<br />
<br />
The dimensions of this worldmap window can be modified. With a right click, you can display (or not) the grey-line. Moreover, you can increase or decrease the format (zoom).<br />
<br />
An additional option allows you to display only the greyline terminator plus a little symbol for the sun which makes reading the information a little easier at times.<br />
<br />
[[Image:WorldMapWithLightTerminator.gif|center|frame|World Map with light terminator]]<br />
<br />
==Radio 1, Radio 2 (Band Maps)==<br />
<code>Windows | Radio 1</code> or <code>Windows | Radio 2</code><br />
<br><br />
Opens (or closes) the radio window.<br />
[[Image:WindowsRadio.gif|right|frame|Radio window (band map)]]<br />
These resizable windows are also called Band Maps.<br />
<br />
The frequencies of the 2 VFOs are displayed. The active VFO has a yellow background.<br />
<br />
If Win-Test has a DX cluster connection, the bandmaps are automatically fed from the DX cluster data stream, from logging contacts, and by manually adding information using '''<tt>Ctrl-Enter</tt>''' instead of '''<tt>[Enter]</tt>'''.<br />
The green callsigns are the new multipliers, the black ones are the new callsigns (not worked so far), and the dupes are in grey and slanted font.<br />
<br />
A double click on a callsign will automatically put the radio on the spot frequency and capture the callsign in the logging field. You just need to complete the QSO and press '''<tt>[Enter]</tt>'''! Press '''<tt>[Alt-F4]</tt>''' to return to your run frequency.<br />
<br />
An '''<tt>[Alt]</tt>'''-double click on a callsign will load the spot frequency into the Sub VFO (VFO B), if your radio supports it.<br />
<br />
While in split mode during 40m and 80m SSB operation, when adding a spot to the band map, Win-Test remembers both the RX and the TX VFO frequencies, and will store this information so that when you select the spot, both VFOs will be set correctly, and you'll be ready to call (unless the QSX frequency has changed in the mean time).<br />
<br />
Moving the mouse pointer over a spot in the band map will bring up additional information, such as the age of the spot the callsign of the spotter, and any comments. Double-clicking the spot with the '''<tt>[Ctrl]</tt>''' key removes the spot from the band map (without confirmation).<br />
<br />
[[Keys#Band_Map|Other key combinations]] can be used to operate with the Band Map.<br />
<br />
===Band Maps Context menu===<br />
<br />
A right click on this window brings up its context menu. <br />
<br />
* The top option in this Context Menu allows you to program the Sub VFO (if your radio supports it) with this spot. <br />
* The '''Propagation''' submenu item allows you to gather propagation information via [[HamCAP]] (if installed)<br />
* The next two entries '''Modify...''' and '''Delete''' allow you to change or remove spots in the band map. Note that you can quickly remove a spot by double-clicking it with the '''<tt>[Ctrl]</tt>''' key pressed.<br />
* Additionally, you can change the scale of the band map display from 1:1 up to 30:1. The scale can also be set through the mouse wheel.<br />
* More options are hidden in the sub menus [[#Extended_information|Display Options]] and [[#Band_Map_properties|Properties...]] where one can set a lot of minor details of the band map.<br />
[[Image:WindowsBandMapContextMenu.PNG|center|frame|Band Map Context Menu]] <br><br />
*<code>29S 11N</code> at the bottom indicates there are 29 spots total, 11 new calls (not yet worked).<br />
* The List tab of the band map has a context menu with several sorting options:<br />
[[Image:WindowsBandMapListViewContextMenuSort.png|center|frame|Band Map List View Context Menu - sorting options]] <br><br />
* The List tab of the band map has a display option that lets you hide dupes and display additional information:<br />
[[Image:WindowsBandMapListViewContextMenuDisplay.png|center|frame|Band Map List View Context Menu - hiding dupes]] <br><br />
<br />
====Special cursors====<br />
Special indicators for the last CQ frequency or the QSY frequency (set with the PASSFREQ text command, or with the <code>Commands | QSY frequency</code> menu option) can also be activated (see picture). <br />
<br />
[[Image:WindowsBandMapCqCursor.png|center|frame|Band Map with CQ cursor]] <br><br />
<br />
To enable them, tag the CQ cursor and/or the QSY cursor items in the Display Options submenu of the context menu itself.<br />
<br />
====Extended information====<br />
The Display Options menu also allows you to select if the expected exchange will be displayed in the band map and other minor details, like day/sunrise/sunset/night symbols, time and sender, comments etc.<br />
<br />
====Markers====<br />
The Display Options menu allows you to enable the displaying of markers. These can be useful for beacons and other known stations on the bands.<br />
<br />
[[Image:WindowsBandmapMarker.png|center|frame|Band Map with a marker file for 10 m beacons loaded ]]<br />
<br />
Markers are defined by text files with a '''.mkr''' extension located in the Win-Test directory. WT can use and display up to 10 files simultaneously; they can be selected in the <tt>Options | Data files | Markers files</tt> menu. <br />
For detailed information, please see [[Menu:Options#Markers_files... | Menu: Options Data files Markers files]].<br />
<br />
Marker display settings can be different for each radio. The syntax of the marker files is very basic and they are easy to create with a simple text editor like Notepad.<br />
<br />
A marker is defined by its frequency (in kHz), a label (one word) and an optional tooltip (30 chars max.) that will flash when the mouse cursor is positioned on the marker for a few seconds. If you include a four or six character gridsquare locator, WT will display heading and distance to this gridsquare in the tooltip window.<br />
<br />
Example:<br />
<br />
28205 DL0IGI Hohenpeissenberg JN57MT<br />
28257 DK0TEN Sipplinger Berg JN47NT<br />
28277.5 DF0AAB Kiel JO54GH<br />
<br />
Two DIRECTIVES (or KEYWORDS) define the background and foreground color:<br />
<br />
* # BACKGROUND color => Sets the background color of the following markers in the file. If no color is specified, the default color is green.<br />
* # TEXT color => Sets the text color of the following markers in the file. If no color is specified, the default color is black.<br />
<br />
The known colors are: White, Black, Red, Green, Blue, Yellow, Magenta, Cyan. The case of the color is irrelevant, so "green" and "Green" are identical.<br />
<br />
Example :<br />
<br />
# BACKGROUND white<br />
# TEXT green<br />
#<br />
14100 Bcn NCDXF Beacon<br />
<br />
This will display a white marker with a green text "Bcn". The associated tooltip will be "NCDXF Beacon". As usual, you can double-click on a marker to set the current radio on the frequency of the marker. A sample file '''NcdxfBeacons.mkr''' is located in the WT repository at: http://download.win-test.com/files/markers/. It displays markers for each NCDXF beacon. <br />
<br />
You may build your own marker files (VHF beacons etc.) and share it with the WT community if you want.<br />
<br />
====Segments====<br />
WT can display band allocations for different license types in the bandmap tab of the radio windows. This allows you to select a run frequency which is in right band segment for US-Advanced or US-Novice amateurs for example.<br />
<br />
Band segments are defined by text files with a '''.seg''' extension located in the Win-Test directory. WT can use and display up to 10 files simultaneously; they can be selected in the <tt>Options | Data files | Segments files</tt> menu.<br />
Please find more detailed information in [[Menu:Options#Segments_files... | Menu: Options Data files Segments files]].<br />
<br />
Due to space constraints - you can't have more than 5 segments displayed per band for any given frequency.<br />
<br />
The segments display settings can be different for each radio.<br />
<br />
<center><br />
{|<br />
|[[Image:BandMapMarkerSegment.png|center|frame|Band Map with marker and segments]]<br />
|[[Image:WindowsBandmapSegments.png|center|frame|Band Map with US band allocation]]<br />
|}<br />
</center><br />
<br />
<br />
The syntax of the segments files is very basic, and the files are easily created with a simple text editor like Notepad. A segment is defined by specifying its lowest and its highest frequency (in kHz). The two frequencies may be linked by an hyphen for easier reading. An optional tooltip text (30 chars max.) can be given to explain the meaning of the color segment. By placing the mouse cursor over a colored line in the band map display, the tooltip will display.<br />
<br />
The BandMap segment color is indicated by the DIRECTIVE (keyword) COLOR like given below. The known colors are: White, Black, Red, Green, Blue, Yellow, Magenta, Cyan. The case of the color name is irrelevant. If no color is specified, the segments will be displayed in yellow.<br />
<br />
Example:<br />
<br />
# COLOR Red<br />
14000-14150 Extra CW<br />
14150-14350 Extra SSB<br />
# COLOR Yellow<br />
14025-14150 Advanced CW<br />
14175-14350 Advanced SSB<br />
# COLOR Magenta<br />
14025-14150 General CW<br />
14225-14350 General SSB<br />
<br />
This will display the US band allocation in the 20-m-band.<br />
<br />
The segments order, and potential overlaps in the file are irrelevant. WT will take care to display them in an optimized way.<br />
<br />
Two sample files are located in the WT repository at http://download.win-test.com/files/segments/<br />
<br />
* '''UsSegmentsDetailled.seg''' displays all band segments for every US licence type.<br />
* '''UsSegments.seg''' displays all band segments in which all US licencees are potentially active.<br />
<br />
You may create your own band segments files for other countries, regions, etc. and share them with the WT community if you want.<br />
<br />
====Band Map properties====<br />
Selecting '''Properties...''' in the context menu of the Radio 1 or Radio 2 band map windows displays the Bandmaps Properties window:<br />
<br />
[[Image:BandMapProperties.png|center|frame|Bandmap properties window]]<br />
<br />
Here you can define the lifetime of two kinds of spots, control the behavior of the logging window when you press '''<tt>[Ctrl-Enter]</tt>''' to create an operator-entered spot, control the automatic entry of data in the logging window when you grab a spot in the bandmap (via double click), select random 100 Hz TX frequency offsets to improve the chances of calling a spot on a clearer frequency (recommended), and the spot bandwidth for each mode (CW, SSB, RTTY) which is used to determine when two spots are on the same frequency. The spot bandwidth can be set between 0 Hz and 5000 Hz, in 100 Hz steps. The lifetime of spots in the band map can be changed from the default (60 minutes) to any other value below 100 minutes.<br />
<br />
Search & Pounce Options allow you to add spots to the band map without having to press '''<tt>[Ctrl-Enter]</tt>'''. Simply enter the callsign and turn the VFO by the specified frequency change threshold to automatically populate the band map.<br />
<br />
{{wbox|Note|To automatically populate the Band Map, you must be in S&P mode. Search & Pounce is not activated by default. Select [[Menu:Tools#Enable_Run.2FS.26P_switching|Tools | Data entry | Enable Run/S&P switching]] (text command shortcut: '''<tt>RUNSP [Enter]</tt>'''), and then press '''<tt>[Ctrl-tab]</tt>''' once to toggle from Run to S&P mode. The [[Menu:Windows#Clock|clock window]] indicates the current mode.}}<br />
<br />
==Secondary Radio==<br />
<code>Windows | Secondary Radio</code><br />
<br><br />
Opens (or closes) the Secondary Radio window.<br />
<br />
[[Image:secondary_window.PNG|center|frame|Secondary Radio Window]]<br />
<br />
This window controls the "other" radio that is currently not in use during SO2R operation, not necessarily radio 2.<br />
For more information, please see [[SO2R/Second_radio_window]].<br />
<br />
==RTTY (radio1, radio2)==<br />
<code>Windows | RTTY (radio 1)<br><br />
Windows | RTTY (radio 2)<br />
</code><br />
<br><br />
Opens (or closes) the RTTY Transit/Receive windows.<br />
<br />
[[Image:RttyWindow.PNG|frame|center|RTTY TX/RX Window]]<br />
<br />
For more information, see [[RTTY#Receive.2Ftransmit_window|RTTY Receive/Transmit window]] in the [[RTTY]] chapter.<br />
<br />
==Rotators==<br />
<code>Windows | Rotators</code><br />
<br><br />
Opens (or closes) the Rotators window.<br />
<br />
[[Image:WindowsRotators.PNG|frame|center|Rotators window with pop-up menus]]<br />
<br />
The three tabs at the bottom may be used to control the display:<br />
<br />
* Antennas<br />
* Stacks<br />
* Rotators<br />
<br />
''Right click'' on the dark blue area of the Rotators window to display the pop-up menu. Use the pop-menu to start or stop the companion program, '''wtRotators''', a program that communicates with one more more rotators, similar to the way that wtDxTelnet communicates with one or more packet clusters. <br />
<br />
Select the '''Start/stop automatically''' option to have Win-Test automatically start and stop the wtRotators program whenever you open or close Win-Test.<br />
<br />
See the [[Rotators]] main topic for more information about configuring and using wtRotators with Win-Test.<br />
<br />
==DX-Cluster Monitor==<br />
<code>Windows | DX-Cluster monitor</code> or '''<tt>Alt-O</tt>'''<br />
<br><br />
Opens (or closes) the DX Cluster monitoring window.<br />
<br />
[[Image:WindowsPacket.gif|center|frame|DX Cluster monitoring window]]<br />
<br />
The contents of this window are logged to to the '''.pkt''' file. Logging can optionally be disabled to save disk space or to prevent malware scanners from slowing down the system -- in particular, when a lot of spots is being received (e.g. via RBN). To disable logging, right-click in the window and uncheck "Stream logging".<br />
<br />
The window is scrollable so that you can step back through history, back - even to the beginning of the file. The scrolled window will not update when new spots arrive. However, there is a little hint in the title bar like '''[+1138 lines]'''. In order to see all spots which have arrived in the mean time you have to move the scrollbar back to the end of the window.<br />
<br />
For more information regarding the setup of DX Cluster connections, please see<br />
[http://docs.win-test.com/wiki/Menu:Commands#DX-Cluster Commands | DX Cluster]<br />
<br />
==DX-Cluster Announcements==<br />
<code>Windows | DX-Cluster Announcements</code> or '''<tt>Alt-A</tt>'''<br />
<br><br />
Opens (or closes) the DX cluster announcements window.<br />
<br />
[[Image:WindowsDxClusterAnn.gif|center|frame|DX Cluster Announcements Window]]<br />
<br />
This window gathers all the spots coming from the DX cluster. New multipliers are green, other stations (but not dupes) are black.<br />
<br />
With a right click, you can choose to display only new multipliers, only spots entered by the operator and/or selected bands:<br />
<br />
[[Image:DXClusterAnnouncementsBands.PNG|center|frame|Band selection pop-up menu for the DX Cluster Announcements window]]<br />
<br />
All spots are logged to the corresponding '''.dxc''' file in the log directory. Logging can be disabled to save disk space or prevent malware scanners from slowing down the system - in particular, when a lot of spots is being received (e.g. via RBN). Manually entered spots are still being logged to the '''.dxc''' file.<br />
<br />
The displayed information is selectable (local time as a sun symbol, time spotted, spot comments, beam heading, and the callsign of the spot sender):<br />
<br />
[[Image:DXClusterAnnouncementsDisplayOptions.PNG|center|frame|Display options for the DX Cluster Announcements window]]<br />
<br />
A double click on a selected line will automatically switch the active radio to the spot frequency, and will grab the call and enter it in the callsign logging field. You just need to complete the QSO and press ['''<tt>Return</tt>'''].<br />
<br />
QSX information (like QSX 7239) is parsed from the comment field of the spot and handled correctly, so that when you click on such a spot, the transceiver will switch to split mode, put VFO A on the RX frequency and VFO B on the TX frequency. QSX is indicated by an asterisk (*) character on the spotted callsign. Cross-band QSX frequencies are being ignored.<br />
<br />
Additional shortcuts:<br />
* '''<tt>[Ctrl] + Dbl click</tt>''' on a spot removes the spot from the Announcements window (without confirmation).<br />
* '''<tt>[Alt] + Dbl click</tt>''' on a spot loads the spot frequency in the sub VFO of the active radio (if your radio supports it) <br />
<br />
For more information regarding the setup of DX Cluster connections, please see<br />
[http://docs.win-test.com/wiki/Menu:Commands#DX-Cluster Commands | DX Cluster]<br />
<br />
==Clock==<br />
<code>Windows | Clock</code><br />
<br><br />
Opens (or closes) the clock window.<br />
<br />
[[Image:clocks.png|center|frame|Clock window samples]]<br />
<br />
To set time in Win-Test, you don't need to change the computer time. You just need to adjust the computer clock in the local time, within the right time zone. Win-Test will compute the UTC time from this information. <br />
<br />
The color of the time display changes in minutes 59 and 00, to prepare an operator changeover in a multi-op environment.<br />
<br />
This window also displays sunrise and sunset times (SR and SS) according to your location. To catch your eye, the color of these times will change when you are within 30 minutes of sunrise or sunset times.<br />
<br />
This window also displays your Locator (which is needed if you want that WT exactly compute SR/SS times as well as Bearings and distance to the correspondent) and the Win-Test operating mode, RUN or S/P, according to your operating needs. For details on this feature see also [[Menu:Tools#Data_entry | Menu:Tools Data_entry]].<br />
<br />
Just as a side note, WinXP allows you to synchronize your computer's clock time through the Internet. Please see more details on Microsoft's support pages ([http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/windows_date_it_overview.mspx overview] and <br />
[http://technet2.microsoft.com/windowsserver/en/library/b43a025f-cce2-4c82-b3ea-3b95d482db3a1033.mspx details]).<br />
<br />
The font type and size, as well as the background and all the usual window colors can be changed through the context menu using a right mouse click on that window.<br />
<br />
==Contest Recorder==<br />
<code>Windows | Contest Recorder</code><br />
<br><br />
Opens (or closes) the Contest Recorder window.<br />
<br />
Before recording, right click and select [[Menu:Options#MP3_Configuration|MP3 Configuration]] to set the recording parameters.<br />
<br />
A right-click on the Recorder window gives help to the keyboard shortcuts. <br />
Use <code>right-click | Files Information</code> to see information about recorded files, or to delete recorded files.<br />
<br />
[[Image:ContestRecorder.PNG|center|frame|Contest Recorder window]]<br />
<br />
==SSB bargraph==<br />
<code>Windows | SSB bargraph</code><br />
<br><br />
Opens (or closes) the SSB bargraph window<br />
<br />
[[Image:WindowsVuMeter.gif|center|frame|SSB bargraph window]]<br />
<br />
This bargraph displays the audio level of the Win-Test's digital voice player (if used, of course). The appropriate level is the yellow part of this bargraph.<br />
<br />
==Close all Windows==<br />
<code>Windows | Close all windows</code><br />
<br><br />
Closes all windows except the log entry area in the left lower area.<br />
<br />
[[Menus|Back to Menus]]</div>N6TVhttps://docs.win-test.com/w/index.php?title=Interfaces&diff=4530Interfaces2015-01-16T00:19:14Z<p>N6TV: /* LPT-port CW keying */ Added link to InpOut32.dll</p>
<hr />
<div>Configuration of interfaces in Win-Test needs only be done once, rather than on a per-contest basis. This means you do not waste time remembering your interface configuration details prior to each contest!<br />
<br />
== Interface configuration ==<br />
<br />
The [[Menu:Options#Configure_interfaces...|interface configuration window]] can be opened by clicking on <code>Options->Configure Interfaces</code> menu in the main Win-Test window, or via the text command '''<tt>SETUP</tt>'''.<br />
<br />
=== Radio configuration ===<br />
At the bottom of the window there is a "Transceivers" section which includes two drop-down lists where you set your radio type ('''Radio 1''' and '''Radio 2'''). First, choose your rig make and model from the appropriate list. Please note that there is only one "Kenwood" entry in the list because all Kenwood rigs use a common protocol.<br />
<br />
On the left hand side of the window, you will see a list of COM ports (only available COM ports on your system will be selectable). After you have chosen the manufacturer and/or model of your rig, check the box corresponding to the COM port to which your radio is connected. For example: <br />
<br />
[[Image:Interfaces.png|frame|center|COM port configuration]]<br />
<br />
Upon checking the box, you will notice that the adjacent drop-down box will now be enabled. You ''must'' choose '''Radio 1''' or '''Radio 2''' from this drop-down list. You must also '''ensure that the port (baud rate) settings are correct for your radio'''.<br />
<br />
By default, the settings of 19200 8-N-1 will be configured, which is probably incorrect for your radio. Click on the adjacent '''<tt>[Configure...]</tt>''' button to display the [[Menu:Options#Serial_Ports|COM port properties dialog]]:<br />
<br />
[[Image:com1-properties.png|frame|center|COM port configuration for Radio1 / Radio2]]<br />
<br />
If you are not sure about the baud rate settings for your transceiver, press the '''<code>[default settings]</code>''' button to change all values to the known hardware defaults for the selected radio.<br />
<br />
There is also a list of known working settings for common contest radios located in the [[Supported_rigs|Supported rigs]] chapter.<br />
<br />
== Configuring other interfaces ==<br />
<br />
As you may well have noticed by this stage, a variety of other interfaces can also be enabled from the <code>Configure Interfaces</code> dialog box. It is just a simple case of ticking the relevant COM port and choosing said device from the drop-down list. Examples include TNCs, SO2R switching boxes (e.g. [[SO2R/EZMaster/Setup|EZmaster]], [[SO2R/MK2R/Setup|microHAM MK2R]], WinKey, W5XD Keyer, etc.). For everything not on the list, you can choose <code>Other interface...</code> and configure the port settings yourself - for example, COM port CW interface (see below).<br />
<br />
=== COM-port CW keying ===<br />
<br />
If you have a simple transistor-based COM port CW interface (see below), you can enable this by again choosing the corresponding COM port, and selecting <code>Other interface...</code> from the drop-down list. Clicking on the <code>Configure</code> button will display the [[Menu:Options#Serial_Ports|COM Port Properties dialog]] including a drop-down list of options for DTR (pin 4) and RTS (pin 7) on<br />
a DB9 connector (pins 20 and 4 on a DB25).<br />
<br />
''Be sure to select '''DTR: CW''' from the drop-down list.''<br />
<br />
[[Image:Schema_COM_InterfaceCW.gif|center|frame|Simple COM port CW interface]]<br />
<br />
This interface was designed for K1EA's CT and is still in use today with Win-Test.<br />
<br />
=== LPT-port CW keying ===<br />
<br />
Likewise, if you have an LPT (parallel) port CW interface (see schematics below), you can enable it by checking the box next to 'LPT' in the [[Menu:Options#Configure_interfaces...|Configure interfaces dialog]]. Clicking on the <code>[Configure]</code> button in the Printer Ports section will display the [[Menu:Options#Printer_Ports|Printer Ports dialog]]. At the very bottom, you can enable CW and PTT on pin 17 and 16 respectively. ''Ensure this is checked.''<br />
<br />
{{wbox|WARNING|In order for LPT keying to function correctly under Windows XP, Vista, or 32-bit Windows 7, you will need an additional utility, '''DLPortIO.dll''' installed by Port95NT.exe, obtainable from the Win-Test website. It is a simple process and only needs to be installed/run once. Please [http://download.win-test.com/port95nt.exe click here] to download. For 64-bit Windows 7, use InpOut32.dll as described in [http://lists.f5mzn.org/pipermail/support/2011-May/081094.html this post].}}<br />
<br />
[[Image:Schema_InterfaceCW.gif|center|frame|Simple LPT port CW interface]]<br />
<br />
=== Digital Voice Keyer ===<br />
<br />
The DVK-100 voice keyer was the first computer-controlled voice memory in the contesting world in the early 90s. Later, some equipment manufacturers built voice memories into their radios like Kenwood (TS-850, TS-950 with the DRU2 and DRU3 units respectively - probably others). These devices can be controlled by Win-Test using the following LPT interface.<br />
<br />
[[Image:Schema_InterfaceDVK.gif|center|frame|Simple LPT port DVK interface]]<br />
<br />
Usually the device has 3-4 different memories which can be triggered by [<b><tt>F1</tt></b>]...[<b><tt>F4</tt></b>] on the computer keyboard.<br />
<br />
=== Sound Card ===<br />
<br />
Wav files can also be played from an internal sound card by utilizing a small interface like shown below.<br />
Messages are recorded using <b><tt>Shift-F1</tt></b>...<b><tt>Shift-F7</tt></b>.<br />
<br />
[[Image:Schema_Interface_SoundCard.gif|center|frame|Sound Card Interface]]<br />
<br />
The use of an isolation transformer is recommended both on the output side of the sound card. Of course, you can go without one but first think about the trouble you will encounter when the Line Out port of your sound card gets killed by stray RF or when someone tells you you got hum on your audio in the middle of the contest. <br />
<br />
[[Image:SoundcardInterface.gif|center|frame|Sound Card interface kindly provided by W9ZRX. This interface is in use at the K3LR M/M station.]]<br />
<br />
W9ZRX has provided this design that comes without a relay to switch Mic input between radio and sound card. Most sound cards allow routing from Mic input to Line Out so that you can control muting Line Out from within Win-Test. Make sure that the Microphone has been enabled as an Input to the Sound Card Mixer. Different Sound Cards set up slightly differently, but most seem to either show the Microphone Input to the Mixer as '''muted''', or the default Mixer Inputs do not include the Microphone until '''enabled'''.<br />
<br />
There are sound cards that do not support this option. The Writelog download site has a [http://www.writelog.com/Downloads/sbrdchk.zip sound card checker] that will help you to determine if you have this problem if it absolutely doesn't work.<br />
<br />
Another way would be to try using the Win-Test PTT output to drive a relay to allow a direct routing between your Mic and the Mic input of your TRX when the PTT output is off. This requires some additional components but better than an external mic to record the DVK messages.<br />
<br />
=== Band Data ===<br />
<br />
Win-Test supports filter and antenna switching by supplying Yaesu-standard Band data on pins 2, 7, 8 and 9 of the parallel port. These pins are equivalent to lines A, B, C and D. This feature allows you to automatically control other devices in your station, probably by using a band decoder like the one from [http://www.qth.com/topten/bdecoder.htm Top Ten Devices]. <br />
<br />
{| {{Prettytable_fixed}}<br />
! Band !! A !! B !! C !! D <br />
|-<br />
| 160 m || 0 || 0 || 0 || 1<br />
|-<br />
| 80 m || 0 || 0 || 1 || 0<br />
|-<br />
| 40 m || 0 || 0 || 1 || 1<br />
|-<br />
| 30 m || 0 || 1 || 0 || 0<br />
|-<br />
| 20 m || 0 || 1 || 0 || 1<br />
|-<br />
| 17 m || 0 || 1 || 1 || 0<br />
|-<br />
| 15 m || 0 || 1 || 1 || 1<br />
|-<br />
| 12 m || 1 || 0 || 0 || 0<br />
|-<br />
| 10 m || 1 || 0 || 0 || 1<br />
|-<br />
| 6 m || 1 || 0 || 1 || 0<br />
|-<br />
| 2 m || 1 || 0 || 1 || 1<br />
|-<br />
| 70 cm || 1 || 1 || 0 || 0<br />
|-<br />
|}<br />
<br />
=== Radio 1/Radio 2 ===<br />
<br />
LPT pin 14 is used to send Radio1/2 information to an external interface. High = Radio1, Low = Radio2.<br />
<br />
=== Headphones Control ===<br />
The signals ''Headphones Control'' (called ''RX Focus'' in the MK2R microHAM SO2R interface) is available on LPT, pin 4. This signal allows to control which radio you want to listen to in the headphones. Must be enabled in the LPT Configuration Window. Low = Radio 1, High = Radio 2.<br />
<br />
== See Also == <br />
<br />
=== From the Win-Test manual ===<br />
<br />
* [[Menu:Options#Configure_interfaces...|Configure interfaces dialog]]<br />
* [[Networking|Networking configuration for multi-ops]]<br />
* [[SO2R/EZMaster/Setup|EZMaster setup]]<br />
* [[SO2R/MK2R/Setup|microHAM MK2R setup]]<br />
<br />
=== External sources ===<br />
<br />
* [http://www.microham.com/Downloads/micro_KEYER_R_2_0_English.pdf microHAM MicroKeyer Manual]<br />
* [http://www.microham.com/Downloads/USB_Interface_II_R_1_1_English.pdf microHAM USB II Interface Manual]</div>N6TVhttps://docs.win-test.com/w/index.php?title=RTTY&diff=4529RTTY2014-12-20T22:00:47Z<p>N6TV: /* Set up MMTTY PTT COM Port */ Clearly indicate COM port set for FSK and PTT must be set, but Radio Command port must be set to NONE.</p>
<hr />
<div>Win-Test includes basic support for RTTY contests using the MMTTY engine, which is used by most Windows-based contest logging programs. <br />
<br />
Follow the instructions below to set up Win-Test for RTTY operation in the quickest and simplest way.<br />
<br />
==Downloading MMTTY Engine==<br />
<br />
{{wbox|Note|If you're already using N1MM Logger or WriteLog, you may already have this engine installed so it's worthwhile checking before-hand.}}<br />
<br />
Win-Test uses the MMTTY engine by JE3HHT, so the first task, before you can start operating RTTY, is to go to the [http://hamsoft.ca/pages/mmtty.php MMTTY home page], scroll to the '''Downloads''' section, download and run '''MMTTY168A.exe'''. For SO2R operating, you will need to install MMTTY twice, in two separate directories. <br />
<br />
If you do ''not'' have a microHAM device, and you wish to use FSK instead of AFSK, be sure to download and install the [http://hamsoft.ca/pages/mmtty/ext-fsk.php EXTFSK extension], which is a ZIP file named '''ExtFSK106.zip''' (at bottom of page). Details for setting up EXTFSK can be found at [http://hamsoft.ca/pages/mmtty/ext-fsk.php the MM HAMSOFT site] provided by VE5KC, and on AA5AU's extensive [http://www.aa5au.com/rtty/ Getting Started on RTTY] pages.<br />
<br />
EXTFSK is ''not'' recommended or needed when using most microHAM devices as your RTTY interface. See [http://lists.f5mzn.org/pipermail/support/2013-September/083201.html this post] by W4TV.<br />
<br />
We recommend setting up MMTTY as a standalone application first, before integrating it into Win-Test, especially if you wish to get FSK going. By the way, although it's possible to control your radio from MMTTY, PLEASE DO NOT configure this, as it will interfere with Win-Test's rig control. Set up only RTTY decoding, RTTY keying, and PTT through the sound card and/or COM ports.<br />
<br />
Now you are ready to set up Win-Test to launch MMTTY; actually you may even want to have it launch two different instances of MMTTY to go SO2R on RTTY!<br />
<br />
==Configuring Received Data Logging on MMTTY (optional) ==<br />
<br />
If you want to keep all sent and received RTTY characters in a text file, then you should activate logging in MMTTY, since Win-Test has no option to log all the RTTY data received.<br />
<br />
To configure logging, start MMTTY (from the desktop, not from Win-Test!), then select '''<tt>File(<u>F</u>) | Options of Received-log </tt>''' to configure the file the information is written to, and enable timestamps. Next select '''<tt>File(<u>F</u>) | Log Rx file(<u>L</u>)</tt>''' to activate Logging. <br />
<br />
Now close MMTTY and restart it to check whether the options are still set correctly. You might need to save the MMTTY options as a profile. Now check the log file. It should have more than 0 bytes and contain data like this:<br />
<br />
<071113 17:07:04 MMTTY Startup><br />
<071113 17:07:07 TX><br />
TEST TEST TEST <br />
<071113 17:07:10 RX><br />
DSGFIEUGSLD SFGAF G<br />
<071113 17:07:04 MMTTY Close><br />
<br />
If all works properly, shut down MMTTY and go back to Win-Test.<br />
<br />
{{wbox|Note|MMTTY saves are buffered, so you might not see all the data logged immediately. After you close MMTTY (or Win-Test), the file will be closed, and everything will be saved.}}<br />
<br />
==Win-Test RTTY configuration==<br />
<br />
Now that you've got the engine downloaded and installed, it's time to fire up Win-Test and get things set up! <br />
<br />
==== Open the RTTY configuration box ====<br />
Open a contest file for a RTTY contest. Once it has loaded, right-click on the Win-Test logging window, and select '''RTTY configuration...''', or just type the text command '''<tt>RTTYSETUP</tt>''' in the logging window, and press <tt>[Enter]</tt>.<br />
<br />
[[Image:Rtty config rightclick.gif|frame|center|Main screen right click]]<br />
<br />
=== Enable MMTTY ===<br />
After selecting '''RTTY configuration''', you will see the dialog below:<br />
<br />
[[Image:OptionsRttyConfiguration.PNG|frame|center|RTTY Configuration dialog]]<br />
<br />
; Run MMTTY : Check this box and add the path to the MMTTY executable file (.exe). You may use the '''Browse''' button to navigate to the MMTTY installation directory to highlight MMTTY.EXE, then click '''Open''' to select the file and fill in the text box.<br />
{{wbox|Note| If you want to do SO2R RTTY (with two radios) you need two installations of the MMTTY engine, in separate directories, one for each radio. Add the path to the second copy of MMTTY.exe in the '''Path of MMTTY for Radio 2''' text box as shown above.}}<br />
; MMTTY window stays on top : Enable this option to have the MMTTY window painted on top of other windows, which is helpful when tuning in RTTY signals.<br />
; Only show FFT spectrum, waterfall and XY scope : Enable this option to display a smaller MMTTY window without a menu or the other MMTTY controls:<br />
[[Image:MmttyXyScopeOnly.png|center|frame|Reduced MMTTY plugin window]]<br />
; INSERT key grabs highlighted callsigns from the RTTY window : Enable this option to load the most recent highlighted callsign into the logging window automatically when you press the <tt>[Insert]</tt> key, without having to click on it with the mouse.<br />
; Favor multipliers : Enable this sub-option to have the <tt>[Insert]</tt> key pick the most recent callsign that is a new multiplier, even if there are more recent highlighted callsigns (that are not new multipliers).<br />
; Activate single mouse click grabbing : Enable this option to use a single-left-click of the mouse, rather than a double-left-click, to load a callsign into the logging window. Note: use a '''middle-click''' (press down on scroll wheel) to load a callsign into the [[Menu:Windows#Partner|Partner window / callsign stack]].<br />
; Radio is automatically activated by a mouse click in the window : Enable this option when using SO2R mode to switch transmitters simply by clicking on the appropriate RTTY window.<br />
<br />
Be sure to click '''OK''' to exit. <br />
<br />
If '''Run MMTTY''' was enabled, the MMTTY window should open automatically after you press '''OK'''. If you have configured MMTTY to run standalone before, everything should start to work right away.<br />
<br />
=== Set up MMTTY PTT COM Port ===<br />
Win-Test and MMTTY run as two separate programs. Only one program can use a COM port at a time. You cannot tell both Win-Test and MMTTY to use the same COM port for PTT. For RTTY mode, only MMTTY should control the COM port used for PTT, not Win-Test: <br />
<br />
[[Image:MMTTY_PTT_Port.png|frame|center|MMTTY PTT and FSK via COM port pins. Click the Radio Command button to set Radio port to NONE.]]<br />
<br />
Similarly, only Win-Test should control the COM port used for rig control (CAT commands), not MMTTY. Under the '''TX''' tab on MMTTY Setup, click the '''Radio Command''' button and make sure that the '''Port''' in that sub-dialog is set to '''None''':<br />
<br />
[[Image:MMTTY_Radio_Command_Port.png|frame|center|MMTTY Radio Command (CAT) port. Radio port should be set to NONE here because Win-Test needs exclusive access to this port for rig control.]]<br />
<br />
=== Testing ===<br />
Try to receive and decode a RTTY signal. If that works, try to key the transmitter and get on the air by pressing '''Alt-K''' (keyboard mode), then type some text. Press '''Alt-K''' again to end transmissions. If you can monitor your signal, you should now hear the typical RTTY diddle.<br />
<br />
In case you still need to set up something in MMTTY, you may do so without exiting Win-Test by clicking '''Options | Setup''' in the MMTTY sub-window (to access the MMTTY menu, you must first disable the '''<tt>RTTYSETUP</tt>''' option '''Only show FFT spectrum, waterfall and XY scope''' if previously enabled).<br />
<br />
Note that you might need the EXTFSK extension for MMTTY if you are using MMTTY via an USB-to-serial adapter rather than a "real" (legacy) serial port.<br />
<br />
==== microHAM interfaces ====<br />
EXTFSK is ''not'' recommended or needed when using most microHAM devices as your RTTY interface. See [http://lists.f5mzn.org/pipermail/support/2013-September/083201.html this post] by W4TV.<br />
<br />
See the [http://www.microham.com/contents/en-us/d190_Click_here_to_edit_title.html Logger Setup Guides] on the [http://www.microham.com microHAM Web Site] for detailed instructions. Click '''Support''', '''Application Notes''', '''Logger Setup Guides''', select your device, then click '''Win-Test''' for a microHAM PDF document with detailed screen shots showing how to use the device with Win-Test.<br />
<br />
For FSK, in the MMTTY '''Misc''' tab, set '''Tx Port''' to COM-TxD(FSK). Select the '''USB Port''' button next to this option, and select option "C" '''Limiting speed''', and click '''OK'''. You can find this setting in the Logger Setup Guides documentation on the microHAM website.<br />
<br />
[[Image:MMTTY-USB-Port-Option.png|center|frame|MMTTY USB Port Option - Option C is recommended]]<br />
<br />
==== LPT port ====<br />
<br />
According to [http://lists.f5mzn.org/pipermail/support/2007-September/074597.html this post by IZ4EFN], FSK keying is also possible through the LPT port. It involves installing and configuring '''TDLPortIO.dll''' as well as EXTFSK.<br />
<br />
== General usage ==<br />
Once you have everything set up, here's a basic guide to logging QSOs. Press '''[F1]''' or click F1 in the RTTY Window to call CQ. Press or click '''[Ins]''' to load the most recently highlighted callsign into the logging window and send the exchange. Press or click '''[+]''' to send the TU message and log the QSO. Press or click '''[F7]''' to send the "?" message.<br />
<br />
=== RTTY window ===<br />
<br />
By default, Win-Test doesn't open the RTTY window(s) automatically. From the Win-Test menu, select '''<tt>Windows | RTTY(radio 1)</tt>'''. This will open the RTTY receive window for Radio 1. <br />
<br />
If you're running SO2R RTTY, select '''<tt>Windows | RTTY(radio 2)</tt>''', which will open a second RTTY receive window for Radio 2.<br />
<br />
[[Image:RttyWindow.PNG|frame|center|RTTY TX/RX Window. The blue highlighting of the two callsigns UA3PAB and N4TV means: these are new callsigns yet to be worked.]]<br />
<br />
Highlight colors:<br />
; Blue : New callsigns<br />
; Yellow : New multipliers<br />
; Green : New double-multipliers<br />
; Red : Duplicate callsigns (dupes)<br />
<br />
Your own transmissions will be displayed in blue text.<br />
<br />
With the mouse cursor, you can double-click (or single-click, if the option is enabled) on a callsign, and it will be copied to the callsign entry field in the logging window. Remember that pressing <tt>[Insert]</tt> when the callsign entry field is empty will copy the most recently highlighted callsign into the callsign field. Clicking on a contest exchange will copy it into the received exchange field. '''Middle-clicking''' on a callsign (click on mouse wheel) will transfer the call to the [[Menu:Windows#Partner|Partner window / callsign stack]]. <br />
<br />
Most of the function keys have a corresponding button at the bottom of the RTTY window which you may click with the mouse to activate instead of using the keyboard. Clicking on a function key button while holding down the '''[Shift]''' key will allows you to reprogram the contents of a message button quickly. All RTTY messages may be edited at once via '''Options | RTTY | Modify standard messages ...''' or the text command shortcut '''<tt>MSGS</tt>''' <tt>[Enter]</tt>.<br />
<br />
Pressing the '''Alt+K''' button toggles in and out of keyboard mode so you can type and transmit any text real-time.<br />
<br />
Pressing the '''(C)''' button clears the TX/RX window.<br />
<br />
To scroll text in the RTTY window, drag the scroll bar with the left mouse button, or turn the mouse wheel. '''[Shift] + mouse wheel''' will jump to the beginning or the end of the RTTY window. <br />
<br />
Most routine situations in RTTY contests can be handled with the mouse alone, without pressing any key.<br />
<br />
=== Defining messages ===<br />
Most of the RTTY messages are already set up for you to use by default, but often you will want to change them. Use $13 in a message to send a Carriage Return (CR). See [[Message_variables|Message Variables]] for a complete list.<br />
<br />
All RTTY messages may be edited at once via '''Options | RTTY | Modify standard messages ...''' or the text command shortcut '''<tt>MSGS</tt>''' <tt>[Enter]</tt>.<br />
<br />
You can also quickly edit a single message. To do this, press '''<tt>Shift-F1 .. F7</tt>''', '''<tt>Shift-[Insert]</tt>''', or '''<tt>Shift-[+]</tt>'''. Note: if you're operating in SO2R mode with '''Shift Binds to Secondary Radio''' enabled, you must use the '''<tt>[AltGr]</tt>''' (or '''<tt>[Ctrl]+[Alt]</tt>''') keys instead of the '''<tt>[Shift]</tt>''' key to reprogram messages. <br />
<br />
[[Image:Rtty macros.gif|frame|center|RTTY Macros]]<br />
<br />
As the '''<tt>++</tt>''' and '''<tt>--</tt>''' speed accelerators used for CW do not make sense on RTTY, you should remove them.<br />
<br />
Once you're done, click '''Validate''' to close the window.<br />
<br />
Please see the [[DVK_CW_RTTY_Messaging#Configuring_CW.2FRTTY_messages|Configuring CW/RTTY messages]] page for more details.<br />
<br />
=== MMTTY window ===<br />
You may occasionally encounter a problem with the cursor disappearing or the application loses focus. To recover, minimize and restore Win-Test using the mouse.<br />
<br />
[[Image:Rtty mmtty.gif|frame|center|MMTTY Window]]<br />
<br />
The above screenshot is of the MMTTY window in normal mode when operating RTTY. This is when '''Only show FFT spectrum, waterfall and XY scope''' is disabled.<br />
<br />
This is a mimimized version of MMTTY, but it allows you to change most of the settings. For example, to enable the XY scope (the two ellipsoides) go to the '''<tt>View</tt>''' menu of MMTTY and tick the '''<tt>XYScope</tt>''' option. For the rest of the bells and whistles of MMTTY, please see the online help of that software.<br />
<br />
== See also ==<br />
* [http://www.microham.com/contents/en-us/d190_Click_here_to_edit_title.html microHAM Logger Setup Guides] <br />
* [http://www.aa5au.com/rtty/ Getting Started on RTTY] - very detailed MMTTY set-up guide by AA5AU<br />
* [[BestPractice1|Getting ready for a RTTY Contest]]<br />
* [[BestPractice4|Setting up an Kenwood TS-850S with the microHAM microKeyer]]<br />
* [http://www.rttycontesting.com/ RTTY Contesting.com]: Great tutorials on how to use MMTTY.</div>N6TVhttps://docs.win-test.com/w/index.php?title=File:MMTTY_Radio_Command_Port.png&diff=4528File:MMTTY Radio Command Port.png2014-12-20T21:55:30Z<p>N6TV: MMTTY Radio Command Dialog the Radio port set to NONE as required in most cases</p>
<hr />
<div>MMTTY Radio Command Dialog the Radio port set to NONE as required in most cases</div>N6TVhttps://docs.win-test.com/w/index.php?title=File:MMTTY_PTT_Port.png&diff=4527File:MMTTY PTT Port.png2014-12-20T21:54:14Z<p>N6TV: MMTTY PTT port with Radio Command Button indicated. Goes with next image MMTTY_Radio_Command_Port.</p>
<hr />
<div>MMTTY PTT port with Radio Command Button indicated. Goes with next image MMTTY_Radio_Command_Port.</div>N6TVhttps://docs.win-test.com/w/index.php?title=User_talk:W0yk&diff=4518User talk:W0yk2014-12-20T05:09:43Z<p>N6TV: Welcome!</p>
<hr />
<div>'''Welcome to ''Win-Test Wiki''!'''<br />
We hope you will contribute much and well.<br />
You will probably want to read the [[Help:Contents|help pages]].<br />
Again, welcome and have fun! [[User:N6TV|N6TV]] ([[User talk:N6TV|talk]]) 05:09, 20 December 2014 (UTC)</div>N6TV