Release Notes V3

From Win-Test Wiki
Jump to: navigation, search

Release Notes

Contents

Release information (3.27.1-dev) (nightly)

Bugfixes

Release information (3.27.0) (Jun 9, 2009)

New Features

Bug Fixes

Release information (3.26.0) (Mar 26, 2009)

New Features

 $CURRENT (or $CURRENTCALL) : Sends the callsign of the current QSO  *despite* the presence of a $CR (always executed on message keypress) later in the message.
 $NEXT (or $NEXTCALL) : Sends the callsign of the next QSO line when  a $CR is included in the message.
 $PREV (or $PREVCALL) : Sends the callsign of the previous QSO line.
 $GRABPARTNER : Grabs the first callsign from the Partner window and  insert it in the callsign field. The exchange guessing is performed  (or not) according to the manual callsign entering setting (Tools /  Data entry / Exchange guessing).

To summarize, you can now enter a QSO (with correction or not), grab another callsign from the Partner window and send his report in one keystroke, by using : 

 $CORRECT TU $CR NOW $GRABPARTNER $NEXT $F2 (w/correction)

or 

 $CURRENT TU $CR NOW $GRABPARTNER $NEXT $F2 (full call) ($F2 is supposed to be the sent report)

If you want to manually grab a callsign from the Partner window you can use : 

 $PREV TU NOW $LOGGED $F2    ($F2 is supposed to be the sent report)

1/ Use the enter key to silently enter the current Q 2/ Grab the next callsign from the Partner wnd (dbl-click or Alt-n) 3/ Send the above message

Use the Options / CW (or RTTY) / Custom variables... menu to set the names and the value of these variables to be used in your CW or RTTY messages. You can also use the VARIABLES text command.

You can also easily set a variable value by entering its name in the callsign and "Enter". WARNING : Don't chose a variable name that is already used or it won't work... Tnx K5AC @ K5D.

Bugfixes

Release information (3.25.1) (Feb 13, 2009)

New Features

Bugfixes

Release information (3.24.0) (Jan 15, 2009)

New Features

Bugfixes

Release information (3.23.0) (Oct 22, 2008)

New Features

Release information (3.22.0) (Sep 16, 2008)

CAUTION: New network protocol version 1.23 released

Reminder: If you use WT in a networked environment, you must have the same WT version on all machines!

New Features

Bugfixes

Release information (3.21.0) (June 23, 2008)

CAUTION: New network protocol version 1.22 released

Reminder: If you use WT in a networked environment, you must have the same WT version on all machines!

New Features

Even if this tool is more supposed to be used after a contest, or a DXPed, to correct a wrong or forgotten entry, each correction is broadcasted to the other stns of the network by default. You can disable this broadcasting to save time, if not needed.

The easiest way to correct a range of Q, is to set the cursor log on the first Q to correct and select the menu item. The operator combo will be then already set. Then, adjust the last Q to correct by using the arrow keys (and optionally the band(s) and mode(s)).

Note that corrections are pretty CPU intensive and it may take a certain amount of time for large logs, because each QSO modification requires internal structures to be updated.

Note : Hesitating and wise users are encouraged to perform a backup of their log before proceeding. These corrections can't be cancelled while they are progress, to avoid any log inconsistancy... Tnx G3TXF and F6IFY.

Bugfixes

Release information (3.20.0) (May 14, 2008)

Note: Contrarily to the WTB backup, the LogSearch exports are not done in a separate background thread. Thus, it is not recommanded 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. During this period of time, an empty file named "LOCK" is created in the backup directory, and deleted once the export is completed. This ensures file integrity check for a third party application using the export file.
We remind you that you can also switch keyboard by using the text command KEYB/xxx where xxx is the abbreviated language code described here: http://www.microsoft.com/globaldev/reference/winxp/langtla.mspx
For example : KEYB/FRA, KEYB/ENU or KEYB/ENG etc.
For convenience, this abbreviation is also mentionned in the keyboard switching dialog.

Bugfixes

Release information (3.19.0) (Jan 24, 2008)

New Features

Foreword: This feature is very limited, and will *not* be further extended in this major version of Win-Test (v3). It is mainly added to help DXPeditioners for the web log search scripts, and for various DX or contesters challenges (RRDXA etc.)
New text commands : OPON (or LOGIN), OPOFF (or LOGOUT).
This feature is only available to multi-op logs.
If you entered a list of operators in the contest settings dialog when creating the log, it will be parsed to init the combo-box. You can also add ops "on the fly" to this combo box.
If you add nicknames to ops of this list (joe, jack, william, averell, josette or whatever - letters and numbers are accepted, allowing exotic nicks like l33t etc.), you can enter them as text commands to quickly change operator, without using the OPON command.
Op. callsigns are limited to 7 chars, while nicks are limited to 13 chars.
The operator changing is propagated across the network, meaning that if you login on a station, you will be automagically logged out of the previous one you were logged on (if any).
The ADIF file export includes the op callsign in the QSO record, if an op. has been defined for that QSO.
The text and CSV export files are also enhanced to allow the inclusion the op. callsign.

Bugfixes

Release information (3.18.0) (Nov 3, 2007)

General

New Features

< key will now switch to the previous field of the main log
> key will now switch to the next field of the main log

Bugfixes

Release information (3.17.0) (Oct 21, 2007)

General

New Features

For that, create/select a free COM port for "Control:" in the "microHAM USB Device Router", then select "microHAM MKII" as a connected device for the corresponding COM port in the "Interface Configuration" window of WT.
Tks microHAM company for great support!

Bugfixes

Release information (3.16.0) (Sep 7, 2007)

New Features

  • Under certain circumstances, the mode was not read correctly at the startup of Win-Test
  • Added the BandMap "Pass to Sub VFO" feature
  • When entering a frequency in the callsign field, the RIT is cleared (as far as it is enabled).
For the IRTS 75-year anniversary, make 75 QSO and you enter a draw to win a week for two in Kinnitty Casle (flights included). For detailled rules, see http://www.irts.ie/CQIR

Bugfixes

Release information (3.15.0) (Aug 8, 2007)

New Features

  • Receive QTC window:
$MYCALL: Send my callsign
$VALID: Save everything and close the window
$QTC: Send <group>/<number>
$NEXT: Move focus to the next QTC line
  • Transmit QTC window:
$MYCALL: Send my callsign
$VALID: Save everything and close the window
$QTC: Send <group>/<number>
$NEXT: Move focus down to the next QTC line
$13: Send carriage return character (specific to RTTY)
$TIME: Send time of the current QTC
$CALLSIGN: Send callsign of the current QTC
$SERIAL: Send serial number of the current QTC
$DONE: If all QTC are sent: mimic the + key
$SERIE: Send the QTC serie (specific to RTTY)
It is also possible to modify the label texts of the buttons for both the "QTC Transmit" and the "QTC Receive" windows. The variable $QTC can be used and will be replaced by the appropriate QTC group/number in the "QTC Transmit" window.
QTC groups and series will be highlighted in the RTTY window.
Assuming you receive the following sequence: 
  QTC: 65/2 QTC: 65/2
  0917-GI8HXY-146
  0918-G8UBJ-068
First click on one of the highlighted "QTC: 65/2": this will automatically open the "QTC Receive" window and fill the QTC group field.
Then click on each QTC serie highlighted lines. Again, they will be passed automatically to the "QTC Receive" window.
  • Orion
  • All kenwood Radios supporting CW-Reverse
  • All radios using a Kenwood-based protocol which are supporting CW-Reverse (Elecraft, SDR-1000).
  • All Icom which are supporting CW-Reverse.
  • FT-1000MP/MkV, FT-2000, FTDX-9000
Other rigs can be considered as far as the protocol can handle it.
Please tell us!
There is no setting in WT in order to enable/disable this feature.
Just set the CW Reverse on the radio, WT will remember that setting for the next time the mode must be programmed onto the radio.

Bugfixes

Release information (3.14.0) (Jul 25, 2007)

Features

Bugfixes

Release information (3.13.0) (Jul 23, 2007)

General

CAUTION : New network protocol version 1.20 released - Reminder : If you use WT in a networked environment, you must have the same WT version on all machines !

Features

  • The Run and S&P sets of messages are editable in the "Messages" Tab of the "Standard CW/RTTY Messages Configuration..." window.
  • Use CTRL+TAB to switch between RUN and S&P mode on the Primary Radio. The status of this mode is shown in the clock window. To change the mode of the Secondary Radio Window, use either SHIFT+CTRL+TAB or a mouse click on the appropriate control in the Secondary Radio Window.
  • It is possible to configure WT to automatically wipe the logged QSO or populate the Band Map when the operator changes the radio frequency, as soon as the Search & pounce mode is activated on that radio. This can be configurated from the "Band Map Properties" (right click in the Band Map windows).
NB: Search & Pounce is not activated by default. This can be done in the menu "Tools | Data Entry | Search and Pounce".
  • When that field is empty, WT assumes that the operator just called CQ, and then sends the INSERT message of the "RUN" mode.
  • When that field is not empty, WT assumes that the operator just replyed to a CQ, and then sends the INSERT message of the "S&P" mode.
  • This feature can be enabled/disabled in the "Options" Tab of the "Standard CW/RTTY Messages Configuration..." window. Other contests are not affected by this option.
Tks N6TV, K3LR, K0XP, N2NL and many others.

Bugfixes

Release information (3.12.0) (Jul 11, 2007)

Features

Bugfixes

Release information (3.11.0) (May 18, 2007)

General

CAUTION : New network protocol version 1.18 released - Reminder : If you use WT in a networked environment, you must have the same WT version on all machines !

Features

New option to display distances in miles in all windows except the stats windows where new items were added (Miles and avg mi/QSO) to ensure compatibility and consistancy. The objectives keywords allowed for distances are now :
Distance in km => KM DISTKM
Avg distance in km => AVGKM KMAVG
Distance in miles => MI DISTMI MILES
Avg distance in miles => AVGMI MIAVG
To avoid any confusion, the DIST and DISTANCE keywords are no more valid. A new field has also been added in the export function to get QSO distance in miles. Tnx K3LR, W9ZRX.

Bugfixes

Release information (3.10.0) (Mar 22, 2007)

Features

You can time shift selected Qsos by any amount of time amount in both directions. You can apply the time shift for the entire log, for the Qso entered by your own station, for Qso entered by several stns, or a range of Qsos.
Even if this tool is more supposed to be used after a contest, to correct a wrong clock setting, each time corrections is broadcasted to the other stns of the network by default. You can disable this broadcasting to save time, if not needed.
Note that time shifting is pretty CPU intensive and it may take a certain amount of time for large logs, because each Qso modification requires internal structures (mainly statistics) to be updated.
Note : Hesitating and wise users are encouraged to perform a backup of their log before proceeding. Time shifting can't be cancelled while it is in progress, to avoid any log inconsistency..
Note that it is still *one unique* field. It is only a display trick.
You can now display segments in the bandmap tab of the radio windows. Segments are defined by textual files with a .seg extension located in the Win-Test directory. You can use and display up to 10 files simultaneously, by selecting them in the Options / Data files / Segments files... menu.
Note that, because of the available area constraints, you can't have more than 5 segments displayed per band for a given frequency.
You can display or not the loaded segments by using the contextual menu item Display Options / Segments / Display. This setting can be different for each radio.
The syntax of the segments files is very basic, and are very easy to create with a simple text editor like notepad.
A segment is defined by its miniumum frequency (in kHz), its maximum frequency (in kHz) and an optional tooltip (30 chars max.). The two frequencies can be linked by an hyphen.
Two sample files are located in the WT repository: http://download.win-test.com/files/segments/
  • UsSegmentsDetailled.seg displays all band segments for every US licence type.
  • UsSegments.seg displays all band segments in which all US licencees are potentially active.
Tnx DL1MGB for inspiration.

- New feature : Markers for bandmaps.

You can now display markers in the bandmap tab of the radio windows. Markers are defined by textual files with a .mkr extension located in the Win-Test directory. You can use and display up to 10 files simultaneously, by selecting them in the Options / Data files / Markers files... menu.
You can display or not the loaded markers by using the contextual menu item Display Options / Markers / Display. This setting can be different for each radio.
The syntax of the markers files is very basic, and are very easy to create with a simple text editor like notepad.
As usual, you can double-click on a marker to set the current radio on the freq. of the marker.
A sample file is located in WT repository: http://download.win-test.com/files/markers/
  • NcdxfBeacons.mkr it displays markers for each NCDXF beacon.
Tnx DL1MGB for inspiration.


Bugfixes


Release information (3.9.0) (Mar 13, 2007)

Features

N+1 can be searched against the log, the callsign database (master database) or both.
It is possible to disable the N+1 search for the unique callsigns which are known in the callsign database. Look at this tool in menu "Tools | Check Log | Show Uniques".
  • QSO column : Includes QSOs (even invalid ones) but not the dupes
  • Dupes column : Includes dupes only
  • Avg column = Total pts for the band / QSO column (see above).
Tnx I2WIJ

Bugfixes


Release information (3.8.6) (Feb 26, 2007)

Features

Bugfixes


Release information (3.8.4) (Feb 8, 2007)

Features

  • Ctrl + Dbl click on a spot deletes this spot (no warning)
  • Alt + Dbl click on a spot loads the sub VFO (if applicable)

Bugfixes


Release information (3.8.0) (Jan 18, 2007)

Features

  • the ARRL DX to BAND/QSO/MULTS/DXCC/DUPES
  • the CQWW DX to BAND/QSO/CQ/DXCC/DUPES/POINTS/AVG
which is the usually used order. Tks K3LR.
  • in microHAM USB Device Router, check "microHAM SO2R protocol on COM port" in the "SO2R" tab. You can also specify "SO2R protocol controled" for RADIO 1 and/or RADIO 2 in the "ACC" tab if you want to let Win-Test control the ACC outputs to switch the antennas.
  • in Win-Test, select "MicroHAM MK2R" on the COM port the USB Device Router is attached to for SO2R control. As it is a virtual COM port, the COM port configuration (bauds, parity...) has no effect: you can choose anything.
The new macro $MK2R=<cmd> has been added in order to send any protocol to the MK2R from a scenario. This can be usefull to set a specific audio configuration which is not a standard R1R1, R1R2 or R2R2. For example, $MK2R=FRD100000010000 will configure the headphones audio to "Left=RADIO1,MAIN VFO and Right=Radio1,SUB VFO". Please report to the SO2R protocol specification of the MK2R to get details on the FRDxxxxxxxxxx command as well as on other ones.
Note that WinKey and PTT/CW events of the Win-Test integrated keyers are not handled by the protocol. It means that if you want to use Win-Key or the WT integrated keyers you must configure them separately. The PTT/CW signals can share the COM port used for the SO2R control. WinKey will require a different COM port in any case.
  • MMTTY window stays on top: when enable, the MMTTY window will be always visible
  • Only show FFT spectrum, waterfall and XY scope: when enable, the MMTTY window is minimized, and does not show the Menu nor the Command Buttons.

Bugfixes

Release information (3.7.0) (Dec 1, 2006)

General

3.7.0 introduces station profiles to help users who are frequently changing of callsigns / address etc... and an integrated file fixer for corrupted data files.

Features

Bugfixes

Release information (3.6.2) (Nov 23, 2006)

Bugfixes

Release information (3.6.1) (Nov 21, 2006)

Bugfixes


Release information (3.6.0) (Nov 20, 2006)

General

CAUTION : New network protocol version 1.17 released - Reminder : If you use WT in a networked environment, you must have the same WT version on all machines !

New Features

  • wt.exe [--alternative-ini|-i <inifile>] [WTB file to load] Tks DL6RAI.

Bugfixes


Release information (3.5.0) (Oct 22, 2006)

General

CAUTION : New network protocol version 1.16 released - Reminder : If you use WT in a networked environment, you must have the same WT version on all machines !

New Features

Bugfixes

Release information (3.4.5) (Oct. 8, 2006)

New Features

  • A timer ($QQSLT macro) or a counter ($QQSLC macro) are associated with these macros to determine if either a short or a long QSL message is to be transmitted.
  • That way you can send a most of the time a short QSL message to confirm the QSO in a pileup, sending your full callsign automatically every minute or 5 QSO only.
  • You can adapt the counter or timer values as well as the short and long messages in the "Intelligent Quick QSL" configuration window, from the Tools menu.
  • You can use the $QQSLC and $QQSLT macros either in the CW/RTTY Messages or in the advanced SO2R scenarios. It is also possible to use the feature in SSB (SO1R and SO2R not avanced) but this needs a specific configuration in the SSB tab of "Intelligent Quick QSL" configuration window.

Bugfixes


Release information (3.3.5) (Sep 20, 2006)

General

CAUTION : New network protocol version 1.15 released - Reminder : If you use WT in a networked environment, you must have the same WT version on all machines !

New Features

  • WT now accept SCP (stands Super Check Partial) plain text files (one callsign per line - no ordering required), DTA CT files and DTB files for compatibility.
  • The preferred format is SCP (plain text).
  • Furthermore, WT now also accepts specialised CheckPartial files by band and by mode for a given contest. This improves log accurancy and QSO rates.
Please, read: http://download.win-test.com/files/checkPartial/#_READ_ME_#.TXT for more informations.

Bugfixes

Release information (3.2.0) (Aug 30, 2006)

General

New Features

CAUTION: Modifications of the default settings must be considered with an extreme attention. It is reserved for very particular configurations or purposes, mainly used by expert users. You're on your own!

We offer some preset example configurations :
  • Silent time master : Can be used if the computer is used to *only* distribute an accurate clock. It will not appear in the status wnd of the other networked computers, but it will be listed in an INVENTORY command. Note that NO QSO will be recorded on (and sent from) this machine with this preset.
  • Silent backup : Can be used if the computer is *only* used for this purpose : It will not appear in the status window of the other networked computers, but will be listed in a INVENTORY command.
  • Packet sharing : Can be used if different stations are networked with different callsigns, do not want a common log, but want to share a commun packet stream. Can be used for several single-ops stations for example.
  • Silent log rebuilding : Can be used if you need to rebuild from scratch a complete log from networked stations, without appearing in the status wnd of the other networked computers, but will be listed in a INVENTORY command.
  • MIC : Enables the mic input when the VK is not playing
  • NOMIC : Mutes the mic input when the VK is not playing (*)
  • MICWHENPLAY : Enables the mic input when the VK is playing
  • NOMICWHENPLAY : Mutes the mic input when the VK is playing (*)
(*) Default settings.
  • VHFers can have a database of stations QRV on such or such band, to ask for a QSY.
  • Operators names
  • List of WT users ;-)
  • etc...
This feature is tailored to deal with few thousands of callsigns only. Don't try it with millions of lines !
If you modify an .xdt file while it is in use, you must reload it by using the "Reload files" item menu.
The # VARIABLE directive allows you to sent the extra information in a CW message by using a variable name. The variable name *must* begin with the $ character.
Example : # VARIABLE $OPNAME will substitute the $OPNAME string in the CW messages with the extra info included in this file, if the sent callsign has matching data.
CAUTION : The variable subsitution only works with the internal CW keyer for now.

Bugfixes


Release information (3.1.0) (Jul 27, 2006)

General

New features

  1. The exact callsign is searched
  2. If not found, the same country with the same zone is searched
  3. If not found, the same country whatever zone is searched
  4. In all cases a zone indicator is also displayed :
    • 'Z' means the current zone is already worked in the current country.
    • 'z' means the current zone is already worked in another country.

Bug fixes


Release information (3.0.0) (Jun 22, 2006)

New features

Retrieved from "http://wtdocs.maiers.de/wiki/Release_Notes_V3"
Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox