The tooltip for info text in QSO entry boxes was out-of-date.
Crash if reset WAE log when there was no selected QTC Series.
Failed to send report or log QSO with certain preference settings for first QSO in a new log. Thanks JH5GHM.
Tabbing into report entry field wasn’t selecting the “S” digit. Thanks GØDVJ.
Rebuild log was setting previous QSO to the first QSO in the log, instead of the most recent QSO in the log.
Name lookup for the CWOps CW Open Competition contest was broken.
This version of SkookumLogger is built using Xcode 5 Developer Preview 6. There should be no differences noticeable by users. The Analyze function in DP6 identified these issues, which have been fixed:
arc4random()in KDMicroHam -startMicroHamHeartbeat
SkookumLogger has simple unit tests that exercise the method for extracting a prefix from a call sign using the CQ WPX rules. The foundation classes for unit testing have changed from OCUnit to XCTest; XCTest is present in the SDK for OS X 10.9 but not 10.8. This affects only developers who want to run the unit tests.
SkookumLogger now ignores a hyphen in the IOTA Reference Number QSO entry field when detecting multipliers. A hyphen is entered for you if you log a QSO with that entry field empty.
SkookumLogger now downloads the “call history file” for TR4W to construct the CWOps database. The previous approach, downloading the web page containing the roster table and parsing the html was broken by recent changes to that page. You don’t need to know this, just keep using the File ▶ Update CWOps Database command as before.
The telnet connection information for the EA7URC DXSpider cluster node has been updated, and DBØSUE has been added to the list of nodes. Thanks DL7ALM.
Logic for detecting multipliers in the IOTA contest was broken, resulting in no multipliers and zero score. Thanks G6NHU.
ADIF export records now include the DXCC field, thanks to a change made to
cty_wt_mod.dat made by AD1C. This has nothing to do with contesting, but K7GQ asked for it and Jim volunteered to add the necessary information. You will need to update your countries database via File ▶ Update Countries Database.
WD7K has provided code supporting the microHAM Digikeyer II. Neither of us has the hardware to test whether on not this works.
The feature that wipes the Pounce QSO entry fields when main receive frequency changes now works for Assisted and Non-Assisted log categories. In programmer-speak: When radio main receive frequency changes and a Pounce QSO entry field has keyboard focus and the difference between the new frequency and the main receive frequency of the Pounce QSO is greater than the Activities Frequency Matching Tolerance, then Clear the Pounce QSO entry fields; then replace the main receive frequency of the Pounce QSO with the new radio main receive frequency. If you tune slowly in small steps, the clear won't happen.
JH5GHM has updated Kenwood radio support to handle the LCW/UCW preference that was introduced in 1.6.19.
The sample antenna configuration has been simplified and cleaned up.
The builtin Counties and SuperCheckPartials databases have been updated. Note that these are unconditionally overridden by databases that you have downloaded, which may be older.
The new amplifier type named Phantom enables automatically setting radio output power per-band without a serial connection to a real amplifier. Use Radio ▶ Amplifier ▶ Operate to toggle whether or not the pseudo-amplifier is in operate or standby mode. To turn the pseudo-amplifier on, choose None as the Port in Serial preferences, then Connect. Do not attempt to connect to more than one device at a time using the None port. Thanks JH5GHM.
The alert that appears when a new USB device is plugged in now includes Tuner as a type that may be immediately connected.
The MainReceiveFrequencyChangeInPounceModeCreateActivity preference introduced in 1.6.18 now has a checkbox in Logging preferences, “Main receive frequency change creates activity”. A related preference checkbox “Main receive frequency change clears entry fields” has been added. Both of these behaviors apply only when the Pounce QSO entry box is active and the log category is Non-Assisted. Thanks W2RU, W2CS, JH5GHM.
A third new preference checkbox has been added to Logging preferences: “Prefer CW Reverse”. This choice tells SkookumLogger which CW mode to use when setting radio operating mode for radios that have both lower sideband CW and upper sideband CW. Thanks W2CS.
The feature introduced in 1.6.18 that creates activities when the radio frequency changes has side-effects that degrade SkookumLogger support for assisted operating. That feature is now only enabled for logs which have Non-Assisted as the choice for the Assisted Cabrillo Category Items in the Log Settings sheet.
Management of K3 frequencies and modes has been revamped to address issues noted in a recent mixed-mode contest. Briefly, sub-receiver mode is managed separately from operating mode, RIT offset is used when difference between transmit and receive frequencies is not zero and less than 10 kHz, and split is used when the offset is greater than 10 kHz. Thanks W2CS.
When Radio ▶ Copy Run to Pounce or Radio ▶ Copy Pounce to Run changes the active QSO data entry radio state display values, the radio is now also set to those values.
JH5GHM has provided updated Kenwood radio support, addressing radio frequency and operating mode control, and DVR support in the TS-590.
The feature introduce in 1.6.18 that creates activities when the radio frequency changes failed to set a time stamp on those activities.
Grabbing spots from activity tables was sometimes failing to set operating mode correctly.
An unhandled exception occurred in KAT500 code when connected to a serial port that was physically connected to a KPA500.
When the main receiver frequency changes while in Pounce mode and the Pounce call field isn’t empty, a new Activity table is created from the Pounce entry box information. This is an experimental feature. To enable it, open Terminal and enter (one line):
defaults write com.k1gq.skookumlogger MainReceiveFrequencyChangeInPounceModeCreatesActivity 1
To disable it, type the same command with 1 replaced by 0.
The Kenwood radio modules have been updated by JH5GHM, adding features related to the TS-590.
The Notes QSO entry field width has been increased. Thanks GØDVJ.
Navigation among the QSO entry fields with spacebar was broken by the frequency detection scheme introduced in 1.6.17, with various symptoms depending on how many characters had been typed into the call field. Thanks GØDVJ.
Contest ID for Special Event Station Module was Generic Logging. Thanks GØDVJ.
Notes entry field tooltip was Name. Thanks GØDVJ.
Not a misfeature: ADIF export spews QSO records in the same order as displayed in the Log table. You may want to short on UTC ascending before doing export; the default is UTC descending. ADIF export for the SES module does not include the Notes information.
Added the Special Event Station “contest” module in the Other group. This module supports logging QSOs whilst operating at an unusual entity like G100RSGB. The sent exchange is simply signal report. The received exchange is signal report and a Notes field. The new Notes entry field populates the Notes column in the log table; you can type anything you want including spaces and nothing. Because the field accepts spaces, you cannot use spacebar to navigate out of the Notes entry field; use tab. The Special Event Station module understands all bands between 160m and 70cm (including WARC bands) except the 60m channels. QSOs are per-band and per-mode. DXCC countries are tracked as "multipliers" and are also per-band and per-mode. Thanks GØDVJ.
When you press the spacebar or the return key with keyboard focus in a call entry field, SkookumLogger now checks whether or not the content of the call field is all digits. If it is, then SkookumLogger treats the number as a frequency in kHz. If the frequency is less than 1000 kHz, SkookumLogger adds the frequency of the lower edge of the current band. Then SkookumLogger sets the radio main receive and transmit frequencies to the frequency you typed, and clears the call field while keeping keyboard focus in the call field.
Calls in the Log ▶ Operator submenu are now sorted alphabetically, so that they are listed in the same order on all computers in a SkookumLogger network.
The UDP packets broadcast for WRTC score reporting had an XML formatting error. Thanks WA1Z.
Log ▶ Delete Last Log QSO was reversing the sort-by-time ordering in the log table.
Edit ▶ Undo has been disabled in all QSO entry fields; using that function caused a hang. Thanks G4FTP.
The SPEED control on a connected Elecraft K3 radio now controls the sending speed of a connected WinKeyer. This feature provides an “analog” control for WKUSB Lites that are built without speed potentiometer, like mine.
The new command Messages ▶ Set Beacon Interval defines the time elapsed between start of DVP message #1 play when Beacon mode is enabled. To use this command, start playing message #1, choose Set Beacon Interval after the message ends and a suitable pause has elapsed.
The URLs for posting and viewing scores has been updated.
Katsuhiro, JH5GHM, reports that SkookumLogger Just Works with the K1EL WKUSB Lite.
Activities preferences has a new checkbox, “Clear creates activity”, default off. When checked, SkookumLogger will create an activity (like Log ▶ Insert In Activity Table) when you choose Log ▶ Clear QSO Entry, using the information in the QSO entry fields about to be cleared. Thanks GØDVJ.
The fonts and colors applied to the call signs in the partials box and the call entry fields are now also applied to the status text in the QSO entry boxes.
Reporting of serial communications errors is now enabled in the release version to support tracking down user issues. Thanks KC7PM, who is seeing hangs with a TS-570 radio connected via a Keyspan USB-serial adapter, as yet unresolved.
The layout of the Log window has been revised to move the QSO entry boxes away from the lower left corner. The partials box is now 2 columns by 9 rows, with 11-character (was 13) columns. The two QSO entry boxes now have three lines, with the status text that was at the end of the information text moved to the first line where it is always visible. To keep the most recent log table entry close to the QSO entry boxes, the log table is now sorted in descending chronological time and scrolled to the top row. Thanks JH5GHM, GØDVJ, W2CS, W2RU.
SkookumLogger now remembers the current operator selection across restarts. Thanks GØDVJ.
The mode for the Phantom radio type wasn't being initialized properly, causing QSOs to be saved with “N/A” as the mode. Thanks KM3T.
The Record Voice Message command is now supported with the Yaesu FT2000 radio. The CAT command set for this radio is somewhat limited; you can record only messages 1 through 4, and you must use SkookumLogger to both start and end (escape key) recording. The companion Repeat Message Play command is disabled for this radio type. Thanks GØDVJ.
Added support for IC-7200 radio by WD7K — thanks Dave.
To cause SkookumLogger to save activity table content each time it discards old activities, and to load the save activities when you start SkookumLogger, open Terminal and type this command:
defaults write com.k1gq.skookumlogger RememberActivities 1
To stop remembering activities, use the same command with 0 in place of 1.
Radio ▶ Announce QSO now sends the QSO to your DX Cluster connection when the active QSO entry box is empty and the frequency of the most recent log entry is different from the current radio frequency.
Mobile entrants inside New England for the New England QSO Party may edit the sent exchange location field in the Log Settings sheet, in order to use a single log for operation from many counties with correct duplicate checking, multiplier tracking, and scoring. Thanks KM3T.
Cabrillo export for VA QSO Party in-state has been updated to meet undocumented requirements. Thanks W2RU.
Posting to Live Scoreboard for mixed-mode contests failed to display numbers for QSOs.
The Edit QSO panel in the Log window (double-click a log table row) now has a field for editing the sent serial number. The field is always present in the top row of entry fields whether or not the contest exchange has serial numbers. You might want to edit the sent serial if you sent a different number than you logged, in order to avoid possibly causing a log-checking penalty for the other station.
File ▶ Post to Live Scoreboard toggles whether or not your current score is sent to the cqcontest.ru live contest score website every 5 minutes. The menu item is disabled when the contest type for the current log is not supported. The item is checked when reporting is turned on, but reports are sent only if the current time is within the contest period for the current log's contest. You can turn reporting on before the contest starts, and SkookumLogger will turn it off at the end of the contest, or whenever you close a log. SkookumLogger does not remember the state of the reporting toggle across log closing or quits. Many thanks to Dmitry, RW4WM for assistance with the server API. Requested by G6NHU.
Help ▶ Live Scores Web Site opens the cqcontest.ru site in your browser.
Added EA7URC to the list of DX Cluster nodes.
The tab key and return key now do what you expect with keyboard focus in the edit transmit frequency field, the edit receive frequency field, and the new edit sent serial field. That is, tab moves to the next field, and return finishes the edit.
The custom Cabrillo QSO record format required (but not specified — so logging authors must guess the format) for UBA Spring contest has been implemented. Thanks GØDVJ.
A spurious software test has been removed that may have disabled pouncing on activities for some types of radios. Thanks DL7ALM.
The Statistics report Rate Summary table now has a column titled BC that tallies the number of band changes during the time interval for each row. The column titled PCT is gone, and the summary row labeled BC is also gone.
Help ▶ 3830 Scores Web Site opens the home page for a new site by Bruce Horn, WA7BNM. This is a very nice site that consolidates access to contest-specific forms for reporting your scores, configurable tables of reported scores, and a searchable database of scores for previous contests. Note that these reports are claimed scores, not adjudicated results, but many in the contest community use this facility to assess their performance within days after an event, and to exchange soapbox commentary about the event. The SkookumLogger Score panel now remains visible when SkookumLogger is inactive, so you can see it while preparing a report form at the 3830 site. You can copy-paste or drag-and-drop numbers from the Score panel to the report form fields.
GØDVJ recently experienced unusual radio communication failures with two different radios. The symptom was that SkookumLogger reported that the serial port for the radio had been removed (unplugged). This error message happens when OS X tells SkookumLogger that a port that it is using has disappeared; SkookumLogger merely passes along the bad news. If you didn’t actually unplug your USB-serial adapter, check that you have installed the current version of the driver for the adapter. Also, when the spurious failure occurs, it is sometimes necessary to reboot OS X in order to restore the driver to a functional state.
If you use the sorting features of Activity tables, you know that clicking on a column title sorts the rows by the content of that column, and that clicking a column title with an arrow (indicating the sorted row) reverses the order of the sort. If you sort on Age, for example, the sort order is ambiguous for rows that have the same age. You can disambiguate this condition by first sorting on a column title with unique content (such as Call), then on the column title with the potentially ambiguous content, to set up a secondary sort order. To further expand your gray matter: this behavior extends beyond two columns to encompass all sortable columns that you have previously selected to be sorted.
Repaired more issues with the Regions Summary table in the Statistics report, including an empty table for the SP DX Contest.
If you unplugged your Winkeyer at just the right instant when SkookumLogger was talking to it, an infinite loop ensued which crashed SkookumLogger.
The Statistics report now includes QSO count, multiplier counts, and best rate statistics for each operator when the log has more than one operator. Requested by GØDVJ.
In CWT events, use of the SkookumLogger exchange archive and CWOps database is now disabled during the contest, forcing you to complete all of the received fields yourself. After the contest, before updating your exchange archive, run the Create Statistics Report function to see a new report section, CWT Logging Accuracy, listing discrepancies between what you logged and what SkookumLogger finds in your exchange archive and in the CWOps database. This capability approximates the Log Checking Reports provided by some contest sponsors, to help you improve your CW contesting skills.
A new menu item, Messages ▶ Record Voice Message ▶ is available if the connected radio has a digital voice keyer and supports computer control for starting and stopping recording. The eight submenu items correspond to the eight F-key messages. Choosing one of the submenu items starts recording for the corresponding voice keyer memory. Tap the escape key to stop recording. The K3 radio module supports this feature, although it does not check that a DVR is actually installed in the radio. [Note for radio module developers: implement the
(void)recordDVRMessage:(NSUInteger)tag message in your Radio class to support this feature.]
A second new menu item, Messages ▶ Repeat Voice Message Play, toggles whether or not a message will automatically replay after a delay when you start a message. The length of the delay is determined by the radio's voice keyer controls (for example, MENU:MSG RPT for a K3). Tapping escape stops message play without turning off repeat mode, but the message does not replay until you tap a the message function key to restart it. [Note for radio module developers: implement or update the
(void)playDVRMessage:(NSUInteger)tag repeat:(BOOL)repeat message in your Radio class to handle the repeat argument.]
tqsl command line arguments have been updated for changes in 1.14 RC4.
SkookumLogger no longer automatically tries to reconnect when it loses an internet connection. Instead, the Information window is presented right away, so that you can decide for yourself what to do.
The Regions table in the statistics report was dysfunctional for single-band events where the contest type has more than one event per year and the events occur on different single bands. Example: UBA Spring Contest. Thanks GØDVJ.
File ▶ Upload to Logbook of the World sends your current log to the ARRL LoTW server. The menu item is disabled if the
tqsl application isn’t found in your Applications folder, or if there is no open log. The function relies on tqsl version 1.14 features and on properly installed certificates. Before using the function, set your SkookumLogger Export preferences for Logbook of the World Password and Location. Password is the string you defined when constructing your certificate container file (.p12), and may be empty. Location is the name of one of the items in your tqsl Station Names list excluding the callsign; for example, “Home” not “K1GQ - Home”. The function blocks with the SPOD (spinning pizza of death) until tqsl has finished, then posts the messages from tqsl in the new Information Messages panel described below. Uploading a 1500+ QSO log took about 40 seconds on a Mac mini. Of course you need a working internet connection, and SkookumLogger does not attempt to deal with any of multitude of error scenarios.
This feature is meant to be a simple-as-possible means for getting your contest QSOs into LoTW, to make you a good citizen in the eyes of those you have worked who care about that sort of thing. Use tqsl and tqslcert directly for their other functions. Version 1.14 of tqsl is being beta tested at this time.
View ▶ Information Messages opens a panel listing lines of informative messages from SkookumLogger. When SkookumLogger wants to let you know about something significant without blocking other activity by using a modal alert dialog, it adds a line to the messages and opens the panel. Otherwise, the panel is not visible unless you open it yourself. An example “significant event” is: an internet connection was lost. Suggestions for other information you would like to see are welcome.
Logging preferences has a new checkbox, “Wipe exchange when erase call”. When checked, erasing the QSO entry call field by multiple presses of the delete key also clears the other QSO entry fields when you erase the last call character. This is the default and the behavior in previous releases. W2RU doesn’t like this behavior, so now he can disable it.
SkookumLogger now supports the four UBA Spring Contests (all occur in March). Requested by GØDVJ.
K3 radio polling rate has been reduced to 0.5 Hz and radio comms changed so that SkookumLogger polls only for information that is not spontaneously generated by the radio in auto-inform mode. The radio frequencies displayed by SkookumLogger will update less frequently when you spin knobs on the radio, but functionality should otherwise be unchanged.
WAE countries were not being recognized as multipliers in the Russian DX Contest.
The minimum OS X version was set to 10.6 instead of 10.7, causing a SkookumLogger crash when starting on Snow Leopard. Thanks DL7ALM.
Reverted to separate multiplier checksheets for States & Provinces (Regions) and VA Counties & Cities (Other) for in-state entrants in the Virginia QSO Party. Requested by W2RU.
Changed the multiplier type for Russian DX Contest oblasts from Other to Regions. Divided oblasts into two groups, Asiatic Russia and European Russia. Oblasts are inferred from call signs using information in the AD1C expanded cty.dat database.
The Other checksheet was displaying empty columns for all bands, instead of a single All column with QSO counts, for contests where multipliers were not per-band.
Virginia QSO Party now supports all contest bands supported by SkookumLogger. In prior releases, only the HF contest bands were supported.
SkookumLogger has a new preference tab named Export. Cabrillo preferences have been moved to this tab from the Logging preferences tab.
Virginia QSO Party had implementation errors that affected multiplier tracking, duplicate tracking, and scoring, for both in-state and out-of-state entrants.
Added support for Virginia (US State) QSO Party, third weekend of March, for both in-state and out-of-state participants. In-state multipliers are US States excluding VA, Canadian Provinces, ARRL DXCC Countries excluding K, KH6, KL and VE, Virginia Counties, and Virginia Cities. Out-of-state multipliers are Virginia Counties and Virginia Cities. Scoring excludes bonus points. You may need to edit your Cabrillo file if you enter one of the more exotic categories.
Serial preferences supports a new hardware device named Tuner with one type, the Elecraft KAT500. This tuner has an integrated 3-port antenna switch. The tuner firmware has configurable options for associating those ports with bands, so that a particular port is selected when the tuner changes bands (the tuner band automatically tracks the radio band). When you connect to a KAT500 in Serial preferences, SkookumLogger monitors the tuner antenna switch choice to synchronize the transmit antenna pattern display in the Great Circle Map window. To inform SkookumLogger which antenna is connected to each tuner port, the Antenna ▶ Configure… window has a new column in the Antennas table titled Tuner Port. The default is 0, indicating that the antenna isn't switched by the tuner. For the KAT500, enter 1, 2, or 3 to associate an antenna with a tuner antenna switch port.
Previously Skookumlogger was doing a rather intricate dance to mute my receive antenna array (by removing DC power to the Clifton Laboratories active antennas) while changing directions. W2CS asked me if I was concerned about damaging the receive array with my transmitted signal, which got me thinking about also muting the receive array when transmitting. Careful contemplation of my navel led me to realize that MOAS has the perfect solution, the inhibit feature. Now, my receive array DC power is toggled with the MOAS Station 2 inhibit port. The MOAS is configured so that Station 1 transmit inhibits Station 2, thus muting the array while I am transmitting. And, the muting dance when changing directions is much simpler: inhibit Station 2 before changing direction relays, then uninhibit Station 2.
Spots with QSX information were using the receive frequency instead of the transmit frequency when guessing mode.
The name lookup feature introduced in 1.6.5 was presenting a warning alert when the CWOps database was not found. Now that alert appears only for CWOps events. Thanks JH5GHM.
QSOs could not be saved in certain circumstances, with a warning about missing required frequency information. Thanks JH5GHM.
Grabbing a spot with QSX info for a mode different from the current radio mode was failing to set the radio mode properly when setting up K3 split operation.
SkookumLogger misbehaved badly when logging a QSO on a computer where the computer’s name had an unexpected format. Thanks JH5GHM.
The About box shows a Version number like this: 1.6.5 (220.127.116.11). The component in parentheses is named the Build version; the last digit of that number indicates the number of significant changes in the new release.
When looking for a name in your exchange database fails, SkookumLogger now also looks in your CWOps database.
The Internet preferences pane adds W1VE in both the DX Cluster Node list and the Reverse Beacon Network node list. Each connects to the same high-performance site running ARCluster version 6. By default, the DX Cluster connection delivers only spots created by “real” users, while the Reverse Beacon Network node delivers those spots along with skimmer spots. You can configure either connection as you wish with ARCluster filters. SkookumLogger delivers out-going spots only to the DXCluster connection.
The Rate Summary table in the statistics report has four new rows at the end of the table showing per-band and all-band totals for these parameters: number of QSOs, number of on-air minutes, QSOs per hour, and number of band changes. Thanks W2RU.
The label for Multi-band QSOs in the statistics report now properly reflect the values presented in mixed-mode contests: Band-mode QSO Counts. Thanks GØDVJ.
An obscure initialization order problem sometimes caused the Pounce box frequencies to be zero when restarting with a previously-connected radio.
Code that was intended to reduce popping when switching receive array direction was simultaneously switching and muting the active antennas. The code now properly mutes before switching, considerably reducing pops.
A link to web site for Dutch PACC Contest was missing.
Using the Antenna ▶ Stop Rotation function was blocking subsequent use of the Antenna ▶ Set Rotator to Target Bearing function until the target bearing was changed by changing the call sign. Thanks GØDVJ.
A new Logging preference, “Typing Stops Beacon CQ,” controls whether or not SkookumLogger stops sending and turns off beacon CQ mode when you type into a QSO data entry field. The default is on, which is the previous behavior.
Why would you want to turn the preference off? Suppose you have a K3 with the sub-receiver. You set CONFIG:L-MIX-R to A Ab, so you hear the main receiver in both earphones, and the sub-receiver in the right earphone. You find a run frequency and CQ in K3 transceive mode using RIT to find off-frequency callers. When your run slows, you turn on beacon CQ mode and begin tuning VFO B (the sub-receiver) to find stations that you haven’t worked yet. You use Radio ▶ VFOs ▶ Exchange to swap VFO A and VFO B, alternating between your run frequency and the pounce target frequency when the timing is right. Some call this style of operation SO2V, for Single Operator 2 VFOs.
How do you know whether or not you have worked somebody? You type the call into the active QSO entry box call field to have SkookumLogger show needed status, as usual. Now you know why you might want to turn off Typing Stops Beacon CQ — entering the call would stop your CQ message and turn off beacon CQ mode.
The SO2V technique described here works across bands (although there are some K3 limitations). But beware, the needed status test applies to the band of VFO A. You can work around this by using the Pass Information window, which shows you every band where you need the pounce target.
A new function, Log ▶ Insert SubRX In Activity Table, creates an activity using the call in the active QSO entry box, with receive and transmit frequencies equal to the sub-receiver frequency. Your “Insert in Activity Table clears entry field” Activities preference applies to this function, and the insertion is sent to other computer running SkookumLogger via SkookumNet.
Why would you use this? Suppose you are operating in the SO2V style described above. You find a target using VFO B and you want to keep track of the target using SkookumLogger’s activity table feature. Log ▶ Insert In Activity Table won’t do; it captures the main receiver and transmit frequencies instead of the sub-receiver frequency. Now you can use Activity Table functions for alternating between run and pounce, and for quickly identifying signals as you tune VFO B.
GØDVJ has confirmed proper operation of the Easy Rotator Control module as implemented in version 1.6.2.
A new function, Antenna ▶ Stop Rotation, instructs a connected rotator to stop turning. Requested by GØDVJ and tested only with the Green Heron controller.
Distance values in the QSO notes fields now have the same format as in the QSO Information string. Thanks GØDVJ.
The version date for the Exchange Database now updates after using the File ▶ Update Exchange Database function. Thanks GØDVJ.
The scale factor for zooming the great circle map is now 1.5 instead of 2.0.
The Messages preference pane lacked documentation for the + token, which sends the name for the call if found in the exchange database. Thanks GØDVJ.
The Phantom radio type was failing to save mode and frequencies when quitting SkookumLogger.
When your exchange database has a name for a received call, the name is shown at the beginning of the QSO Information string.
The Log table has two new columns, Operator and Station. When you log a new QSO, the Operator field is set to the checked call in the new Log ▶ Operators ▶ menu. That menu lists all of the calls in the Cabrillo Operator List table (see below). Check an entry in the menu to define the operator call to be used for future QSOs. Use this feature if you what to track who worked each QSO for post-contest analysis.
When you log a new QSO, the Station field is set to the name of the computer running SkookumLogger. You set the computer name in the Computer Name field of your Sharing system preferences. Use this feature if you want to keep track of which station made each QSO when you are using SkookumNet.
Both of the new QSO fields are directly editable. If you don’t care about these data, hide the columns by right-clicking on the table heading row and unchecking the appropriate items.
There were two problems in submitting Cabrillo files for the REF contest. First, the LOCATION field must contain “DX” for entrants outside France/French Territories. That detail has been added to the help tag for the Location field in Log Settings. Second, the email robot rejects the same file that is accepted by the web interface. So, use the web upload page. Thanks F6LEN.
The Cabrillo Operator List box in the Log Settings sheet now looks like this:
Enter the call sign of the station you are using in the Host Call field. Enter one or more operator calls in the Call table. For new logs, both of these are preset to the call in your Me preferences. Open the Log Settings sheet, add the appropriate call in the Host Call field, and delete that entry in the Call table.
The exchange database is saved and loaded using a binary file format. A copy of the database is also saved in JSON format, a structured text file. Now, SkookumLogger will read the JSON file instead of the binary file if the binary file isn’t found, providing a means for manually changing the database content outside SkookumLogger. The basic steps are to edit the JSON file, move the binary file aside, start SkookumLogger, and choose File ▶ Update Exchange Database. Note that editing JSON files is not for the faint-of-heart. Any mistake in the structure, such as a missing comma, will cause the read to fail.
RSGB changed the start dates and durations for the 2m and 70cm AFS contests, and the duration of RSGB 80m Sprints. While making these changes, the four end-of-month sprint events were added. Thanks GØDVJ.
The CWT module had buggy logic for deciding whether to save the received exchange information as a CWOps member or a state/province/country in the exchange database. Thanks W2RU.
The table in the rate summary section of the statistics report now has a variable number of rows, depending on the duration of the contest. For events shorter than two hours, each row spans 5 minutes. Between 2 and 4 hours, 10 minutes; 4 to 12 hours, 15 minutes; 12 to 24 hours, 30 minutes; longer than 24 hours, 60 minutes.
Support has been reinstated for Florida QSO Party and for Tennessee QSO Party, for entrants outside those states. As a reminder, SkookumLogger supports contests that a user has requested; very rarely is support added because somebody might want it. In other words, if you are a SkookumLogger user in Florida or Tennessee, you must ask for support.
SkookumLogger now supports the French HF Championship (REF) contest, for entrants outside France/French Territories. However, the robot would not accept my Cabrillo log for the January event.
In contests with a grid (locator) received exchange field, the distance to the worked station is inserted in the Notes field when you log a QSO. Thanks GØDVJ.
In contests with Locator multipliers, the statistics summary table for locators now displays distance for each table row (grid), and the largest value is printed below the table. Thanks GØDVJ.
Added support for Yaesu FTDX-5000 radio. Testing thanks K7GQ/KH6CW.
The list of of contest names in the Log Settings sheet has been reorganized by adding more groups. The groups are ARRL, CQ, RSGB, National DX Contest, QSO Party, Other, and Generic. The first three groups contain contests by a specific sponsor. The National DX Contest group contains worldwide contests not in the first three groups with a focus on working participants in the sponsor's nation. The QSO Party group contains, well, QSO parties. The Generic group has a few general-purpose event types for contests not specifically supported by SkookumLogger. Finally, the Other group has contests that don't clearly fit into one of the other groups.
The Easy Rotator Control module now uses the Yaesu GS-232B protocol for reading and setting azimuth. This interface is being tested by GØDVJ.
Time Tracker was creating an off period before the first QSO, even when the off period had duration less than the minimum off period.
Worked around a bug affecting distance and bearing values displayed in Locator checksheets.
Some checksheets were empty for single-band contests.
File ▶ Create Statistics Report generates a text file containing information like that created by the K5KA/N6TV
cbs program. Use this feature after a contest to amuse yourself by attempting to derive useful insights through study of rate tables and so on.
It is very important that the Time Tracker parameters are set properly before you run the function. Otherwise, time-dependent information (rates) will be incorrect. Until now, this wasn't an issue, and still doesn't affect your log or your Cabrillo export.
You do not want to use this function until after a contest. It can take some time to run, depending on the duration of the contest. The statistics consider every QSO in your log, without ignoring dupes or suspects.
When you run the function, you may see some windows flash open then close. That's normal; the checksheet and score windows need to have been opened at least once before creating the report.
This feature should work for any contest supported by SkookumLogger. Let me know if you discover otherwise, or if you have suggestions for other content or cosmetic improvements. Also consider bragging to your friends using
cbs that you aren’t limited to the few contests supported by that program.
The Time Tracker window now looks like this:
During a contest, the “Outside Contest Interval” label reads “--- Off Period ---” when SkookumLogger thinks you are in an off period, otherwise “--- On Period ---”. An off period begins when Time Since Last QSO is larger than Minimum Off Period, and ends when you log a QSO. At the instant that you enter an off period, the Off Time Used jumps forward and On Time Used jumps backwards by the same amount, since SkookumLogger thought you were in an On period up to that point. So, keep an eye on Time Since Last QSO to anticipate changes in in these parameters.
Time Since Last QSO and Time To End update every second. Off Time Used and Off Time Remaining update every second when in an off period. On Time Used and On Time Remaining update every second when not in an off period. Nothing updates when outside the contest interval, unless you change one of the four editable fields at the top of the window.
SkookumLogger uses a high-resolution (sub-millisecond) representation for times. Log checkers have to work with the times in Cabrillo files, which have one minute resolution, so their determination of off periods will be different. For my 2012 SS log, the difference was less than a minute.
For the K3 radio only, SkookumLogger has an experimental scheme for managing RIT/XIT that is undocumented. That scheme is now controlled by a hidden preference and disabled by default. In the normal scheme, SkookumLogger uses the K3 split mode whenever it needs to set different receive and transmit frequencies and does not change RIT/XIT offset or on/off states. Thanks W2CS.
When a Radio ▶ Band ▶ function is selected, SkookumLogger now stops messaging sending before telling the radio to change bands.
This release bumps the version from 1.5.x to 1.6.x because the companion User Guide has been significantly expanded. All of the original Guide content has been made consistent with this version of SkookumLogger, and a new part has been added to serve as a reference manual for preferences, windows, and menus.
Well, I admit that the 1.5.x release notes web page had become so large that it was bogging down my web site authoring tool (Flux).
QSO data entry behavior has changed slightly. If you enter a call, then clear the call by pressing the delete key multiple times, or by selecting the entire call and typing delete, all other exchange fields will be cleared as well. This was not the case in the past, which sometimes caused logging errors when you didn't update pre-filled exchange information for the new call. If you want to replace the call without clearing the exchange fields, select the entire call and type over the selected call without typing delete.
There have been quite a few cosmetic changes to improve terminology and consistency issues exposed while authoring the Guide update. None that I can remember affect SkookumLogger behavior, although you may find some of your customized shortcut keys no longer work because I changed some menu item titles.
Log ▶ Clear Pounce QSO Entry was clearing only the call field. Thanks W6FB.
Time Tracker was accumulating too much on-time in contests with off-times. Thanks W6FB.