VUSC for Windows

VUSC for Windows

Version 6.38

1. VUSC - VHF/UHF/SHF/Contest for Windows

This program was developed for the VHF/UHF contests and it is a successor of the previous MS-DOS version. Operator experiences of contest stations OK1KRA,OK2KKW,OK2A,OL4A,DM7A and others have been used at its development. Of course any ideas for improvement are very welcome. Currently there are English, Czech and German program versions including the relevant manual.

2. Technical prerequisites

The program is designed for using on the PC with operating system Windows 98SE/Me/2000/XP/Vista/7/8. Program was not tested under Windows 95 or NT.

Hardware requirements:

· processor: at least PII at 200 MHz

· RAM: at least 64 MB

· free space on hard disk: about 5 MB, depending on the database size

· ports (optional): serial RS-232C (COM) (CW keying, elbug paddle, rotator control, TRX), parallel Centronics (LPT)(CW keying, elbug paddle, rotator control, band switch control), USB (rotator control)

· (optional) sound card, network card

The requirements on RAM size may vary depending on the database sizes and number of QSOs in a contest.

Software:

· Windows 2000/XP/Me/98SE/Vista/7, DirectX 9.0c or higher, LINX DLportIO Driver (optional, only when using parallel port LPT for keying/paddle or rotator and band switch control)

· MBUSB Driver (only when using USB port for rotator control, see the chapter on the rotator control). Currently the USB rotator control does not work under 64-bit Windows 7/8 as the MSUSB driver is not available yet.

3. Installation

Before the installation check the version of DirectX. It’s very likely, that some version of the DirectX is already installed in your PC. You can check it by running the program dxdiag.exe, usually located in C:\WINDOWS\SYSTEM32 or C:\WINNT\SYSTEM32. If there’s no DirectX or the version is older then 9.0c download it from http://www.soft32.com (search for the “DirectX Redistributable”) or http://www.microsoft.com/downloads/details.aspx?id=35 and follow the installation instruction.

A new installation of the VUSC is done by double-clicking on the self extracting archive file VUSC_setup_en.exe. The whole installation directory path must NOT contain any spaces, dots or hyphens!

If you intend to use the LPT (parallel) port for CW keying, band switching or rotator control, install the DLportIO driver by running Install.exe in the subdirectory DriverLINX\install after the VUSC installation. The MBUSB driver for the rotator control over USB is installed automatically when the interface is connected for the first time (see below the chapter 16 on the rotator control).

If you perform an upgrade of the previous version it's better to get a special upgrade archive file VUSC_upgrade_<version number>_en.exe. If you experience problems with the program start after the upgrade replace the file vuscwin.cfg in the installation directory by vuscwin.cfg from the subdirectory data or use one of the templates vuscwin*.cfg suitable for your display resolution (see below). In this case you have to renew your individual setting (CW/SSB memories, windows layout etc.), though.

As the setting of suitable fonts and window layout may be difficult for an inexperienced user, four sample configuration files (vuscwin1024.cfg, vuscwin1280.cfg, vuscwin1400.cfg, vuscwin1600.cfg) are supplied with the program for various display resolutions. For a new installation you can copy the one suitable for your display resolution under the name vuscwin.cfg and use it as a start point for your own configuration. You can also change the windows configuration for a different resolution dynamically at runtime by choosing "Options->Resolution". The windows layout and fonts are changed as set in the relevant configuration file (vuscwin1024.cfg, vuscwin1280.cfg, vuscwin1400.cfg, vuscwin1600.cfg). The other settings remain unchanged. Options->Resolution->User sets the windows layout and fonts as currently set in the configuration file wuscwin.cfg. You can use it to renew the right layout in case a window "disapears" or other problems with the windows layout. The program also creates the configurations file quickstart.cfg where all changes are stored while program running. This file is used to completely restore the current configuration when the quick restart is needeed (for instance during the contest after PC or program crash). It's read if you choose the "quick restart" when VUSC starts.

In rare cases there may be a problem with the (optional) driver DLportIO.SYS after the installation of some Windows system updates (which are usually automatically installed from the Microsoft Web server). For an unclear reason the update installation program changes the registry database entry for the DLportIO driver which causes driver load failure at VUSC start. The remedy is as follows:

Go to Start->Run type into the box regedit. Go to then to the folder:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\dlportio

Open it with double click and change the value of the key Start to 2 (the original value is usually 3). Check also if the file DLPortIO.SYS is in the directory under the key ImagePath (usually C:\Windows\drivers). Close the regedit and restart your PC. If the problem persists try to change the key value to 1 and reinstall the driver.

CAUTION! Make sure that you’re really changing just the key Start as described above. Some changes in the registry database may corrupt your Windows system. If you don’t feel sure about this ask someone experienced for help.

If you want to uninstall the VUSC program from your PC simply delete the installation directory and the relevant shortcut. As the program doesn't make any use of the Windows registry database it's not necessary to uninstall it in the Windows control panel.

4. List of files

The complete installation contains following file:

· VUSC.EXE - contest program

· VUS_BASE.ASC - ASCII database file sorted by stations

· VUS_BASE_DEF.ASC - default ASCII database file sorted by stations

· QSL_BASE.ASC - QSL database ASCII file

OWNH.HDR - stored individual data of the log header sheet

· CONTLIST.TXT – list of evaluated contests

· QSLTEM.HDR - QSL label form

· VUS.HDR - log header form for contests evaluated by distances

· VUS2.HDR - log header form for contests evaluated by locators/multipliers

· VUS3.HDR - log header form for Nordic Activity and Tesla Contest

· QRBPAT.DAT - file containing the point pattern for the evaluation by locators

· VUSC_EN.HTM - English documentation in HTML format

· SCHEMA_EN.JPG - scheme of CW keying and rotator interfaces

· VUSCWIN.CFG - configuration file containing CW memories, port settings and other technical parameters, window layout, font setting etc. There are also configuration file templates for various display resolution vuscwin1024.cfg, vuscwin1280.cfg and vuscwin1600.cfg to make the setting easier.

· QUICKSTART.CFG - a file similar to VUSCWIN.CFG used for the quick restart.

· RIVER.PNT, ISLAND.PNT, COAST.PNT, COUNTRY.PNT – Files with the direction map data.

· Drivers DLPortIO and/or MBUSB - optionally installed if LPT and/or USB should be used for rotator, band switch or CW keying

Following files are created while working with the program:

· #######.DIX - contest file

· #######.BIN - work file

· #######_$$$.LOG - log file from one band

· #######_$$$.EDI - contest log file from one band in EDI format.

· @@%%%%%%.EDI - contest log file from one band in EDI format for sending by e-mail named according to the general contest rules

· #######_$$$.LDB - sorted list of calls with their locators from the relevant band.

· #######_$$$.SUM - summary sheet of one band (calls with their contest numbers) as required by some contest rules.

· #######_$$$.QSL - file to print on QSL labels

· #######_$$$.ADI - file in ADIF format for upload to http://www.eqsl.cc/qslcard/

· #######_$$$.REM - list of QSOs with remark

· QUICKSTART.CFG - configuration file for the quick restart containing the most current setting

· QSL_BASE.DAT - QSL binary work file

· Subdirectory ####### for storing of logs, sound files, work file backups and other contest specific files. Only the files ######.DIX and @@%%%%%%.EDI are stored in the main directory.

####### - stands for the name of the contest

@@ - category number according to the general contest rules

%%%%%% - own callsign

$$$ - three characters band code:

144 - 144 MHz

432 - 432 MHz

129 - 1296 MHz

232 - 2320 MHz

340 - 3400 MHz

565 - 5.6 GHz

10G - 10 GHz

24G - 24 GHz

47G - 47 GHz

76G - 76 GHz

120G - 120 GHz

144G - 144 GHz

248G - 248 GHz

5. Program start

Before the start you should check the right local time and time zone setting in Windows. It’s not necessary to set UTC time on your computer provided the system time and the local time zone settings (including the daylight saving) are correct. The program allows later time corrections, but you avoid troubles and additional work if you start with the right time and zone setting.

Start the program by double clicking on VUSC.EXE file or the shortcut on the desktop.

If you work in the network it’s absolutely necessary to synchronize time on all computers after the program start, before the contest operation begins. Choose one computer with the right time and zone setting, open a contest, log it on the relevant band(s) and use the menu “Network->Band to synchronize” on other computers to synchronize the clock and time zone (see the chapter on the Network operation for details). Not adhering to this may cause data lost or damage.

The program is designed for minimal display resolution 1024x768 pixel. Optimal resolution is 1280x1024 or higher. You can change the size, layout and fonts ("Options->Font") of all windows to match them to your display and individual needs. When choosing the fonts of the log grid choose one of the nonproportional fonts, so the cursor position always fits to the characters. The most common nonproportional fonts are:

Andale Monospace, Arial Monospace, Consolas, Courier, Courier New, Letter Gothic, Lucida Console, OCR-A, OCR-B, MICR, Typewriter, Typewriter Elite, Typewriter Gothic.

Also choose the fonts of the column headers so the column width fits to the fonts of the log grid.

You can close most of the windows you don't need by clicking on the cross in the header bar. For technical reasons some windows are permanent and can't be closed. Closed windows appear again when the program is started. All windows can be minimized in an icon by the right click on their header bar and choosing "Minimize". If the configuration is saved the windows stay minimized even after the restart. The minimized windows can be restored to their original size and location by double clicking on the icon. If you terminate the program with “Contest->Exit” the current configuration setting is automatically saved in the file vuscwin.cfg for the next start. The configuration can be saved also explicitly by using “Contest->Save config”. If you choose "Quick restart" at the program start, the configuration file quickstart.cfg is read instead of vuscwin.cfg. This file contains the latest configuration including the open contest, network connections etc. before the program close (or eventual crash) to renew the latest state.

In rare cases the program may crash after the start. A bug in the sound card driver was indentified as a most common reason. The driver crashes when a DirectX function is called. In such a case start the program from a command line "Start->Run" with the argument nosnd:

vusc.exe nosnd

It switches off the sound card entirely. Of course the funtionality depending on it can't be used (SSB CQ call, CW monitor and audio recording). On the other hand the CW keying works OK without the sound card. The parameter "nosnd" can be also added to the shortcut on the desktop if needed.

6. Contest operation

The program VUSC has primarily been designed for on-line usage by the operator during the contest. To open a new contest, choose the menu item “Contest->New” and enter the contest name, contest (evaluation) type, own locator and callsign. There are following supported contest (evaluation) types:

"Distances"

"Locators w/o multipliers"

"Locators with multipliers"

"Czech Activity"

"Nordic Activity"

"AEGAN Contest"

"AGCW Contest"

"Tesla Memorial"

"Dutch Activity"

If you use the type “Locators with/without Multipliers” you can supply your own file with the point pattern for a specific contest. Take a look at the default file QRBPAT.DAT for an example. You can also open an existing contest file with “Contest->Open”. Following file formats can be read: VUSC specific format (extension ".dix"), EDI format (".edi") or a crash recovery file (".bin"). These file types can also be merged to an open contest using the option "Contest->Add". CAUTION! The QSOs on the same band and with the same contest number will be overwritten with the QSOs from the file. A text file ("*.txt") can also be added to an open contest (menu "Contest->Add"). The text line format must look as follows:

<YYMMDD> <HHMM> <Call> <RST> <QSO number> <Received RS(T)> <Received number> <Locator>

Field delimiters are any number of spaces and/or tabelators.

The old *.DIX files from the MS-DOS VUSC version higher then 4.03 can be opened, but they are automatically converted to the new Windows format when saved and can not be used by the MS-DOS version any more.

At the program start you can choose the option "Quick restart". In this case the last contest is opened, all network connections and other settings are restored including displayed bands, network messages and todo list. Also synchronization can be made from the relevant bands (details see the chapter on the network operation). The program is designed for the direct use in the contest; no paper log is needed. The contest data are secured, so they don’t get lost even if the program and/or computer crash for any reason. Only the last QSO currently being entered may be lost. In such case (if you don't use the option "Quick restart") open the contest file with the relevant contest name having the extension “.bin”. If a ".bin" file with the same name exists in the same directory when opening a ".dix" file (i.e. the program was not correctly closed) a warning message is issued and you can choose if you want to read the original file or the crash recovery copy containing the most recent state (this also applies for the quick restart). In addition you can write backup copies (for instance on a flash disk) at any time during the contest by using the "Save as" menu option or program automatic periodical backup copy saving in the menu "Options->VUSC".

The log has a classic form. It means that the QSOs are entered as they have been made in time and all fields (including QSO number) can be changed at any time also in previous records (the same approach as in the CT contest log from K1EA). Only be careful when manipulating QSO numbers because the other stations have them already in the log. Also avoid putting higher QSO number before the lower one or entering two or more QSOs with the same number as it can overwrite existing QSOs on other nodes in the network.

Normally you move over the input fields using SPACE or TAB key. For changing the other fields, click on them with mouse. Another option is to invoke a special typeahead window ("Options->Typeahead"). The items can be typed there in any order and entered with the key RETURN similarly as for instance in the program TACLOG. The program automatically distinguishes the data type, which is also indicated in the lower part of the window. If the automatically determined type does not fit it can be changed by using the SPACE key.

After bad experiences with too restrictive input data checks, the program allows to enter double and/or incomplete QSOs. All data can be changed at any time and all changes are immediately reflected in the entire log and also updated on other computers (nodes) in the network if it's used. For faster data entering it is possible to omit the callsign prefix and report 59(9). Also the first two letters of a locator if omitted are automatically extended, first according to the callsign prefix, then (if the prefix is not found) for the area of one big WW locator around your own QTH. The boundaries for this area can be changed in the setting “Options->VUSC” “North-South default border” and “East-West default border" as well as the default callsign prefix.

To avoid unintentional data change (especially by unexperienced operators) you can lock the entered QSO. In such case a confirmation of the warning message is needed to log the change.

The current UTC time is automatically supplied, if not entered manually. If you work in the network the clock must be synchronized (see above the previous chapter). It’s absolutely necessary to synchronize time on all computers in the network after the program start (using "Network->Band to sychronize"), before the contest operation begins. Otherwise the data may be lost or damaged!

For a quick filtering of calls when checking an incomplete call/locator received you can use meta characters "*" and ".". The "*" matches a string of any characters, the "." matches just one character. To make the usage of meta characters clear look at the following examples:

If a string like DL.KN is entered, all callsigns of set DL1KN, DL2KN ... DL0KN with their locators and bands are displayed in the window "Current contest check". Similarly if you enter *KN all callsigns ending with KN are displayed. The same rules apply for locators.

The program VUSC uses 2 databases for checking the callsigns, locators and bands from previous contests. The first one is the locator database. The search results of the locator database are displayed in the window “Database check”. There are 3 possible checks. The locator check (F9) - the callsign must be completely entered except for /P, /A and similar extensions. A list of all locators from the previous contests for this callsign is displayed. The callsign check (F10) - the locator must be entered completely. The “super check” (F11) - searches for records containing partials of callsigns and locators. For the check "locator->callsign" (F10) the complete locator must be entered. The first number at the displayed records means the number of occurrences of the combination call/locator in previous contests, the second number is the azimuth from the current QTH as soon as it is known after opening of an existing contest or creating a new one. You can set which of the 3 checks is performed by default when entering callsign/locator by using "Options->VUSC->Default database check". Normally you should use "Super Check" for checking partials. However, on less performant PCs you may experience some delay when entering the callsign/locator especially with the large database. In this case set the default option to "Call Check", which needs less system resources.

If you have activated the ON4KST connection (see the chapter about the packet and DX cluster below) records with callsign and locator from this source appear also in the database window with the special label KST instead of number of QSOs.

The data from the database window can be copied into the log by double clicking on the relevat line.

The second database contains the information about the bands on which the particular callsign has been worked with. Its results apear in the "Current log check" window in blue under the header "QRV on:". The information can be used especially for negotiating skeds on the other bands.

Apparently wrong database records in the locator database (for instance if a locator differs only in one letter against the currently received locator) can be marked and removed from the database by clicking on it and deleting with DEL key or by choosing "Delete" from the menu. The records are permanently deleted from the database only if you respond “Yes” to the question "Do you want to permanently remove deleted records from the database?" when ending the program.

For general overview different types of statistics including the direction map can be selected in the menu in the window "Statistic" including a direction map for each band. The window size and position is automatically changed according to the chosen statistics so the map or graphs are correctly displayed, but it also can be changed with the mouse as you choose.

To enter and edit the QSO records use following keys:

Arrows UP, DOWN - move over the records.

Arrows LEFT, RIGHT - move inside of one field.

SPACE - move to the next field right

TAB - move to the next field left

Home - move cursor to the begin of a field

End - move cursor to the end of a field

Page Up - list of one page up

Page Dn - list of one page down

INS - toggle insert/overwrite mode

CTRL/Page Up - jump to the begin of the log

CTRL/Page Dn - jump to the end of the log

Delete - delete character under the cursor

Backspace - delete character left from the cursor

CTRL/W, F12, ALT/W - wipe out a not finished QSO

CTRL/N – enter a remark to a QSO, it's indicated in the column RM of the main window

Return, Enter – Save a new QSO or confirmation of changes of an existing QSO, without the confirmation no change is made and the old data are restored.

CTRL/Return - same as Return, but in addition a window for entering the band and frequency for a sked appears and a message is sent to another node in the network according to the chosen band.

Right click on a QSO – Context menu with the most frequent QSO operations

Function keys:

F1-F8 CW/SSB memories (see below)

ALT/F1-F8 CW/SSB memories with repeating (see below)

F9 - locators database check for a call

F10 - calls database check for a locator

F11 - super check partials of calls and locators

F12 – wipe out current line

General control keys:

ALT/A - database window

ALT/B – band selective display

ALT/C - packet window

ALT/D - band down

ALT/E - start QSO edit menu, also the right mouse click on a line

ALT/F – find a call

ALT/G – create log

ALT/H - help

ALT/I - QSO context menu (the same as the right click)

ALT/J - to do window

ALT/K - not used

ALT/L – switch to the message window in network mode (see below)

ALT/M – mode change CW/SSB

ALT/N – send CW from keyboard

ALT/O – open a contest

ALT/P - not used

ALT/Q - quit the program without saving any file. All data entered/changed since the program start is lost. Only a copy of the work file (*.bin) is saved in the directory of the same name as the contest for security reasons.

ALT/R – log recalculation

ALT/S – send sked menu

ALT/T - time shift and/or system time set up. It serves for correction if time was wrong set at the contest start.

ALT/U - band up

ALT/V - statistics window

ALT/W – wipe out a not finished QSO

ALT/X - program exit with saving of the contest file and configuration changes (file vuscwin.cfg).

ALT/Y - not used

ALT/Z - band map window

ALT/- - CW speed down

ALT/= - CW speed up

ESC - return to the main window

Sound recording control:

CTRL/R – record

CTRL/S – stop record/playback

CTRL/P – pause record/playback

CTRL/B – back (playback)

CTRL/E – forward (playback)

Rotator control:

CTRL/< - turn left

CTRL/> - turn right

CTRL/space - stop

CTRL/? – turn to the azimuth of the current QSO (if valid)

The technical parameter setting (ports, packet, connector pins, sound card etc.) is described in the relevant chapters below.

7. Contest evaluation

If the network was not used during the contest the logs from diverse bands can be merged into one file with the “Contest->Add” function. The separate evaluation band by band is possible, too. You start the evaluation of the relevant band from the menu option “Create Log”. In the following dialog choose the band and fill out the header page. All entries for every band are stored in the file OWNH.BIN, so you don't need to repeat the constant data as first operator's name, QTH etc. By editing of files VUS.HDR (evaluation by distances), VUS2.HDR(evaluation by locator and multipliers), VUS3.HDR(Nordic activity contest) and QSLTEM.HDR you can change the format of header page and QSL label. In the file QSLTEM.HDR the strings in the format @n@@# are placeholders for the QSO data. You can change their order and/or layout on the QSL label or they can be omitted as well. On the other hand the item length can not be changed except of the contest name. The numbers denote the QSO items as follows:

1 - contest name
2 - own callsign
3 - own locator
4 - call
5 – date
6 - time
7 – band
8 - own RS(T) and contest number
9 – mode
10 – power
11 - antenna

In the files VUS.HDR, VUS2.HDR and VUS3.HDR it is only possible to change their layout. The strings @@@@@ are used as placeholders for the variable header page data.

The following files are created after the evaluation for every band:

· contest log from a band to print (*.log)

· sorted list of calls with their contest numbers (*.sum)

· contest log in the EDI format for electronic exchange (*.edi)

· sorted list of calls with their locators used for the database update (*.ldb)

· file with the QSL labels to print (*.qsl)

· ADIF format file for QSL upload and other purposes (*.adi)

· file containing the QSO with remarks (*.rem)

The first two files are to be printed; the EDI-files are for the electronic data exchange (e-mail, web upload etc.). The *.ldb file contains data for the database update (see below). The next two files deal with QSL. The first one contains labels for QSL to print, the other one is for the electronic QSL exchange via http://www.eqsl.cc/qslcard or similar servers. The program does not print the files directly, due to the very wide spectrum of printer types with various control character sets. The files contain only the ASCII data in pages separated by <FF>. For printing it is recommended to load the file into any word processor/editor (for example MS-Word) and format the output according to your needs. In the worst case the files can be printed using the command in the command prompt window:

print /D:<printer name> filename

The files are formatted 38 row and 76 columns by default. Do not forget to sign the statement on the header page when sending the paper log.

8. Database maintenance

As mentioned before there are two databases callsign/locators and callsign/bands. Users can build up their own databases from the previous contests. Sample databases contaning about 500 records are provided with the program. For a routine database update after the contest reply "Yes" to the question "Do you want to update the databases?" at the end of the evaluation run. The information about callsigns, locators and band from the currently evaluated contest/band are entered into both databases. Also the records in the locator database marked for deletion during the contest (see above) are permanently removed. Every time a new contest/band is evaluated the occurrence counters of the combinations call/locator are bounced. The contest name is entered then in the file CONLIST.TXT to avoid double processing of the same contest/band.

The primary database files are VUS_BASE.ASC and VUS_BAND.ASC. The files are in ASCII format and can be edited with any text editor (Notepad, WordPad, etc.). You can fix errors like cancelled prefixes, typo errors etc. The file CONLIST.TXT can be edited as well for eventual reprocessing of a contest/band. Before updating databases the old versions are saved in the files VUS_BASE.OLD and VUS_BAND.OLD. If any error occurs you can renew the previous state by renaming them back to VUS_BASE.ASC and VUS_BAND.ASC. If you decided not to update a database during the evaluation (not recommended) you can do it later by using "Contest->Database->Add file". In the following dialog window select the file <contest name>.ldb (the sorted file with the calls and locators created during the evaluation of the particular contest/band) in the contest directory and open it. The same method can be used to include informations into the locator database from other sources or even to merge two locator databases. The file must have following format:

The separator is any number of spaces or tabs. If the number of QSOs is not present it defaults to 1.

After manual editing of the locator database file or contest evaluation you can read in the new database into memory using "Contest->Database->Check and load". The database is checked sorted and read in. It applies only for the locator database, the band database is updated only with the contest/band evaluation.

If the locator database file is not found or the check at the program start detects errors an error message is issued and the default database file VUS_BASE_DEF.ASC is opened.

If you upgraded VUSC from the previous version without the band database you can fill it using following procedure:

1. Backup the files VUS_BASE.ASC and CONLIST.TXT into a separate directory.

2. Delete the file CONLIST.TXT from the VUSC directory.

3. Start VUSC and open and evaluate the contests/bands from which you want to update the band database.

4. Delete the files VUS_BASE.ASC and CONLIST.TXT from the VUSC directory.

5. Copy VUS_BASE.ASC and CONLIST.TXT from the backup into the VUSC directory.

The database maintenance changed significantly since the version 6.34. The utilities tr.exe, usort.exe and dbase.bat are not used any more and can be deleted from the installation.

9. QSL maintenance

The evaluation program supports also printing of QSL and a small database of the QSO for which the QSL has been sent. There are several processing options:

No QSL – no QSL are created.

All QSL - QSL for all QSOs of a band are created.

New QSL - only QSL for the new QSOs (which are not in the database yet) are created.

Update QSL Database – if checked, the QSOs are written into the QSL database.

A QSO is considered to be new if the callsign is new and/or the band and/or the locator. Database ASCII file (QSL_BASE.ASC) is sorted by the callsigns and bands and it can be edited by any text editor (Notepad, WordPad) in order to correct mistakes. If you insert a line you have to regard the right sorting. Unlike the locator database this one is updated automatically during the program run. The file QSL_BASE.DAT is only a work file without any other meaning. As mentioned above the ADIF file (extension *.adi) is to upload to http://www.eqsl.cc/qslcard , LoTW or for other purposes.

10. CW/SSB control

The program VUSC supports direct CW keying and elbug paddle connected to the serial or parallel port as well as the SSB modulation of the TRX. The circuits and the default pin-out are described in the appendix below. The pin-out can be changed in "CW/SSB/Packet->Setting". Note that in case of paddle connected to the serial port there is no galvanic connection between the cable shielding (i.e. also paddle body) and the PC ground. Therefore you should avoid direct contact to the TRX or PC ground. Normally leave the check box "Virtual Ports" checked so both physical and emulated COM ports (USB Adapter) work. Uncheck this only on old PCs with physical COM ports if you experience problems with the keying and/or paddle.

There are 8 CW/SSB memories, which can be programmed and used for the automatic keying or modulation. The memories can be maintained with "CW/SSB/Packet->Program CW" or "CW/SSB/Packet->Program SSB". They are also stored in the configuration files vuscwin.cfg and quickstart.cfg, so they are permanently available. The following symbol variables can be used for the CW memory programming.

$O - own callsign

$C – callsign of the current QSO

$L - own locator

$R - report of the current QSO

$Q - report with short nines

$N - contest number of the current QSO

$M - contest number with short zeros

$<1-8> – memory content under the keys F1-F8

In addition to the standard CW characters there are also following composite characters:

+ - AR

\ - correction

) - BK

( - KN

% - AS

* - SK

When programming the CW memories you have to pay attention not to create a loop by putting a memory symbol ($number) into the same memory or even indirectly through another memory. The program would work, but after stack exhausting the keying would be automatically stopped. For every memory a button label can be also defined to identify the assigned memories.

The speed can be changed from 6 WPM to 60 WPM by using the slide bar in the "CW/SSB control" window or shortcuts. The keying can be done either directly from the keyboard in the window "CW/SSB control" or with the paddle. You can enter all symbol variables as well. Sending can always be interrupted by hitting ESC, by touching the paddle or clicking on the button "Stop" in the "CW/SSB control" window. The CW keying is possible only in the CW mode. The following shortcuts can be used:

F1-F8 - memory send

ALT/F1-F8 send CW/SSB memory with repeating

ALT/= - increase the speed by 1 WPM

ALT/- - decrease the speed by 1 WPM

ESC – interrupt and return to the main window

ALT/N – direct CW input from the keyboard

The program also supports WinKey or MicroHam for CW keying. Set the relevant COM port for the communication under "Port key/Winkey" and check the boxes "Winkey" and "Virtual port". For some unclear reason the USB router (needed for communication with MiycroHam - see its documentation) filters and changes some WinKey commands. Therefore the speed limits and PTT times setting for Winkey must be set identicaly in VUSC and in the USB router. The speed can be controlled from the program as well as by the WinKey (MicroHam) potentiometer.

For the TRX SSB modulation (usually CQ) you have to prepare the WAV files by using the Sound Recorder in Windows or similar program.

The CW or SSB memory can be sent also in the repeat and pause mode. Set the parameters in the "CW/SSB Control" window, choose the memory to repeat and click "Start". Clicking the button "Stop" , hitting ESC or touching the paddle terminates the keying. The shortcut keys <ALT>/F1-F8 play the relevant memory with repeating using the current parameters.

The headphone output of the sound card is the best choice for the TRX modulation. Some computers have also the volume control of this output, which can be used for the optimal modulation level setting. Otherwise you have to use a resistor trimmer. Of course a shielded cable is necessary for the connection between the computer and the TRX.

11. Network operation

The network enables the communication of connected computers, sending of QSOs, skeds, synchronization, sending of messages among them, packet sharing etc. A connected computer is called a network node.

The network is in “disabled” state after the program start. It means just limited network functions are enabled. This avoids the receiving the QSOs from other nodes and other log related operations before a contest file is open when for example a node has been taken into operation when a contest is running, the node had to be restarted etc. The full network functionality is enabled by unchecking the "Network->Disable" menu item. Do it only when the contest is open on the local node and synchronization (see below) has been made. The contest file name must be the same on all nodes in order to avoid operator mistake and overwriting the contest log with one from another contest. The network is also automatically enabled when a node is logged on a band.

After opening a contest a node can (but does not need to) be logged on (assigned to) one or more bands. The band(s) for a particular node can be entered by "Network->Own band". The network is then automatically enabled for this node. The skeds scheduled on other bands can be sent to this node (see below). The assignment of bands to nodes is displayed in the window "Nodes". Only one node can be defined for a specific band, but one node can serve for more bands. The assignment is valid until a new node is assined to the same band. For assigned nodes their IP addresses are displayed. The bands which are not assigned to a node are marked with 0.0.0.0. Automatic network search for on-line nodes is performed when the program is started or a new band is assigned. The same check is made always when the node list is refreshed by clicking the button "Network ping"; an "A" (active) next to the IP address means an on-line node, an "O" (own) own band. The program automatically checks the network connections every 20 seconds and updates their status (network heartbeat).

A new or changed QSO on any node is sent automatically to all other nodes after hitting the RETURN key.

If a node is assigned to a band the skeds on this band sent from another node (band) are displayed in the "To Do" window. By double clicking on an item in the "To Do" list the QSO is copied into the current line in the log. The skeds which could not be made can be deleted from the "To Do" window by pressing DEL key.

For relaying information among the nodes a text message can be sent either to a specific node or to all nodes in the network by using ALT/L or by clicking into the input line of the window "Network Message". Only nodes assigned to a band can be chosen as a specific message target.

If any information on a node gets lost during the operation (for example computer crash, network connection interrupt, later connection to the network etc.) you can synchronize the local log with a log of another node using "Network->Band to synchronize". At first the system time and zone setting is transferred. Then you can choose either the transfer of the complete log from the node or just the selected band. A message with the number of QSOs to transfer is issued at the transfer beginning and the message "Synchronization complete, nnn QSOs transferred" indicates the successful completion. Use the synchronization also when an inconsistence in QSO numbering on the network is detected. Again it’s very recommended to synchronize all nodes in the network before the contest in order to ensure the identical time setting. If any problem occurs during the synchronization, the synchronization is automatically interrupted after 5 seconds time out. The broken synchronization can also be reset by disabling and re-enabling the network ("Network->Disable").

If a new QSO is inserted/changed from a foreign node (i.e. which is not assigned to the relevant band) a confirmation is required, because it can cause double numbering on this band. The same confirmation is needed if a band is overtaken by another node.

When running secondary nodes (for example a second search and pound working place in the VHF contest) on one band use the button "Book #" for requesting a contest number from the node which is assigned to the relevant band in order to avoid double QSO numbering. The number is booked with regard to the current state at the primary (usually run) node. If the operator entered a call and moved to the next input field, the QSO number will be blocked for this QSO and the other operator at search and pound node will get the next available number.

12. Network – installation and configuration

The program VUSC for Windows utilizes the TCP/IP network protocol. You have to configure it before the operation. If there’s a DHCP server in the local network you don’t need to do any other configuration except checking the firewall setting (see below). If not, you have to set fix IP addresses for every node. Choose the network TCP/IP protocol configuration of the relevant network interface in the "Start->Control Panel" and set the IP addresses. Use the address range 192.168.x.x, network mask 255.255.255.0 or any other general recommended range for local networks. Do NOT use the automatically Windows set local IP addresses (usually from the range 162.254.x.x, mask 255.255.0.0). In Windows XP or 7 you can take advantage of setting the fix IP address as an alternative TCP/IP setting so it's automatically used when no DHCP is active in the local network. Check your setting by command ”ipconfig” in the command prompt window and also check the connection between the nodes with the ping command.

If you’re using firewall software on the individual nodes, make sure that the VUSC port # (default 5068) is enabled in both directions for VUSC and also broadcast packets are allowed. CAUTION! Some freeware firewalls in their free versions (for example Sygate Personal Firewall) don’t support allowing broadcast packets for a single application. In this case it’s better to switch the firewall off. If this is not possible for security reasons you can check the option "No broadcast" on ALL nodes and enter the IP addresses for individual bands manually in "Network->Setting". You can even use this method for connecting remote nodes in non-local networks (for example over the Internet), where the broadcast packets can't be relayed.

If an individual node in a foreign network is behind the router define either a port trigger for the VUSC port or define a fix routing rule for the packets from the VUSC port to the IP address of the node where VUSC is running.

In the network configuration you can also choose the relevant network interface if there are more installed on your PC. The network is re-initialized in this case, i.e. the network is disabled and you have to assign the node to the relevant band(s) again. The same applies if you change the VUSC port.

13. TRX control

VUSC supports control of certain TRX types over the serial interface. Most of the ICOM types (with the CI-V protocol) and KENWOOD types are supported. Also Elecraft K3 is supported as it's using the KENWOOD protocol. Since every YAESU model has different control protocol, only FT1000MP, FT847, FT897D and FT736R are currently supported.

First you have to connect the serial ports with the proper cable (the cable type can be different for various TRX types - straight or null modem, check the TRX manual) and set up serial connection and other parameters in the menu "TRX->Setting". Since the computer can be assigned to more bands and (especially on the microwave bands) the transverters are often used you have to set the band on which the TRX works and eventually the frequency offset. The computer must be also assigned to the same band on the network on which the TRX works to display the frequency and mode even if there are no other computers on the network. Then you can choose in the menu "TRX" the appropriate TRX type to activate the connection. After activating the operating frequency and mode are displayed in the window "Nodes" (this information is automatically sent to other nodes on the network). Also the current frequency is displayed in the "Band map" window. With a double click on a spot in the band map the TRX is tuned to the spot frequency and the callsign is copied into the log. If you want to change any setting and the TRX connection is active you have to close it first using "TRX->Close".

For ICOM TRXs the ICOM-address has to be maintained accordingly and on some ICOM TRXs you must also ensure that the menu item 38 (CI-V Transceive) is set to OFF on the TRX side.

14. Packet radio, DX cluster and ON4KST chat

The packet radio operation is supported for modems as of TNC2 standard (currently TNC5+) and for Internet servers using the telnet protocol. For the modem connection to the COM port, use the standard null-modem cable (see the modem documentation). The communication parameters (port, speed etc.) can be set in "CW/SSB/Packet->Packet/Chat Setting". The communication with the modem works only in the terminal mode. It means that some settings (as for example channel select, own call, TX delay etc.) must be done manually after starting the program and modem. See the modem documentation for details. The speed, port and other parameters are also stored in the file vuscwin.cfg. To connect to a modem (or a telnet server) use the menu "Packet->Connect/Disconnect" in the Packet window.

For telnet servers an IP address or a server name and the port number must be set. The most used servers with their parameters are preset in the program and can be selected from the list. Other servers you find on the web page http://www.iw5edi.com/ham-radio/?dx-cluster-telnet-links,65 .

If the local network is active the computer with the packet connection can work as a packet server for those computers on the network on which the option "Packet Remote" has been chosen. Check the option "Packet->server" in the menu of the packet window. The packet server IP address is also displayed in the network "Nodes" window. The current packet configuration is displayed in the title of the packet window.

The communication with the TNC modem runs in the terminal mode. So it may be needed to set manually some TNC parameters which the special packet programs set automatically, especially own callsign (TNC command I), modulation delay (TNC command T), channel select (TNC command S) etc. The TNC commands (escape sequences) are entered in the lower line of the packet window beginning with the * (star) character.

For better overview the DX spots from the packet are gathered into the Band map window. Four lists are maintained for 2m, 70cm, 23cm and microwave bands. You can choose them in the menu "Band". The new spots are displayed in blue, the spots with already made callsigns in black. By checking the item "Band->Filter Made" these spots can be filtered out. For microwave bands a bit mask in hexadecimal format can be entered in the dialog “Options->VUSC”. The mask determines the relevant microwave bands of the current contest on which a QSO must be made for a spot to be considered as made. The bits correspond to the bands from the least relevant one. For example 68 (hexadecimal) means 13cm, 6cm and 3cm bands, 78 means 13cm, 9cm, 6cm a 3cm, E8 means 23cm, 6cm, 3cm a 24GHz etc. The spot is considered to be completed if a QSO is made on all so selected band. With the "Band->Wipe" the whole map for a band can be cleared. In the dialog "CW/SSB/Packet->Packet/Chat Setting" time out can be set after which the items are deleted from the list.

Except of the normal DX cluster nodes it is also possible to connect to the ON4KST chat using the telnet connection type. You have to have an user account on ON4KST chat. Get the registration on the www.on4kst.com if you don't have it. Fill its name (usually callsign) and choose the server info.on4kst.com in "CW/SSB/Packet->Packet/Chat Setting". Choose "Packet->Connect" in the Packet window and enter the password and the chat number as the server prompts. The DX cluster spots work as usual and come into the relevant lists in the "Band map" window. Except of the DX spots the program also gathers the callsigns and locators from the logged on users and display them in the list "Spots->ON4KST users". According to the current selected band the already made callsigns are displayed in black, the new ones in blue. Double click on an OK4KST user enters /cq in the packet communication line so a direct message can be typed and sent to the station. The user list is refreshed automatically every 20 minutes or directly using the command "/sh us" in the packet communication window. If you need to refresh the spot lists use the command "/sh dx 100". Check out the "/help" command for other ON4KST chat options. The chat messages are displayed in the packet window in black; the message directed to you is in red similarly as in the web chat.

The callsigns with locators from the user list are also displayed in the Database check window with the special label KST instead of the number of QSOs. Be careful when using it, though as a lot of stations are logged on with an incorrect locator.

15. Sound recording

If you have troubles with receiving a DX station it may be useful to record the signal for further examination. Choose the microphone as a signal source and disable the other ones (mute) in the recording sound mixer control. Double click on the little speaker on the Windows task bar to get the mixer control and go to the menu "Option->Properties->Recording" to get the recording controls. Use a shielded line to connect the TRX speaker with the microphone input on your PC and set the appropriate signal level so the record is not distorted.

The sound recorder controls are record, play, back and fast forward. You can choose either the button controls or shortcuts mentioned above. The usage is similar to a normal tape recorder. The sound files *.wav are stored in a subdirectory of the same name as the contest. Their name consists of time stamps of the record start and end, record hour and minute and the callsign. The hour, minute and callsign is taken at the end of the recording. Beside the normal controls storing of a QSO with <Enter> ends up automatically the recording. The file size is about 1MB per minute. You should be careful when using the recorder in order not to fill your hard disk with the sound files.

When the recording is running the seconds are counted in the main window. One second represents about 1MB of the disk space. The files have the standard *.wav format and can be played by any player or further processed.

16. Rotator and band switch

The rotator control is possible over LPT, COM or USB port. For LPT and USB a simple hardware interface is needed. You’ll find the schema in the appendix below. The COM port control supports Yaesu and SPID rotor standards (for more information see the relevant Yaesu/SPID documentation). You may experience some delay in the rotator position display when using the SPID rotator. It is due to low communication speed supported by the SPID firmware, which, unfortunately, can't be changed.

A feedback potentiometer (or another sensor device which delivers lineary proportional voltage from 0 to about 4.5V) as position indicator is a prerequisite for the interface using USB or LPT. The potentiometer value can be from 100 ohms to about 30 kohms. The higher feedback potentiometer value increases the risk of interference voltage being induced in the connection wires when transmitting. The output of the external sensor is to be connected to the point C (see the schema).

The interface is designed with an 8-bit ADC which has sufficient precision for normal contest antennas. However, if the LPT interface is used, the program is able to evaluate 9th bit on the ACK signal (pin 10). In this case you can replace the A/D converter with a type with more bits and achieve higher precision (for example for a dish antenna). The power supply for the feedback potentiometer can be from current or voltage regulator (see the schema below). Both options have pros and cons. The voltage regulator requires 3 wires to the potentiometer, but it can be used with different potentiometer values (i.e. different rotators) without any adjustment and the power supplies for the interface and the motor can be galvanically separated for safety reasons. The current regulator needs only 2 wires, but it must be adjusted to a particular potentiometer value and the interface and motor must have at least common ground or a separate power supply of about 12V must be used only for the current regulator (see the schema).

For the USB interface the programmed PIC circuit CY7C63001C-PXC (order Nr. CY7C63001PFW variant 1) is needed. It can be ordered together with the Windows driver MBUSB at the company AK MODUL-BUS GmbH on the web page http://www.ak-modul-bus.de for 15,- euros. Unfortunately the web page is only in German, but the ordering is simple. On the web page find the field "Suchbegriffe" (Search) and type CY7C63001C. You will see a couple of links, choose "Mikrocontroller CY7C63001C-PXC mit Firmware". On the next page check under the title "Bestellen" (Order) if the order number is CY7C63001PFW and choose "Port-Chip Variante 1" in the field below. Put the number of pieces into the field "Anzahl" (Number) and click on the button "In den Warenkorb" (In the cart). This puts your order into the cart. Click then on the icon Cart in the upper right corner and you'll get to the check out page in English. Major credit cards as well as PayPal are accepted. Download also the latest driver version from http://www.ak-modul-bus.de/cgi-bin/iboshop.cgi?show1200000510,254447591177330 or click on Downloads on the ordering page. Under the title "Treiber für den Mikrocontroller CYC63001 mit der Firmware Port-Chip Variante 1" oder "Port-Chip Variante 2" click on "Details" and click "Download starten" on the next page. The archive zip-file contains files MBUSBprt.sys and MBUSBprt.inf. Extract the files into a separate directory. You can also use the driver supplied with the VUSC installation. Driver installation is performed automatically when the PIC gets connected to the PC for the first time. Windows will find a new hardware and ask for a driver. Enter the directory with the extracted files and finish the installation. The PIC behaves similarly as other USB devices (for instance flash memory). It can be connected and disconnected at any time while the PC is running. However, the interface must be connected before activation of the rotor window.

Interface set up procedure:

1. Check (in case of current regulator or external sensor adjust) the maximum voltage at the point C between 4.2 and 4.7 V. The maximum voltage may not exceed 5V in any case, because it can destroy the A/D converter.

2. Set the voltage at the point A (using the trimmer 680) to about 0.1V lower then the minimum voltage at the point C.

3. Set the voltage at the point B (using the trimmer 2k2) to 50% of the voltage between the points A and C.

4. Start the program and set the parallel ports for rotator and eventually band switch in the menu "Rotator/Band switch->Setting". The rotator requires a dedicated port. On the other hand the band switch port can be shared with CW/PTT keying. If the checkbox USB is checked the LPT port setting is not relevant and the connection is established automatically when the USB interface is connected. MBUSBPRT driver is installed automatically when you connect the USB interface for the first time. Enter the path to the driver (files MBUSBPRT.SYS and MBUSBPRT.INF) when asked by Windows installation wizard.

5. Connect the interface to the port and in the menu "Rotator/Band switch->Rotator" activate rotator window. Turn the antenna to the most left position (counter clockwise) and check if the counter value displayed in the setting window (i.e. the voltage at the point C) is minimal. If not switch over the end contacts of the potentiometer (3 wires connection) or ground the other end contact (2 wire connection). Enter the beginning azimuth in the left field of "Range" and confirm with "Set".

6. Turn the rotator to the most right position (clockwise, check whether the counter value is growing while turning), set the azimuth value in the right field of "Range" and confirm with "Set". The azimuth values must be positive and the end value must be higher the beginning value. For example if the beginning value is 60 degrees and the rotator turns over 380 degrees the end azimuth value will be 60+380=440 degrees.

7. Click OK.

After the calibration the software limit switches are automatically set to the beginning and end azimuth values. If you have limit switches in your rotator make sure that their beginning and ending positions comply with the minimum and maximum voltage on the feedback potentiometer respectively.

If you just need to rectify the antenna direction on the already calibrated interface you don't need to repeat the calibration. Aim the antenna to the known azimuth (for instance a beacon), enter its azimuth in the field "Rectification" and click "Set".

CAUTION! After booting the computer the parallel port LPT may be in an undefined state. Switch on the motor power supply after the activation of the rotator window to avoid unwanted switching on the motor. Also when ending the program switch off the motor power supply before rotator control deactivation.

Rotor control keys:

CTRL/< - turn left

CTRL/> - turn right

CTRL/space - stop

CTRL/? – turn to the azimuth of the current QSO (if valid)

The band switch works on the chosen LPT port. The band is hexadecimal coded on the upper four data pins (6-9). The switching is accomplished either manually in the menu “Rotator/Band switch” or automatically with the band change if you check "Band auto" in the same menu.

17. Appendix - schemes and pin-outs of the interfaces

Use only shielded cables for all connections between the computer and TRX. The shield should be connected to the signal ground (GND). The 100 Ohm resistor in the collector of the keying transistor is only for the protection. It can be leaved out if necessary.

The default paddle pin out is compatible with the program N6TR.