There are significant changes to SD every few weeks. The latest version may be downloaded from http://www.ei5di.com
If you own or manage a website, please add a link.
To keep up-to-date with the latest news about SD, please subscribe to the SD User Mailing List.
Follow the link at http://www.ei5di.com
IOTA.LST has been updated for 2018, to include announced DXpeditions. It is loaded automatically for this contest.
Country reference file SDIOTA.CTY updated.
Alt-M toggles ESM (left-Alt only).
Alt-R or Alt-S toggles between Run & S&P modes.
Note: Alt-R does not assert RUN, and Alt-S does not
assert S&P. They simply toggle the mode when ESM is
enabled.
Left-Alt must be used, as Right-Alt has been a long-term alternative to Ctrl (keyboard mode) for some non-UK/US keyboards where Ctrl does not work as expected.
With rig control enabled, the rig QSYs to 14108. Decimal frequencies are supported - for example 14108.6.
Previously, SD required /M or /R suffixes to suppress dupe checking.
When logging a station already worked on the current band & mode, SD displays previous counties worked but does not pre-fill a county.
The QSO will be a dupe when there is a match on call, county, mode and band.
This feature is controlled by the QSOPARTY parameter in relevant templates.
On reloading, if the most-recent QSO logged had this suffix, the next serial was reset to 1. Fixed, thanks G3KZR.
For example, here are my stats for ARRL DX CW 2018 - K3 barefoot on 20m to a 3-el yagi at 30 feet. The calculations are accurate, because SD records QSO times to the second.
The stats are stored in Records 3, 4 & 5 of the .ALL file, following the Name and Address fields, and are included in Cabrillo logs under the tag X-BEST-RATES.
Please ensure SCP is enabled (with the SCP command) to benefit from BERU.DTA.
This is all possible because, although it is a Windows program, SD runs in terminal or console mode with no requirement for graphics support. In addition, SD was designed to be fast and efficient on the original, very slow PCs - and has remained fast and efficient ever since. All SD's features are supported on Linux and the Pi, including rig-control and WinKey.
To run SD on the Raspberry Pi, ExaGear from eltechs.com is required, together with Wine downloaded from Eltechs. The registration fee for Exagear is approximately $25, but is often cheaper, and they offer a free 3-day trial - that's how I started. QEMU, which is free, may be a viable alternative to ExaGear on the Pi - but has yet to be evaluated.
Some competence in Linux is needed to configure ports for rig-control and WinKey. Help is available via the sd-user mailing list.
Windows console programs running under Wineconsole are restricted to a display of 25 rows and 80 columns, whereas SD's native resolution is 27 rows by 82 columns. SD accommodates this difference with the BORDER command. The BORDER value is set to one or zero on Windows PCs, but must be zero for all other platforms.
It is sometimes necessary to use the BORDER conmmand twice or more, after starting SD, to get a stable logging window on Linux and the Pi.
I'd welcome reports of success in running SD on various platforms. Please send your reports to the SD User mailing list - sd-user at contesting dot com. If you have not previously subscribed to the mailing list, you will be added to the list.
Without a key file, SD runs in DEMO mode. In this mode, all features are supported except that logging is delayed for 30 seconds once 30 QSOs have been logged in individual events - previously this happened after 10 QSOs.
SD's DXpedition and Special-Event logging options are fully working and unrestricted, with no need to register or have a key file. SDX has been discontinued.
A reminder that it can be quicker to retrieve a wanted call from the window rather than typing it in full, especially when there are few partial calls displayed.
Use Up or Down-Arrow to access the window, and the arrow keys to navigate to the wanted call. Enter transfers a highlighted call to the logging line.
When there is a single call in the window, Up or Down- Arrow (nothing else) transfers the call to the logging line. If you've not tried this, you're missing out!
Dupe checking was not affected, but it helps to know immediately if the call you're typing has the potential to be a dupe.
When SCP is in effect, and there are many matches (for example, DL), the display reverts temporarily to Check Partial - showing matches from the log only.
In the Getting Started section of SD's manual, the standard settings for SD's Windows Size is Width 82, and Height 27. With EXPAND enabled, the Height should be set to 36, and the Font Size reduced to make SD's expanded window fit your screen.
If you haven't a clue about what all this means, try the EXPAND command to see for yourself - and read "Getting Started" in the manual.
ps - it seems to have worked - see the non-UK Unassisted results at RSGB 1.8MHz
It is flagged by appending /X to a callsign in the log. When the log is reloaded, these QSOs are ignored for scoring or multiplier purposes.
Now, if SD.KEY is not found, SD looks for any file with its name starting with SD.KEY and treats this as the key file.
A reminder of how the Band/Mult analysis works: The bands 10 to 80m (for IARU HF) are shown beneath the callsign. Any bands needed as mults are highlighted. In addition, if the station has been worked on other bands, they appear as black, including the current band - they can't be mults on bands already worked. You know instantly, while typing calls, whether you need that station on another band (or mode) for a mult.
For Non-UK entrants, the UK prefix multiplier summary has been corrected and is updated as prefixes are typed. You see instantly whether that station/prefix would be a mult on another band or mode. This feature also applies to all other contests with prefix mults, including Oceania, All Asian, CQMM, Asia Pacific Sprint, SA Sprint and OKOM (home side). It does not apply to CQ WPX, where prefix mults count once only.
Updated IARU.REF file supplied. It is used to pre- fill the IARU HQ Society initials, corresponding to the country indicated by the callsign, when you type any alphabetic character (one is enough) in the zone field. This is useful when HQ stations, not already in IARU.LST, are worked.
Caps Lock: Restored the Caps Lock indicator ^ - shown to the left of the callsign field on the logging line.
SDX supports DXpedition and Special Event logging on the 10 bands from 160-6m. It is free and unrestricted.
To see how it works, load any contest log with SD and observe what happens when you use Up Arrow to access QSOs.
For a callsign match on any pre-loaded .LST file, the name is pre-filled.
When the .ALL file gets corrupted, it can be recreated from the audit (.AUD) file but, obviously, it's better to prevent this happening. In any case, SD lets you edit band and mode directly with F1/F2/F3.
If you really must edit the .ALL file directly, take a copy of the file before you start, and use Notepad. This is a text editor and, unlike word processor programs like Word or WordPad, it does not add hidden characters to your QSO records.
Now, at startup, you are advised if any record/QSO has the wrong length, and SD displays its line number in the .ALL file together with the contents of the record - for the user to fix. This way, no subsequent QSOs will be affected.
SDX comes with a corresponding SDXCHECK program for creating Cabrillo or ADIF logs, and is intended to be installed in its own folder (SDX).
Registered SD users may continue to use SD's DXpedition option, but only with their own callsign.
Updated the RSGB District Codes (in RSGB.MLT) for 2017. The single BT district code for all Northern Ireland (GI) has been replaced by six separate codes, one for each GI county.
To log district codes from non-UK entrants, it is necessary to Tab to the District Code field from the Serial field - if the serial is followed by Enter the QSO is logged immediately; should this happen by mistake, use Up Arrow to edit the QSO just logged.
As you type calls, SD flags their multiplier status, with P and/or C, above the call.
http://sa-sprint.com/rules/
When you type a membership number, SD displays the callsign and name under the logging line. Then, Enter or Down Arrow places the call in the callsign field, and pre-fills the name & number in the exchange field - ready for logging.
Reverse lookup already applies to the FOC Marathon, the INORC Naval Contest and the CWops Mini Tests.
Fixed a formatting error in the window showing worked and wanted prefixes by band.
http://www.rsgbcc.org/hf/rules/2016/IntDX.shtml
SO2R support is discontinued.
This applies to both WinKey and SD's internal keyer. With WinKey, however, it works only when CW speed is controlled from the keyboard, not from WinKey's speed pot. If necessary, use the POT command to toggle control to the keyboard. Under keyboard control, change speed with Page Up and Page Down.
Fixed time-dependent scoring, and dupe resetting after three hours.
When you type a call and SD flags it as a dupe, press Enter to see the remaining time (minutes and seconds) before that call will no longer be a dupe. Press minus or Alt-W to clear the logging line.
The TUNE command may be abbreviated to T (followed by Enter). The command is "sticky" - Enter toggles tuning on and off until you clear the callsign field with Esc or Minus.
http://sa-sprint.com/rules/
Everyone can take part.
Mults are SA prefixes - they count once only.
http://flspota.org/rules/
The QSO Rate window has been disabled to permit the continuous display of park codes worked and wanted (171 of them).
This contest option is free and unrestricted for all users - with or without a registration key file.
On reloading logs, the DXCC analysis in the Score window was correct but country checking was reset. Fixed.
Some events benefit from a custom SCP file, for example the CWops mini-tests each Wednesday. This is controlled by the template SCP_FILE parameter. If the custom DTA file is not found, SD looks for MASTER.DTA and loads it. If MASTER.DTA is not found, SD tells you and continues with SCP disabled.
While it is possible to access "Properties" when SD is running, the recommended option is to do this from SD's desktop startup icon - right-click on the icon and select Properties (the last item on the list).
The only tabs of interest are Options, Layout and Font - in that sequence. You need to do this for both SD and SDCHECK.
OPTIONS Tab:
Use legacy console - Yes (selected)
Cursor Size - May be ignored
Command History - May be ignored
Edit options
LAYOUT Tab:
Window Size
Window Position
FONT Tab
Size - Select the largest font size that fits SD's window to your screen, or smaller if preferred.
Whatever version of SD you're using and, in particular if it's V18.30, use Defender or any other virus checker to scan your whole computer. If you get warnings, let your virus checker delete the files concerned, then install V18.31.
Updated template to NOT interpret exchanges from UA2 stations as possible cut numbers - removed the "TRUESERIAL: Y" parameter.
There are no mults in this contest, but calls corresponding to new countries are highlighted.
Since the four contests have varying scoring and multiplier rules, SD's scoring will not be accurate. However, the single Cabrillo log may be submitted to all four contest sponsors (for them to score).
If your preferred background colour is black, you'll need to select an alternative colour for dupes.
Fixed the RESET command - it sets all colours to SD's defaults.
The "by date" listing becomes more useful as the number of logs in your SD folder increases. This is the access date of the logs, not their creation date.
Reminder: You can delete any highlighted log by pressing Z. It's useful for removing test files.
The Score window now shows Prefix and Country mult totals, by band, on separate lines. Note that, since country mults count once only, the only significant figure is the total - individual band totals merely reflect what bands you used early in the contest.
In the JIDX contest, JD1 QSOs were flagged as zero-pointers. Fixed, thanks VK2AR.
In CQWW, for second and subsequent own-country QSOs on each band, the callsign turns red as you type it. Previously, this happened only after the QSO was logged.
Added the band/multiplier worked/needed analysis as callsigns are typed.
In addition, prefix mults (which count by band) have the prefix highlighted, and country mults (which count once only) have the full callsign highlighted.
For this to work as intended, you should edit the SD-DUPECLR parameter in your SD.INI file. Change its value to 4.
This feature is useful only when searching and pouncing and, in particular, near the end of a contest when you're running out of stations to work. While running, it's not relevant and you'll not notice it.
0000 should be logged when no locator is received. This is converted to ---- in Cabrillo QSO records.
1. Plain text, with a .SCP extension
2. Compressed, with a .DTA extension
SD uses only the original .DTA compressd files.
Previously, some SCP files bundled with SD were given the SCP extension. They have now been renamed with the DTA extension. They are CWOPS.DTA, FOCSD.DTA and INORC.DTA, loaded automatically for the relevant contests.
MASTER.DTA, the worldwide SCP file, is no longer distributed with SD. You can get your up-to-date copy from supercheckpartial.com. W/VE users should also download MASTERDX.DTA and MASTERSS.DTA. All other users should download MASUSVE.DTA. SD's templates have been updated, where relevant, to load the appropriate DTA files.
CWOPS.SCP and CWOPS.LST are included with SD's installation files, or may be downloaded from www.ei5di.com/sd/cwops.zip
SDCHECK - the Cabrillo option restores the lists of countries and continents worked. Thanks OE2BZL.
The FOC reference file FOCSD.LST has been updated to include special calls for the Marathon, and is loaded automatically.
Reminder 1 - if, when typing a call, the SCP window shows a single call, Up Arrow will instantly retrieve the call and complete the logging line - unless, of course, the QSO would be a dupe. No other contest logger does this.
Reminder 2 - if you hear a member's number and type it in the callsign field (no Space or Enter needed) SD instantly displays the call and dupechecks the QSO. If not a dupe, press Enter to complete the logging line - with Call and Number placed in the correct fields. No other contest logger does this. If a dupe, press Minus (-) to clear the QSO fields.
The opening screens of SD and SDCHECK have been reformatted to display the options for listing and loading any log in the SD folder. For SD, this directory listing includes an option to delete any selected .ALL file, and corresponding files with .LOG, .AUD and other extensions. It's a good way to remove files used for testing and no longer needed.
This last feature has been in SD since V14.00 in March 2008 but has remained largely invisible until now. Note that SD V18 does not load logs created with V17 and earlier.
When naming new logs, it helps to start the name of test logs with TEST, and to include the year or date in the names of all logs.
For a country multiplier (or bonus), the full callsign is highlighted. For a prefix multiplier, only the prefix is highlighted. The prefix may follow the callsign as in W1ABC/VE - in this example the prefix is VE0, and VE (only) is highlighted.
For district and zone multipliers/bonuses, the code or number itself is highlighted.
For dupes, the complete QSO is dimmed slightly, with no "D" following.
I believe this style is less cluttered and easier to understand.
All prefix, district and country mults are indicated as described above. ON prefix tracking is new. In effect, all features provided by SDU, the former standalone program for the UBA Contest, are now included in SD.
The templates for both sides of this contest have been updated, and UBA DX contest logs from earlier years may not load correctly, if at all. The former UBA.CTY country reference file has been replaced by the standard DXCC.CTY file.
The Section, UKEI or DX, was repeated for each Cabrillo header. Fixed.
When editing previously logged QSOs, some callsign prefixes, for example MI, were not recognised as UK prefixes. In turn, the District Code field could not be accessed. Fixed. Thanks EI2KA.
For post-contest logging, SETDUPE may be used as before, but a simpler option is to ignore it, then restart SD and let it rescore the log.
Any QSO in the log may be edited, but no real-time consistency checks are done for dupes or mults. However, after a restart SD will do this and score the log correctly.
The CLEAR, or CLS, command helps to correct this - you may have to select a smaller font, or use the CLEAR command more than once.
Reminder: To change SD's font/window size, click on the SD icon at the top LHS of SD's Window, select Properties, then Font, then Lucida Console, then Size - and experiment with different font sizes to suit your screen.
Points are now shown by QSO, and in total.
Reports are not required in this contest, even though they may be exchanged on-air. RSTs are no longer shown, and the RST command (to vary RST Sent) is disabled.
A small square, showing above the first character of the callsign, indicates that the full call might be a dupe. Once the square disappers, or if it does not appear, the full call will not be a dupe.
This works for either prefix or suffix checking, in combination with SD's Check Partial Function. Use full stop or comma in the callsign field to switch between prefix and suffix checking.
Note: single characters in in the callsign field are ignored - checking starts with the second character.
Updated the oblast table - it is used in this contest and in RDXC.
I believe this is now fixed (I was wrong last time).
Note that SD's control commands for WinKey work only on standalone units. For microHAM devices with integrated WinKey chips, the only way to change WinKey settings is with the microHAM control panel. This is because microHAM devices discard control commands from all contest and station loggers.
SD's MEMORY command (new in this version, and applicable to WinKey only) toggles dot/dash memory (I'll call it DDM) ON or OFF - enabled/disabled if you prefer. SD's default has always been ON. The STATUS command displays WinKey's current settings - but, again, not for microHAM devices.
The difference (for single-paddle keys) is easy to demonstrate, especially at slow speeds. Use SD's MINWPM command to set WinKey's minimum speed to 5 WPM (this is not possible with earler versions of SD), then the speed this speed with WinKey's speed pot or the keyboard. Start a dash, and let go immediately (a quick tap only). Before the dash ends, tap (and let go) the dot "side" of the paddle. If WinKey sends the dot after the dash has finished, DDM is enabled, otherwise it is disabled. There is NO advantage with single-lever paddles, indeed with ANY paddles, in having DDM disabled. When enabled, sending and timing is easier - leading to fewer mistakes. Otherwise, a common mistake is to send "O" rather than "Q", or "M" rather than "K". As already mentioned, SD's default setting is ON, but the MEMORY command lets you experiment with the "more difficult" OFF option.
In effect, with DDM, keying is more tolerant of timing errors - in particular, when the dot key is pressed (or tapped) early. It has minimal effect on dashes being tapped early, because our natural inclination is to hold dashes for longer, simply because they are longer. However, dash memory can still be demonstrated at slow speeds. Tap (and let go) the dot key and, before the dot has completed, tap the dash key. With DDM the dash is played. Again, DDM "covers up" timing errors where a dot (usually) is pressed or tapped early - before completion of a dash element. On the other hand, DDM cannot correct errors due to a "late" press or tap.
With dual-paddle keys there are additional factors to consider. Winkey supports three standard options, or modes, using SD's IAMBICA, IAMBICB and ULTIMATIC commands. Note that "Iambic B" and "Accu-Keyer" modes are identical for all practical purposes. All three modes relate to what happens when the paddles are squeezed and held (this is clearly not relevant to single-paddle keys).
When the paddles are squeezed, both Iambic A and Iambic B send alternating dots and dashes, with the first element (dot or dash) dependent on which paddle was closed first. In mode A, the keyer completes the element being sent when the paddles are released. In mode B, the keyer sends an additional, opposite, element to the one being sent at the instant both paddles are released. This feature is entirely separate from DDM.
Ultimatic mode differs from the two Iambic modes in that, when the paddles are squeezed, the element corresponding to whichever paddle is last to make contact is repeated continuously until the "squeeze" ends. In action, it's very similar to single-lever keying, except that there is no need to release the dot paddle when dashes are generated, and vice-versa.
The same DDM benefits, described for single-lever paddles apply with Ultimatic - the greater tolerance for (early) timing errors when sending characters that are not amenable to continuous squeezing - for example "Q" or "K". With DDM, the letter "Q" may be formed by pressing and holding the dash paddle, and momentarily tapping/squeezing the dot paddle AT ANY TIME while the second dash is being sent, then releasing the dash paddle while the final dash is being sent. With no DDM, the dot paddle must be pressed when the second dash ends. This is easily verified with SD. Ultimatic users can not easily switch to either Iambic mode.
With Iambic A, DDM permits the insertion of, say, a dot by tapping the dot paddle while continuously pressing the dash paddle. The letter "Q" may be formed by pressing and holding the dash paddle, and momentarily tapping/squeezing the dot paddle at any time while the second dash is being sent, then releasing the dash paddle while the final dash is being sent. This is handy when calling CQ.
This does NOT work without DDM. It is still possible to insert a dot while continuously pressing the dash paddle, but only when the dot paddle is held/squeezed until after the second dash has completed - otherwise the result is the letter "O". In this respect, as with single-lever paddles, there is NO advantage in using Iambic A mode with DDM disabled. When enabled, the result is more tolerance with timing - and fewer mistakes.
Iambic B, or Accu-Keyer, mode is a little different. The "extra" dot or dash element which appears after a "squeeze" is often confused with Dot/Dash memory, but it is nothing of the sort. It is simply the one feature that distinguishes Iambic B from Iambic A. The presence, or otherwise, of DDM still makes a difference. This may be verified by trying the letter K. With DDM, the dot paddle can be tapped (and released) at any time while the first dash is sending, and the letter K will be formed. Without DDM, the dot paddle must still be pressed at the time of completion of the first dash, otherwise the result is M. Once again, there is no advantage in using either Iambic mode without DDM. All users are likley to have fewer mistakes with DDM enabled due to greater timing tolerances.
Again, all that has been decribed may be verified with WinKey and SD at slow speeds - 5 wpm is recommended.
There is a final issue that is relevant. WinKey, and perhaps other keyers, use a Switchpoint parameter to control dot/dash memory. Here is the description from the WinKey manual -
I believe that, with the exception of the first and last sentences in that paragraph, everything else is wrong - and indicates a lack of understanding of the basic function and purpose of DDM - even though the author/designer has made provision for it.
It seems to me that DDM should be ON or OFF, with no in-between, but perhaps I'm the one who doesn't have a full grasp of the issues? In any case, when DDM is enabled in SD, WinKey's Switchpoint parameter is set to its minimum "ON" value 10 - meaning that any tap on a paddle after the opposite element has been playing for a time corresponding to one fifth of a dot will be "remembered".
Many operators use dual-lever keys without ever intentionally squeezing the paddles. In effect, they are using the keys as single-lever devices. In these circumstances the keyer mode, whether Iambic A or B, or Ultimatic, has no relevance. The only parameter that still makes a difference is DDM, and I maintain that it should ALWAYS be enabled. It seems to me that iambic keying is a solution looking for a problem. Single-lever users can confidently use any keyer or paddles - regardless of the keyer mode. On the other hand, dual-padddle users are confined to their individual mode of choice. Yes, there may be benefits in terms of a reduction in hand/finger movements with certain characters but there is also more potential for errors. Instead of just left and right (the only two options with single-lever keys), we have, in addition, squeeze left first, and squeeze right first.
If in doubt please get, or try, a single-lever paddle. Mine is the Begali HST II, one of their less expensive models.
It's not generally realised that it's harder to manufacture a good single-lever paddle than a good dual-lever version. The difficulty arises due to the need to hold, or stop, a single paddle between the dot and dash contacts - with no mechanical play, and with no unwanted elements being sent due to contact bounce at low tension or contact spacing.
Most single-lever paddles have a central "stop" post which solves the contact bounce problem. However, they typically require an intermediate "lever" arrangement between the paddle and the contact points - which can lead to imprecision and a need for precise adjustments to minimise mechanical play. The Begali HST II uses an ingenious cam arrangement with no need for stop posts or intermediate levers, and with zero mechanical play. Do yourself a favour and try one - you'll soon appreciate why single-lever paddles are generally preferred in high-speed CW sending competitions.
Added IOTA.REF - enables lookup (from callsign field) by IOTA reference, and displays your corresponding multiplier status for all bands on both modes.
I was unable to reproduce this problem, but have updated the relevant code to reduce the chances of this happening again.
Esc interrupts the CQ message while it is playing, and a second Esc is required to disable repeats. A single Esc, between repeats, disables repeats.
The WINKEY command has been replaced by WINKEYON and WINKEYOFF commands - or the shorter versions, WKON and WKOFF.
When you use the WKON command, and no WinKey is connected or recognised, keying remains internal. The WKOFF command switches keying to internal. It has no effect when internal keying is already in use.
All speed change parameters appear to work reliably and consistently, for both internal keying (serial or parallel port) and WinKey.
Use the STATUS command to check your settings.
Your expiry date of the key file for activating updates is shown on SD's opening screen.
SD V18.00 and later will not work with V17 or earlier logs. However, SDCHECK is unrestricted and works with all logs - it does not need a key file.
When the key file is missing or edited/corrupt, or if SD is used with an unrelated callsign, SD runs in DEMO mode. In this mode, QSO logging is delayed for 30 seconds after the first 10 QSOs in each log.
There are no unrestricted contest options for unregistered users.
Repeats are interrupted when any character is typed in the Callsign field, or when minus is pressed. While the CQTIMER value is non-zero, Enter, in an empty Callsign field, re-starts repeats.
The former R0 to R15 commands are discontinued.
Word Spacing - WinKey: The installation default for a word space when creating SD.INI is now 6 dot units rather than 7, as the shorter word space is generally preferred for contesting. For an existing SD.INI, you must change the value of the SD_WKBIT0 parameter to 1 to enable this feature.
Improved QSO headings and the location of points and mult indicators on logged QSOs.
NOTE: SD tracks new counties, by band as appropriate, but does not count them as multipliers. There are no mults in these contests.
The polling interval has been changed to 10 seconds, and the timer is reset at the start of any message playback. This minimises the chances of an unwanted speed change during message playback. Thanks G3LET.
This parameter has been added to all relevant templates.
When reloading a log, SD cleared received data, other than serials, from non-UK QSOs. This did not affect scoring. Fixed.
This had several effects. SDCHECK listed this, incorrect, call in every Cabrillo QSO record, and ignored any QSOs with the same call. When a log was reloaded, SD removed (deleted) any QSOs with this call (invariably the last QSO, but there could be others) due to "own call" QSOs being treated as unwanted QSOs (see V17.46).
Fixed, thanks SM5BKK.
Templates updated - you are now asked for your Precedence, Check and Section when starting a new log, rather than the previous "Fixed Exchange".
If it was the QSO that has just been logged, and no other QSOs have been logged in the meantime, the ZAP command is the best option.
If it was an earlier QSO, add /ZAP or /Z to the callsign, or change it to your own callsign. The QSO will be removed next time the log is loaded with SD. QSOs with /ZAP or /Z or "own call" are ignored by SDCHECK.
In doing this, SD looks for, and extracts, any 4-character grid square field in the reference data for the callsign - regardless of its position.
Previously, the loading of contest-specific .LST files was hard-coded.
Left Ctrl is a better option, because it's easier to find, and it has been reinstated as the default option. To disable Left Ctrl, change the value of SD_LEFTCTRL to zero in your SD.INI file.
A reminder of another SD feature for logging HQ stations not included in IOTA.LST - overtype the pre-filled zone with any alphabetic character (any single character will do), followed by Enter. The QSO will be logged with the HQ initials corresponding to the country of the callsign.
The installation would not work while SD was still running. Fixed by forcing SD to stop. Thanks 5B4AIZ and I7ALE.
When editing previously-logged QSOs, the Serial field is now skipped - no serials are received from SP stations.
However, it was unreliable in that, occasionally, it had to be pressed twice. This is how it works now.
To assert Keyboard Mode:
To return to Logging Mode:
The mode now corresponds to that of the template selected. Previously, it had to be manually entered.
SD now shows the options available to the user, then resumes.
SD now shows the options available to the user, then resumes.
www.radiosport.org.rs/HFTeslaMemorial/index.php/rules
www.nauryz-dx-contest.com/index.php/rules/contest-rules-2014
The PORTS command has been replaced. CWPORT, or KEYPORT, assigns a port for CW, whether internal or for WinKey. RIGPORT, or CATPORT, assigns a port for rig-control.
Added diagnostic options for switching the status of DTR and RTS on the keyer and rig-control (CAT) ports.
KEYDTRON KEYDTROFF KEYRTSON KEYRTSOFF
CATDTRON CATDTROFF CATRTSON CATRTSOFF
These settings are not permanent - they apply only to the current session.
Using SD's internal keyer:
DTR is used for keying, and RTS for PTT - but
only if PTT has been enabled with the PTTON
command.
Rig-Control:
Polling uses XMT, and responses from the rig
apear on RCV. SD does not use other handshake
signals, if any - their status is ignored.
To use either DTR or RTS to power an external level converter, use the RIGPOWER or CATPOWER command.
With SD's internal keyer (but not with WinKey) a single serial port (or USB-Serial converter) may be used to support both keying and rig control - but only when power is not needed for an external rig-control converter. Use the SHARE command to enable this facility, followed by CWPORT or RIGPORT as required.
WinKey devices communicate with SD using the same "pins" (XMT and RCV) as for rig control, That's why separate COM ports are required.
When using certain external USB-Serial controllers, RTS and DTR being asserted caused a conflict with SD's internal keying on any other port (WinKey is not affected).
The command RIGPOWER (or CATPOWER) toggles DTR/RTS On or Off. The settings are permanant until the command is next used.
Should it ever be necessary, to be certain of having an up-to-date file, CTY.DAT may be downloaded and renamed as CQWW.CTY.
SD's CQWW.CTY and DXCC.CTY files include non- standard CQ and ITU zones which SD pre-fills, on a callsign match, in contests with zones in the exchange.
Control file added for IC-7100. Thanks G0NEY.
Restored display of points for each QSO.
When SD pre-fills the district code (on a .LST file callsign match), data entry reverts to individual serial and district code fields.
For UK entrants, UK QSOs do not count for points or mults.
For DX entrants, the exchange field has been enlarged to permit Serial and District Code to be entered as a single field - for example: 21BT, followed by Enter, is logged as 021 BT in their respective fields.
On Win7/8, a fast processor and an FTDI converter are needed - for example, an Intel i7 and a Startech ICUSB2321F. With an Intel i3 processor, neither converter gave satisfactory CW.
If you need perfectly smooth CW at all times Winkey will guarantee it.
Removed all code related to internal CW sidetone.
For all contests, your cumulative operating time is shown under the Date and Time bar. Time starts when the first QSO is logged. Gaps between QSOs of 60 minutes or longer are ignored, and time starts again from the next QSO logged.
Seconds are not significant. A QSO logged at 12:00:59 is considered to have taken place at 12:00:00.
The SHOWTIME command toggles the display of operating time. The display reverts to ON each time SD is started.
The standard way to quit is with the QUIT or END commands in the Callsign fields in the opening or logging screens.
The SIDETONE command is relevant only when WinKey is connected - it toggles WinKey's monitor speaker On and Off.
QSOs with ON stations already registered with the UBA score 10 points. This is controlled by the SPECIALCALL parameter in the UBA Field Day templates - QUBAFDC.TPL and QUBAFDS.TPL. Maintenance of these is the responsibility of users.
Introduced the HOMEMULTS template parameter. When this is "N", own country QSOs do not count as mults.
The net effect is that inter-Scandinavia QSOs may be logged, but do not count for points or mults.
Fixed the Cabrillo QSO format.
For non-EU entrants in the CW event, QTCs sent are flagged as sent, as and when the keyer has "sent" them - This helps when you need to repeat an earlier QTC before returning to the next "unsent" QTC. Thanks 5B4AIZ.
When you type the call of a station that would be a dupe, but which SD indicates is OK for QTCs, press Minus or Esc to clear the call. When you then use the QTC command, SD pre-fills the call in the QTC opening screen.
Although there are no multipliers in this event, SD tracks Call Areas in VK and ZL to add a bit of interest.
QSOs with individual stations, on each band/mode combination, may be repeated after three hours. When you type a call that is currently a dupe, SD displays the remaining time (minutes and seconds).
Updated the template file, to prompt for the op's Years Licensed at startup, and for use by SDCHECK in Cabrillo logs. Supplied REMDAY.CTY, showing VK and ZL call areas.
SD stores details of QSOs (Call, Frequency, Mode, Time) in its Band Map table - derived from the older Quick Memory table. Not all QSOs are stored. If you have two or more successive QSOs on the same frequency, only the most recent one is stored. Callsigns that you don't work, or want to return to later, are stored when you press Minus.
The Band Map table may be displayed using F10, as before, offering instant QSY to any selected entry - with rig control enabled, of course.
However, the main feature of SD's Band Map implementation is not the table. Rather, it's the fact that as you tune up and down the band, calls worked and needed appear automatically under the frequency display. Calls you haven't worked are highlighted in upper case - simply press Down Arrow to transfer them to the Callsign field. The ones you've worked already appear in lower case - you know you can keep on tuning.
As you tune, Band Map calls appear and disappear according to your frequency threshold. The default is 200 Hz either side of the centre frequency - change it the THRESHOLD command.
In the absence of rig control, logged QSOs are not added to the Band Map - there would be no benefit without their frequencies. However, Minus does add callsigns - for what they're worth. You might use this to record the calls of simultaneous callers, then work them successively using the Band Map as a prompt.
When SD is stopped, Band Map entries expire.
V17.12 improves the consistency and accuracy of the Band Map displays.
If, before logging the QSO, the callsign was edited, SD did not automatically clear the original IOTA reference. This could cause an incorrect or inappropriate island reference to be logged. Fixed.
Edited SDIOTA.CTY to fix an incorrect reference being pre-filled for IT9, Sicily.
This operation does not prevent any other callsign reference file being loaded by SD at startup - as held in SD.INI.
Up Arrow, to edit earlier header entries, did not work. Fixed.
Note that when variable RST Sent is enabled, ESM (Enter Sends Message) is disabled. Also, after logging an island station, the numeric part of the island reference is not cleared from the logging line - this has no effect on subsequent QSOs.
This bug applied to all contests, but became apparent in IARU because of the many calls ending in HQ.
Note that when variable RST Sent is enabled, ESM (Enter Sends Message) is disabled. Also, after logging an island station, the numeric part of the island reference is not cleared from the logging line - this has no effect on subsequent QSOs.
This bug applied to all contests, but became apparent in IARU because of the many calls ending in HQ.
SD checks for a later version and, if available, invites you to download it.
SD emails the version number and the default DXCC country prefix, from DXCC.CTY, corresponding to the callsign used. This helps me to identify levels of use of SD in each country. At most, a single email is generated for each PC per day, regardless of how often SD is run. No personal information is included.
Every fourth time SD is run, your browser opens the donations page at ei5di.com, but not if you are a registered user with a current key file in your installation folder.
SD displays the frequency in red when the rig is tuned to these segments. Thanks DL8MBS.
With no rig control, calls logged are not stored in the Band Map. Calls flagged with minus are stored and shown in upper case.
To retrieve a band map call shown under the frequency display, press Down Arrow - this works only when the callsign file (on the loggging line) is empty.
With rig control disabled, Minus "-" always stores the callsign in the Band Map. This was broken in V17.01. Thanks VK4TT.
Band Map entries expire after 90 minutes. Use the BMTIME comand to change this setting.
With rig control enabled, calls are shown as you tune close to (within the threshold of) their original recorded QSO frequencies. The default threshold is 300 Hz, and may be changed with the THRESHOLD command.
Calls already worked are shown in lower case. Calls not worked (ones that you deleted from the logging line with Minus) are highlighted.
When you log successive QSOs on the same frequency (while running), only the most recent call logged on that frequency is shown when you next tune across the frequency.
When you log successive QSOs with the same station, on different bands, the second QSO is not stored in the band map.
The band map may be more useful in shorter contests, where many stations occupy a fixed "run" frequency for most of the time - you see their "worked" or "not worked" status without having to wait for them to identify.
At present, band map entries do not expire unless you delete them - use F10 to display the complete table of entries. For V17.02 I will add the option to delete those older than any selected time period.
For Polish entrants, the Serial Received was missing from Cabrillo QSOs. Fixed, thanks SP4QCU.
Added an independent Band indicator at the end of each QSO record (1 = 10m, 2 = 15m etc). If there is ever a conflict between Frequency and Band in an individual QSO, the Band takes precedence when the file is reloaded. The Band indicator is included in audit file records.
When rig-control is enabled and working, the corresponding frequency is held also. This may be used as a manual Band Map.
F10 displays the Quick Memory table. Use the arrow keys to select an entry, and F10 (or Enter) to retrieve it to the logging line. Your rig is switched to the correct band as necessary.
If rig control is enabled (non-zero COM port assigned) but is not working for any reason, arbitrary frequencies will be stored. They have no significance and no effect, because rig control is not working. Callsigns may still be restored to the logging line, but there will be no band change.
When rig-control is disabled, with the COM port set to zero, callsigns alone are stored. Again, they may be selected and restored.
If you're not using rig control, you should use the PORTS command to set your Radio 1 control port to 0.
A reminder that, with rig control enabled, moving a station to another band for a multiplier QSO is fast and simple with SD. Enter the agreed frequency to QSY the rig. Enter "Q" to repeat the callsign, log the QSO then press F10 twice to return to your previous frequency. This is quicker to do than to describe - so long as you have automatic antenna switching and no amp to retune.
Restored SO2R support - enabled or disabled with the 2R command, followed by PORTS to assign COM ports and names for the two rigs. Toggle between them with the backslash "\" key.
With the callsign field empty, equals "=" sets the inactive rig to the same frequency as the active rig. Comma "," swaps frequencies. The active rig is indicated by R1 or R2 at either side of the date/time field.
In mixed-mode events, the mode on the active rig will correspond to the frequency. If necessary, use the S (SSB) or C (CW) commands to switch. The X (eXchange) command lets you switch sidebands on both SSB and CW. The CW setting is held for both rigs across all bands.
B40, B20 etc, and their equivalents 40M and 20M, switch the active rig to the new band - this may also be done by direct frequency entry, for example 14020 or 14183.56.
SV callsign mults are marked with asterisk * beside the call, and country mults are shown with M after the points field.
Callsign (Member) mults are marked with asterisk * beside the call, and country mults are indicated by M after the points field.
Following edits of previously logged coordinates, points are unchanged, but are updated when the log is restarted.
The default internal port addresses, when selecting printer ports with the PORTS command, are
51 : LPT1 : Decimal 888 : Hex 378
52 : LPT2 : Decimal 632 : Hex 278
53 : LPT3 : Decimal 956 : Hex 3BC
General-Purpose Template Options:
There are now three only. They facilitate logging in events for which there is no custom template.
The exchange options are -
1. Send a serial only (apart from RST).
2. No serial, but some other fixed information.
3. Send a serial plus some other fixed information.
The corresponding template options are -
1. General, Serial
2. General, No Serial
3. General, Serial +
Option 1 tracks DXCC countries as multipliers, by band and mode (if you use both modes). Mults have no other significance as they are not marked in Cabrillo QSO records.
In Option 3, serials and other exchange elements are logged in a single, space-separated, field.
This parameter replaces hard-coding for DARC contests with DOKs, for Holyland and RDXC districts, and for IOTA island references.
CQ and ARRL Single-Mode Contests:
CQMM DX Contest (PY):
SDCHECK:
OKOM Contest:
Default RST in Mixed-mode Events:
RSGB DX Contest (Proposed):
IOTA Contest:
WAE - QTCs from non-EU stations.
Keyer Message Playback:
RSGB Club Calls:
SDCHECK:
In the exchange field, SD switches the data entry mode to Insert (INS under the callsign) to facilitate entering a serial when the Name has been pre-filled. This could toggle your default data entry mode from Overwrite (OVR) to INS. Fixed.
The full list of free options is shown at www.ei5di.com.
The first is a "Once-off Registration". Users get a key file giving unrestricted access to the current version (and earlier versions) of SD for a fee of 10 euros. The key file does not expire, and there is no need to ever register again unless you decide you want whatever features and bug fixes are provided in later versions of SD.
The second option adds access to future versions released within 12 months of registration - the fee is 20 euros. Again, the key file never expires.
In contests which are not free, or where the key file is out-of-date with regard to the version used, or is used with a non-matching callsign, SD remains in DEMO mode and logging is delayed after 10 QSOs - by 30 seconds for each new QSO.
This helps to prevent user errors caused by selecting the wrong template when starting a new log, or the wrong log when restarting SD. When SD is running in demo mode, the word DEMO appears after the contest name. When DEMO is not shown, you know for certain that SD is not in demo mode, and will not slow down after 10 QSOs.
All templates (more than 200) now include parameters for constructing Cabrillo QSO records directly, by mapping fields from the .ALL to the .LOG QSO records. Previously, many Cabrillo features were hard-coded and difficult to maintain.
Please refer to the Templates secion in the manual SD.PDF for more information.
Note: The RSGB RoPoCo and Club Calls contests are exceptions - Cabrillo QSO records remain hard-coded.
Cabrillo header records are now V3.0, the current standard.
When reloading, SD skips the screen showing your Name & Address and the contest parameters. Startup is simpler and faster.
SD's default is now unexpanded - where the partial calls display temporarily replaces the score window. This is suitable for 16x9 ratio screens, enabling SD's window to closely fit the screen.
The alternative location is underneath the logging line - with SD's window expanded accordingly. It displays the partial calls closer to the logging line, an advantage when running at high rates.
Own-area QSOs now score on all bands. Thanks VK3NRW.
You can have fun searching logs to find your best rates for the Last 10 and Last 100 QSOs.
Applies to logs from V15.00 or later.
This applies typically to North American QSO Parties when two or more take place at the same time.
In contests with serials, SD displays the current serial (the one for your next QSO) on the logging line, regardless of whether you have typed anything in any field of the QSO.
In CW contests, it is sometimes necessary to repeat a Serial Sent after a QSO has been logged. Until now, the test for sending the "previous" serial (the one just logged) was an empty callsign field in the logging line (the next QSO).
This test is not appropriate when you have already entered a Serial Received or, more specifically, have typed any printable character in the Callsign, RST, or any exchange field for the current QSO. In such cases, SD now sends the current serial - even when you have edited or, perhaps, cleared those characters in the meantime.
To fully reset, or wipe a QSO, use Minus or F11 as usual. When repeating an exchange, SD then sends the previous serial.
Thanks GM3SEK.
Fixed missing Area character in Cabrillo logs - thanks G3RSD.
In all other events SD loads your default .LST file. This is the one you most recently loaded, if any, with the LOAD command, and its name is held in the SD_LOAD record in your SD.INI file.
The CLEAR command clears all callsign reference data already loaded, and the SD_LOAD record. Thanks K4GM.
POLLTIME and LINKTIME settings: These were set to fixed values, dependent upon your BPS setting, each time SD was started. Now, user-selected values are preserved in SD.INI.
If rig control is not working fully with your rig, here's what you should try - assuming the PORTS command has already been used to define the appropriate COM port for your rig.
1. Set the BPS to the maximum supported by your rig - and ensure your rig is set to the same value (if variable).
2. Set POLLTIME to 1000 and LINKTIME to 800. Use the STATUS command to confirm the settings.
3. Confirm that rig control is working. If not, there is a separate issue. If working, reduce LINKTIME until rig control fails. Then increase LINKTIME by 25% or so, and confirm that rig control is restored - and the frequency displays correctly even when continuously turning the VFO dial.
4. Reduce POLLTIME until rig control fails, then increase it by 25% or so and confirm that rig control is restored. Note that lower values of POLLTIME make rig-contol more responsive, in terms of how quickly the frequency display is updated.
Thanks G4CWH.
This is not an April Fool item! It has been an undocumented feature in SD for some time.
Russian stations in RDXC, which overlaps with CQIR, send a 2-character district code instead of a serial. SD's serial field is truncated to two characters when appropriate.
The February event is CW, SSB or Mixed-mode, and DX entrants work UK only. The November event is CW only, and everyone works everyone with the exception that non-EU entrants work EU only.
Separate templates (UK and DX) are supplied for the February event - they each support both CW and SSB, with no need to specify the entry category in advance of creating your Cabrillo log with SDCHECK.
A single template, for both UK and DX, is supplied for the November event - CW only.
For the November event, everyone works everyone (except that non-EU entrants work EU only). Separate templates are supplied for CW, SSB and Mixed-mode entries. Separate templates for UK and DX are not required.
CQWW - Scoring:
RSGB 1.8 MHz Contest - November:
CWops Mini Tests:
RSGB 2nd 1.8 MHz Contest:
CW Open:
Editing QSOs:
RDA Contest:
Restored automatic loading of this file at startup in the RDA contest - thanks ES5EP.
SD pre-fills the district code on a callsign match.
Increased the record limit for .LST files from 20,000 to 32,000.
For information - Rig Control:
RSGB 80m Sprint:
The mode was not always the mode selected at startup. Fixed, thanks G4RCG
Rig Control:
Otherwise, the features of F11 and F12 are unchanged. F11 deletes (wipes) an unlogged QSO without updating Quick Memory - whereas Minus also updates Quick Memory. F12 silently logs a QSO when ESM is enabled, in contrast to Enter which logs the QSO and plays the ESM message.
The "old" band-change commands, B80, B20 etc. may still be used to switch directly to any band supported in the contest.
Using the DXpedition template, band changes on the rig to WARC bands caused a spurious QSO to be logged with the corresponding command (B30, B17, B12) as the callsign. Fixed - thanks PA0JNH.
Direct Frequency Entry:
Fractions of a kHz are supported, to one or
two decimal places. For example, 3510.2,
followed by Enter, tunes the rig to 3510.20
kHz. 14234.56 tunes to 14234.56 kHz.
CW Message Playback:
Alt-F1 and Alt-F2 now change bands in the same way as F11 and F12 above. This is intended to help contesters who have been weaned on some other contest loggers, and are new to SD.
INS/OVR Data Entry Mode:
IOTA Contest:
Thanks: www.ng3k.com/misc/iota2011.html
www.iota-expedition.com/IOTA2011/iota2011.html
On a matching call in IOTA11.LST, the corresponding IOTA reference is pre-filled on the logging line. However, after entering the serial, the pre-filled reference disappeared, and had to be typed. Fixed.
Post-Contest Logging Mode:
IOTA Contest:
ZAP Command:
All contests:
SCP (Super Check Partial) is another default option, using MASTER.DTA which is distributed with SD. This file contains the calls of all contesters who are active in major events. Other reference subsets may be downloaded from supercheckpartial.com. They must be named MASTER.DTA in the SD folder, otherwise SD will not find them.
If you prefer not to use SCP, toggle it with the SCP command.
Rig Control:
The RS (Reverse Sideband) command in 15.45 has been replaced by the X (eXchange) command - it's faster. SD now tracks the most recently selected sideband on each band, independently for both CW and SSB, whether switched on the rig itself or from SD with the X command. Note that not all rigs support alternate sidebands on CW.
As you return to each band, SD reverts to the previously used sideband and mode. When a band has not been used previously in the current session, the frequency defaults to near the lower band edge.
When you enter frequencies directly, the rig is switched to the appropriate sideband on SSB. For CW frequencies, the sideband is set to your preference, normal or reverse, as set by the CWREVERSE command.
IARU HF Championship:
Rig Control - CW:
When you change mode, from SSB to CW, on the rig, the CW sideband remains at whatever it was set to previously on the band concerned.
When you use SD to change mode to CW (with the C command), the CW sideband is set to your preferred option in SD.INI - as defined by the CWREVERSE command when last used.
The RS command (Reverse Sideband) has been introduced to instantly change CW sideband - this is often faster than doing it on the rig itself.
Why should anyone worry about reverse sideband on CW? There are two reasons. The first is to reduce QRM (it doesn't always work), and the second is for consistency - depending on whether you're tuning up or down the band.
Rig Control:
Allowable bands are defined by the MAXBAND and MINBAND, or SINGLEBAND parameters in each template. These parameters are not required for any contest using all 6 HF bands.
DXpedition and Special Event Option:
Check Partial - EXPAND Command:
The main purpose is to enable Check Partial (and SCP) calls to be placed below the callsign field on the logging line because it helps to have this information close by.
SD checks callsign for dupes as they are typed. However, when no check partial display is visible, you know the call will not be dupe - perhaps after only two or three characters have been typed
If this has never been an issue for you, there may be no reason to use EXPAND. Note that you may have to maximise the window to see it in full.
You can move the cursor to the Check Partial calls with Down Arrow, and then navigate with the arrow keys. Enter retrieves a highlighted call. Note that "dupe" calls are not highlighted, and can not be retrieved.
When there is a single, non-dupe, callsign listed, either arrow key (Up or Down) will instantly retrieve it - ready for logging. This is often faster than typing the remainder of the call.
Reminder: Comma toggles the partial list between "anywhere" and "prefix only". Full Stop (period) changes the list to "suffix only". Please try this for yourself - most users don't know about it.
If the expanded desktop window does not fit on your display, use the information on SD's opening screen to adjust your font and window size as appropriate - experiment with Lucida Console font sizes.
Full-screen operation is not supported, and the BORDER command is discontinued.
IOTA Contest:
To check the multiplier status for a specific island reference on the current band and mode, type the reference in the callsign field - redundant zeros are not required. For example, type EU1. If it's a multiplier, "M" appears above, and your multiplier status for EU001 (Dodecanese) on all bands, and both modes, appears below. No other contest logger does this. Add 2 to see your status for Shetlands EU012, and add 3 for Scottish Coastal Islands EU123.
Multiplier slots are highlighted. Use Esc or Minus to clear the IOTA reference and multiplier analysis.
CVA DX Contest (Brasil):
US Counties QSO Party:
California QSO Party CQP:
Rig Control - Changing Mode:
All Asian Contest:
Age is prefilled when callsigns, worked earlier, are typed.
Key Files - Opening Earlier Logs:
Band Edits:
Following band edits, QSO frequencies are set to the lower band edges - even when rig control is enabled.
CW Open Contest:
LOAD the CWOPS.LST file, maintained by K8JP and distributed with SD, or combine it with any other .LST file you use to display names on a callsign match.
CQMM DX Contest:
#N (Name) Keyer Parameter:
Key Files:
SDCHECK:
Fixed the Claimed Score field in Cabrillo logs.
For some contests with country multipliers, SDCHECK reported errors in the .CTY file. Fixed.
MQP - Maritime QSO Party:
All Contests:
All Contests:
All Contests:
Both SD and SDCHECK automatically convert earlier V15 files as they are loaded. Cabrillo logs are unchanged - the frequency is recorded in kHz only.
Older .ALL files, from V14 and earlier, are no longer supported.
CQMM DX Contest:
FOC QSO Party:
CQMM DX Contest:
A South American QSOs may count as both a prefix and a country multiplier.
SDCHECK updated to generate the Cabrillo log to the required V3.0 standard.
DXpedition & Special Events:
In addition, for matching calls, QSO totals are shown to the right of the callsign field.
RSGB RoPoCo - SSB:
Cabrillo log - Restored RoPoCo Sent in QSO records.
SPDX Contest:
RSGB RoPoCo:
Fixed the display of RST for SSB - shown as 599 for the first QSO.
International Naval Contest:
Commonwealth Contest:
Updated all CTY files:
RSGB Commonwealth Contest:
Check Partial:
Check Partial by suffix, using full stop, is still available, but is effectively redundant.
In ARRL DX, check partial did not work for calls beginning with a valid state or province abbreviation, such as AB or NY. Fixed - thanks GM4SID.
Logs not loading:
WIA (John Moyle) Field Day:
REF Contest:
AUTOFILL COMMAND:
This command has been broken for some time and is now discontinued. Use F5 to send your own call, in S&P mode, when the exchange field is not empty.
RSGB Commonwealth Contest:
Country Multipliers:
One obscure effect, which seems to be related, is that your QSO total, in the score window, may not update for a few seconds after a QSO has been logged - even though band and score totals do update immediately.
SSA Manadstest:
DEMO Command:
The DEMO command brings up a screen inviting the user to type some text, followed by Enter. The corresponding code is then generated by WinKey - WinKey is required for this feature to work.
A second Enter clears the field, ready for another piece of text. If nothing is typed, Enter returns SD to the logging screen.
FOC Marathon:
In either case, just by typing the membership number, you see which bands are needed with that member. Enter substitutes the callsign for the number.
This works also for FOCQP and CWops. It will be extended to all events using membership numbers.
Band/Mult Summary:
Vermont QSO Party:
RSGB 1.8 MHz Contest:
Missing Template:
CQ160m Contest:
What happened to V15.31?
UBA Contest:
Fixed data entry for ON stations already worked - the province was pre-filled in the serial position.
NOTE: SD does not track or score Belgian prefix multipliers at present. The Dupe Sheet (by band) option in SDCHECK makes it easy to count these prefixes, and revise your claimed score.
RSGB 1.8 MHz Contest:
If you're not sure, in advance, about which section to enter, select the Mixed option.
The Mixed option tracks CW and SSB bonuses independently. As you type prefixes, SD instantly displays the bonus status (both modes) and, for UK stations worked earlier, the district code bonus status on the other mode. For example, type D to see your bonus status for Germany - no other key is needed.
REF Contest:
Earlier V15 versions of SD should not be used in this event
Template Parameters:
The TOPBAND parameter is now obsolete.
NOTE: Many templates have been updated. Results may be unpredictable if they are used with earlier versions of SD.
Band/Mult Summary:
This is not a new feature but it has been simplified and improved, especially for single-band mixed-mode events - including the RSGB 1.8 MHz contest.
You instantly see which band/mode slots are needed, for mults or otherwise.
The bands needed as mults are shown in blue. Band/Mode slots already worked are shown in black. The current band/mode slot (also black) has a contrasting background.
In addition, a QSO count (including the current QSO) is shown for any station worked on other bands - so that you can say or send "Thanks for X QSOs" - without having to count the bands shown underneath in black. Press F9 to see full details of earlier QSOs.
Voice Keyer:
If a COM port has been assigned for SD's internal CW keyer (regardless of whether it is used for CW), it may be used for PTT for both CW and SSB.
If WinKey is in use, a separate COM port is required to control PTT. Use the SSBPORT parameter in SD.INI for this purpose. You must edit SD.INI directly - there is no integrated option in SD.
This feature has not been tested.
RSGB AFS Contest:
Template Files:
RSGB 1.8 MHz Contest:
Note: You select your entry mode when creating your Cabrillo log, and not when starting the new log with SD. This way, you can change your mind about your entry category during the contest
NAQP:
Initial Mode:
AGB Party:
Serial & membership number may be entered as a single field when A is typed between the two numbers. For example, 23A48 (followed by Enter) is logged as 023 A48 in the respective fields.
Country multipliers are not tracked. This is unlikely to be a problem in a single- band 80m contest.
Use the SETDUPE command, at the beginning of each 15-minute period to reset dupe checking. Do not reset multiplier checking.
SDCHECK creates a log in Cabrillo format. Note that Cabrillo makes no provision for recording multipliers or points at individual QSO level - regardless of what may be required by contest rules.
WW PMC:
AUDIT to .TXT File:
This option was broken in V15.00. Fixed. Thanks G4BJM.
General Purpose Templates:
The first set is for events where you
exchange serials only (apart from RST).
SD still tracks countries by band/mode, as appropriate, because it's often useful to know, but ignores country totals for scoring purposes.
The second set is for events where you
exchange at least two data elements, one
of which may be a serial - for example,
Serial & Name, or Serial & Membership No.
The data elements must be separated by Space. If the first element is numeric, SD assumes it is a serial and inserts leading zeros, as appropriate, when the QSO is logged. Countries are not tracked.
If you're not sure which template to use for a specific event, try as many as you need, and observe what happens. You can change QSO points by editing the relevant template (.TPL) file at any time - even after the contest. Template file names are held in TEMPLATE.TXT. Please experiment, and let me know if you develop new templates.
SDV:
From 2011, Large Square multipliers count only for QSOs with UK stations.
SDV V14.31 has been updated accordingly. In general, SDV is not supported - whether in terms of bug fixes or enhancements, and that's why it is free.
ARRL 10m Contest:
Removed redundant "State or Province" question in the SDCHECK Cabrillo option.
In the Cabrillo log, Mexican abbreviations showed two characters, not three. Fixed.
ARRL 160m Contest:
CQWW Cabrillo Files:
Key File - SD.KEY:
Lost or damaged key files are not replaced. You should backup and print your file so that it may be restored or recreated when needed.
CQWW - Russian & Chinese Zones:
Rig Control:
A reminder that, after a frequency change, you can return to your original frequency by pressing F10 twice.
ESM in S&P Mode:
ARRL SS:
Rig Control:
LOAD Command:
CQWW Zones (USA):
PORTS Command:
Template Parameters:
Added the DUPETIME parameter - indicating the number of minutes after which contacts with the same station/band/mode will not be flagged as dupes. Used in the LZ Open and Dnieper Cup contests.
SDCHECK:
Logging Callsigns:
Zone/District Mult Window:
WAG Contest:
ILQP and other QSO Parties:
Dnieper Cup:
ARRL SS:
MCC Maritime QSO Party:
SYLRA Contest:
NRRL Fylkestest:
RSGB CC:
DXpedition Mode:
WinKey:
TRCDX Contest:
YODX Contest:
Caused by the omission of the SENDSERIAL: Y parameter in the corresponding template. Thanks GM4SID.
SDCHECK - DXpedition Mode:
WW PMC Contest:
WAE Contest:
Maryland-DC QSO Party:
SDCHECK - IOTA:
Fixed the "Multiplier Summary" and "Print File" options - IOTA references were not shown in full. Thanks OZ4ZT.
IOTA Contest:
When you're operating from an island, your own IOTA Reference is shown underneath the serial on the logging line (in case you forget).
It is now cleared any time the band/mode mult analysis appears.
When you type an IOTA Reference in the callsign field, you get a corresponding band/mode analysis - with slots needed in blue. This was broken in V15.14.
IOTA Contest:
Fixed autofill of IOTA References on a callsign match with .LST file records.
IOTA.LST, an up-to-date DXpedition call reference list, is included. It may be combined with your usual LST file, using NotePad, or loaded separately with the LOAD command.
A reminder that you may change mode with the C(W) and S(SB) commands. Without rig control, you can change band with B80, B40 etc. or 80M, 40M etc. commands. The former combined comands, such as 20C (change to 20m CW) have been removed - this applies to all contest options.
SCAG Sprint:
Don't forget to LOAD the SCAG.LST file included (Thanks SM3CER). SD asks you which LST file you want to load - type SCAG, not SCAG.LST.
Mode:
If rig control is enabled, the mode will follow the rig's setting in contests which permit mixed mode operation. Use the C(W) or S(SB) commands to change the rig's mode.
If the contest is single mode, SD will remain in this mode regardless of the rig's mode. Note that, in contests which permit both CW and SSB, you define your entry category when you create your Cabrillo log, and not when you start the contest.
IARU HF Contest:
.AUD Audit File:
Keyboard Mode and Sidetone:
SDCHECK:
IARU HF Championship:
Note: If an HQ station sends initials that SD has not pre-filled, type a single letter (any letter, followed by Enter) in the Zone field to log the correct initials. This option works even without IARU.LST.
SDCHECK:
Dupe Checking:
Note that, in QSO Parties, mobiles and rovers (/M or /R) are ignored for dupe checking purposes, although the Check Partial window shows when they have alrady been worked - they appear in lower case.
COM Ports:
When a single COM port is shared in this way, any level converters used for rig control must have their own power supply - no power is available from the COM port. WinKey COM ports cannot be shared.
Rig Control:
Enter sends the characters to the rig - use repeated Enters if necessary. To return to logging, use Esc to clear the field, followed by Enter.
CW Operators Club:
Use the LOAD command to load the CWOPS.LST callsign reference file - included in SD's setup files. SD displays Name and Number on a matching callsign. Enter a Membership Number to see the corresponding Name and Callsign - then Down Arrow to rearrange the fields, ready for logging.
Multipliers are unique callsigns.
Portugal Day Contest:
WinKey:
Fixed some spurious WinKey error messages, which were accompanied by erratic keying.
Fixed the routine (Shift-F1 etc.) to update keyer memories - the cursor remains in the empty callsign field, with no spurious keying on completion of editing.
Fixed the operation of the Previous Serial (#P) keyer memory parameter.
Check Partial Window:
Rig Control - Change Mode:
In this context, the CWREVERSE command toggles your rig's preferred CW "sideband" where Normal indicates that the CW pitch increases, away from zero beat, as you tune up the band, and Reverse indicates that the CW pitch decreases, towards zero beat as you increase frequency. Your preferred setting (0-Normal, 1-Reverse) is held in the SD_CWREV parameter in SD.INI.
NOTE: Some rigs do not support "reverse" CW sideband. Check the CW Value 1 and 2 entries in your .SD rig-control file.
Band Change after Edit:
DXpeditions and Special Events:
Countries are tracked by band and mode.
The corresponding SDCHECK export options are Cabrillo, ADIF and Text. Any data received is included, but there is no record of data sent, other than RST. Cabrillo logs include QSO sequence numbers.
In due course, I will add import options for other SD logs to enable maintanance of a basic station log (with DXCC checking by band and mode) in a single SD-compatible file.
Dupe Checking in State QSO Parties:
NOTE: In these events, no dupe checking is done on /M and /R callsigns. If they are logged, and ARE dupes (logged with the same county code as before), SD will not flag them as dupes.
Digital Voice Recorder:
The DVR command toggles between playback of SD's internal pre-recorded WAV files, if any, in your SD folder, and pre-recorded voice messages from your rig's DVR.
This feature depends on having rig control enabled - in the usual way with the PORTS comand. SD sends commands to play the appropriate recordings, as defined in the parameters in the .SD control file for your rig. To date, it is implemented and tested only for the Elecraft K3.
To understand how to implement this feature for other rigs, follow the example of the parameters in K3.SD, SD's control file for the Elecraft K3.
If you are successful with your rig, please send me a copy of your updated .SD file.
With mode set to SSB, and Caps Lock Off, F1 to F8 plays the corresponding audio file from your rig. In ESM (Enter Sends Message) mode, here is what happens -
ESM - RUN Mode
Enter, when the QSO is logged, plays M3, your "Thanks" recording.
UBA Contest:
Scoring is hard-coded in SD - the values in the template files are ignored.
Limitation: On the DX (non-ON) side, SD tracks European Union country, and Belgian province mults, but not Belgian prefix mults. I will add prefix tracking before the next UBA contest in January 2011.
Commonwealth Contest:
As callsigns are typed, the country/band analysis below the callsign reflects the bonus status at all times (blue=bonus), and the top RHS window shows the status, for the current band, for all Commonwealth areas in the corresponding continent, making it easy to spot wanted bonuses.
Serial and HQ may be logged as a single field. For example, 24HQ, followed by Enter, is logged as 024 HQ.
Edits of previous QSOs which flag or unflag HQ stations do not always score correctly - in terms of updating other QSOs which may themselves need to be flagged or unflagged as bonus QSOs. However, all QSOs are rescored correctly when SD is restarted.
TIMES Template Parameter:
In the template file for the Commonwealth Contest, TIMES is set to three - the first three QSOs with each Commonwealth area count as bonuses.
IOTA Contest:
Here are some of SD's IOTA features.
As you type callsigns, SD identifies the country or call area and displays all coresponding IOTA references - those available as multipliers on the current band and mode are highlighted.
SD identifies the continent, as calls are typed, and pre-fills the abbreviation in the IOTA Reference field. Hit Enter to log a blank reference (no need to delete the continent), or simply add the reference number. Leading zeros are not required. For example, add 4 to a pre-filled "EU" to log EU004.
When editing IOTA references, leading zeros (if any) are dropped and the cursor is positioned after the continent. SD adds the zeros, as necessary, after edits.
When entering a callsign which can only, or is very likely to, belong to a specific IOTA reference, the reference is pre-filled. You may overtype the numeric part, or use Esc to delete the field, as appropriate, before logging the QSO with Enter. This feature is controlled by storing the first IOTA reference, in SDIOTA.CTY, in lower case.
When entering island callsigns worked previously, or any callsign associated with a specific IOTA reference, the mult status, by band and mode, is displayed under the callsign. You can instantly decide whether it's worth asking for a QSO on another band or mode.
When you enter any call worked earlier, you see a display of band/mode slots worked and needed. Those already worked (including the current band & mode) are shown in black - so you can say, for example, "Thanks for 4 QSOs". When it is the callsign of an island station, multiplier bands/modes are highlighted.
To see the band/mode multiplier status for a specific IOTA reference, type it in the callsign field. For example, type EU5 to see the information for EU005. Add 1 to see the information for EU051. Use Esc to clear the field, ready for callsign entry.
Key File:
SCAG Sprint:
Marking QSOs for Deletion:
Cosmetic:
SCOREMULTS Template Parameter:
SD tracks countries worked, but does not count them as multipliers in the Score.
This applies to RSGB 80m CC and AFS, and to simliar events. Serial Sent was missing from corresponding Cabrillo logs - this has been fixed.
Another benefit is that the new templates facilitate variable scoring, in contests with no mults, by own country, own continent and other continents - by band and mode.
The following templates have been changed. They are not compatible with earlier versions of SD.
QBALTIC : Baltic Contest : Updated
QGEN : General - No Mults : Deleted
QGENCW : No Mults - CW : Added
QGENSSB : No Mults - SSB : Added
QGENMIX : No Mults - Mixed : Added
QREMDAY : WIA Remembrance Day : Updated
QRSGCC : RSGB CC : Updated
QRSGAFS : RSGB AFS : Updated
QRSGLPFD : RSGB LP Field Day : Updated
Editing QSOs:
JIDX Contest for DX entrants:
Keyer & Serials:
New Simplified Format for SD's .ALL files:
The new QSO format is similar to Cabrillo, but without the duplication of any fixed elements in the sent exchange - apart from "Serial Sent" when relevant.
Unlike Cabrillo, QSO points are shown, together with indicators for dupes, and for country, and district or zone multipliers.
The file formats for SDC, SDI, SDU and SDX are unchanged. These programs were last updated in V14.24, and will not be updated again.
Automatic Rescoring:
ZAP Command Updated:
POINTS Command:
Serials:
The SETSERIAL (or SERIAL) command lets you reset Serial Sent at any time - for only for contests with the SENDSERIAL parameter in the corresponding template.
Edited QSOs:
RSGB RoPoCo:
WAG Contest:
SCP Window:
Keyboard Mode - CW:
When using WinKey with PTT enabled (use SD's STATUS command to check - and the PTTON command if necessary) PTT is now activated continuously while in keyboard mode.
ARRL SS:
OKOM Contest:
Check Partial & Super Check Partial (SCP):
With SCP, the default option shows calls that match the typed characters, regardless of their position in the call. Comma toggles the display to matching prefixes, and Full Stop (Period) shows matching suffixes.
SD now reverts to the default prefix option when QSOs are logged, or wiped with Minus. Otherwise, with suffix checking, you may not be aware of potential dupes until the full call is typed.
ESM - Enter Sends Message:
Band/Mult Status:
Bands already worked, for that specific callsign, are displayed in black - giving an instant count of QSOs with that station (including the current band).
Band not worked (for that station) are shown in white, as are bands that are not mults for the corresponding county, or zone, when applicable.
The display has been simplified in that a "dupe" band is shown in black - the same as any other band worked. Of course, when a call becomes a dupe as it is being entered, it turns red.
Again, on a callsign match, the current band is always shown in black, even if the QSO would be a multiplier. However, the multiplier status continues to be shown above the callsign. The net result is that you always know whether the call being typed is a dupe or a mult, and the number of bands worked.
In the FOC Marathon, when working a station on the fourth or fifth band, the remaining bands are highlighted to indicate the need to get the extra band bonuses.
WinKey - Esc stops playback:
POLLTIME and LINKTIME:
SDC - Commonwealth Contest:
ARRL DX Contest:
CW Auto-Start:
RSGB 160m - for UK entrants:
ARRL 10m Contest:
Registration:
When you register, you get a key file, by email, for a single callsign of your choice. SD operates as normal when used with that callsign - allowing for country identifier changes. With no key file, or if used with an unrelated call, SD runs in DEMO mode, and logging is significantly delayed after 30 QSOs. A corresponding delay is included in all SDCHECK options in DEMO mode.
The key file, SD.KEY, gives access to new versions of SD for twelve months. Any copy of SD downloaded within this time will continue to work indefinitely, without restriction, when used with the registered callsign in the presence of the key file.
The key file is a standard ASCII text file with 57 numeric digits. You should print and secure this file, so that you can recreate it when necessary. If you edit the key file, it will not work.
If you prefer not to register, you may continue to use any version of SD you already have. The last "free" release was V14.30.
ARRL DX:
WIA Remembrance Day Contest:
Note: For the purpose of dupe-checking over the previous two hours, duplicate QSOs already logged on the current band and mode are disregarded when comparing times.
WAE:
Restored the analysis of countries worked/ wanted as prefixes are typed. Thanks EA8CN.
Fixed the display of QTCs available, as callsigns are typed, for DX entrants. Note: the count does not yet exclude a QTC reported back to the same station - that will be fixed in V14.29. Thanks 5B4AIZ.
WIA Remembrance Day Contest:
When a call is entered that has been worked less than 2 hours ago, the remaining time is shown. Thanks VK2NU.
IARU HF Championship:
SDCHECK: The Cabrillo option repeated the mode question and entered it twice in the CATEGORY record - for example CWCW instead of CW. Fixed.
Band Map:
Keyer Memories and WinKey:
Repeat Feature on CQ Calls:
BWQP:
Contests With No Mults:
SD.MAP - Keyboard Mapping File:
CW Field Day:
Cabrillo Logs:
RST:
Icom IC-7200:
EU Sprint - CW:
Restored the QSOs by Callsign window, and fixed the corresponding band summary for matching calls shown beneath the callsign on the logging line.
Holyland Contest:
ES Open Championship:
New York QSO Party:
SCP - Super Check Partial:
The SCP command is retained, but only as an alternative to Equals when operating in SO2R mode (where = equalises the frequency on both rigs).
SD - Real-time Displays:
Until now, it displayed a similar (redundant) analysis in a window on the top right of the screen.
Now, as prefixes are typed, this window shows a worked/wanted analysis for all countries in the corresponding continent - for the current band and mode.
If the prefix corresponds to a country which gives district or area codes, SD shows the corresponding worked/wanted analysis window.
The bottom line is that all relevant multiplier data is shown, in real time, as prefixes are entered. Some day, all contest loggers will do this. To see how it works, try a test file for RDXC (the Russian DX Contest) or the RSGB 160m contest for UK entrants.
Thanks EA8CN.
Manchester Mineira Contest - MMAA (PY):
URE Anniversary Contest:
CW Keyer Memories:
SCP - Super Check Partial: (SD Only)
If you prefer to see SCP calls by prefix only, press comma - this display is often more relevant and less cluttered. To return to the default (full) SCP display, press comma again. In effect, comma toggles the SCP display between "Full" and "By Prefix". Thanks to G3UEG for the suggestion.
To see SCP calls by Suffix only, press full stop (period). With this option, and with auto insert enabled (toggled with the AI command), the cursor moves to the start of the callsign ready for characters to be inserted. Otherwise, the cursor does not move. For information, I use the OVR (Overwrite) mode with auto insert enabled. That way, anything I type replaces what's underneath (no need to separately delete unwanted characters), with the exception that, when the cursor is positioned at the start of the callsign field, the mode is temporarily changed to INS (Insert) - as you might expect!
As always, with SCP disabled, comma and full stop display calls, by prefix or by suffix, from QSOs already logged. Again, with SCP disabled, equals "=" enables SCP temporarily. Once you log a QSO, it reverts to disabled.
A reminder that you can retrieve any non-dupe callsign in the Check Partial window, with or without SCP, by using the Up Arrow key. When there is only one callsign in the window, Up Arrow immediately moves it to the logging line. This can save a lot of time, especially with longer callsigns. Another SD exclusive.
Broken code in SD V14.23 (integrating SCP with dupe and mult checking) caused problems in logging the exchange in the UBA Spring contest and many other contests. Fixed, thanks EI7GY.
WIA Remembrance Day HF Contest:
ARRL DX Contest:
SDCHECK: Fixed the Claimed Score calculation for W/VE entrants. Thanks VE7JKZ.
SDU - UBA Contest for DX Entrants:
SD.INI File:
SCP - Super Check Partial:
PACC for DX Entrants:
WinKey:
SDV:
FOC Marathon:
Ten-Ten QSO Parties:
Black Sea Cup International (BSCC):
VK Shires Contest:
SDCHECK:
Partial Call Checking - by Suffix:
The cursor now moves to the start of the callsign field, and what happens next depends on your data entry mode.
If it is "Insert" (INS), any additional callsign characters are inserted before the cursor.
If it is "Overwrite" (OVR), additional callsign characters replace the existing ones, and that's probably not what you want. However, as standard with OVR mode, you can use the Space Bar to move the existing callsign characters to the right - before typing new characters.
With Auto Insert data entry mode (OVR with the "V" highlighted), the mode is temporarily switched to Insert so that additional callsign characters are inserted before the cursor. Once you use any cursor-control character, or leave the callsign field, the mode reverts to Overwrite (OVR). This is easier to test than to describe!
With Auto Insert, whenever (and however) the cursor is moved to the start of the callsign field, the mode switches temporarily to Insert. I recommend this mode - it's what I use at all times. Use the AI command to toggle your data entry mode between OVR and Auto Insert.
For information - I'm working on integrating Super Check Partial (SCP) calls so that potential dupes and mults will be displayed in a consistent way.
HADX Contest:
Rig Control:
WWPMC Contest:
IRTS Counties Contest:
WinKey - Callsign Type-ahead:
WinKey - Callsign Type-ahead:
Now, the only effect is that the "missing" characters are not included in the initial F2 exchange message. When the QSO is logged, the full "corrected" call is sent as part of the F3 TU message - and is logged in full.
Contests with Country Mults:
SETDUPE Command:
Stew Perry Contest:
Your grid square is entered as 6 characters, although only the first 4 are used, and it is stored in SD.INI.
SDCHECK - ARRL SS:
DARC XMAS Test:
SSA Manadstest:
SDX - DXpeditions & Special Events:
Fixed a disappearing QSO syndrome. Some QSOs were not written to the log file - although they were always present in the audit file.
SDCHECK - Cabrillo:
SD - Post Contest Mode:
NRRL Telefonitest:
ARRL SS:
JT DX Contest:
Country Multiplier Files:
CQ 160m Contest:
SDVCHECK:
PA QSO Party:
PMC WW Contest:
Ohio State Parks on the Air:
RSGB & EU Sprints:
LZ Open:
When a dupe callsign is typed, the remaining time, before it will no longer be a dupe, is shown in place of the word "Dupe".
The "Countdown Timer" window now highlights calls that may be worked again, after 29 minutes. They are shown for 10 minutes, and are dimmed if worked within this time.
Thanks LZ1GL.
RSGB 80m Sprint:
EU Sprint and RSGB 80m Sprint:
Red - you must QSY at least 2 kHz.
Normal, followed by red #. This applies only to the RSGB Sprints - it indicates you must QSY at least 3 kHz before calling CQ.
Normal - you may call other stations or call CQ.
With ESM disabled, or in SSB events, SD does not know the mode (RUN or S&P) of the QSO you've just logged, and will show the frequency in red. If the frequency is yours (you have just logged a QSO where you called the other station), minus toggles colour between red and normal - but only when the callsign field is blank.
CW from Printer Ports
Rig Control - Omni VII:
District Codes - not multipliers:
The template parameter NON-AREA-MULTS (already used in Type 10 contests) controls this. If "N", district codes not already in the .MLT file are logged, but will not be mults. If "Y", you have the option of adding new district codes - they will all count as mults.
With this parameter missing, the default is "Y".
Voice Keyer:
For serial ports, RTS is used for PTT. For parallel ports it is Pin 16.
RSGB 80m Sprint:
Following a QSO where you called the other station, you can stay on the frequency for one further QSO.
With rig-control and ESM enabled, SD colour-codes the frequency display to let you know your status at all times.
When the frequency is shown in red, you must keep moving. When it is in the "normal" colour, you may call other stations (QSY over 2 kHz). When the normal colour is followed by #, you can call CQ (QSY over 5 kHz).
An abbreviated version of the frequency of your previous QSO is shown for reference.
King of Spain Contest:
Updated the Cabrillo option in SDCHECK - it no longer asks the question "Log Serial Rcvd". The "correct" answer is "N" and it's now hard- coded. Thanks G4RCG.
SDI - IOTA Contest - Callsign Edits:
Edits on previously logged QSOs did not take effect until another QSO was logged. Fixed. Thanks G3PJT.
IOTA references corresponding to callsigns which had been deleted were sometimes carried over to the next QSO. Fixed. Thanks G4BJM.
SDIOTA.CTY: Added Shetlands as a separate call area. Thanks MM0XAU.
SDICHECK: Edits done using the Edit option updated on screen but did not always update on file. Fixed. Thanks EI7GY.
EU HF Championship:
RSGB 80m Sprint:
SDV - District Multipliers:
WAE:
Fixed delays in logging CW QTCs when no keyer port was enabled. Thanks G3ZRJ.
Broken code meant that only the RSGB.MLV district code file could be selected. Fixed.
CW Keying:
WinKey: At startup, with no CW port enabled, WinKey will be disabled, and must be enabled with the WINKEY command, if relevant, once a port has been enabled with the PORTS command. The STATUS command shows relevant settings.
PORTS Command: The range of serial (COM) ports directly supported is now 1 - 24. Use 51-54 for LPT1 - LPT4. If you are currently using ports 9-12 for parallel port keying, you must update these now.
ESM - Toggling modes:
As before, the Grave Accent key (below Esc) toggles the mode without sending any message.
Elecraft K3:
Score Window:
SDI - IOTA Contest:
Bill Windle QSO Party:
Bill Windle QSO Party:
INORC Contest:
Added callsign/membership .LST lookup - similar to the existing FOC Marathon features.
With a suitable .LST file, SD displays the membership number on a callsign match, or the callsign when a membership number is typed. In the latter case, Down Arrow will then swap the membership number and callsign - ready for logging.
Italian Manual:
ESM with AutoStart:
CW in Keyboard Mode:
When switching to keyboard mode, with serial port keying, PTT worked correctly but there was an initial key down - not cleared until the first keyboard character was sent. Fixed. Thanks I4FTU & W4ATK.
Audible Dupe Warnings:
Country (CTY) Prefix & Multiplier files:
King Of Spain Contest:
Updated the template file to select CQWW.CTY, rather than DXCC.CTY, as the country multiplier file.
Indiana QSO Party:
Rig Control:
GQP:
MIQP:
FQP:
SETDUPE:
LZ Open:
The logging area now shows the full exchange, both sent and received. RSTs are suppressed. Thanks LZ1GL.
Rig Control:
When you change the default values, using the LINKTIME and POLLTIME parameters, the new values are again stored in SD.INI and apply each time you start SD.
Rig Control in Mixed-mode contests:
SDX - Dxpeditions & Special Events:
RoPoCo Contest:
If you used Esc to clear a callsign that would be a dupe, the postcode or area code logged earlier for that callsign was pre-filled for the callsign entered next. Fixed. Thanks GM3POI.
ESM - RUN & S&P modes:
RoPoCo Contest:
SDX - DXpeditions and Special Events:
LZ Open:
Note: The received exchange must be logged with a space in the middle - as, for example, 010 034.
Post-Contest Logging:
SD:
RDXC:
Rig Control Parameters:
Increased the automatic POLLTIME and LINKTIME values at startup - following reports of loss of synchronisation with the previous values.
SDC - Commonwealth Contest:
The rescore option failed when logging a dupe. Fixed.
When restarting SDC, dupes were not counted. Fixed.
SD - Editing previous QSOs:
Startup:
Rig Control Parameters:
WinKey:
Fixed intermittent delays in starting messgage playback when rig control is enabled.
WinKey sometimes changed speed for no good reason. Caused by broken code when resetting WinKey's speed to "normal" after message playback. Fixed. Thanks G3KZR.
WinKey:
Winkey is now polled independently of POLLTIME and LINKTIME - the rig-control timer parameters.
Switching ESM Mode:
SDC - Comonwealth Contest:
Added a RESCORE option. This is required because, at present, SDC does not always flag a bonus when a "normal" QSO is subsequently edited to "HQ".
There are no data integrity issues, and no issues with scoring non-HQ QSOs - it's just a matter of flagging and counting bonuses for HQ QSOs. In effect, RESCORE re-inputs all QSO data and eliminates any editing issues.
Use this option before preparing your Cabrillo log to ensure your Claimed Score is correct.
To do a re-score, start SDC and, when asked for the name of the Contest File, enter RESCORE. You're then asked for the name of the file to be re-scored, and everything is automatic after that.
Your original file is renamed .OLD, and the new re-scored file is .ALL - for further use with SDC or SDCHECK.
Re-scoring works only for .ALL files created by SDC. Depending on priorities, I may add input options for SDC's audit (.AUD) files and Cabrillo logs - and perhaps add it to the other HF loggers.
WinKey Speed Changes:
Temporary speed changes within messages are now reliable and consistent. Use #1 to #9 to increase speed - from the current WPM value. They may be chained - for example #9#9 gives a temporary 18 WPM increase. To reduce speed, use #-1 to #-9.
To reset speed to the default value, use #0. SD adds this to the end of all messages - you don't need to do this yourself, and it's no harm if you do.
Restrictions:
When speed is controlled by WinKey's pot -
When speed is controlled by the keyboard -
With internal keying (WINKEY disabled), the speed change and "instant QRS" features work only when no message is playing.
If this sounds a bit complicated, you're right. It's not so simple to control WinKey while supporting all possible speed options. The "best" option is probably WinKey - with the speed pot.
ESM - Enter Sends Message:
Keyer:
Alabama QSO Party:
Changed the template for Alabama entrants. QSOs with other Alabama stations may count as state mults but not as county mults.
GQP - Georgia QSO Party:
WinKey Speed Changes:
The speed-change keys are ignored when WinKey is enabled.
BCC QSO Party:
Mult counts may not be correct if you edit or zap QSOs. However, they will be correct any time you start SD. SDCHECK shows the correct Claimed Score in your Cabrillo log.
LZ Open:
Previously, you had to type the full call for the purpose of dupe checking.
A new window displays a countdown of the time until stations previously worked can be worked again. Any call you hear that's not already in this window cannot be a dupe - unless you've logged more than 40 QSOs in the last half hour. It also serves as a reminder to chase calls as their remaining time drops to zero. Thanks G3LET.
FOC Marathon:
Restored the dupe warning after entering a member's number - when both the callsign and the number were 4 characters long. Thanks G4BJM.
WinKey Speed Change:
In Keyboard CW mode, toggled with Ctrl, speed changes with the Up and Down arrow keys are now supported, but not with WinKey's pot.
SD polls WinKey, in a similar way to polling the rig, to get WinKey's status and pot position. WinKey and SD are more responsive to speed changes when POLLTIME and LINKTIME are minimised.
If you're not using rig contol, set POLLTIME to 50 and LINKTIME to 20. With rig control, use the fastest BPS supported by your rig, and set POLLTIME and LINKTIME to the lowest values that maintain control.
Country .CTY Prefix & Multiplier files:
PACC - Cabrillo:
WinKey:
You can restore control to the WinKey pot by turning it. Depending on the position of the pot, there may be an initial abrupt change in speed. This is not a bug - it's caused by the speed being a function of the position of the pot together with the preset values for Minumum Speed and for Speed Range. Use the MINWPM and WPMRANGE commands to change these values, if preferred.
If you get into trouble, the WKINIT (or INIT) command will return control to the WinKey hardware.
This has been tested on WK2 with a direct USB feed, and on WK1 using a microHAM USB/RS232 converter and the latest microHAM router software.
PGA Contest - SP:
DARC-10m:
Icons:
Dupes:
Logging Area Codes:
Previously, you had to log the QSO with the old "incorrect" area code and then edit it.
This feature applies equally to IOTA island references in SDI, Belgian provinces in SDU, and district codes in SDV.
Croatian CW Contest:
SD - SETDUPE Command:
SDU - UBA Contest:
UBA Winter Contest - DX Side:
Country .CTY Prefix & Multiplier files:
SDVCHECK:
ILQP - Illinois QSO Party:
SD's Manual:
Non-English characters:
Multiplier Files:
Washington State Salmon Run:
Resetting Dupes and Multipliers:
The SETDUPE command was introduced for V9.15 in June 1998. It reset dupe checking and the Check Partial dispay.
SETDUPE now resets multiplier and dupe checking, and all corresponding display boxes. Once you use this command, you must not edit QSOs from previous sessions. If you do, there is no guarantee that SD will track dupes and mults correctly.
Display of non-English characters:
The CODEPAGE command lets you select alternative character sets - known as code pages. Code page 850 is the default option for SD and is recommended for most European and US keyboards. The code page value is stored in SD's configuration file SD.INI. Code page selections are ignored when they are not supported by your PC.
CODEPAGE works with WinXP. It may not work with earlier versions of Windows.
Regardless of the code page selected, some non- English characters will not display correctly when SD runs with a raster typeface.
To change the typeface, click the SD.EXE icon at the top left of SD's window, select Properties, then Font. Select the Lucida Console TrueType font, and choose an appropriate typeface size such that SD's window is as large as possible on your screen.
Country .CTY Prefix & Multiplier files:
NORWAY.MLT updated. Thanks LA6GF.
LZ DX Contest:
OKOM Contest:
RSGB 1.8 MHz Contest:
Fixed a bug which prevented a UK station being logged as a dupe.
Country Files:
Ukraine DX Contest:
PAQP - Pennsylvania QSO Party:
SDV - VHF Contests:
TOEC:
CAQP - California QSO Party:
Oceania Contest - and others with prefix multipliers:
PACC:
EU Sprint & RSGB 80m Sprint:
CQIR - Ireland Calling 29/30 September:
RDA (Russian District Award) Contest:
Keymens Club of Japan (KCJ) DX Contest:
New Jersey QSO Party:
Holyland Contest:
EU HF Championship:
WAE QTCs:
QTC totals are now shown by band.
After sending QTCs, the CW repeat of the QTC Reference has been removed.
After receiving QTCs, the QTC reference is confirmed on CW.
Cabrillo Log. Updated to include QTC totals by band. The QTC records are now appended to the QSO records in the .LOG file, so that only the .LOG file is needed for your entry.
RDA (Russian District Award) Contest:
RDA.MLT is the new multiplier reference file containing several hundred of the more common district codes. Other district codes are added automatically to RDA.MLT as they are logged - with full multiplier tracking.
RDA.LST is a callsign reference file with some 17000 Russian callsigns extracted from previous RDA logs, and is loaded at startup. SD then auto-fills the 4-character district code on a callsign match.
NAQP:
Fixed potential errors when editing states on previously logged QSOs.
SDCHECK:
Added name and state to ADIF export.
All Programs:
SD and SDCHECK: Commas are now accepted in Address and Soapbox fields.
IARU HF Championship:
SDI - IOTA Contest:
SD.PDF - Manual:
.CTY Country Multiplier Files:
Internal CW Keyer:
Fixed PTT for Keyboard Mode from parallel ports.
IARU HF Chanpionship:
Updated IARU.REF. Some on-air HQ initials differed from the "official" initials.
IARU HF Championship:
For example, if you receive RSGB from GB7HQ, enter "R", or any other letter, to log "RSGB".
Valid non-numeric "Zones" - AC, R1, R2 and R3, are not affected.
The FORCEHQ command toggles this feature. The default is ON.
SD - Venezuela Independence Day Contest:
SD is written in
PowerBASIC
To EI5DI's Home Page