Loading...
 

2.1.1 Configurer Dialog

The Configurer is our name for the tabbed dialog that appears when you click Config on the Entry Window top menu, and then choose Configure Ports, Mode Control, Audio, Other. The Configurer has many tabs with program settings influencing all aspects of the behavior of the program. Be careful in setting up items on the different tabs, to be sure that you understand that the option you are choosing is what you want.

All settings are remembered by the program in N1MM Logger.ini. Function key definitions, telnet clusters, call history, and country information are not saved in the .ini file, but in the database that was in use when you loaded them. That means, for example, that function key definitions loaded or modified when you are using one database will only appear in that database. You will need to export them from that database and load them into another database before they would show up there. The N1MM Logger.ini file contains the name of the .mdb file you were last using, which the program will load when it is started, as well as the name of the current contest and other recently-opened contests.

If you have not unchecked "Hide extensions for known file types" in Windows Explorer Options, you will not see N1MM Logger.ini. You will see "N1MM Logger" with a Type of "Configuration Settings". Also, do not be confused by the file N1MM Logger.ini.init". This is used by the program during installation. You should not modify this file, because if you ever have to delete your .ini file and start over (to resolve a configuration problem, for example), it provides the basis for starting a new one

tipMultiple ini files
You can invoke an ini file whose name is different from N1MM Logger.ini by using the file name as a command-line argument when the program is started.

For example, suppose you wanted to be able to choose between two separate configurations, one for SO2R and one for SO1V, perhaps using different radios and with different settings. You could create two new copies of your N1MM Logger.ini file in the N1MM Logger program folder and rename them to, for example, SO2R.ini and SO1V.ini.

Then create two desktop shortcuts for N1MM Logger by right-clicking in an unused area of the screen and selecting New > Shortcut. Use the Browse button to find your N1MM Logger program folder and click on the N1MM Logger.exe file. You will notice that the file name appears in the location box within quotation marks, e.g.
"C:\Program Files\N1MM logger\N1MM Logger.exe" . Click just to the right of this file name within the box after the closing " , press the space bar once and add the name of one of your new ini files, e.g. SO2R.ini, so that it looks like
"C:\Program Files\N1MM logger\N1MM Logger.exe" SO2R.ini

Note that if the name of your new ini file contains a space, such as "RTTY SO2R.ini", you will need to enclose the file name in quotation marks as well, e.g. "C:\Program Files\N1MM logger\N1MM Logger.exe" "RTTY SO2R.ini"

Click Next, choose a name for the shortcut, e.g. N1MM Logger SO2R, and click Finish. Repeat this procedure for other specific shortcuts.

Each of these shortcuts will now start up the Logger using the ini file named in the shortcut. Any configuration changes you make will be stored in the named ini file, thus enabling you to save different configurations in the two files and to choose which configuration to use by starting the program from the appropriate desktop icon.

1. Configurer >Hardware tab

The Hardware tab is used to set up your radios, packet interfaces, telnet connections, CW/PTT/digital ports and the interfaces to other devices, such as SO2R controllers, multi-purpose interfaces, and keyers, if they require serial or parallel ports. Set the values appropriate to your station. If you do not have one of the items listed connected to a port, make sure the port selection is 'None' and the check boxes are not checked for that port.

1.1. Hardware setup

The program supports 8 serial ports (COM1 - COM8) and 3 parallel ports (LPT1 - LPT3).
Set up each port depending on what equipment is connected and enter the appropriate information.

1.1.1. Why Only 8 ports

One of the first things people notice when they begin setting up N1MM Logger is that there are only COM ports 1-8 available. This is a limitation of some of the components used in the programming, and cannot be changed at this point without a prohibitive amount of effort.

In helping people who say "but my lower-numbered COM ports are all committed to other things", we have found that it often turns out that some of these ports, though seemingly in use, are in fact relics of the past. As an example, COM3 used to be the standard port for built-in modems, and even though those modems have largely gone the way of the dinosaur, many computers still show COM 3 as committed to that use.

If you are familiar with the use of Device Manager, you can always set up several hardware profiles, including one for ham radio that deletes the devices that are getting in your way (printers and so on). That way, you are only a reboot away from being ready to go for radio or being back in everyday mode.

Sometimes, though, ports will not seem to be committed, but when you try to create virtual serial ports (with a USB-to-serial adapter, for example) Windows will inexplicably skip some lower number ports. Ron Rossi, KK1L, has contributed the following note about how to track down and eliminate these phantoms. Be aware that it involves a little beyond the basic user-level skills, so ask for expert local help if you're not comfortable with what he suggests.

Often there are ports assigned which no longer have devices connected to them. These are called "phantom ports". These can be discovered and removed. It may then be possible to move ports around to accommodate the program.

Here is how to have Device Manager show any "phantom" ports.

  1. Click Start
  2. Click Run
  3. Type cmd.exe in the textbox and click OK
  4. Type set devmgr_show_nonpresent_devices=1 and hit ENTER
  5. Type cd\windows\system32 and hit ENTER
  6. Type start devmgmt.msc and hit ENTER
  7. When the device manager opens, click the View menu
  8. Click Show Hidden Devices
  9. Click on the + sign next to the Ports to see the full list of Com ports being used
  10. Highlight the port you wish to delete and then press delete


Accept when asked to do so and continue with any more that you wish
to delete.

Here's what the Device Manager looks like before you delete the phantom ports:

Image


If you want, you can right-click on any of the shaded ports and examine their properties. Each one will show up as a "device no longer connected to this computer."

1.1.2. Options on the Tab

Image

Setting up each port -

  • Radio - The radio that is interfaced with the program using this port for radio control, i.e. control of the radio's frequency and mode. A maximum of two radios can be connected. Select 'None' if this port is not being used for radio control (even if it is being used for some other purpose, such as PTT or CW). If you have only one radio connected, only one of the boxes in this column should be set to anything other than None.
  • Digital - Checking this box means this port is used for digital communication (MMTTY/MMVARI/Fldigi engine or TNC). This box cannot be checked if this port is used for radio control.
    • Use this to indicate the port that is used for a TU or TNC that is being used for RTTY.
    • Use it also to indicate the port that will be used for PTT in digital modes, if PTT is to be controlled from the digital engine (not applicable if the digital engine is 2Tone) and the same port is also used during non-digital modes (in which case the CW/OTher box will also be checked). If the only time the port is used is in digital modes from MMTTY or Fldigi, it is not necessary to check this check box; you can simply configure the port directly within the digital engine without setting it up in the Configurer.
      • Exception: if you do PTT on the radio control port or from a Winkeyer, do not check the Digital box for that port.
      • Second exception: if you are using a port with MMTTY or MMVARI using the EXTFSK add-in, do not check the Digital box for that port.
  • Packet - Check this box if the port is used for packet radio (TNC). Do not select if no TNC is connected for packet radio.
  • CW/Other - Check this box if this port is used for CW, PTT, a foot-switch, a DVK or an SO2R controller. This selection may be made in combination with a Radio, Digital or Packet selection provided the uses are compatible (e.g. Winkeyer and radio control cannot use the same serial port, because both use serial communications, whereas keying CW on the DTR control line can be compatible with radio control on the same port if your hardware interface supports it).
warningUse ONLY ONE method of PTT or CW keying
Note that having multiple ports configured for CW or PTT can cause problems; for example, having two methods of PTT control operating at the same time can result in the radio failing to switch to transmit, or worse, locking up in transmit at the end of a function key message. Pick one method of CW keying and one method of PTT control, check the CW/Other box for the port or ports you need for them and complete the port configuration using the Set button, and make sure CW/Other is not checked for ports that you are not currently using. For digital modes, do not configure PTT control from the digital engine (MMTTY or Fldigi) if you have PTT control operating from the main N1MM Logger program.
  • Details - Click on the Set button in this column to open a window with a set of controls that depends on what is selected in the preceding columns (Radio, Digital, Packet, CW/Other). To the right of the details column is a summary of the detailed settings. See below for details.

The radio buttons in the upper right corner are used to fit the program to your desired mode of operation.

  • SO1V - Single Operator 1 VFO
    • In SO1V mode, the backslash, Pause, Ctrl+Right-arrow, grave accent(`) and Ctrl+Alt+K keys are disabled to prevent opening the second Entry window. If the second Entry window and/or Bandmap window were open, they will be closed when exiting the Configurer after selecting SO1V.
  • SO2V - Single Operator 2 VFO (one radio, using both VFOs)
    • Permits using two separate Entry windows, one for each VFO; the full SO2V functionality is usable only with radios that have dual receivers
  • SO2R - Single Operator 2 Radio
    • Permits using two separate Entry windows, one for each radio

1.2. Set button examples

  • COM7 details shown when Radio selected (serial port)
  • COM5 details shown when CW/Other selected for Winkeyer (serial port)
  • COM3 details shown when Digital selected (serial port)
  • LPT1 details shown when CW/Other selected (parallel port)

Image

Image
Of course, there will be many more possible combinations, depending on your setup.

  • Speed - The speed of the serial port to radio/if-interface link (check the manual of your radio/TNC)
  • Parity - The parity used (check the manual of your radio/TNC)
  • Data Bits - The number of data bits used (check the manual of your radio/TNC)
  • Stop Bits - The number of stop bits used (check the manual of your radio/TNC)
  • DTR - The following selections can be made (pin 4 on DB9 connector):
    • PTT - used for keying the radio
    • CW - used for sending CW to the radio
    • Always on - DTR is always 'high'
    • Always off - DTR is always 'low'
    • Handshake - DTR is used for handshaking
  • RTS - The following selections can be made (pin 7 on DB9 connector):
    • PTT - used for keying the radio
    • Always on - RTS is always 'high'
    • Always off - RTS is always 'low'
    • Handshake - RTS is used for handshaking

noteWindows 98 Users
We do not officially support Windows 98, but we know some people are still using it. If you are, and are having trouble getting your radio working, try this - Go into the Windows Control Panel, select the serial port, advanced settings and mark the port for XON/XOFF or "NONE" handshaking. Many radios now do not support hardware handshaking, and you have to turn it off to get data to/from them
  • Icom Addr (hex) - The address for the radio used, enter without the "H" i.e. 26 not 26H. (This field is only shown when an Icom is the selected radio)
  • Radio Nr - The radio controlled from this port
    • In SO1V (one radio, one VFO used) Radio Nr = 1
    • In SO2V (one radio, two VFOs) Radio Nr = 1
    • In SO2R select the radio (1 or 2) connected to or controlled by this port
      • If one LPT "CW/Other port" is set up as Radio=Both, and another LPT "CW/Other port" is set up as Radio=2, route band data for second radio to second port
      • When using CW/Other with an external SO2R controller the lowest numbered (first) LPT port must be assigned RADIO=BOTH (toggles pin 14)
        • I.e. When using LPT-2 and LPT-3 then LPT-2 must have Radio=Both
  • Dig Wnd Nr - Set this to indicate which Digital Interface window uses this port for PTT and/or FSK keying (only shown when Digital is checked)
    • If only one DI window is used, select 1
    • If two DI windows are used, select the DI window number this port will be used for
    • If the port is being used for FSK keying, you will also have to configure it in the MMTTY Setup window
  • Allow ext. interrupts - Allow external interrupts from this port (serial port - DSR pin 6; parallel port - pin 15), e.g. from a footswitch. An interrupt on this line will bring focus to the Entry window and stop a CQ in progress
  • Winkeyer - Select when using a Winkeyer keyer. Speed, Parity, Data bits, Stop bits or Handshake settings do not have to be adjusted; they are fixed and set by the program. Settings for the keyer can be done on the Winkeyer tab in the Configurer. If you select Winkeyer, DO NOT set DTR to CW.
    • Not possible if the port is used for radio control, digital or SO2R control (incompatible uses)
    • Note: Only one Winkeyer is supported, but a single Winkeyer can key two radios
  • Two Radio Protocol - Support for the MK2R or other SO2R controller from microHAM (using control protocol on COM port). USB-only SO2R (no LPT port required) with the MK2R/MK2R+. Protocol used may be either the MK2R proprietary protocol or OTRSP (Open Two Radio Switching Protocol)
    • Disabled when selection for CW/Other is turned off or when a radio is selected
    • OTRSP forces the port speed etc. to 9600,N,8,1
    • More info in the Digging Deeper chapter on supported hardware
  • CW/Other Port Addr - specify port address for serial and parallel ports
    • Note: For real ports, the address here should be the same as used for this port in Windows
      • The initial default address in this box may not be correct in some computers or for some add-in cards; if the port does not work, check the port's properties in Device Manager to determine the correct address. There is more information on this topic in the Interfacing chapter.
    • For USB-to-serial adapters, the address here can be ignored
    • When both RTS and DTR are set to PTT they will both be keyed for PTT with the set PTT delay
    • Packet uses as handshaking RTS + XON/XOFF
    • When using a self-powered interface set the handshaking to always on (DTR), always on (RTS) to supply power to the interface

noteLPT Port Numbers
With N1MM, SO2R and LPT CW, the LOWEST number port must have the CW output for BOTH radios if it is used with a conventional LPT SO2R box (DXD, KK1L, N6BV, etc.) or microHAM MK2R/MK2R+ in LPT (Classic auto control) mode, The LPT with CW, PTT and the TX/RX/Split controls must be connected to the SO2R controller. If N1MM is configured for CW on TWO LPT ports (first port: Radio=1, second port Radio=2) then CW will be present only on the port representing the radio with transmit focus.

  • DVK - DVK interface for MK2R, W9XT & other external DVKs. See this page for detailed information, pinouts, and limitations
    • When DVK is selected, the Antenna selection via the LPT port is disabled
    • Note: The DVK pins and the antenna pins on the LPT port overlap
    • When using an external DVK, all of the Run and S&P SSB function keys should be set to empty.wav and not left blank
    • microHAM MK2R: if DVK is checked, N1MM Logger will use the DVK in Router instead of its own DVK support
  • FootSwitch mode - Pin 6 on the serial ports and pin 15 on parallel ports. The combo box options are:
    • None - No footswitch
    • ESM Enter - Pressing Footswitch will cause the same action as pressing Enter key in ESM mode
    • Typing Focus - Pressing Footswitch will switch typing focus
    • Switch Radios - Pressing Footswitch will switch the radios (in SO2R)
    • Normal - Pressing the footswitch it will behave if it was connected to the PTT of the active transmitter and is automatically connected to the proper (active) radio.When the footswitch is released the focus will be set to main Entry window
    • F1 - Pressing Footswitch will cause the same action as pressing functionkey F1
    • F2 - Pressing Footswitch will cause the same action as pressing functionkey F2
    • F3 - Pressing Footswitch will cause the same action as pressing functionkey F3
    • F4 - Pressing Footswitch will cause the same action as pressing functionkey F4
    • F11 - Pressing Footswitch will cause the same action as pressing functionkey F11
    • F12 - Pressing Footswitch will cause the same action as pressing functionkey F12
    • Band lockout - Implemented mostly for multi user stations to block second signal on the same band/mode. It may be useful for single user as well. This mode should allow you to control PTT for both radios (in case of SO2R) in different modes (SSB/CW). The advantage of using it (compared to the foot switch directly connected to the radio) is - it stops AutoCQ and Dueling CQ's


It is possible to hook up a footswitch to a serial or parallel port. This should help users with only one or no serial ports (when a USB to serial adapter is used) to get the footswitch connected to the computer. A pull-up resistor is needed between DSR input (pin 6 on both DB9 and DB25) and +12 VDC. For using a parallel port as a footswitch, a pull-up resistor is needed between pin 15 and +12 VDC. Multiple footswitches (one per parallel or serial port) can be used where different settings may be used for each one.

1.3. PTT Options

Originally, Push-to-Talk (PTT) was actually a copyrighted term, describing how operators of one company's radios could press a button on their microphones to switch from Receive to Transmit. Over the years, however, it has come to denote any form of transmit/receive switching external to the radio. It could be as simple as a microphone button or a footswitch working directly with the radio, or as sophisticated as control by a logging program.

N1MM Logger provides several options:

  • PTT via serial or parallel port - This option uses the RTS or DTR lines on a serial port or pin xx on an LPT port. This more-or-less standard method requires a simple one-transistor interface to switch the radio. USB-to-serial adapters can be used for this function; ordinary USB-to parallel adapters will not work, because they lack the ability to control individual lines in the parallel interface - the one exception is the SO2RXLAT interface developed by PIEXX.
  • PTT via Winkeyer - If a Winkeyer, a keyer that emulates the Winkeyer, or an interface incorporating a Winkeyer chip is used, its PTT output can be used in all modes to control transmit/receive switching.
  • PTT via radio command - For radios that support it, this option eliminates any need for external hardware other than a serial port cable or a serial to USB converter. Check your radio manual for details.

Warning: At the moment, there is no provision for both controlling radio PTT via radio command and simultaneously introducing a delay before N1MM begins to send a stored message, so if you need to protect external equipment (see below) you should not use this option.

1.3.1. Selecting a PTT Method

Image

warningUse only one PTT Method at a Time
Do not select PTT via DTR or RTS in addition to Radio PTT via Command. Whether on the same port or another, doing so can result in conflicts that may cause PTT lockups or other malfunctions. If these occur, a first troubleshooting step is to verify that you do not have more than one PTT method checked.


The screenshot above shows all of the PTT options except for Winkey PTT - shown below. Selecting PTT via radio command is done on the port that you have set to control the radio; the three checkboxes allow you to select by mode.

1.3.2. PTT delay:

This is an important aspect of PTT operation. Some amplifiers are slower than many radios, so if the radio begins to transmit as soon as PTT is asserted, it may result in hot-switching of the amplifier's internal transmit/receive relays, which can result in damage. In addition, for VHF operation, preamplifiers located at the antenna may need to be properly sequenced to avoid damage from transmitted RF.

  • In the case of PTT via serial or parallel port, this delay is set in the Configurer, on the Hardware tab, when configuring a port for PTT. Note that you will only see this option if you have first selected PTT on either RTS or DTR.
  • For Winkeyer PTT, set this delay (called lead-time in Winkeyer parlance) on the Winkeyer tab of the Configurer. This affects both hand-sent CW and stored messages. You will probably find that any value over 20 milliseconds (probably enough for most amps) throws off your hand-sent keying.




1.4. Other Information


It is possible to have the PTT on the same serial port as the radio with interfaces that support this (e.g. with a keying circuit connected between RTS and the radio's PTT input).

If the type of CW/Other port chosen is LPT1, LPT2 or LPT3, additional information will be present on the parallel port. See Radio Interfacing for more detailed info.

1.5. Windows NT/2000/XP (32 bit OS)


Under 32 bit Windows operating systems, using the parallel and serial ports for PTT and CW keying requires a special dll. In N1MM Logger version 11.10.0 and later, this is inpout32.dll, which is installed with the Logger. In older versions of the Logger, it is dlportio.dll, which is installed using the program Port95nt.exe. A link to this file can be found in the Installation chapter. There is also information on installation for WIndows Vista and Windows 7, and for 64-bit OS versions, in that chapter.

2. Configurer >Telnet Cluster tab

  • Telnet Cluster - The default telnet cluster to connect in the Telnet Window
    • Ctrl+D - delete a row in the table or use right click menu
  • Edit button - Change Telnet Cluster List
    • File
      • Import... - Import a text file with Packet/Telnet cluster nodes into the program
      • Export... - Export the the Packet/Telnet cluster nodes to a text file

3. Configurer >Files Tab

Image


The files Tab is used to set the path to the Buckmaster callsign database if present, and to wav files used for voicing callsigns and serial numbers on SSB.

3.1. Files Field Descriptions

  • Callsign database path - Used to identify the directory of the Buckmaster callsign database to be used by the logging program. Be sure to include a trailing '\' in the directory name. Make sure that the path to the CD is set correctly. You can set the path to the Buckmaster database here and type in the full path to the Buckmaster database on your CD. For example: If your CD-ROM is mapped to the 'E' drive, the full path is: E:\HAM0\
    • Don't forget the back-slash '\' at the end of the path! Also, make sure to copy the HAMCAL32.DLL from the CD to the program directory where N1MM Logger is installed. On older CDs, this file is located in the \API\WINDOWS directory. It may be located elsewhere on newer CDs
  • Letters file path - The full path to the letters directory, where the individual letter and number wav files are stored for use by the ! and # macros. This is used for voicing call signs or serial numbers, more fully described here. The {OPERATOR} macro can be used to invoke different sets of letter files for each operator's voice. Example: C:\program Files\N1MM Logger\letters\{OPERATOR}\ . This provides the ability to have a separate letters file for each operator in a multi-op, or for guest ops, without having to move your own letters and numbers files out of the letters directory. Again, don't forget the backslash at the end of the path.

4. Configurer >Function Keys Tab


Image


Function keys for each message are set here.

4.1. Function Keys Field Descriptions

  • Monitor via PC speaker (Win98/ME only) - The CW sent by the program plays via the PC speaker (only for Windows 95, 98, ME, disabled for NT/2000/XP machines)
  • Send Corrected Call (Before End of QSO Msg) - Send Corrected Call (Before End of QSO Message) - If the callsign is corrected after answering a call, then the corrected call will be sent before the End of QSO message (as configured by the End of QSO Key). E.g. 'PA1M TU DE N1MM' instead of 'TU DE N1MM'
  • Send Partial Calls - Only CW. When sending a partial corrected call only the corrected part will be send (prefix or suffix). If not checked the whole call will be sent
  • Work Dupes when Running - Work dupes is for ESM in Run mode and don't send the QSO B4 Key. All it does is determine what is sent when a dupe calls you AND YOU PRESS ENTER. Normally you do want to work dupes. See the chapter Off topic for a discussion
  • Use Contest Word Spacing for CW - The box is defaulted ON for "Use Contest Spacing for CW". This setting changes the spacing between words in your CW, where "N1MM 599 5" is 3 words. Default is 6 bits for "contest spacing". When box is not checked, 7 bits between words is used, which is "normal spacing"
  • Send Cut Numbers - In CW this causes serial numbers, and RSTs if you are using the {SENTRSTCUT} macro, to be sent using the Cut Number Style set at the bottom of the dialog. Ctrl+G can be used to toggle this option while operating. The new status after toggling will be shown in the status line at the bottom of the entry window. Numbers other than serial numbers and {SENTRSTCUT} will not be affected by this option. This option does not apply to SSB or digital modes
  • Send leading zeros in serial numbers - Send leading zeros to make into 3 digit number. In CW: Select leading T with the Cut Number Style selector. RTTY: In RTTY zeros will be added, so 1 will become 001
  • Stop Sending CQ when Callsign changed - Typing a character in the callsign field will stop a (repeated) CQ
  • ESM only sends your call once in S&P, then ready to copy received exchange - This is many times called the "Big Gun versus Little Pistol switch" . When selected and in Enter Sends Message mode the cursor moves to the Exchange field when there is something in the Callsign field and Enter is pressed (so it does not keep the cursor in the callsign field). If you don't usually get a station on the first call then deselect this option. Read more about Big Gun \ Little Pistol operation inder ESM HERE
  • String to use on CW between his call key and exchange key (default is one space) - Just as it says. Example ' ur '
  • Keycode of Ins Key Substitute - Enter the number for the Ins Key substitute as mapped below in this configurer dialog. Defaults to 186, the ; character. The program can automatically enter the keycode in this field . Place the cursor in the keycode field and press the key you want to substitute, it will put the correct keycode in. 186 is an extended key code. Not all keyboards map keys the same way. Note that you can't use a Shift, Ctrl, Alt etc. key. I would not advise using a key like Numeric + that is already in use. It may or may not work. In this case Numeric +, does NOT work
  • Keycode of TU/Log Key Substitute - Enter the number for the TU/Log Key substitute as mapped below in this configurer dialog. Defaults to 222, the ' character. The program can automatically enter the keycode in this field . Place the cursor in the keycode field and press the key you want to substitute, it will put the correct keycode in. 222 is an extended key code. Not all keyboards map keys the same way. Note that you can't use a Shift, Ctrl, Alt etc. key. I would not advise using a key like Numeric + that is already in use. It may or may not work. This particular case (Numeric +) does NOT work
  • Cut Number Style - the following cut number styles can be chosen:
    • T1234567890 (leading T) - leading 0 will be replaced with a T. So 007 will become TT7 and 030 will become T30
    • O1234567890 (leading O) - leading 0 will be replaced with an O. So 007 will become OO7 and 030 will become O30
    • T123456789T (all T) - all zeros will be replaced with a T. So 007 will become TT7 and 030 will become T3T
    • O123456789O (all O) - all zeros will be replaced with an O. So 007 will become OO7 and 030 will become O3O
    • T12345678NT (TN) - all zeros will be replaced with a T, all nines with an N. So 097 will become TN7 and 090 will become TNT
    • O12345678NO (ON) - all zeros will be replaced with an O, all nines with an N. So 097 will become ON7 and 090 will become ONO
    • TA2345678NT (TAN) - all zeros will be replaced with a T, all nines with an N, all ones with an A. So 091 will become TNA and 190 will become ANT
    • TA234E678NT (TAEN) - all zeros will be replaced with a T, all nines with an N, all ones with an A, all fives with an E. So 091 will become TNA and 1590 will become AENT
    • TAU34E67DNT - the zero, one, two, five, eight, nine will be replaced with a T, A, U, E, D, N respectively

4.2. Remapping Function Keys

Select which function keys to send messages. Each type of message has a combo box for you to set the appropriate function key. If the program is sending the wrong message check here first. The only restriction is that a key must mean the same thing in Running and in S&P. Function keys do not have to be unique for a selected message. There is little reason to do so although if you want it can be done. For the following messages a function key can be selected

  • CQ Key - defaults to F1
  • Exchange Key - defaults to F2
  • End of QSO Key - defaults to F3
  • His Call Key - defaults to F5
  • My Call Key - defaults to F4
  • QSO B4 Key - defaults to F6
  • Again Key - defaults to F8 (can be disabled)
  • Next Call Key - defaults to Disabled

ESM Mode Work dupes when running Mode QSO B4 Key Again Key Action Result action
On don't work dupes Run Disabled F-key DUPE callsign entered Send AGN message when Enter pressed
On don't work dupes Run Disabled Disabled DUPE callsign entered Send the EXCH when Enter is pressed, station will be worked and logged with Enter, Enter
On don't work dupes S&P Disabled F-key DUPE callsign entered Pressing Enter does nothing, no blue buttons in the Entry window
On don't work dupes S&P Disabled Disabled DUPE callsign entered Pressing Enter does nothing, no blue buttons in the Entry window
On work dupes Run - Disabled DUPE callsign entered. Mistake with received QSO data Send EXCH when Enter is pressed
On don't work dupes Run - Disabled Mistake with received QSO data Send EXCH when Enter is pressed
On - S&P - Disabled Mistake with received QSO data Send EXCH when Enter is pressed. After the user corrects the entry, it will log and not send anything


5. Configurer >Digital Modes Tab


Image

The Digital modes tab is used to set up the interfacing to external Controllers (TNCs), or for PTT control using MMTTY/MMVARI for sound card digital modes.

In SO1V mode, there is only one Digital Interface window, DI-1. In SO2V and SO2R modes, there are two Digital Interface windows, DI-1 and DI-2. Each DI window is associated with one of the two Entry windows. Each DI window is opened from the Window > Digital Interface menu item in the corresponding Entry window. The Digital Modes tab in the Configurer is used to configure both Digital Interface windows.

5.1. Digital Modes Field Descriptions

  • Digital Interface 1 / 2
    • TU type
      • None
      • Soundcard - use this selection for MMTTY, MMVARI or Fldigi sound card software
      • Other - use this selection for a TNC or TU such as a PK-232 or KAM
      • Dxp38 - for the HAL DXP-38 TU
    • Port, Speed, Parity, Data Bits, Stop Bits, Flow Control - Used when Other or Dxp38 is selected, to set the parameters for the COM port used to communicate with the TNC or TU (e.g. 9600 baud, N, 8, 1, no flow control for the DXP-38)
  • DI-1 MMTTY Mode | DI-2 MMTTY mode
    • When using MMTTY, select whether AFSK or FSK is being used
    • The serial port MMTTY will use for PTT and FSK has to be set in the MMTTY Setup. More information in the MMTTY support chapter
  • DI-1 MMTTY Path | DI-2 MMTTY Path
    • The path to the MMTTY engine goes here including the file name of the program
    • It's not necessary that MMTTY be in the same directory as N1MM logger
    • Via the 'Select' buttons the path and file name can be selected
    • It is possible to select two instances of MMTTY in two separate folders. You must do this if you want the MMTTY settings in the two instances to be different (e.g. left vs. right channel, different sound cards, etc.)
  • DI-1 Fldigi Path | DI-2 Fldigi Path
    • The path to the Fldigi engine goes here including the file name of the program
    • Via the 'Select' buttons the path and file name can be selected
  • DI-1 MMVARI RTTY Mode | DI-2 MMVARI RTTY Mode
    • When using MMVARI for RTTY, select whether AFSK or FSK is being used
    • If AFSK is selected the serial port (if any) with a check in the Digital check box and with Dig Wnd Nr corresponding to the DI window number will get passed to MMVARI when the DI window is opened, so that MMVARI can use it for PTT control
    • If FSK is selected, the port to be used for PTT control is not passed to MMTTY. It must be defined in the EXTFSK or FSK8250 setup window
  • DI-1 MMVARI FSKPort | DI-2 MMVARI FSKPort
    • Choose FSK8250 if you are using a true serial port or a device that can simulate a serial port and handle 5-bit codes at 45.45 baud (this does not include most USB-to-serial adapters, but it does include some commercial interfaces designed to support FSK RTTY)
      • When MMVARI is opened for FSK RTTY, a small window labelled FSK8250/16550 1.03 will open, or appear on the Windows Task bar. In this window you select the COM port number and the signal line to be used for PTT (RTS or DTR). FSK keying will be done on the TxD line. If this is a USB device that simulates a serial port, check Limiting speed. You can use the _ box at the top right to minimize this window after completing the setup
    • Choose EXTFSK if you are using a regular USB-to-serial adapter
      • When MMVARI is opened for FSK RTTY, a small window labelled EXTFSK 1.05a will open, or appear on the Windows Task bar. In this window you select the COM port number and the signal lines to be used for FSK keying (normally TxD) and PTT (RTS or DTR). You can use the _ box at the top right to minimize this window after completing the setup

6. Configurer >Other Tab


Image

The Other tab is used to set up default values and select special modes and functions.

6.1. Other Tab Field descriptions


  • Packet Spot Time (min) - Indicates how long (in minutes) spots are kept in the bandmaps. The default is 60 minutes, any integer may be specified
  • Repeat time in millisecs - Specify the repeat interval (CW or SoundBlaster) in the Entry window (Auto-CQ). The default value is 1.8 seconds. Enter a value in seconds or milliseconds. The maximum value is 32767. This is the same as Ctrl+R or 'Config | Set CQ repeat time' in the Entry Window
  • Default # Spots in SH/DX/# - The number of returned spots by the SH/DX command in the bandmap window. The default value is 30 spots. The number of returned spots for the SH/DX command in the Packet / Telnet window is not affected by this value and has to be changed in the Entry window under 'Config menu | Edit Packet/Telnet Buttons'
  • SSB Tuning Tolerance (Hz) - SSB mode: Clicking on or next to a station in the bandmap window will put the call on the callsign frame (if the callsign field is empty) of the Entry window. This value gives the maximum frequency distance to the call on the bandmap when it will be put on the callsign frame. The value has to be between 0 and 20000 (20 kHz). The default value is 300
  • CW Tuning Tolerance (Hz) - CW mode: Clicking on or next to a station in the bandmap window will put the call in the callsign frame (if the callsign field is empty) of the Entry window. This value gives the maximum frequency distance to the call on the bandmap when it will be put on the callsign frame. The value has to be between 0 and 20000 (20 kHz). The default value is 300
  • RTTY Tuning Tolerance (Hz) - RTTY mode: Clicking on or next to a station in the bandmap window will put the call on the callsign frame (if the callsign field is empty) of the Entry window. This value gives the maximum frequency distance to the call on the bandmap when it will be put on the callsign frame. The value has to be between 0 and 20000 (20 kHz). The default value is 300
  • CW Weight - Adjusts the CW weight (between 30-70% limits). The default value is 50. Thie weight command not only works for serial or lpt CW but also for Winkeyer
  • SSB Up/Down Arrow Incr (kHz) - This value gives the frequency jump amount in SSB by the up/down arrow keys. NB. Never make it smaller than the smallest step your radio can make in SSB. Older Icom rigs are known to have a smallest step of 100 Hz which is quite big. When the step is made smaller than the minimum step size the Up/Down Arrows don't seem to work. Also controls the amount of each frequency change when tuning the RIT on radios that support doing so from the computer.
  • CW Up/Down Arrow Incr (kHz) - This value gives the frequency jump amount in CW and digital modes by the up/down arrow keys. NB. Never make it smaller than the smallest step your radio can make in CW. Most rigs have a smallest step in the order of 10 Hz. When the step is made smaller than the minimum step size the Up/Down Arrows don't seem to work. Also controls the amount of each frequency change when tuning the RIT on radios that support doing so from the computer.
  • PgUp/PgDn Incr (kHz) - This value gives the frequency jump amount for the {PGUP} {PGDN} macros (Note: the PgUp and PgDn keys are not used for this; the {PGUP} and {PGDN} macros must be used in function key macros. These macro names are holdovers from early versions of the program)
  • Primary CW speed Step - The primary speed step is used with PgUp/PgDn button or the speed adjust in the Entry Window
  • Secondary CW speed Step -The secondary speed step is used when Shift+PgUp/PgDn is pressed. Alt+PgUp/PgDn adjusts the CW speed of the inactive radio/VFO in SO2R/SO2V mode
  • Clear automatically populated exchange on callsign change - When selected (default is Off), if the callsign in the Entry window is changed by the operator, this option clears the contents of exchange fields in the Entry window that were populated (filled in) from a CallHistory file, from previous QSOs in the contest, or from a Telnet spot. Does not affect exchange data that have been manually filled in.
  • Keep log of all QSOs to facilitate recovery of log - This is the transaction back-up log file. This journaling back-up text file has all QSOs from the contest in it. So if the database for some reason would become corrupt it is possible to import this file in a new database and go on with the contest
    • When this option is selected the transaction log is created for each contest you log to
    • The file is closed after each transaction and reopened to force the data to be written to disk
    • To keep things simple and foolproof, you are not allowed to change the name of the transaction log
      • The name is used to make sure you are loading it properly, and to prevent mixing logs of two contests
      • Example name: 'hamDB - CQWWCW - 2005-09-19.TRN' i.e.: Database name- contest name - date log created. The database name ends in "DB", rather than .mdb, to remind users that this is NOT the log file maintained in the ham.mdb database
    • To Recover your log, you MUST import the transaction log into a NEW (empty) database and a NEW contest log
      • >File >NewDatabase followed by >FIle >New Log in Database
        • The new contest log must be the same contest as the contest from the transaction file (Example: if restoring CQWPXCW, the new contest must also be CQWPSCW)
      • Why? To prevent a user recovering from a database problem making the problem worse. This will prevent any issues from duplicate contacts and a number of other problems
      • Use >File >Import >Recover QSOs from a Transaction Log - to import the transaction log file
    • As you load the transaction log, a new transaction log is automatically made with the transactions in the first log. Thus you should never have to merge logs. You always use the last one
  • Start Contest Reporting Application - Start the contest reporting application. With this application you can show your contest efforts in real time during a contest to the world. Next to this application a website is needed where everyone can see the score. This application does automatically upload scores from the current selected contest to the configured website
  • Mute mic on supported radios - Mute the microphone during transmit. Normally used to enter audio via an other radio input then the microphone. Default is to not mute
    • Tentec Orion: If "Mute" is checked, it causes the Orion's mic input to be muted and the Aux input to un-mute during voice keyer events
    • Supported radios are: Tentec Orion and Elecraft K3
  • Format for DXSpider Cluster - This will send the right SH/DX message for DXSpider clusters from the button in the top of the bandmaps (Example: SH/DX/30 on 20). Also SH/QRZ will be sent instead of SH/BUCK. Only select this when connecting a DXSpider cluster. Connect the cluster and send: SH/VER A DX-spider cluster will say something like: DX Spider Cluster. The 'normal' setting is not selecting this option
  • Auto-Completion Mode - Auto-completion of callsigns. It works like Internet Explorer's address bar. If you type in a partial callsign, the program will attempt to match it with a call that you have already logged or is uniquely identified in the check window. If it matches, the rest of the call will be added to the callsign textbox and highlighted. You can then either accept the call as displayed, or keep typing. If you keep typing, the highlighted portion will be replaced by what you type
  • Use Reverse CW - When selecting CW send a command to the radio to use Reverse CW

7. Configurer >Winkeyer Tab


Image

The Winkeyer tab is used to control functions of the K1EL Winkeyer keyer chip. Winkeyer is designed by K1EL and G3WGV. It is only active when the Winkeyer box has been checked on a serial port, and that port (whether real or virtual), has been connected either to a stand-alone keyer or to a device that embeds the Winkeyer chip, such as various MicroHAM products and RigExpert. Consult your unit's manual along with the Winkeyer chip manual for more information on these settings.

Winkeyer is fed ASCII characters from N1MM Logger (via COM or USB Ports), and converts the ASCII to timed CW. The pot speed range is from a minimum of 10 wpm to a maximum of 55 wpm. Winkeyer can also be used to control PTT. Winkeyer PTT can be used on modes other than CW. Note: This only works for Winkeyer versions 10, and 21 and greater.

7.1. Winkeyer Field Descriptions

  • Keying Mode - Select the keying mode. Choices are: Iambic A, Iambic B, Ultimatic and Semi-Automatic. The default is Iambic-B
  • Autospace - Select when the autospace feature should be used. When using the paddles to send, if a pause of longer than one 'dit' time is detected, THREE dit times of pause will be inserted before the next character. See the manual for more information
  • Pot is wired with two leads - Select when the potentiometer on the board is wired only with two instead of three wires. Under normal operation, leave unchecked. Unless you've built the keyer yourself, or your keyer vendor recommends this, leave unchecked
  • Pin 5 Function - Select the function of pin 5. Unless your keyer's manual tells you otherwise, the default of PTT is likely what you want here. The Winkeyer manual is also a good reference. The choices are:
    • PTT (default)
    • Sidetone
    • 2nd CW (second output, do not use for SO2R - see below))
    • None
  • Sidetone Frequency - Select the sidetone frequency. The default sidetone frequency is 469 Hz
  • Reverse Paddles - Reverse the left and right paddle
  • Ignore Winkeyer Speed Pot - Ignore the setting of the Winkeyer potentiometer
  • Lead Time - Set the lead time value in 10ms Increments (up to 2.55 seconds). This value reflects the amount of time that the Winkeyer PTT will be asserted BEFORE keying commences
    • If when sending CW you are missing the first dot or dash, or if paddle-sent CW doesn't seem responsive (again, missing the first character) set this to at least 10 mSec
    • NOTE that this field denotes 10 mSec intervals — '1' in this box means 10 mSec
    • IF Pin 5 function is set to PTT, set this value to at least 1 (10 mSec)
  • Tail Time - Sets the tail time in 10 mSec Increments (up to 2.55 SECONDS). This value reflects the amount of time that the Winkeyer PTT line will be held after keying stops. Tail Time = 1 results in a tail time of one dit time (v2.2; 10 msec in earlier versions of Winkeyer), Tail Time = 2 adds 10 msec to that, Tail Time = 3 adds another 10 msec, and so on. If Tail Time is set to zero, then Hang Time is used instead
  • First Character Extension - Sets the extension time in 10 mSec steps (up to 2.55 seconds). Normally ONLY used with older, slower-keying rigs at speeds above 25 wpm, this setting will add time to the first element sent to help with the lack of T/R speed of those rigs. This value is usually set by experimentation. See the Winkeyer manual for more information on setting this value
  • Keying Compensation - Normally only used with high speed (>30 wpm) QSK operation. Adds time (in 1 mSec increments) to both dashes and dots to adjust for rig switching delays (however slight). See the Winkeyer manual for more information
  • Hang Time - Provides a CW-Speed dependent means of holding PTT after CW sending is finished. Hang Time can be used to set a CW-speed dependent delay of 1, 1.33, 1.67 or 2 letterspaces (not dit spaces). Tail Time must be set to zero to use Hang Time
  • Winkeyer 2
    • Sidetone - Gives a sidetone when sending CW (when using paddle and computer input)
    • Paddle only sidetone - Gives a sidetone only when sending by paddle
    • Use 2nd output - If this option is checked, when the N1MM Transmit focus is in the second radio Entry window, CW and PTT will be switched to Winkeyer Output 2. This is convenient for minimal CW SO2R, because no additional hardware is needed to switch CW and PTT between radios. You'll still need to do something about the received audio switching, though. Select this option only for SO2R operation.

noteSetting CW Speed and Weight in Winkeyer
Speed setting is done just as with other keying methods. The PgUp and PgDn keys will increase or decrease the speed (default is 2 WPM steps). You can also overwrite the value in the speed window, or use its up/down arrows. Ctrl+PgUp/PgDn increases or decreases the speed by a larger amount (default is 4 WPM). Both values can be adjusted on the Other tab.

Setting the speed using the speed control pot changes BOTH the paddle speed and the N1MM sending speed. Setting the speed using the entry window changes both the paddle sending speed and N1MM sending speed but ONLY UNTIL the next time the speed pot is adjusted, i.e. the absolute position of the speed pot then overrides any changes made in the entry window.

CW weight for Winkeyer can be set on the Other tab, but is not usually changed from the 50% default.

8. Configurer >Mode Control Tab


Image

The mode control tab determines how the mode will be controlled on the connected radio, whether the program sets the mode when changing frequency or not, and what mode it changes it to. This dialog also gives you control over how contacts will be logged.

noteMode logged vs. Radio mode

In an ideal world, the mode in the log, the radio's mode and the mode in the software would all be the same. For traditional voice and keyed CW modes (CW, USB, LSB, AM, FM) this actually holds true. With the obvious exception of radios that do not support all of these modes, there is a one-to-one correspondence between the names of the modes on the radios, in the software and in the log. If these were the only modes that existed, it would always be possible to change modes on the radio and have the software follow (or vice versa) without risk of confusion or error, and there would be no need for mode control configuration settings.

However, when digital modes are brought into the picture this one-to-one correspondence breaks down. Any SSB-capable radio can be used for digital modes using a sound card, even if the radio itself does not have any native digital modes. This results in a many-to-one relationship (many different modes in the log can map to a single mode on the radio). In the case of RTTY, some radios have a native RTTY mode using FSK keying, and when it exists, this mode is uniquely associated with RTTY and not with any other digital mode in the log. However, the reverse is not true; depending on the hardware configuration and the operator's choice, RTTY in the log may correspond with either RTTY or SSB on the radio. In the case of some radios, there may also be an additional mode or modes in the radio tailored either specifically for AFSK RTTY or for sound-card digital modes generally.

Because of this breakdown in the one-to-one correspondence, a radio-first priority system cannot be imposed in all situations - once digital modes are involved, setting the mode on the radio does not always uniquely identify the mode that should be logged. Instead, the primary rule is "software first". Setting the mode in the software always controls what the radio does. You can select the mode in the software simply by typing the name of the mode (CW, SSB, USB, LSB, AM, FM, RTTY, PSK) into the entry window in the callsign box and pressing the Enter key. Provided the mode you have chosen is supported by the contest (this is determined by the Mode category in the contest setup window), the software and the radio will switch to the mode you have commanded, and that is the mode that will be logged, When the MMVARI or Fldigi digital engine is used, the specific digital mode logged will depend on what mode has been selected within the digital engine. Since not all radios use the same radio mode for digital modes, there are settings in the right side of the mode control configuration window that determine which radio mode is used for each of RTTY and PSK.

Despite the lack of a complete one-to-one correspondence between the modes in the log and in the radio, there are many situations where some degree of automated mode switching is possible, based either on the radio's mode or on the frequency, and within the limits imposed by the current contest setup (i.e. what modes are supported within the current contest). The settings that control whether this kind of automation is used, and on what basis, are in the left side of the mode control window.

One of these options is to use the band map. You may be able to use this within a single mixed-mode contest where the modes are kept well-separated in frequency. Unfortunately, this doesn't work in all situations. During major CW contests, for example, CW may be used pretty much throughout the normal digital sub-band. On the other hand, during a major RTTY contest you may find RTTY being used on frequencies that would normally be considered to be CW frequencies. For this reason, using the band map to determine the mode is not a foolproof set-and-forget option. Depending on the modes supported by your radio and the nature of the particular contest(s) you are operating in, you may need to choose one of the other options.

noteDigital Interface Window - Open or Closed?

There is a difference in mode control behavior between the situation where the DI window and digital engine window are open and the situation where they are closed. This is due to the way serial ports are used by the digital engines and by the Logger. The digital engines are separate processes from the rest of the Logger, and a single serial port cannot be shared between two processes. Since serial ports can be a scarce resource in a complex contest station, the Logger allows time-sharing of serial ports between digital (FSK & PTT) and non-digital (CW & PTT) uses. It does this by switching the ports between the processes depending on whether the DI window is open or not. When the DI window is opened, serial ports that have the Digital box checked in the Configurer are closed by the Logger so that they can be opened by the digital engine. When the DI window is closed, these ports are released so that the Logger can open them for use in other modes.

Thus, whether the DI window is open or closed can make a significant difference to the hardware configuration. Whenever a serial port is time-shared between the Logger and a digital engine, that port cannot be used for PTT or CW keying in non-digital modes while the DI window is open.

In order to support the wide range of possible hardware configurations in a hardware-independent fashion, mode control in the Logger depends on whether the DI window is open or not. When the DI window is closed, radio-first mode control works between non-digital modes, but switching the radio mode to (or through) a digital mode or tuning the radio's frequency into (or through) a digital band segment does not open the DI window and switch the software to digital mode. To switch into a digital mode, the DI window must be opened from the software. This can be done by using the Entry window to select RTTY or PSK mode in a contest that supports digital modes, or by using the Window > Digital Interface menu item.

Once the DI window is open, changing modes on the radio does not close the DI window and the software does not switch out of digital mode, which means that radio mode-driven mode control does not work when the DI window is open. Mode changes in this state must be performed from the software. If the software is commanded from the Entry window to use a non-digital mode, the DI engine is closed by the software in order to free up any time-shared ports for the Logger to use.

8.1. Mode Control Field Descriptions

  • Mode recorded in log - Set how to determine the mode that will be entered in the log
    • Use radio mode (default) - if the DI Window is not open, use the mode received from the radio. If the DI Window is open, the mode used depends only on the digital engine and not on the mode received from the radio, as follows:
      • In digital modes, the mode in the log will be RTTY if using the MMTTY engine or a TNC
      • When using the MMVARI or Fldigi engine, the mode will be as selected in the MMVARI or Fldigi window (digital modes only for Fldigi)
    • Follow band plan - use the mode the internal bandplan gives for this frequency
    • Use contest mode or bandplan - if the contest is a single mode, use that mode. If mixed, use the bandplan (as above)
    • Use contest or radio mode - if the contest is a single mode, use that mode. If mixed, use the mode from the radio (as above)
    • Always: - always log the mode selected here (CW, SSB, RTTY, PSK31, PSK63, PSK125) regardless of the mode from the radio
  • Mode sent to radio - Select how to determine the mode sent to the radio
    • This applies only for digital modes. See the note below for details

noteDigital Mode Selection
Every radio seems to have a different range of choices and names for digital modes. Some radios have no modes specialized for digital modes, some have only one digital mode for FSK RTTY (for sound-card digital modes, you use USB or LSB), some add to this a separate mode intended for sound-card digital modes like AFSK RTTY and PSK31, and some radios have three separate digital modes for FSK RTTY, AFSK RTTY, and other sound-card digital modes like PSK31. There may also be two versions of each of these, one "normal" and one "reverse" (opposite sideband). Every manufacturer uses different names for these specialized modes.


For simplicity, N1MM Logger has its own radio-independent terminology. The Logger uses RTTY for the radio mode normally used for FSK RTTY (which is usually but not always called FSK or RTTY on the radio). If the radio has a mode that is designated for AFSK RTTY, the Logger calls it AFSK. AFSK-R is the "reverse" of this AFSK mode, i.e. on the upper sideband instead of LSB. If there is a mode intended for sound card data modes that is different from the AFSK-R mode, it will be called PSK in the Logger. Not all radios have all of these modes, so not all choices will necessarily be available, depending on what radio(s) is/are configured.

The translation between the mode name used on the radio and the mode name used in N1MM Logger is described at Click here to see the table

For RTTY, if you are using FSK, you should normally select RTTY. If you are using AFSK, you should normally select AFSK or LSB/USB, depending on whether your radio offers a specialized AFSK mode or not.

For PSK, the choice would normally be one of: PSK (if available), AFSK-R (on some radios), or USB.

9. Configurer >Antennas Tab

Image

The Antennas Tab defines how antennas will be selected by the program, if you have appropriate hardware, and also controls the rotor program. The example above illustrates the features of this tab.

Close
noteTip
Unlike most software you don't map bands to bcd outputs 0-15 with N1MM Logger. You map antennas to bcd outputs 0-15. You can still map bands, but the antenna approach is much more powerful. It supports multiple antennas per band, stacks, and multiple bands per antenna. See the screen shot above.

9.1. Field Descriptions

  • Code - The code which will be presented on the LPT port as binary coded decimal output, using pins 9, 8, 7 and 2
    • The codes themselves are pre-determined. Sixteen different codes are the most that can be represended by the state of 4 pins.
    • Each code represents ONE ANTENNA,, and you can have many different combinations. In the example above, there is no antenna corresponding to the code of 0.The other 6 are each defined separately.
  • Antenna -Text to describe the antenna. This text will appear on the status bar of the Entry window when you change bands or switch antennas for a given band.
  • Bands - The bands on which this antenna will be selected
    • List bands in MHz e.g. 1.8, 3.5, 7, separated by commas if more than one is covered by the antenna, as in the illustration.
    • The first antenna in the table will be selected when changing to a band. Press Alt+F9 to toggle through all the antennas for the current band .
    • An antenna may be used on any number of bands
  • Rotor Description - enter the description as defined in setting up the rotor program. It must be exactly the same in each, because these names make the connection between the two programs.** More than one rotor can be selected (separate using commas), for example to turn a stack where more than one rotor is involved.
  • Offset - This offset is added to the rotor position to determine the antenna position. This is useful for antennas that are mounted at 90 degrees for pattern interference reasons, or for antennas that have simply turned some in the wind over the winter. The offset can also be entered for the selected rotor in the rotor program
  • Bidirect - Set to 1 if the antenna can be set bidirectional (0 = not bidirectional, 1 = bidirectional) (e.g. Steppir)
  • Start Rotor Program - Start rotor program automatically by N1MM Logger main program. You will need to stop it manually

noteLPT Port Conflict
When DVK is selected on the same LPT port, antenna selection on the pins will not work because the DVK pins and the antenna pins overlap.

10. Configurer >Audio Tab


Image

warningBefore We Start
Any time you change the Default sound card in your Windows Control Panel while N1MM Logger is running, you must shut N1MM Logger down and re-start it. Otherwise, the program and the operating system may be on "different pages", and it can cause audio functions not to work or to work strangely. Moreover, any time that you change the Windows Default sound card, you will have to come back to this tab and reset your audio options. You can imagine how we found this out!

For the Two Sound Card SO2R ($5 SO2R) check the SO2R chapter.

Select at the top of the page the configuration to use. (example picture how to connect can be found in the SO2R chapter.)

1 - Only use Radio 1 Output Device, Output on both channels

  • One radio and one sound card to play wav files and record new messages and mute the microphone when playing wav files
  • Only the top part of the dialog above (Tx Sound Card Setup) has to be set up. Bottom part is deselected (greyed out)


2 - Two Radio, Output left channel on left radio, right channel on right radio

  • One sound card to play wav files to each radio
  • Only the top part of the dialog (Tx Sound Card Setup) has to be set up. Bottom part is deselected


3 - Two radio, Sound Card $5SO2R, CW Only

  • $5 SO2R with one sound card for CW only
  • The drawback here is that no switching of the headphones is done
  • You will have to wire a cable to the CD or aux input of a sound card in order to make use of this feature
  • You'll need to define your mode as SO2R in the Hardware tab
  • Both Tx Sound Card Setup and Rx Sound CardSetup must be filled in


4 - Dual Cards - Two radio, $5 Sound Card SO2R

  • Full $5 SO2R with audio switching - two soundcards are needed
  • Switching of the headphones is done
  • You will have to wire a cable to the CD or aux input of a sound card in order to make use of this feature
  • You'll need to define your radios as SO2R in the Hardware tab
  • Both the Tx and RX Sound Card setups must be completed.

  • Tx Sound Card Setup - It is best to choose the default sound card (the one named in your operating system's Sound section in the Control Panel) for the Tx sound card. This is because the CD input is not used for Tx and can be used normally.
    • Select Radio 1 Output Device - Select the sound card to use for sending WAV files (DVK) on Radio 1
    • Select Radio 2 Output Device - Select the sound card to use for sending WAV files (DVK) on Radio 2
    • Radio 1 Output Device is an Internal Radio Codec - Check if you are using a CODEC built into Radio 1 instead of a separate sound card (CODEC is used here and elsewhere in this manual as a synonym for sound card)
    • Radio 2 Output Device is an Internal Radio Codec - Check if you are using a CODEC built into Radio 2 instead of a separate sound card
    • Select Port to Mute - Typically, this is used to mute the microphone during stored message playback, so you would select Microphone from the drop-down list. The two options are for Radio 1 and 2, left to right.
    • Select Message Recording Device - Select the sound card to use for recording stored messages for later playback on either radio
    • Select Message Recording Port - This is used for recording messages on the fly, and will almost always be the Microphone.
    • Recording Channels - Select 1 or 2, depending on your transceiver's line output capabilities and whether you want a one or two-channel recording - for example in SO2R mode.
    • Recording Bits - 8 bits gives the most compact recordings, at the price of audio fidelity.
    • Recording Sample Rate - Select the sample rate to record. The lower the rate the smaller the files but, audio quality will be less
noteNot All Sound Cards are Created Equal
The Configurer lets you pick parameters that your sound card may not support... usually 16 bit, 11025 Hz/sec is safe for all cards. If you choose a parameter that is not supported by your card, you will see Error 4 in the status line of your Entry Window when you try to play back a message.

The output port for recorded messages going to the radio is always the sound card's Line Out or Speaker Out port

  • Rx Sound Card Setup (used for SO2R Headphone Switching) - Two line-level inputs are required for SO2R switching by sound card.
    • Device - Select the (second) sound card to use
    • Left Radio Input Port - Select the Left Radio Input Port which receives the audio from the radio.
      • Must be different from Right Radio Input Port
    • Right Radio Input Port - Select the Right Radio Input Port which receives the audio from the radio.
      • Must be different from Left Radio Input Port


Last Modification: 06 March 2014 19:19:05 EST by n2ic.