Advanced Functions

In the 'Basic Functions' chapter the more standard routines like changing frequency, band and mode can be found. In this chapter the more advanced features are addressed. Not needed for everybody but nice when you think you need the,

Call History Lookup

In some contests part of the exchange is known if the callsign is known. So it would be easy to have this information shown (or already prefilled) if the callsign is entered. Lookup examples are names (Friends file in RTTY contests), gridsquares for VHF contests, ages in All Asian DX contests etc. In all cases the possibility to use this lookup function means changes in the contest class by the programmer. A lookup is only done when the cursor is in the callsign field in the Entry window and SPACE or TAB is pressed.

Note:  there can be only one call history table actually present in a given database at a time, and it remains active regardless of the contest unless replaced with another or unless you turn off the lookup function.

Call history is implemented in a separate table in each database. This table is called CallHist. The Entry window menu options for Call History Lookup are:

• Config | Call History Lookup
  • Toggle to let the contest use the Call History table. In this table station information like Name, GridSquare, Section, State, Age etc. can be stored and retrieved during the contest. This setting will cost some performance because the program has to lookup information when leaving the callsign field from this table in the database. This table has to be filled with 'Import Call History' and the contest has to be suited for it before it can be used! Provision has been made in the table for additional fields: State, Birthdate, CK. These are in the table, but do not have any effect on logging.
• File | Import | Import Import Call History
  • Some contests use exchanges which are very often the same the next you work a station. This table can be used by some of the contests to show information in one of the exchange fields or fill a macro when a callsign is entered. This information can be Name (RTTY friends file), Grid square, age, etc. For more information see the VHF and up contesting chapter (VHFREG1 is a VHF contest which uses this table to fill the grid square). When importing a new file with information the contents of the CallHist table will be deleted first. So export first if you want to keep the content!
• File | Import | Export Call History
  • Exports the information in the Call History table. This table can only be filled by using 'Import Call History'.
• Tools | Update Call History with Current Log - 
  • Update the call history file selected with the qsos from the current log file. Contacts will be added when new or updated when already in the call history file. For the 2 grid fields the behavior is a bit different. When both grid fields are filled and a new third grid has been logged, the second grid (oldest) will be removed, and replaced by the contents of the first field. The new grid will be added to the first position. The same change in position will happen when only the first grid is filled and a new grid has to be added from the log. A 4 digit grid will be overwritten y a 6 digit grid when the first 4 characters are the same.

Creating a lookup file for importing in CallHist table

The import function expects a text file with on each line the information as mentioned in the order below.
Order: Callsign (15), Name (25), Grid1 (6), Grid2 (6), Section (5), State (5), CK , Birthdate
The delimiter between the fields may be a comma, a semicolon, a space or an equal sign. The delimiters may be mixed in the file but not within one line! The callsign is needed, all other fields are optional. The equal sign is introduced so a friends.ini file used by many RTTY contest programs can be used without converting.  The length of each field is given behind the name. The CK has to be an integer and the Birthdate must be a date.

A missing CK must be entered as -1, since any check from 00 through 99 is valid (ARRL Sweepstakes).
Birthdate is expected to be used for the AA contest to compute the other stations age. This will obviously be a little tricky to deal with.
Be sure to put birth dates in a universal format, e.g. 1980-12-31

Example call history file:

Or

K1CC,RICH,FN31,FN32,,,-1,1900-01-01
KG1D,LES,,,,,-1,1900-01-01
N1MM,TOM,FN31,,CT,CT,61,1949-10-01
# this is comments (line starts with a #)
W1RM,PETE,,,,,-1,1900-01-01

• The callsign is needed and may not be omitted
• When the Grid square is needed and the name is not known it does not have to be filled. Don't forget the delimiter! A second grid square may be entered at the position of Grid2. Grid1 should be filled if one grid square is known/used. Filling Grid2 is optional.
• Example 'State needed' gives many delimiters. Depending on the contest class an entered name will be used or not.
• There is no maximum for the number of lines. For VHF contesting we normally import a file with over 50,000 lines and there is no noticeable delay in searching (on a fast computer). There is a gridsquare file available from the N1MM website under 'Downloads', select the menu: 'Other Files'. It was created by PA1M for use in European VHF contests.
• Pressing the SPACE bar or TAB when the cursor is in the callsign field will look for a callsign in the CallHist lookup table.
• It is possible to add comment lines in the Call History file, use a # on the first position of the line. See example above.
• Sweepstakes will pull in the Section and CK, the 10m contest will pull in the State, NAQP will pull in the Name & State. PAbeker will use Section. VHFREG1 uses Grid1, Grid2 and name etc. If the contest doesn't use one of those fields you're out of luck!
• To check if a contest uses the call history create a file with one one call to import and each field filled with unique content. When call history enabled this content should show up when this call is entered (and space or tab pressed). By the unique content you can estimate which field (Name, CK etc.) is being used.
• A great tool to use has been made by Carel, PC5M and is called 'Thucydides'. Check out the chapter 'Third Party Software' for more info.

Tip 1 by Kenny, K2KW

For those of us with limited dB skills, there is a relatively easy way in Excel to get the data into the right format. Start off by parsing out the data from an old log into different columns. (In Excel, there is a Text to Columns conversion, if your data starts off in one line). Once you get the basic data extracted and parsed, insert additional columns for all the fields as required. Then insert a field for every comma you need, resulting in 8 data fields, separated by 7 fields with single commas in them. By now the data should look exactly as you need it, but in 15 different columns. Then in yet another field, use the Excel Concatenate function:"=concatenate(A1, B1, C1, etc)" You will list every column. This function will then concatenate all the data into one long string, and then just copy and paste all the columns (you can do it all at once) with data into an ASCII file. I had just done this at work last week and it works great. Sounds complicated, but it's quite easy.

Tip 2 by Tom, N1MM

In the log window, choose 'Select All' and use 'Copy Generic Print String' to speed up this approach. The data in the clipboard can then be pasted into Excel.

Tip 3 by Thomas, PA1M

Use 'Thucydides' by Carel, PC5M . Basically how Thucydides works is that you will build up a separate database in which you can store all your qso's or data from other history.txt files.
This Thucydides database has provision for all known contest fields (e.g. ARRL states, German DOK's, Dutch provinces, etc..)so you can import your log's and it will be stored separate. Of course when information is changed (e.g. a station moved to a different state) it will be updated in the Thucydides database.
When you need now a history.txt for a specific contest you can instruct Thucydides to use only those database fields which holds the correct information and output this at the correct fields in the history.txt to be used by Logger. Both this import and export behaviour is 100% under user control and can be changed (if needed) just by changing an accompanied MS-Excel file.
As Thucydides is not altering any Logger data or databases it is quite safe to play around with it and of course history use is limited to those contests for which Logger has been enabled.

Check out the chapter 'Third Party Software' for more info.

How to update the Call History

N1MM logger does NOT make use of that data and the QSOs made during various contests automatically. The database once importedis the same after the contest. Updating this database can be done in 2 ways.

1. Use the menu item 'Update Call History with current log' in the Tools menu. The current Call History data will be updated with the information from the currently selected contest.

2. Export the old Call History database and use a utility to merge the new information and import the combination.

Of course a Call History file shared by others could be used or the examples from the N1MM website under 'Other Files' in the 'Downloads' menu item.

NB. When importing a new Call History file, the old Call History file in the database will be deleted! Make a backup first or export the old Callhistory when not sure.

Transmit on same band with two radios 

Big Gun versus Little Pistol switch

• Stations normally come back to you on the first call.
• In the Configurer under the Function Keys tab check 'ESM only sends your call once in S&P, then ready to copy received exchange'.

• You have to call mostly several times to get through to being answered.
• In the Configurer under the Function Keys tab uncheck 'ESM only sends your call once in S&P, then ready to copy received exchange'.

Hint: One little trick to use with the Big Gun switch on is to program my call in F8 instead of "again".  This way, when you don't get the guy on the first call, hit Enter again to repeatedly send my call until he answers (and the cursor is always in the right place when he does answer). 73, Ted W4NZ

Stay in Run Mode (great for Dxpeditions) or stay in S&P mode

Auto Send

1. Find the first letter in the call.
2. Find the last number after the first letter.
3. Find the Nth letter after step 2.

• W4WYP would start sending at Y
• S57AD would start sending at D
• KH6/WA4WYP would start sending at Y  (using the "/" rule as well)
• WA4WYP/4 would start at Y  (/4 will not be looked at)

Enter Sends Messages mode (ESM mode)

Setting the option "Enter Sends Messages" in the Config dialog will enable a mode that allows you to make entire QSOs without using the function keys. ESM works for both running and S&P mode, but the messages are different for each mode. To set ESM, go to Config, and check Enter Sends Messages (ESM mode), or use the shortcut Ctrl+M.

Basic ESM Functionality
When running, pressing 'Enter' with the callsign textbox empty will send CQ. If someone answers you, type in his callsign. Hit 'Enter' again, and the program will send the exchange. After entering the other stations info, hitting 'Enter' again will send the end of QSO message (TU/QRZ) and automatically log the contact. See the chart below for a detailed list of what is sent at various states of the QSO.

Here's a typical scenario where N1MM is calling CQ in the CQ WW CW Contest:

Hit "Enter" - sends CQ N1MM
PA1M calls in - type "PA1M"
Hit "Enter" - sends "PA1M 5NN T5", note that PA1M's zone is filled in for you.
PA1M sends "599 14" (zone matches what program filled in)
Hit "Enter" - logs QSO & sends "TU de N1MM"

That's 3 keystrokes + typing PA1M's callsign. Slick!

On the other end, the S&P station (PA1M) can also use ESM. During the same QSO:

You hear N1MM calling CQ - type "N1MM"
Hit "Enter" - sends "PA1M", note that N1MM's zone is filled in for you
N1MM sends "PA1M 5NN T5" (zone matches what program filled in)
Hit "Enter" - sends "599 14"
N1MM sends "TU de N1MM", completing the QSO and logging it

Once again, that's 3 keystrokes + typing N1MM's callsign. In some other contests, like CQ WPX, you will also have to type in the exchange, but in any contest ESM cuts the effort required to complete a QSO to a minimum.

Keeping track of which ESM "state" you are in can be confusing when things get hectic. To help you understand which state you are in, the function keys on the Entry Window will change color (aqua blue) to alert you which message will be sent next. The goal here is that it should always be obvious what will happen next.

There will be times when you get out of sync, or where you need to send something different than what the next "Enter" will send. Don't panic. Just press the correct function key(s) (F2, F4, etc as needed). If you finished out the QSO with the F-keys, just hit Alt+Enter, which will log the QSO without sending anything, and you are ready for the next QSO (and ESM is reset to the beginning state).

• not have a prefix and at least one characters suffix
• prefix is a letter followed by a number
• prefix is a letter followed by a number, letter, number combo.

Note: If a CQ is being sent, typing a character in the callsign field while in ESM will stop sending a CQ message being transmitted (this can be set in the Function Keys Tab from the Configurer dialog using "ESM only sends your call once in S&P, then ready to copy received exchange ").

When the copy is solid, and no copying mistakes are made, ESM will just send the basic messages in the previous example. Depending on what information is in the Call window and Exchange window and what state the QSO is in, different messages can be sent. The chart below outlines the possible combinations of information in the Entry window, and what will be sent in each situation.

NB: When in ESM and in S&P, If the cursor is not in the call textbox and the Exchange is not finished, the program will send " Again? (F8)"

When a dupe callsign is in the callframe, the call is put in the call textbox and highlighted.

The actual messages sent by each of those function keys (e.g. CQ Key, Exchange Key, My Call Key, etc.) are set in the configuration dialog ('Config | Change Packet/CW/SSB Digital Message Buttons'). There are 24 messages that can be set: the first 8 messages are for Running mode, and the second 8 for S&P mode. Each mode (CW, SSB, Digital) can have a separate set of messages, which are saved by the program. If the program is sending the wrong message, check here first! In the middle of the contest, you can also change the messages for the current mode by right-clicking on (one of) the message buttons in the Entry window.

How to prevent the cursor moving to next exchange field<

In ESM mode when running and trying to send a partial call entered in the callsign field, the cursor jumps to the report field before you can finish typing the call...

Solution 1

When you press Enter in ESM mode while running, the cursor will be placed highlighting the ?.  If you type a letter, say "J", the ? will be changed, and you will have G4UJS in the callsign.  Whenever you press the space bar, and the cursor is placed in the callsign, the ? will be highlighted, ready to be replaced without typing Del or Backspace...

When you are Running with ESM enabled and while entering you place a ? in the callsign field the cursor will not move to the exchange field but stay in the callsign field highlighting the ?

Solution 2

To enjoy all the ESM features and still stay synchronized with the pile-up, go to 'Config | Function Keys' and deselect 'Fill in his exchange'.

How to skip sending the callsign or exchange field (SSB)?

To avoid PTT when setting up ESM on SSB without sending a callsign or exchange put in SSB a single space or the path to Empty.wav as the wav file for the callsign and/or the exchange buttons.  The program will not assert PTT and immediately simulate the space bar being pressed.

NB: The next button to be sent shows in turquoise.  If you don't like what ESM will send, you may choose another.

QSYing wipes the call & spots QSO in bandmap

If you turn on this feature (in the Config menu), it will spot stations in the bandmap which you haven't worked yet or don't want to work all. These stations are not spotted on packet/telnet but only locally. Any call greater or equal to 3 characters that you don't work but have entered in the callsign field will be automatically spotted in the bandmaps when you turn the VFO to another frequency. This way you can place stations on the bandmap which you can't work direct (big pileup?) so want to store them somewhere. Also useful when you want to add stations to the bandmap who you don't want to (or may not) work but like to have the callsign in the bandmap so when searching for stations you know who is on that frequency so you can turn on.
All bandmap features work on these 'spotted' stations so they are easy accessible if needed. Self spotted stations are easy recognized because they are shown in bold.
This feature is also very useful in a M/S or M/M environment. Often there is a MULT station that is tuning the bands, but may not want to post the spot until the QSO has been worked by their own RUNNING station. (I do not wish to get into an ethics discussion, but this is done quite often) This feature allows the MULT station to build a band map full of calls for the RUNNING station to work when it gets a chance.

That means you can do the following:

• Tune to 21200.
• Enter VU2PTT.
• Tune off.
• VU2PTT is "spotted" at 21200, and the Entry Window is cleared.
• Tune to 21208.
• Enter G4UJS.
• Tune off.
• G4UJS is "spotted" at 21208, and the Entry Window is cleared.
• Repeat as long as desired.
• Go back and work all of them using Ctrl+Up and Ctrl+Dn to navigate.

Note: There is also a "Spot all S&P QSOs" option. It has a number of rules, but will spot everything you WORK on packet, if it has not already been spotted on the same frequency.

Single Operator Call Stacking in all modes

Below you will find instructions on using the various Macro's and Keystrokes for CW,SSB and Digital. We would like any feedback on the operation and use as we have implemented it.

{SOCALLSTACK} & {STACKANOTHER} or CTRL+ALT+G
These are call stacking macros that only function in RUN mode. SOCALLSTACK allows the operator to stack a partial or full callsign. If a callsign is stacked and a second callsign is in the callsign window, the calls are exchanged. Stacked callsigns appear on the callsign entry frame and the bandmap on the CQ-Frequency.

STACKANOTHER or CTRL+ALT+G allow the operator to stack additional callsigns. When the macro completes, the callsign entry window is empty.
The stacked callsign can contain a question mark. If it does, the question mark will be highlighted when the callsign is popped off the stack. If the callsign window is empty and SOCALLSTACK is executed, it will move the next callsign from the stack into the callsign entry window.

When you are spotted, the station callsign will appear in bandmap on the run frequency. SOCALLSTACK will delete and not move the station callsign into the callsign entry window. For this to function correctly, make sure your station callsign is correct in the station information window. SOCALLSTACK will also delete the CQ-Frequency and BUSY@ text (ALT+M) that sometimes appears in the bandmap.

Callsigns can be deleted from the stack without popping them into the callsign entry window with ALT+D.

SOCALLSTACK is functional in CW, phone, and digital modes and is compatible with manual key operation or ESM. It can also be used in SO1V, SO2V and SO2R modes and in multi-station environments. SOCALLSTACK has not been tested for compatibility with multi-operator call stacking. Multi-operator call stacking is the program feature that allows a second operator to listen to the run radio and send calls to the run operators entry window.

In CW mode, the function key that uses this macro can include CW strings. For instance, this macro: {LOGTHENPOP}  TU NW {F5}{F2}  will log the current station, pop the next callsign off the stack, and send "TU NW" followed by the new callsign and report all in one transmission. If there is an error in the callsign or missing/invalid report, the macro is aborted, no CW is sent, and the current callsign remains in the callsign window. If the current callsign is logged and no callsign can be popped off the stack, the CW message is changed to the TU-message identified in the Configuration menu. If the macro only contains {LOGTHENPOP} (nothing else), nothing is sent for this last case.

In SSB mode, the function key that uses this macro can include a wavefile. For instance, this macro: {LOGTHENPOP}wav\{operator}\TnxNow.wav will log the current station, pop the next callsign off the stack, and send the TnxNow recorded wave file in one operation. If there is an error in the callsign or missing/invalid report, the macro is aborted, the wave file is not played, and the current callsign remains in the callsign window. If the current callsign is logged and no callsign can be popped off the stack, the wavefile is changed to the TU-message identified in the Configuration menu. If the macro only contains {LOGTHENPOP} (nothing else, no wave file) no message is played for this last case.

Digital Call Stacking

To turn this off or on there is a menu selection in the Setup dropdown menu in the Digital Interface.

• With it turned off everything operates the way it is before Call Stacking was added.
• Only works in RUN Mode and only with a valid callsign.
• Single Click on Call in Digital RX window or Alt-G when grabbing a call
• If there is no callsign in the call box of Entry Window it will function just like it normally does by placing the callsign in the call box.
• If there is a call already in the call box then clicking on another call orhitting ALT-G to use the grab window will move the call that is currentlythere up to the bandmap and call frame of the entry window and place thecurrently clicked or grabbed call into the call box.
  

The usage here is if a two stations call you can then stack one call and work the other. Then instead of hitting enter if in ESM to send F3 or LOG. You would then hit the F-Key that contains : {TX}{ENTER}! {LOGTHENPOP} TU NW {F5}{F2}{RX}

Alt-Key and Single Click on Call in Digital RX window or Alt-CTRL-G when grabbing a call:

This will take the clicked on callsign and place it directly to the stack in the bandmap. Any number of calls can be placed here for working one after another.

The usage is 3 or 4 stations call you at the same time do a single click or Alt-G on the first call to place it in Entry window. Then do and ALT-Click or Alt-Ctrl-G(to pull from grab window) to place the others on the stack.
Then use the F-key that contains: {TX}{ENTER}! {LOGTHENPOP} TU NW {F5}{F2}{RX} to work them all in a row until the last call is off the stack then you would use F3 or hit enter in ESM to log the final one.

{LOGTHENPOP} will not function if CQ-Frequency is in the Call Frame.

Double Click on Call in Digital RX window:
The function of the Double click does not change and will over ride whatever callsign is in the Entrywindow Call Box with the clicked on callsign.

Macro Substitution: {LOGTHENGRAB}  This will log the current contact and Grab the top callsign that is in the grab window of the DI. Will only work in Run Mode
Digital use of macro Substitution: {STACKANOTHER}  This acts just as ALT+Ctrl+G for the grab window but allows it to be called by a macro.
If you hit the F-key that contains {TX}{ENTER}! {LOGTHENPOP} TU NW {F5}{F2}{RX} while there are no calls stacked it will send your TU key.

Call Stacking (same or different bands) - Multi-User mode

A callsign can be stacked from one radio to another when in 'Multi-User Mode'. It does not matter if the target station is on a different or on the same band. A second operator can stack a call on your PC, and he could find stations and stack them for you to work. 

• To indicate which station you want to stack for, right click on it's "cue-ball" in the info window, and select the option "Target for call stacking".
• A maximum of one callsign can be stacked. If the stack is empty another one may be stacked
• After the target station pops the call into the entry window callsign area, the partner station needs to manually wipe his entry line before entering another call. It doesn't automaticall clear.

Stacking within same band but not on the same frequency - Use the bandmap by tuning off a station whose callsign you copied.

Additional functionality when on the same CQ frequency (within tuning tolerance) then you will see the other station keystrokes in your callframe and vice-versa.

Serial number server

• S&P mode when the cursor leaves the callsign field or the Exchange key (F2 default) is sent.
• • Either through spacing, tabbing, or hitting Enter in ESM or pressing the Exchange key.
  • This is needed so you can enter calls to check for dupes while not reserving a serial number.
• RUN mode as soon as you enter a letter in the call-sign field. 
• • This because on SSB people frequently talk before they type, and they need to see the serial number displayed earlier. A serial number is not assigned in S&P mode until the space bar is pressed, so you can do dupe and check multipliers without committing a serial number to it, by entering it in the callsign field without pressing [Enter] or [Space].
    

• Serial numbers issued by the second radio may be out of time sequence with those issued by the main one. This occurs because certain program actions cause a serial number to be reserved for the use of a station, and if that station does not use that number until after the other station has made several QSOs, when the log is viewed in chronological order the serial number will appear to be out of order. I don't think there is anything to be done about this.
• For similar reasons, depending on operator actions at one or the other station, such as shutting down the program while a number is reserved, there may be some gaps (numbers not issued) when reviewing the final log.
• The most important aspects of serial numbering are that the serial sent to a station be correctly logged, and that there be no duplicate serial numbers sent; N1MM logger seems to meet both these criteria.
• Sometimes it's possible a number will be skipped when given out but not used (example: QSO not made after all or deleted). Contest committees do accept this behavior!.

Most sponsors are more interested in serial number accuracy than in serial number time order. If you think about it, it is impossible to guarantee the order of serial numbers in a two radio situation. This assumes that you always log the time when the QSO is added to the log, which is the right time from a rules point of view. i.e. end of contact.

Contest Reporting Application

Note that this will keep reporting everything until you uncheck it. Doesn't matter if you are testing, or operating in a contest. It will be reported. So turn it off if you don't want that.

When the application has been started the dialog below will be shown.

• Stop Send / Send Score - Stop the sending of scores to the configured website.
• Get Scores - Clicking this button will open the configured website in your browser so you can view your and other stations scores.
• Setup - will open the Setup dialog below.

• Score Post Time (min) - Set the timer how often your score will be uploaded to the configured website. The possible times to set are: 2, 5, 10,15,30 and 60 minutes. Also a manual mode possibility can be selected. To send the score the 'Send Score' button has to be pressed.
• Score Posting URL - The url of the website to post your scores to.
• Score Reading URL - The url where the scores are displayed.
• Listening IP - Shows the IP address on which N1MM logger is running. By default this is the same computer as where the real time scoring application is running on. This setting is set by N1MM logger.
• Listening Port - Shows the port from which N1MM logger will send the information to the real time scoring program. This setting is set by N1MM logger.

• Defaults - Fill the dialog with default values.
• Cancel - Cancel the entered values and close the dialog.
• OK - Save the values and close the dialog.

During major contests several real time score reporting web sites will be up and running. An example website  from Gerry, W1VE below.

The viewing site supports many filters, so that you can look at only what you want to look at. Filter by Class, Power, CQ Zone, IARU Zone, State/Prov and lots more. Your filter preferences are saved as a cookie by your browser for up to 7 days. The page automatically refreshes every 60 seconds with score information.

the website will support many contests as listed on the site.

How to start contest with other number then 001?

1. Start second part  as a separate contest and make the first QSO with number 001 and log it, then correct (Ctrl+Y) to proper sent number.
2. Start  second  part  as a separate contest, enter fake QSO, open QSO in EDIT  window,  change  SENT number from 001 to last number you sent in the  previous  part of the contest, save changes, et voila, it's done. When a couple of real contacts entered, delete fake QSO.

SO2R

Single Operator 2 Radio (aka SO2R) is an operating technique that when done properly, can add many extra QSOs and multipliers to your log. This is accomplished by increasing your efficiency during "dead" time, specifically when you are sending on one radio. Efficiency is increased by listening on a 2nd receiver while you are transmitting on the 1st radio. On the 2nd radio you are scanning the bands for needed QSOs and multipliers. If you find a new station to work on the 2nd radio, you leave it staged on the 2nd Entry Window until you get a free moment to work this station. Even adding a few QSOs an hour will greatly boost your score.

A complete chapter has been devoted to SO2R.

Footswitch support