Loading...
 

2.7.3 Digital Setup

1. Quick Start RTTY Setup

First, make sure you are familiar with basic operation of N1MM Logger+ in CW and SSB. It's not a good idea to try to use the program in digital modes if you aren't familiar with at least the basic operation (see the Getting Started section of the manual for an introduction).

Next, have a quick look at the Overview section below - if you are new to digital modes, this may give you a better idea of how things fit together, and even if you are an old hand at digital modes, it's worth taking a few minutes to ensure you know how to adjust sound card levels and sampling rates.

Once you are ready to begin, decide which digital engine(s) you want to use - an external TU/TNC, MMTTY, 2Tone, MMVARI or Fldigi. One of these (MMVARI) is built in to the Logger, but the others all will need to be downloaded. Each digital engine used by the Logger stores its configuration information in the directory the engine is run from. For that reason, you should create a separate directory for each copy, separate from the directory you use when you run it stand-alone or from some other logging program. These directories should not be in the C:\Program Files or C"\Program Files(x86) path; putting the program in one of those paths prevents it from writing to its own configuration files. If you use more than one copy of a digital engine (for example, for SO2V or SO2R, or for additional RX-only windows), you need a separate directory for each copy. For more detailed information, check out the following sections on Downloading and Installing MMTTY/2Tone/Fldigi/GRITTY (GRITTY is receive-only and cannot be used from the main Digital Interface window).

After these preliminaries, start N1MM Logger+ and open the Configurer (Config > Configure Ports, Audio, Mode Control, Other). Make sure the Hardware tab is selected (this is the tab the Configurer starts up in by default).

In what follows, it is assumed that you already have radio control, CW keying and PTT control configured and working, and what you are trying to do is add in the capability for digital modes.

In many cases, especially if you are planning to use AFSK, you will already have PTT control configured from the Logger. If the same method you use in other modes is acceptable for digital modes, you don't need to do anything special about PTT for digital modes. If you are planning to use FSK for RTTY, you will be setting up a serial port for FSK keying from within the digital engine, and you can use that same serial port for PTT control in RTTY. If you are using VOX (or an external VOX such as a SignaLink), you do not need to configure PTT control in the Configurer.

All that being said, there are two cases where you need to do something about PTT control for digital modes in the Configurer. The first is if you plan to use MMVARI as your digital engine, and you want to use a control line from a serial port for PTT control. In that case, you must designate that serial port in the Configurer, check the Digital check box for that port, set the appropriate control line (DTR or RTS) for PTT, and set the DigWndNr to 1 for most cases, or 2 for DI-2 in SO2R/SO2V. The second case occurs if you are using a single serial port interface for both CW/PTT keying in CW/SSB, and also for FSK keying in RTTY. In that case you must check both the Digital and CW/Other check boxes for that port, configure DTR and RTS for CW/SSB, and set the DigWndNr (1 for SO1V or for DI-1 in SO2R/SO2V, 2 for DI-2 in SO2R/SO2V).

Next, you need to select the Digital Modes tab in the Configurer. First, set the TU Type to Soundcard (unless you happen to be using a hardware TU/TNC). If your main digital engine is MMTTY or 2Tone, then under DI-1 MMTTY Setup, select AFSK or FSK as appropriate for your setup and set the MMTTY Path to point to the copy of MMTTY.exe or 2Tone.exe you will be using with the Logger. If you will be doing SO2V or SO2R, repeat for a separate copy of the digital engine under DI-2 MMTTY Setup. If you will be using Fldigi, there are separate places to enter the paths to Fldigi.exe. For all of these, it is recommended that you do not try typing in the path directly. Instead, click on the Select button, which opens a standard Windows file Open dialog window, and then navigate till you find the desired .exe file and select it.

Once the paths to the digital engines are set up, select the Mode Control tab in the Configurer. On the right side, beside RTTY, set the Mode sent to radio - this should be RTTY if you are using FSK, but if you are using AFSK, it should be either AFSK (if your radio offers a separate mode for AFSK RTTY), LSB (for most radios with MMTTY or 2Tone), or USB (for Fldigi).

This completes the basic steps in the N1MM Logger+ Configurer. For more detailed explanation of the various options available, see the section below titled Setting Up the Configurer.

Back in the main Entry window, if you have not already done so, choose a contest type that allows digital modes (i.e. not a CW- or SSB-only contest), and set the Mode Category to one that includes RTTY or Digital (don't choose MIXED - that's for CW+SSB only; choose MIXED+DIG instead). Type RTTY into the call sign box and press Enter. This should open the Digital Interface window. If it does not, use the Window > Digital Interface menu item to open the Digital Interface window (in SO2R/SO2V, each Entry window has its own Digital Interface window that opens from that Entry window's Window menu). If your preferred digital engine does not open (e.g. if you see the MMVARI window when you wanted MMTTY), then in the Digital Interface window use the Interface menu item to switch to the digital engine you want to use (use the MMTTY menu setting for both MMTTY and 2Tone).

Select the Setup > Settings menu item in the Digital Interface window. Under Preferred RTTY Interface, select your preferred digital engine. Under Alignment Frequency, enter your preferred Mark audio frequency (e.g. 2125 Hz), after making sure that this preferred Mark frequency is consistent with the default frequency in your digital program (e.g. the HAM setting in MMTTY) and the default frequency in your radio. If you are using MMTTY, then under MMTTY Window Settings, select either Normal or Control Menus, in order to have easy access to the MMTTY setup window. When you have completed the setup in the Digital Setup window, click on Save Configuration.

There are a host of other options in the Digital Interface and Digital Setup windows. A complete reference manual for the menu options in the DI window is in the section below titled The Digital Interface - Menu Selections, and a reference manual for the Digital Setup window is in the section titled The Digital Interface - Setup. For a description of how to use the DI window, see the section titled The Digital Interface - Window.

You're not done yet. Now you have to complete the configuration inside the digital engine itself. This is especially important for FSK, since the configuration of the FSK port is carried out inside the digital engine, not in the N1MM Logger+ program. There are separate chapters in the manual for MMTTY, MMVARI, Fldigi, and TNCs/TUs. There are too many possibilities to cover here, so consult the chapter(s) appropriate to your situation and complete the setup as described there.

2. Setup Overview

Setting up an interface requires configuring the Logger for the selected interface. Configuring has to be done within N1MM Logger+ in a few places, including the Configurer as well as the Digital Interface window. You will also have to perform some configuration from within your chosen digital engine.

You do not need to download or install any additional files or programs to use MMVARI or a TU/TNC. However, before you can use MMTTY, you will have to download and install it. The same applies to 2Tone and Fldigi. This process is described in the next two sub-sections.

A brief note about hardware connections. If you are using a TNC or TU, the hardware connections will be explained in the documentation for the TNC. If you are doing sound card digital modes (including RTTY) using MMTTY, 2Tone, MMVARI or Fldigi, your hardware connections will depend on the radio, the sound card and the interface (if any) in use. It is impossible to cover all of the permutations and combinations in detail, but the following general comments apply.

First, unless the sound card (or "codec") is built in to your radio, you must have some means of connecting the radio's audio output to the sound card's input. The ideal connection would be from a fixed-level ("line out") output on the radio to a "line in" input on the sound card. If your radio has one receiver, this will probably use the left channel of the sound card; with dual receivers, the second receiver may use the right channel (of course, this requires a stereo sound card; some external sound cards, such as the SignaLink, are mono and will not support dual-channel receive; also, in Windows Vista, 7, 8 and 10 the Windows configuration for the sound card device must be set to two channels for the sound card to work in stereo). If your sound card does not have a line level input, you may need to use a microphone input, and in this case you may need an attenuator to reduce the line level output from the radio to the lower level needed for the microphone level input on the sound card.

To transmit, there must be some means to convey modulation from the computer to the radio. For FSK RTTY, this is an on-off keying signal, which is normally generated by a serial port connected to the radio's FSK keying input through a simple keying circuit. This serial port cannot be the same port that is used for radio control or for a Winkeyer or other serial device. If it is a USB-to-serial adapter, you will probably need to use MMTTY's EXTFSK or EXTFSK64 plugin. If you are using MMVARI for RTTY using FSK keying, select the appropriate plugin (FSK8250 for true serial ports, EXTFSK or EXTFSK64 for USB-to-serial adapters) in the Configurer under the Digital Modes tab.

For AFSK RTTY and for all other sound card digital modes (e.g. PSK31), with the exception of radios with an internal codec, there must be a connection from the sound card's output ("line out", or speaker or headphone output) to the radio's audio input. If the only audio input on the radio is a microphone input, you may need attenuation to reduce the level to avoid overdriving the transmitter.

You also need some means to control TX/RX switching (PTT). The most common method is to use hardware PTT control from a serial or parallel port via a simple keying circuit. Hardware PTT can be controlled either from the digital "engine" (MMTTY, MMVARI, 2Tone or Fldigi), or from N1MM Logger+ itself. N1MM Logger+ can use the same port for PTT control that it uses for radio control, but if you want to use serial port PTT from the digital engine instead, you must use a different port from the one that is used by the Logger for radio control. If you have a serial port set up for FSK keying, you can use a control line (RTS or DTR) on this same port for PTT control from the digital engine. If PTT is controlled from a digital engine rather than from the Logger, and you use that same serial port from the Logger in other modes (e.g. for CW keying), then you must check the Digital box for that serial port in the Configurer and make sure to indicate the appropriate Dig Wnd Nr (1 for DI1, 2 for DI2).

If you do not have a separate serial or parallel port available for PTT in digital modes, you can control PTT directly from the Logger. For example, if your radio control interface supports PTT using RTS or DTR on the radio control serial port, you can configure the Logger to use this method. If no method of hardware PTT control is available and if your radio supports PTT via radio command, you can use software PTT control from the Logger. Warning: Using both software and hardware PTT control at the same time can cause problems; do not use both methods in parallel.

As an alternative to hardware and software PTT control, you may be able to use VOX. This does not work with all radios, it cannot be used for FSK RTTY, and setting of audio levels and VOX triggering levels can be tricky, but some users have found this to be the simplest method of PTT control, since it does not require any additional hardware connections. Some external interfaces (e.g. SignaLink) perform a VOX function external to the radio, i.e. they generate a hardware PTT signal based on the presence of an audio signal without any connection to a serial port on the computer. If you are using such an interface, or VOX within the radio, you do not configure any PTT in the Logger or in the digital engine, as PTT control in these cases is external to the software.

If your radio has a built-in codec connected to the computer via a USB cable, you can configure the digital engine (sound card software) to use this codec in place of a sound card in the computer. The only difference between this and a conventional computer sound card installation is that the audio cables between the sound card and the radio are replaced by a USB cable between the computer and the radio. This USB cable may also service one or more USB-to-serial adapters inside the radio, for CAT control and possibly also for CW/PTT/FSK keying. Despite the fact that the codec and the serial adapter share the same physical cable, there is no logical connection between the two devices. If the virtual serial port created by the USB device driver is used for CAT control, it must be configured in the Logger, while the codec using the same USB cable is configured separately in the digital engine. If there is a virtual serial port used for "hardware" keying of PTT/CW/FSK, it must be configured in the same way as it would have been if it were a real serial port in the computer, e.g. in the Logger if it is used for CW keying, or in the digital engine if it is used for FSK keying.

Sound Card Level Settings

On receive, to make best use of the sound card's available dynamic range you would adjust the sound card's recording level control (and/or any other level controls or attenuators there might be in the receive audio path) so as to just barely avoid overdriving or saturation on the loudest signals. In MMTTY, an input signal that is too strong will cause the word "Overflow" to be displayed in the MMTTY spectrum window. The recording sound level should be adjusted to be just below the point where this word is displayed on the strongest signals.

On transmit (AFSK RTTY and other digital modes), it is important to avoid setting levels high enough to cause either appreciable audio harmonics or intermodulation distortion (IMD). The goal is to come up with a combination of settings in the sound card playback mixer and the radio's mic gain or line in gain setting that results in audio signals just below the point where fast-acting ALC is triggered. On many radios, this is the point where the ALC meter just starts to move (special case: this is not true of the Elecraft K3/K3S and KX3, where the proper audio settings are those that result in 4-5 bars displaying on the radio's ALC meter). With many sound cards, you should try to avoid setting the playback gain in the sound card all the way to the maximum; the sound card's output may not be very linear at the maximum setting. A setting somewhere in the upper middle part of the range is ideal, provided it produces enough signal for the radio. Gain distribution is also important. A very low level out of the sound card followed by large amounts of amplification in the radio's audio circuits will risk picking up hum and noise and adding them to your transmitted signal.

Sound card level adjustment should always be done using an audio frequency in the middle of the radio's filter bandpass. This is where both received and transmitted signals will be strongest. If level adjustment is performed using an audio frequency near the edge of the bandpass, the resulting level settings will be too high. During operation, if a desired signal is found near the edge of the bandpass, the Logger's Align button can be used to retune the radio so the desired signal is placed at the optimal point in the bandpass.

If you are using the Windows default sound card for generating transmitted signals in digital modes, make sure to disable all Windows sounds. Most amateurs who spend significant time in digital modes prefer to use a separate sound card. It does not need to be a high-end audiophile sound card; digital modes like RTTY do not require anything extraordinary in the way of a sound card. The parameter of most interest is the noise floor; the noise level in a second sound card may be lower than that in the sound card on the computer's motherboard, and this may help improve reception of digital signals.

If you are using a USB audio codec inside the radio as your sound card, make sure that it has not been set to be the Windows default sound card. In this situation, the Windows default should still be set to be the sound card in the computer. There are two reasons for this. One is that the radio's sound card will disappear from Windows when the radio is turned off, which makes it unsuitable as the default device. A more important reason from an amateur radio point of view is that if it is the Windows default, it will cause Windows sounds to be transmitted by the radio instead of playing them on the computer's speaker - not a good idea! Also, setting one of the inputs or outputs on a sound card to be the Windows default causes Windows to disable the other inputs or outputs on that sound card, which can lead to inability to select the desired input or output. For all of these reasons, if at all possible you should avoid letting Windows select as its default the sound card or codec you are using for digital modes.

Sound Card Sampling Rate

If you are using a sound card or codec, you may also need to pay some attention to the sound card sampling rate. This will be the case either if you are using Windows Vista, 7, 8 or 10, or with any version of Windows when you are using 2Tone, regardless of whether that is as your main digital engine or as an auxiliary decoder in one of the additional RX windows.

In Windows XP, application software programs (such as the digital engines in the Logger) are able to set the sound card sampling rate directly. If you use two or more engines in parallel with the same card, you need to ensure that all of the engines are using the same sampling rate. The 2Tone engine does not offer a choice of sampling rates; it always uses 12000 Hz. Since the sampling rate for all digital engines connected to the same sound card should be the same, this means that if you are using 2Tone and MMTTY in parallel, you should set MMTTY's sampling rate to 12000 Hz as well.

In Windows Vista, 7, 8 and 10, application software cannot set the sampling rate directly. The hardware sampling rate is set in the Windows Control Panel. Many sound card drivers will offer a choice between DVD (48000 Hz) and CD (44100 Hz) sampling rates. Software that uses the sound card should have its sampling rate adjusted to an exact integer sub-multiple of the hardware rate. If you are using 2Tone, since the software sampling rate is fixed at 12000 Hz, you would set the sound card to an exact multiple of 12000 Hz (such as 48000 Hz, the standard DVD sampling rate). If you are not using 2Tone, you can choose either hardware sampling rate, but whichever one you choose in the Control Panel, you should choose corresponding rates in the sound card applications (12000 Hz corresponding with 48000 Hz, or 11025 Hz corresponding with 44100 Hz).

If the hardware and software sampling rates are incompatible (e.g. software set to 11025 Hz using a sound card set to 48000 Hz, or two different software engines, one set to 12000 Hz and the other set to 11025 Hz), you may find that the software calculates audio frequencies incorrectly. For example, tones that the software generates using 2125/2295 Hz settings may actually be at lower pitches with a smaller shift, and if you are using narrow filters in the radio, the filter bandpass may appear at the wrong place in the waterfall. In AFSK, logged and spotted frequencies may also be incorrect.

In Windows Vista, 7, 8 and 10, to set the sampling rate in the sound card, open the Control Panel and find the area for Sound settings. You can also find this by right-clicking on the little speaker icon at the right end of the Task Bar and selecting "Recording devices". Under the Recording tab in the Sound settings window, select the sound card device and input that you are using for receive audio in digital modes and click on the Properties button. Select the Advanced tab, and set the sample rate and bit depth (16 bits is good) to the desired values (e.g. 16 bit, 48000 Hz). If you are using AFSK, do the same under the Playback tab for the sound card device and output that you are using for transmit audio.

To set the sampling rate in MMTTY, open the MMTTY Setup window, select the Misc tab, and in the lower left part of the window set the Clock to the desired setting (e.g. 12000 Hz). To set the sampling rate in MMVARI, open the Digital Setup Window, select the MMVARI Setup tab and the Soundcard Setup tab under that, and set the Clock Adjustment RX Freq to the desired setting (e.g. 12000 Hz). In Fldigi, the sample rate is found in the Fldigi configuration under the Audio/Settings tab - there are separate sample rate settings for Capture (receive) and Playback (transmit). Remember to save the configuration in Fldigi after you make any changes.

2.1. Downloading and Installing MMTTY

MMTTY is not installed as part of the installation of N1MM Logger+. It must be downloaded and installed separately. It is possible to use N1MM Logger+ in RTTY without using MMTTY (e.g. by only using an external TNC, or AFSK RTTY from MMVARI). If you intend never to use MMTTY, you can skip the rest of this section. However, most RTTY users will probably want to have the ability to use MMTTY, at least as an option. In particular, if you would like to make use of the additional RX windows for "diversity decode", you will most likely need to install MMTTY (unless you have several TUs/TNCs you can use for the purpose).

If you do not have a copy of MMTTY, then before continuing with the digital setup it is recommended that you download a copy of the MMTTY installer from the MM HamSoft website. You can find a copy of the full installer for the current version of MMTTY at that website. This file is a self-extracting executable, similar to the N1MM Logger+ installer. Download the file to a temporary folder and then execute it. It is recommended that you install MMTTY in its own program folder and not in the N1MM Logger program folder. By default, the installer will install MMTTY to C:\Program Files\MMTTY\, but in Windows Vista, 7, 8 or 10 you should not install MMTTY in the Program Files or Program Files(x86) path, because that will prevent MMTTY from saving its settings.

Note for users of Windows Vista and Windows 7, 8 and 10: User Account Control (UAC) in these versions of Windows prevents user programs from writing configuration information into the Program Files path. Even if programs are run with Administrator privileges, UAC may interfere with the ability to use separate configuration files for separate copies of the same program. Therefore, it is suggested that the folder for MMTTY, as well as any folders for extra copies used in the second DI window and the four additional RX windows, should not be in the Program Files path. It is suggested that you create a new folder outside the Program Files path, such as C:\Ham Radio\MMTTY, and then place any individual sub-folders for separate copies of MMTTY within that folder. Another option would be to create a DigitalEngines subfolder inside the N1MM Logger+ user files folder (the one inside your My Documents folder), and then create various subfolders within DigitalEngines for copies of MMTTY, 2Tone and Fldigi that you want to use with various DI windows and RX-only windows, as illustrated lower down in this section.

If you wish to use FSK keying from MMTTY through a USB-to-serial adapter or via an LPT port, you will also need to download a copy of EXTFSK (from the MM HamSoft website) or EXTFSK64 (from http://www.qsl.net/ja7ude/extfsk/indexe.html) and install the appropriate files in each folder or sub-folder from which you intend to use MMTTY to transmit FSK using a USB adapter or LPT port.

If you already have a copy of MMTTY installed on your computer, you can use that copy from N1MM Logger+. However, if you also use MMTTY stand-alone, it is possible that you may want (or need) to have a different setup for stand-alone use than with N1MM Logger+ (e.g. if you use the radio control port from within MMTTY stand-alone; this is not possible when MMTTY is used with the Logger). If you need a different setup with the Logger than the one you use stand-alone, then you should create a separate folder for each copy (for example, you can create a sub-folder inside either the N1MM Logger+ user files folder or the MMTTY program folder for the second copy of MMTTY). You need to copy only the MMTTY.exe and UserProfile.ini files from the main MMTTY folder into the additional folder (plus the extfsk.dll and/or extfsk64.fsk file(s) if you are using EXTFSK and/or EXTFSK64 for FSK keying). You can also copy MMTTY.ini, but if you don't, MMTTY will create a new copy of MMTTY.ini when it is run.

If you plan to use two copies of MMTTY in SO2V or SO2R mode, one for each received audio stream, you will need to create two copies in separate folders with different configurations. In SO2V, one of these copies can be configured to use the left channel and the other copy to use the right channel of a single stereo sound card. In SO2R, you can either use a stereo sound card as in SO2V, or you can use two separate sound cards, one for each radio.

If you want to use MMTTY for diversity decoding in additional RX windows, you will need to create another separate sub-folder for each additional RX window. For example, you can create sub-folders called DI1, DI2, DI1RX1, DI1RX2, DI2RX1, DI2RX2, etc. so that you can run several copies of MMTTY simultaneously; one for each main DI window, plus up to 4 additional RX windows for each DI window. Into each of these windows, you need only copy the MMTTY.exe, MMTTY.ini and UserPara.ini files from the main MMTTY program folder created when you first installed it. Each copy of MMTTY must then be configured to use the appropriate sound card and channel. The "Additional RX" copies usually use the same sound card and channel as the parent copy in the main DI window, but they can be configured to use different decoding algorithms or profiles to give you "diversity decoding", i.e. several different decoding methods used on the same receive audio.

A sample folder structure might be as follows (each of the bottom-level folders contains a copy of the .exe file and .ini or other configuration files for that particular instance of the program).

Digital UserDirectoryOrganization Example

Once MMTTY has been downloaded and installed, you can proceed to use the Configurer to set up N1MM Logger+ to use it - see section 2.5 below. For instructions on setting up additional RX windows, see section 2.6 below.

2.2. Downloading and Installing 2Tone

2Tone is not installed as part of the installation of N1MM Logger+. It must be downloaded and installed separately. You cannot run 2Tone stand-alone. Most people who use 2Tone have already downloaded and configured MMTTY, and simply use 2Tone as a drop-in replacement for the MMTTY engine. If you are using 2Tone in the main DI1 or DI2 window, change the MMTTY path in the Configurer under the Digital Modes tab to point to a copy of 2Tone.exe . If you are using 2Tone in an additional RX window, configure that window for MMTTY but change the path in the setup to point to that window's copy of 2Tone.exe . Note that if you are using 2Tone in more than one DI or RX window, every window you use it in must point to a different copy of 2Tone.exe, i.e. a copy that has been unzipped into a different folder.

You can find the latest version of 2Tone in the G3YYD folder in the Files area of the N1MMLogger-Digital user group at Yahoo. Download the zip file containing the latest version and unzip its contents into the folder(s) or sub-folder(s) you wish to run it from (a separate folder for each window you wish to use it in). The first time you install 2Tone in a folder, copy the entire contents of the zip file into the folder; when installing updated versions, you do not need to extract the ini files from the zip file if you wish to keep using the configuration information from the previous version.

The configuration steps in N1MM Logger+ are the same for 2Tone as for MMTTY. To configure N1MM Logger to use 2Tone as the decoder for one of the main Digital Interface windows (DI1 or DI2), follow the instructions in section 2.5 below, taking care to ensure that the DI Path points to 2Tone.exe instead of MMTTY.exe . If you wish to configure N1MM Logger to use 2Tone as the decoder in one of the additional RX windows, use the Setup > Add. RX Windows > Open Add. RX Window (4 Avail.) menu item to open the additional RX window. The first time that window opens, it will display a setup window - see section 2.6 below. Set the Window Type to MMTTY, but then in the Path box change the path to point to the appropriate copy of 2Tone.exe instead of MMTTY.exe . Click on Save.

Initially the additional RX window will be in a separate window from the main DI window. If you wish to embed the additional RX window into the DI window so that text decoded in the main and additional RX windows will appear one above the other within the DI window, select the Setup > Add. RX Windows > Enable Attached RX Windows menu item from the DI window's menu bar. The separate window will be minimized to the task bar; if you want to close the additional RX window, or if you need to change settings in its Setup window, you can open it from the task bar.

For detailed instructions on configuration settings within 2Tone itself, see the 2Tone.pdf file in the downloaded 2Tone zip file.

2.3. Downloading and Installing Fldigi

FLdigi is not installed as part of the installation of N1MM Logger+. It must be downloaded and installed separately. It is possible to use N1MM Logger+ in RTTY and PSK contests without using fldigi. Fldigi supports a wide range of other digital modes, but most of these are rarely used for contesting. Fldigi can also be used as a receive-only CW decoder. If you want to use fldigi as a CW decoder, you need to download and install it. If you intend never to use fldigi, you can skip the rest of this section.

If you do not have a copy of fldigi and you wish to be able to use it, then before continuing with the digital setup you should download a copy of the Fldigi installer from the W1HKJ website at http://www.w1hkj.com/ . You can find a copy of the full installer for the current version of fldigi at that website. This file is a self-extracting executable, similar to the N1MM Logger+ installer. Download the file to a temporary folder and then execute it. It is recommended that you install fldigi in its own program folder and not in the N1MM Logger program folder. By default, the installer will install fldigi to C:\Program Files\Fldigi-x.xx.xx\, where x.xx.xx is the Fldigi version number. This is OK for fldigi when it is run stand-alone, but in Windows Vista, 7, 8 and 10, a copy of fldigi that is used from within N1MM Logger+ cannot be placed in the Program Files or Program Files(x86) path. Therefore it is recommended that you create a separate folder for fldigi somewhere outside the Program Files paths (for example, in a special folder within the N1MM Logger+ user files folder in your My Documents area), make a copy of fldigi.exe from the original fldigi program folder and place the copy in the new folder. You do not need to copy any of the other files; that copy of fldigi will create new configuration files the first time it is run from the Logger.

Note that older versions of fldigi only use the left channel on input; for that reason, in most SO2V installations these older versions of fldigi can only be used from Entry Window 1. Starting with Fldigi version 3.22.06, fldigi is now capable of using either sound card channel for input. In any copy of fldigi that you want to use with the right channel of the sound card, use the Configure > Sound Card menu item in the fldigi window to open the fldigi configuration window. Select the Right channel tab, and near the bottom under Receive Usage, check the Reverse Left/Right channels check box to switch fldigi to use the right channel on RX. Click on Save to save the configuration change, and then close the configuration window.

Newer versions of fldigi may default to requiring confirmation from the user before you shut them down. If that shutdown is initiated by shutting down N1MM Logger+, instead of by shutting down the DI windows and engines first, this can result in fldigi continuing to run after the Logger has shut down. This will cause problems the next time you start up the Logger. To prevent this from happening, you need to make a change in the fldigi configuration file. In each folder that fldigi is run from, find the file called fldigi_def.xml (Note: this file is created the first time fldigi is run from this location, i.e. it will not exist until after you have run that copy of fldigi at least once). Right-click on the file name, select Open with... and then select Notepad or Wordpad as the program to open the file with. Look for a line that reads <CONFIRMEXIT>0</CONFIRMEXIT> or <CONFIRMEXIT>1</CONFIRMEXIT>. If you see a 1 between the two keywords, change it to a 0 and save the file. Repeat this for every copy of fldigi you use from within N1MM Logger+ (DI1, DI2, CW Reader 1 and/or CW Reader 2).

2.4. Downloading and Installing GRITTY

GRITTY window

GRITTY is an innovative receive-only RTTY decoder by Alex VE3NEA (the author of DX Atlas, CW Skimmer and several other amateur radio programs). Its decoding algorithm is quite different from the algorithms used by other RTTY decoders. It can be used as one of the additional RX windows in N1MM Logger+ (see section 1.6 below) to provide additional information about received call signs and exchanges which can sometimes enable you to copy a signal even when the decoder in the main Digital Interface window is unable to decode the information successfully.

GRITTY is not installed as part of the installation of N1MM Logger+. It must be downloaded and installed separately. A zip file containing the GRITTY installer can be downloaded from http://www.dxatlas.com/Download.asp . The installer is a self-extracting executable, similar to the N1MM Logger+ installer. Download the zip file to a temporary folder and then unzip it and execute the setup program. It is recommended that you install GRITTY in its own program folder. By default this will be in the Program Files path. Unlike MMTTY, 2Tone and Fldigi, when GRITTY is used from N1MM Logger+ it can be run from the program files path. GRITTY's configuration information is stored outside the program files path, and the interface with N1MM Logger+ creates a specially-named ini file to allow different configuration files to be used from the Logger as compared with GRITTY run stand-alone. The name of this ini file indicates which DI window (1 for SO1V, 1 or 2 for SO2R or SO2V) and which additional RX window number (1 through 4) the configuration applies to (for example, Config13.ini contains the GRITTY setup for additional RX window no. 3 from the DI-1 window). You can find the location of these configuration files from the GRITTY Help > Data Folder menu item.

GRITTY's decoding method is based on Bayesian statistics. It performs an analysis on the received characters bit-by-bit and develops a probabilistic model, comparing incoming text to known-good call signs, common keywords and previously-decoded text in order to predict the most likely correct interpretation even in the presence of errors. In some situations, it can pick out call signs from error-filled text that would appear to be garble to other decoders. Of course, it must be used with care; while it can predict the most probable interpretation of a received string of bits and noise, this interpretation is not guaranteed to be correct. For example, it can sometimes be tricked into decoding apparent call signs from pure band noise.

GRITTY performs best when the incoming audio is not passed through a narrow filter, e.g. by using a wide SSB filter instead of narrow CW-style filters. When used with narrow filters, GRITTY can sometimes refuse to decode anything even when other decoders are succeeding. When this happens, one tactic that may work is to temporarily widen the IF filter in your rig to pass a broader range of audio frequencies. In the presence of heavy QRM such as strong nearby signals, it may be necessary to use narrow filtering in order to prevent AGC pumping from adversely affecting the other decoders using more traditional methods. Fortunately, once GRITTY has started to decode using a wider filter, the IF filter can often be narrowed back down and GRITTY will continue to decode now that it has some previously-decoded text to work with.

You can find more information on setting up and using GRITTY, and on how it works, in the GRITTY Help file.

2.5. Setting Up the Configurer

There are three tabs in the Configurer that need to be set up when configuring N1MM Logger for digital modes. The first is the Hardware tab, where serial ports used for digital modes are set up. If you are using VOX or an interface that performs the VOX function externally (e.g. SignaLink), you do not need to configure a port for digital modes under this tab.

Configurer Hardware DigitalExample

  • The Digital box in the main Configurer window indicates to the Logger that this port is used for digital mode control in certain special cases, as follows:
    • Use this to indicate a port that is used for an external TNC - only the Digital check box is checked for the port
    • Use it to indicate a port that is used for PTT control from MMVARI
    • It is possible to time-share a port (sequentially, not simultaneously) for both serial port CW keying (e.g. on DTR) and for PTT and FSK using MMTTY or 2Tone for RTTY (e.g. on RTS and TxD). If you are time-sharing a port like this, check both Digital and CW/Other for that port. When the DI window is closed, the settings in the DTR and RTS boxes will determine how the port is used; whenever the DI window is open, it will be the settings in the digital engine (e.g. MMTTY or 2Tone) that determine how the port is used. The figure above shows COM2 being used by the Logger for CW keying and by MMTTY for FSK keying
    • If you use a serial port with MMTTY or 2Tone for FSK and/or PTT keying and you do not use that serial port in other modes or in MMVARI, there is no need to configure that port in the Configurer; in this case, all of the setup is done within MMTTY


Configurer SetDialog SharedCwDigitalPort

If you have checked the Digital check box, click on the Set button for the same port and select the radio number and DI window number to be associated with the port. The figure above demonstrates an example where COM2 is being used by the Logger for CW keying from DTR, and by MMTTY for FSK keying from VFO B (SO2V).

  • The Radio Nr box indicates which radio this digital interface is for in SO2R mode; in SO2V and SO1V, Radio Nr is always = 1
  • The Dig Wnd Nr indicates whether this port is used for DI1 or DI2. This applies to SO2V and SO2R; in SO1V, Dig Wnd Nr is always = 1
    • You must choose a Dig Wnd Nr for each port that has the Digital box checked; otherwise the program will not assign the port to a DI window!


The next tab to be set up is the Digital Modes tab.

Configurer DigitalModes

  • Digital Interface 1/2 (left part of window)
    • TU Type:
      • None - if you do not plan to use the DI1 or DI2 digital interface
      • Soundcard - for any of the sound card digital engines (MMVARI, MMTTY, 2Tone or Fldigi)
      • Other - use this setting for most terminal units or TNCs (e.g. for a PK-232 or KAM TNC)
      • Dxp38 - use this setting for the HAL DXP-38 terminal unit
    • Speed, Parity, Data Bits, Stop Bits, Flow:
      • These are only used when the TU Type is Other or Dxp38
      • Set these parameters appropriately for the TNC or TU (Example settings: 9600, 8, N, 1, Xon-Xoff)

  • DI-1/2 MMTTY Setup (upper right part of window - this area is also used for 2Tone setup)
    • MMTTY Mode: Select AFSK or FSK
    • MMTTY Path: Select path to MMTTY.EXE or 2Tone.exe, including the name of the executable file (i.e. not just the path to the folder). Using the Select button for this purpose will open a File Open dialog that will allow you to navigate through the file system to find the MMTTY.exe or 2Tone.exe file, which avoids the possibility of a typing error when entering the path
      • The paths for the two DI windows are not the same, since each DI window runs its own copy of MMTTY or 2Tone

 SO2V/SO2R in MMTTY

You can use MMTTY with both receivers in a two-receiver setup with a single stereo sound card. You will need to install two copies of MMTTY in two separate program folders in order to allow one copy to be configured to use the left channel of the sound card and the other copy to be configured to use the right channel of the sound card.

 SO2V/SO2R Shut Down Issue

When two copies of MMTTY are used in DI1 and DI2 with a different COM port for each copy for PSK/PTT keying, you may need to close the two DI windows separately before shutting down N1MM Logger. If both DI windows are open at the time N1MM Logger is shut down, the COM port assignments in the two copies may get confused due to a glitch in MMTTY, which means the port assignments may be wrong the next time the Logger is started up.

  • DI-1/2 Fldigi Setup (midle right part of window)
    • Fldigi Path: Select path to fldigi.exe (complete path, including the name of the executable file). Use the Select button to simplify the task of finding the path and typing it in correctly
      • The paths for the two DI windows will normally be different in order to allow for different configurations (e.g. different audio sources) in the two copies

 SO2V/SO2R in Fldigi

Starting with FLdigi version 3.22.06, you can use Fldigi with both receivers in a two-receiver setup with a single stereo sound card. You will need to install two copies of Fldigi in two separate program folders in order to allow one copy to be configured to use the left channel of the sound card and the other copy to be configured to use the right channel of the sound card on receive.

  • DI-1/2 MMVARI Setup (bottom part of window)
    • MMVARI RTTY Mode: Select AFSK or FSK
    • FSKPort: (FSK only)
      • 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 low speeds (this does not include most USB-to-serial adapters, but it does include some commercial interfaces designed to support FSK RTTY as well as some multi-port USB-to-serial adapters)
        • When MMVARI is opened for FSK RTTY, a small window labelled MMVARIFSK1 1.04 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
        • FSK8250 supports all of the RTTY speeds supported by MMVARI and the selected COM port or device
      • 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.06 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
        • The only RTTY speed supported by EXTFSK is 45.45 baud
      • On high-performance multi-core systems only, you may choose EXTFSK64 instead of EXTFSK. EXTFSK64 uses a more accurate timing mechanism than EXTFSK, but this mechanism uses significant CPU resources. EXTFSK64 is not appropriate for use on XP based systems or hardware running older dual-core Intel/AMD CPUs or Atom based CPUs. On systems that are capable of supporting it, EXTFSK64 can key FSK from LPT ports as well as USB-to-serial adapters. See http://www.qsl.net/ja7ude/extfsk/indexe.html for more detailed information on EXTFSK64
        • When MMVARI is opened for FSK RTTY, a small window labelled EXTFSK 2.0 will open, or appear on the Windows Task bar. In this window you select the COM or LPT 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
        • EXTFSK64 can key FSK at speeds other than 45.45 baud (e.g. 75 baud)

 SO2V/SO2R in MMVARI

You can use MMVARI with both receivers in a two-receiver setup with a single stereo sound card. In the DI Window's Digital Setup dialog box under the MMVARI Setup tab, simply configure the DI1 SoundCard to use the left channel and the DI2 SoundCard to use the right channel.


The third tab to be set up is the Mode Control tab, which determines what mode the radio will be set to use in RTTY and PSK.

Configurer ModeControl DigitalExample

This example is for a radio or radios with separate modes for FSK, AFSK and PSK (e.g. Elecraft K3 using FSK D, AFSK A and DATA A respectively). This particular setup uses AFSK from DI-1 (radio 1) and FSK from DI-2 (radio 2). The appropriate choices in the list boxes under Mode sent to radio will depend on the particular radio type (see Supported radios). For FSK RTTY, the correct choice will normally be RTTY. For AFSK RTTY, depending on the radio the appropriate choice might be AFSK or LSB/USB (or if you are using Fldigi and your radio has an upper sideband digital audio mode, perhaps PSK). For PSK31 and other sound card modes, the radio mode would be PSK (if available), AFSK-R (on some radios) or USB on most radios. For more information, see the Configurer page under the Config >Mode Control tab.

2.6. Additional RX Windows for RTTY

N1MM Logger+ supports up to four additional RTTY receive-only windows for each DI window. The purpose of these windows is to allow simultaneous use of more than one decoding algorithm on the same audio input. While it is possible, by using wide bandwidth filters, to use the additional windows to decode different signals from the one in the main DI windows, the normal use of the additional windows is to decode the same signal as the one in the main window, using a different decoding method to improve the overall ability to decode signals in difficult situations.

These receive-only windows may use additional copies of MMTTY or 2Tone, configured with different "profiles" (e.g. multipath, fluttered, different detection algorithms). Alternatively, they can be used with a copy of Fldigi or GRITTY, or with additional TNCs or TUs. You can use any of the transmit-capable digital interface engines in the main DI window (MMTTY, 2Tone, MMVARI, Fldigi or a TNC/TU). The additional RX windows may be configured to use either the same sound-card interface engine as the main DI window with a different profile, or a different interface engine, including GRITTY (read-only), but not including MMVARI (MMVARI can only be used in the main DI window).

The receive-only windows are invoked from the DI window's Setup > Add. RX Windows > Open Add. Rx Window (4 Avail.) menu item - the number in the menu item indicates how many of these windows are unused and still available. The first time one of these windows is opened, its Setup window will be displayed.

Digital AdditionalRxWindow SetupDialog

The setup information that must be entered includes the engine type (MMTTY, TNC, Dxp38, GRITTY or Fldigi - the MMTTY setting is also used for 2Tone), the path to the copy of MMTTY/2Tone, Fldigi or GRITTY for that window (if used), and/or the COM port information for a TNC (if used). Note that the path is the path to the .exe or executable file, not just the path to the directory in which it is located, i.e. when you use the Select button to find the engine, you must click on the actual executable file, then on the Open button in the File Open window. Alternatively, you can double-click on the executable file in the window.

After the setup information has been entered, click on the Save button to register the information. The additional RX window must be closed and re-opened (it may do this automatically), and then it will be available for use. If the engine type is MMTTY, Fldigi or GRITTY, a separate spectrum display window is also opened for the software digital engine, and can be used as a tuning indicator. Once the additional RX window is active, you can click on call signs and exchanges in the text window to pass them to the Entry window, the same as you can in the main DI window.

It is possible to embed or attach a copy of the additional RX windows directly into the RX window area in the main Digital Interface DI window, using the DI window's Setup > Add. RX Windows > Enable Attached RX Windows menu item. Each such attached window is denoted with its number (1, 2, 3 or 4), which is normally on a green background. If the number is clicked on with the mouse, the background color changes to yellow and the text in that window is frozen temporarily, similarly to the green/yellow bar on the left of the main receive window and the regular additional RX windows.

DigitalInterface MainWindow AttachedRXWindows

The separate additional RX window(s) is/are minimized to the task bar when the attached windows are enabled, but they may be restored from the task bar in order to be able to change setup parameters or to close the additional RX window. The icon(s) for the additional RX window(s) are grouped together with the icons for N1MM Logger+ on the task bar. If any of the additional RX windows use sound card software for decoding, the spectrum display windows for those digital engines may also be mimimized to icons on the task bar, but these will be separate from the Logger icons; note that the icon for the digital engine (MMTTY - black crossed ellipses on a white background; 2Tone - 2T; GRITTY - green crossed ellipses; or Fldigi - miniature waterfall) controls the display for the digital engine only, not the RX text window. In the screen shot below, as a result of hovering the mouse over the the N1MM Logger+ icons they have been expanded to thumbnail images above the task bar. The title of each thumbnail indicates which window will be restored if you click on that thumbnail.

Windows task bar with icons and thumbnails for digital windows

If Fldigi is used in parallel with other decoder engines, you need to be aware of the fact that fldigi assumes by default that the radio is in USB, whereas the other decoders assume LSB. If your radio is in LSB (this includes the FSK RTTY mode in amateur transceivers), you will need to tell fldigi to reverse its tones using the Rev button in the corresponding DI or additional RX window. This Rev button is not accessible from the attached RX-only windows; if you have enabled attached windows, you will need to restore the non-attached window to gain access to the Rev button for that copy of fldigi. Alternatively, if the radio is in USB (or FSK-R, etc.), fldigi will be on the correct sideband but you will need to reverse the tones in the other decoders using their respective reverse settings in the digital engine windows.

3. The Digital Interface - Window

The Digital Interface window, or DI window, is nearly the same regardless of which type of interface (MMTTY, MMVARI, FLDIGI or TNC) is being used. Its appearance (font sizes and foreground and background font colors) can be customized using the Skins, Colors and Fonts dialog window (main Entry window, Config > Manage Skins, Colors and Fonts).

DigitalInterface MainWindow Nonscrolling

The Digital Interface is opened from the Entry window's Window > Digital Interface menu item. If you are using two entry windows (SO2V/SO2R), each entry window has a separate DI window associated with it - DI1 with the VFO A/Radio 1 Entry window, and DI2 with the VFO B/Radio 2 Entry window. Each DI window is opened from its corresponding Entry window's menu bar. If the digital "engine" chosen in a Digital Interface window is sound card software (MMTTY, MMVARI, Fldigi or 2Tone), a separate window including a tuning display and various other digital engine-specific information will also be opened when the Digital Interface window is opened - see the section of the manual relevant to the specific digital engine that has been selected.

The DI window may be configured either in scrolling mode or in non-scrolling mode. Scrolling mode is the same as N1MM Logger Classic - new text is always added below previous text (i.e. usually on the bottom line of the RX window), and previously received lines scroll off the top of the window. Non-scrolling mode is new in N1MM Logger+ - previously received text does not move, but stays where it was first displayed until it is overwritten with new text. The line on which incoming text is being displayed is indicated with an underline, and this line moves steadily down the screen until it reaches the bottom, after which the top line in the window becomes the new incoming text line. The advantage of this mode is that received call signs and exchanges do not move, making them easier to click on.

The Digital Interface caption displays either the offset frequency (radio's dial frequency +/- audio frequency) or the radio's dial frequency, depending on what you have chosen in the Digital Setup.

  • TX - Indicator to show which window has transmit focus (useful when using two sessions like SO2R)
  • Letters/Figs - Shows the text under the mouse in reverse case (letters/figures switched)
  • MouseOver - Shows the text under the mouse; this is the text that would be selected by a mouse click


Top RX window - This is the receive window. Depending on the scrolling option you choose in the Digital Interface's Setup window, you can make this window either a scrolling window (old text scrolls off the top of the window as new lines are inserted at the bottom), or non-scrolling (new text appears on the active line, which is underlined; each time a new line starts, the text that was previously in the next line down is cleared and that line becomes the new current line; if the current line is at the bottom of the RX window, the line at the top of the window is cleared and becomes the current line where new text is entered). Some users find it easier to use a non-scrolling window where text does not move after it is entered (so incoming newlines do not cause text to scroll up just as you want to click on it). Other users find it easier to use a scrolling window so that new incoming text is always near the bottom of the window where they don't have to move the mouse very far to click on it. The Logger gives you the choice.

There are 2 ways of moving a callsign from the RX window into the callsign box in the Entry window. You can single click on a callsign and it will transfer over to the main logging window, or, whenever a callsign is detected in the RX window it will be sent to the callsign grab window for easy movement to the logging window by clicking the Grab button or using a function key with a {GRAB} macro in it. By clicking on the colored bar on the left you can pause input to the receive window to scroll back through the (last 2000 lines of) text using the scroll bars. When the window is paused the color of the bar will turn yellow. To turn input to the window back on click in the bar again and everything that was to be printed to the window will now enter the window. When the receive window is paused it is possible to select and copy text in the window.

Bottom TX window - This is the transmit window, a free form typing window. If you click on the TX button the cursor will be placed into this window and whatever is typed will be sent. The size is static and doesn't change size (2 lines). For TNC users: when not transmitting, anything typed in the TX Window will be sent to the TNC. Used to send TNC commands to change settings etc.

Callsign Textbox and Grab - When a callsign is encountered in one of the receive windows it will be placed in the Grab list in this textbox and when you press the Grab button it will transfer the callsign over to the main Entry window. The grab callsign window holds the last 10 callsigns seen in the RX window. The most current one is at the top and is highlighted. Dupe callsigns will not be shown in the grab window. The Sort Order in the grab window can be selected by right-clicking; you can choose either Last In First Out or First In First Out as the sort order

 Callsign not added to grab List

If the callsign in the callsign field in the Entry window is the same as the callsign in the received text, the call in the Entry window does not get placed into the grab call list. Clicking on a callsign in the RX window to move it into the Entry window will remove that callsign from the Grab list.


Message buttons - The Digital Interface window can display 0, 8, 16 or 24 extra message buttons for preprogrammed messages. Configuring these message buttons is done in the Digital Interface window under 'Setup | Settings' or by right clicking on them, which brings up the Digital setup dialog. The width of these message buttons dynamically adjusts in relation to the width of the interface window

  • Clr RX - Clear the receive window (also possible using the right click menu, unless the Rt Click = Enter option has been selected)
  • Align (MMTTY and Fldigi only) - This is used to move the signal that you are copying into the passband of your filters. Set the frequency in the setup area. For example, if your filters are centered on 2210 Hz, RTTY signals close to the 2125/2295 Hz pair will be copied well, but signals at higher or lower frequencies may not make it through the filters. If you click on a signal at a frequency in the waterfall that is not close to the nominal 2125/2295 pair, it may not decode very well. After clicking on the signal, if you click on the Align button your transceiver will be retuned to line the signal up on the configured frequency. This is essential in FSK where the transmit frequencies are fixed in the radio, and useful also in AFSK if you want to use narrow filters
    • Note that when you are using the MMVARI interface engine, the Align button appears on the MMVARI window instead of on the Digital Interface window
  • TX - Start the RTTY transmission, the transceiver is keyed. Will be colored Red when transmitting
  • RX - Stop the RTTY transmission - the transceiver changes back to receive. Will be colored Green when in receive
  • HAM (MMTTY only) - Restore the MMTTY frequency and shift settings to the HAM default
  • AFC (MMTTY only) - Can be used to turn MMTTY's AFC on or off (colored background means AFC is on)
  • Lock (Fldigi only) - Locks the transmit frequency at the current location. If you move the receive frequency, e.g. by clicking elsewhere in the waterfall, the transmit frequency does not change. Used for operating split
  • Rev (MMTTY and Fldigi only) - In sideband-sensitive modes like RTTY, reverses the tones (e.g. opposite sideband)
  • Grab - Transfer the selected callsign in the Callsign textbox to the callsign field on the main Logger Entry window. Once the callsign is filled, whatever you click on next will fill the next exchange box. When the Digital Interface is in transmit, calls are not added to the Grab window
  • CLR - Clear the Grab list

3.1. Receive Window Callsign Colors


When a callsign is recognized in the receive input stream the callsign will be colored according to the same color scheme that is used in the Bandmap Window and brought to the Grab window. Valid callsigns that are separated by spaces are always recognized, and optionally the Search routine can be used to search for known call signs from the Master.scp file in garbage text strings. When the search in garbage text is enabled and two calls are found in the same string, only the last one gets highlighted. Also, if the call sign being copied contains a shorter call sign that is in the Master.scp file, using the search in garbage feature may result in the shorter call sign being recognized instead of the longer one. The highlighted calls in text strings are clickable.

If the "Use Generic Routines" option is chosen under Callsign Validity and Highlight in the Digital Setup, anything that looks like a callsign will be highlighted with a color that indicates its multiplier status using the same colors as in the Bandmap and Entry window. If the "Use Master.scp File" option is chosen, callsigns that are not in the Master.scp file will be highlighted in yellow in addition, either by changing the background to yellow (if the multiplier color is in the foreground), or by changing the text color to yellow (if the multiplier color is in the background). Regardless of which option is chosen, anything that passes the check routines and looks like a callsign will be placed in the Grab window.

3.2. Mouse Assignments

  • Left mouse key clicking
    • Single clicking on a callsign grabs it and places it in the Callsign field on the Entry Window dialog
    • Single clicking on Exchange info etc. (not on a callsign) grabs it and places it in the Exchange field on the Entry Window dialog. If there are two or more exchange fields, as in some contests, you must take care to ensure that the keyboard cursor is in the exchange box corresponding to the element you are clicking on; if you click on an exchange element while the cursor is in the wrong box, the element will be transferred to the wrong place, and if there was something else there, it will be overwritten
      • Note: The callsign field must be filled first! If there is nothing in the callsign field, single clicking on exchange info will not do anything
    • Double clicking on a callsign grabs it and overrides the current information in the Callsign field on the Entry Window dialog
    • Ctrl+Single clicking - will force what ever you are clicking to be sent to the box containing the typing cursor in the Entry window (You may need to click first in the Entry window, or else use the space bar, to select the box where you want to place the new data)
    • Shift+Single clicking - will cause the moused over text to be Letter/Figs converted on the fly while sending to Entry Window (only in RTTY Mode)
    • Alt+Single clicking - if Digital Call Stacking is enabled, will transfer the call sign being clicked on to the Bandmap call stack (see Single Operator Call Stacking for more information)
  • Right mouse key clicking on RX window
    • Will give a menu only when the menu item 'RT Click = Return NOT menu' is NOT selected!
      • Clear RX - Clear the receive window. This receive buffer can contain a maximum of 10,000 characters
      • Output to Text File - Output the received text to a text file named RTTY1.txt
      • Help - Show the help file for this window
  • Right mouse key clicking on TX window
    • Will give a menu only when the menu item 'RT Click = Return NOT menu' is NOT selected!
      • Clear TX - Clear the transmit window
      • Paste - Place the TX text in the Paste buffer
  • Right mouse key clicking in GRAB window
    • Gives a menu:
      • Clear List - Clear the entire grab window
      • Clear Selected Call - Clear the selected call in the grab window
      • Sort Order - Choose the order in which call signs are pulled from the grab window:
        • Last In, First Out
        • First In, First Out

3.3. Keyboard Assignments

  • Alt+T - Toggle TX/RX, when in TX the cursor will be set to the TX window of the active interface
  • Ctrl+K - Toggle TX/RX and move the cursor into the DI's TX window to send manual information using the keyboard; press Esc or click on the RX button to terminate manual sending
  • Alt+G - Grab most recent callsign from callsign textbox. Upon grabbing that callsign gets deleted from the grab list
  • Ctrl+Left/Right arrows - When two radios are configured in SO2R or a dual-receiver radio is used in SO2V, and two digital windows are open, pressing Ctrl+Left arrow or Ctrl+Right arrow will swap from one active Digital Interface to the other. Digital Interface 1 will follow VFO A/Radio 1, Digital Interface 2 will follow VFO B/Radio 2

4. The Digital Interface - Menu Selections

The digital interface has a menu at the top which varies depending on which type of interface is selected under the Digital Modes tab in the Configurer.

4.1. Configurer Selection: Soundcard

  • Setup
    • Settings - Opens the Digital Setup window; see the section on 'The Digital Interface - Setup' below
    • Turn AutoTRXUPdate On/Off
      • If your radio's dial displays the actual transmitted frequency (i.e. the Mark frequency in FSK RTTY), you would turn this option off
      • If your radio's dial displays the suppressed carrier frequency (e.g. SSB mode), you would turn this option on. This causes the program to add (USB) or subtract (LSB) the audio frequency from the digital engine to/from the radio's dial frequency so that the frequency that appears in the Entry window, the Bandmap, the log and spotted to the DX cluster is the actual transmitted frequency, not the suppressed carrier frequency

 AutoTRXUpdate can affect other modes

If the AutoTRXUpdate option is turned on, it takes effect whenever the DI window is open. If you leave the DI window open and switch to CW or SSB, the offset will continue to be applied, and the frequencies in the Entry window, Bandmap and your log will be incorrect. You should always close the DI window when switching from digital modes to other modes. Also, if you are likely to want to use a non-digital mode the next time you start the program, you should close the DI window before shutting down N1MM Logger in order to ensure that the DI window does not cause this option to be applied the next time you start the Logger.

    • Bring to Foreground when made Active - Bring the Digital Interface and Engine to the foreground when its Entry window has focus
      • This adds ability to stack Digital Interfaces and Engines and have the correct one on top when the associated Entry window has focus
    • SoundCard
      • RX Mixer - Shows the Record control mixer dialog from the Windows operating system. Only for Windows versions XP and earlier
      • TX Mixer - Shows the Play control mixer dialog from the Windows operating system. Only for Windows versions XP and earlier
        • These menu items are not available when using the Fldigi engine. They are also not available in Windows 7, 8 and Vista
    • Setup MMTTY - The MMTTY setup is shown. This menu item is only visible when MMTTY is selected
    • AFC On/Off with CQ - If set then the AFC will turn on with CQ message or TU messages. Turning AFC on when soliciting new callers with a CQ or QRZ message can help tune in off-frequency callers
    • NET On/Off with Run Change - Option to turn Net function on in S&P and off in Running mode. In S&P mode, you normally want to transmit on the same frequency you are receiving on; in AFSK, turning NET on ensures this. In Run mode, you normally leave NET off in order to allow the receiver to track off-frequency callers without moving your TX frequency
    • Turn Hover Mode On/Off - With this option selected, when the mouse is hovered over a valid callsign the callsign is automatically transferred to the Entry window's callsign box without having to click on it. This option is most effective when used in combination with the RT Click = Return NOT menu option
      • Note: Your own call is excluded from being picked up
    • RT Click = Return NOT menu - When this option is selected, a right-click in the RX window will perform the same functions as pressing the Enter key. This is designed to work with ESM; in ESM, in a routine QSO pressing the Enter key automatically sends the next message in the normal QSO sequence. For example, when CQing, once a callsign has been placed in the callsign box (either by left-clicking on it or using the Hover mode option), right-clicking will send the exchange and move the cursor to the exchange box, left-clicking on the received exchange will transfer the exchange to the entry window and right-clicking will send the TU message and log the contact. A complete QSO can be performed with simply a couple of left-clicks and a couple of right-clicks. As always with ESM, you need to be aware of the current ESM state. If the exchange data is not yet valid, or if the cursor is in the callsign box after the exchange data has been entered, the ESM state and the resulting action may not be what you expect
    • Send Text File - Send a text file. A file open dialog will appear from which the file to be sent can be selected
    • Output Main RX Window to Text File - When this is checked, text that is displayed in the main RX window will be saved to a text file in the ExportFiles directory in the N1MM Logger+ user files area. The file name will be date stamped (mmddyyyy), as in 05312012DigitalInterface1Output.txt (for DI1)
    • Digital Call Stacking - Used together with the {LOGTHENPOP} macro. See Single Operator Call Stacking for more information
      • Enable using First In First Out - Enables the Digital Call Stacking feature. Calls are popped off the stack in the order they were placed there
      • Enable using Last In First Out - Enables the Digital Call Stacking feature. Calls are popped off the stack in reverse order, i.e. most recent first
      • Enable using FIFO Mults First - Enables the Digital Call Stacking feature. Calls are popped off the stack in order of their multiplier value. In those contests where one QSO can yield 2 or 3 mults, the higher-mult calls will be taken first. Among calls with the same multiplier value, calls are popped in FIFO order, i.e. in the order they were placed there
      • Disabled - Disables the Digital Call Stacking feature
    • Use RX Window Callsign Pause Routines - When this option is selected, moving the mouse in the RX window over a valid callsign while the callsign box in the Entry window is empty will cause incoming text to stop appearing and the RX window to pause scrolling. At this point you can either click on the callsign to transfer it into the Entry window, display any incoming text that was held back during the pause and resume scrolling, or simply move the mouse off the callsign to display any held incoming text and resume normal scrolling. Also with this option selected, when the left mouse button is clicked in the RX window to select text the RX window will pause until the mouse button is released after the text has been selected, at which point the selected text will be copied to the clipboard, any held incoming text will be displayed and normal scrolling will resume. If there is a scrollbar present in the RX window, moving the scroll bar will cause incoming text to be paused until either text has been selected and the mouse has been released, the pause strip at the left side of the window is clicked, or the right mouse button is clicked in the RX window
    • Add. RX Windows
      • Enable Attached RX Windows - After one or more additional RX window(s) has/have been set up using the last submenu item below, this option can be selected in order to attach or embed small RX text displays from the additional RX window(s) into the main DI window. When the additional RX windows are attached to the main RX window using this option, the attached windows appear above the main RX window. The non-attached RX windows are minimized to the task bar when the attached windows are enabled, but they may be restored from the task bar in order to see more text than is visible in the attached window, to access the setup options, or to close the additional RX window without closing the main DI window. The task bar icon for the additional RX window is grouped with the main N1MM Logger icons. If the additional RX window is using a software decoder, there will also be a separate task bar icon for the digital engine; do not confuse the two task bar icons
      • Open Add. RX Window (4 Avail.) - This allows you to open an auxiliary RX window for diversity decoding of the same RTTY signal, e.g. by using a TNC in the main DI window and MMTTY or 2Tone in the auxiliary window, or by using a different copy of MMTTY or 2Tone with a different decoding algorithm to decode the same audio input. There are up to 4 such windows available (the remaining number available appears in the menu). Each additional window is associated with either DI1 or DI2, depending on which DI window menu was used to open it. There is a separate Setup dialog for each additional RX window, which is accessible from the menu bar at the top of the additional window. The first time an additional RX window is opened, its setup dialog will automatically be displayed. The decoder type (MMTTY, TNC or DXP38 - use MMTTY for 2Tone), and the path to the program or the COM port information for a TNC must be filled in before the additional RX window can be used. Once all of the additional RX windows you intend to open from either DI window have been set up and tested, you can use the Enable Attached RX Windows option to attach the additional windows to the main DI window
  • Interface
    • MMVARI - Select MMVARI as the interface
      • No other installation required - the MMVARI engine is installed during the N1MM Logger install
    • MMTTY - Select MMTTY (or 2Tone) as the interface
      • Requires MMTTY (or 2Tone) to be installed and the DI-1/2 path(s) to MMTTY to be set up in the Configurer
    • Fldigi - Select Fldigi as the interface
      • Requires Fldigi to be installed and the DI-1/2 path(s) to Fldigi to be set up in the Configurer
  • Help - Shows help file

4.2. Configurer Selection: OTHER

  • Setup
    • Settings - Opens the Digital Setup window; see the section on 'The Digital Interface - Setup' below
    • Turn AutoTRXUPdate On/Off
      • If your radio's dial displays the actual transmitted frequency (i.e. the Mark frequency in FSK RTTY), you would turn this option off
      • If your radio's dial displays the suppressed carrier frequency (e.g. SSB mode), you would turn this option on. This causes the program to add (USB) or subtract (LSB) the audio frequency from the digital engine to/from the radio's dial frequency so that the frequency that appears in the Entry window, the Bandmap, the log and spotted to the DX cluster is the actual transmitted frequency, not the suppressed carrier frequency

 AutoTRXUpdate can affect other modes

If the AutoTRXUpdate option is turned on, it takes effect whenever the DI window is open. If you leave the DI window open and switch to CW or SSB, the offset will continue to be applied, and the frequencies in the Entry window, Bandmap and your log will be incorrect. You should always close the DI window when switching from digital modes to other modes. Also, if you are likely to want to use a non-digital mode the next time you start the program, you should close the DI window before shutting down N1MM Logger in order to ensure that the DI window does not cause this option to be applied the next time you start the Logger.

    • Bring to Foreground when made Active - Bring the Digital Interface and Engine to the foreground when its Entry window has focus
      • This adds ability to stack Digital Interfaces and Engines and have the correct one on top when the associated Entry window has focus
    • Turn Hover Mode On/Off - With this option selected, when the mouse is hovered over a valid callsign the callsign is automatically transferred to the Entry window's callsign box without having to click on it. This option is most effective when used in combination with the RT Click = Return NOT menu option
      • Note: Your own call is excluded from being picked up
    • RT Click = Return NOT menu - When this option is selected, a right-click in the RX window will perform the same functions as pressing the Enter key. This is designed to work with ESM; in ESM, pressing the Enter key automatically sends the next message in the normal QSO sequence. For example, when CQing, once a callsign has been placed in the callsign box (either by left-clicking on it or using the Hover mode option), right-clicking will send the exchange and move the cursor to the exchange box, left-clicking on the received exchange will transfer the exchange to the entry window and right-clicking will send the TU message and log the contact. A complete QSO can be performed with simply a couple of left-clicks and a couple of right-clicks
    • Send Text File - Send a text file. A file open dialog will appear from which the file to be sent can be selected
    • Output Main RX Window to Text File - When this is checked, text that is displayed in the main RX window will be saved to a text file in the ExportFiles directory in the N1MM Logger+ user files area. The file name will be date stamped (mmddyyyy), as in 05312012DigitalInterface1Output.txt (for DI1)
    • Digital Call Stacking - Used together with the {LOGTHENPOP} macro. See Single Operator Call Stacking for more information
      • Enable using First In First Out - Enables the Digital Call Stacking feature. Calls are popped off the stack in the order they were placed there
      • Enable using Last In First Out - Enables the Digital Call Stacking feature. Calls are popped off the stack in reverse order, i.e. most recent first
      • Enable using FIFO Mults First - Enables the Digital Call Stacking feature. Calls are popped off the stack in order of their multiplier value. In those contests where one QSO can yield 2 or 3 mults, the higher-mult calls will be taken first. Among calls with the same multiplier value, calls are popped in FIFO order, i.e. in the order they were placed there
      • Disabled - Disables the Digital Call Stacking feature
    • Use RX Window Callsign Pause Routines - When this option is selected, moving the mouse in the RX window over a valid callsign while the callsign box in the Entry window is empty will cause incoming text to stop appearing and the RX window to pause scrolling. At this point you can either click on the callsign to transfer it into the Entry window, display any incoming text that was held back during the pause and resume scrolling, or simply move the mouse off the callsign to display any held incoming text and resume normal scrolling. Also with this option selected, when the left mouse button is clicked in the RX window to select text the RX window will pause until the mouse button is released after the text has been selected, at which point the selected text will be copied to the clipboard, any held incoming text will be displayed and normal scrolling will resume. If there is a scrollbar present in the RX window, moving the scroll bar will cause incoming text to be paused until either text has been selected and the mouse has been released, the pause strip at the left side of the window is clicked, or the right mouse button is clicked in the RX window
    • Add. RX Windows
      • Enable Attached RX Windows - After one or more additional RX window(s) has/have been set up using the last submenu item below, this option can be selected in order to attach or embed small RX text displays from the additional RX window(s) into the main DI window. When the additional RX windows are attached to the main RX window using this option, the attached windows appear above the main RX window. The non-attached RX windows are minimized to the task bar when the attached windows are enabled, but they may be restored from the task bar in order to see more text than is visible in the attached window, to access the setup options, or to close the additional RX window without closing the main DI window
      • Open Add. RX Window (4 Avail.) - This allows you to open an auxiliary RX window for diversity decoding of the same RTTY signal, e.g. by using a TNC in the main DI window and MMTTY or 2Tone in the auxiliary window, or by using a different copy of MMTTY or 2Tone with a different decoding algorithm to decode the same audio input. There are up to 4 such windows available (the remaining number available appears in the menu). Each additional window is associated with either DI1 or DI2, depending on which DI window menu was used to open it. There is a separate Setup dialog for each additional RX window, which is accessible from the menu bar at the top of the additional window. The first time an additional RX window is opened, its setup dialog will automatically be displayed. The decoder type (MMTTY, TNC or DXP38 - use MMTTY for 2Tone), and the path to the program or the COM port information for a TNC must be filled in before the additional RX window can be used. Once all of the additional RX windows you intend to open from either DI window have been set up and tested, you can use the Enable Attached RX Windows option to attach the additional windows to the main DI window
  • Interface
    • MMVARI - Select MMVARI as the interface (e.g. for PSK or other sound card digital modes)
      • No other installation required - the MMVARI engine is installed during the N1MM Logger install
    • OTHER(Tnc) - Select the TNC or TU as the interface
  • Help - Shows help file

4.3. Configurer Selection: DXP38

  • Setup
    • Settings - Opens the Digital Setup window; see the section on 'The Digital Interface - Setup' below
    • Turn AutoTRXUPdate On/Off
      • If your radio's dial displays the actual transmitted frequency (i.e. the Mark frequency in FSK RTTY), you would turn this option off
      • If your radio's dial displays the suppressed carrier frequency (e.g. SSB mode), you would turn this option on. This causes the program to add (USB) or subtract (LSB) the audio frequency from the digital engine to/from the radio's dial frequency so that the frequency that appears in the Entry window, the Bandmap, the log and spotted to the DX cluster is the actual transmitted frequency, not the suppressed carrier frequency

 AutoTRXUpdate can affect other modes

If the AutoTRXUpdate option is turned on, it takes effect whenever the DI window is open. If you leave the DI window open and switch to CW or SSB, the offset will continue to be applied, and the frequencies in the Entry window, Bandmap and your log will be incorrect. You should always close the DI window when switching from digital modes to other modes. Also, if you are likely to want to use a non-digital mode the next time you start the program, you should close the DI window before shutting down N1MM Logger in order to ensure that the DI window does not cause this option to be applied the next time you start the Logger.

    • Bring to Foreground when made Active - Bring the Digital Interface and Engine to the foreground when its Entry window has focus
      • This adds ability to stack Digital Interfaces and Engines and have the correct one on top when the associated Entry window has focus
    • Turn Hover Mode On/Off - With this option selected, when the mouse is hovered over a valid callsign the callsign is automatically transferred to the Entry window's callsign box without having to click on it. This option is most effective when used in combination with the RT Click = Return NOT menu option
      • Note: Your own call is excluded from being picked up
    • RT Click = Return NOT menu - When this option is selected, a right-click in the RX window will perform the same functions as pressing the Enter key. This is designed to work with ESM; in ESM, pressing the Enter key automatically sends the next message in the normal QSO sequence. For example, when CQing, once a callsign has been placed in the callsign box (either by left-clicking on it or using the Hover mode option), right-clicking will send the exchange and move the cursor to the exchange box, left-clicking on the received exchange will transfer the exchange to the entry window and right-clicking will send the TU message and log the contact. A complete QSO can be performed with simply a couple of left-clicks and a couple of right-clicks
    • Send Text File - Send a text file. A file open dialog will appear from which the file to be sent can be selected
    • Output Main RX Window to Text File - When this is checked, text that is displayed in the main RX window will be saved to a text file in the ExportFiles directory in the N1MM Logger+ user files area. The file name will be date stamped (mmddyyyy), as in 05312012DigitalInterface1Output.txt (for DI1)
    • Digital Call Stacking - Used together with the {LOGTHENPOP} macro. See Single Operator Call Stacking for more information
      • Enable using First In First Out - Enables the Digital Call Stacking feature. Calls are popped off the stack in the order they were placed there
      • Enable using Last In First Out - Enables the Digital Call Stacking feature. Calls are popped off the stack in reverse order, i.e. most recent first
      • Enable using FIFO Mults First - Enables the Digital Call Stacking feature. Calls are popped off the stack in order of their multiplier value. In those contests where one QSO can yield 2 or 3 mults, the higher-mult calls will be taken first. Among calls with the same multiplier value, calls are popped in FIFO order, i.e. in the order they were placed there
      • Disabled - Disables the Digital Call Stacking feature
    • Use RX Window Callsign Pause Routines - When this option is selected, moving the mouse in the RX window over a valid callsign while the callsign box in the Entry window is empty will cause incoming text to stop appearing and the RX window to pause scrolling. At this point you can either click on the callsign to transfer it into the Entry window, display any incoming text that was held back during the pause and resume scrolling, or simply move the mouse off the callsign to display any held incoming text and resume normal scrolling. Also with this option selected, when the left mouse button is clicked in the RX window to select text the RX window will pause until the mouse button is released after the text has been selected, at which point the selected text will be copied to the clipboard, any held incoming text will be displayed and normal scrolling will resume. If there is a scrollbar present in the RX window, moving the scroll bar will cause incoming text to be paused until either text has been selected and the mouse has been released, the pause strip at the left side of the window is clicked, or the right mouse button is clicked in the RX window
    • Add. RX Windows
      • Enable Attached RX Windows - After one or more additional RX window(s) has/have been set up using the last submenu item below, this option can be selected in order to attach or embed small RX text displays from the additional RX window(s) into the main DI window. When the additional RX windows are attached to the main RX window using this option, the attached windows appear above the main RX window. The non-attached RX windows are minimized to the task bar when the attached windows are enabled, but they may be restored from the task bar in order to see more text than is visible in the attached window, to access the setup options, or to close the additional RX window without closing the main DI window
      • Open Add. RX Window (4 Avail.) - This allows you to open an auxiliary RX window for diversity decoding of the same RTTY signal, e.g. by using a TNC in the main DI window and MMTTY or 2Tone in the auxiliary window, or by using a different copy of MMTTY or 2Tone with a different decoding algorithm to decode the same audio input. There are up to 4 such windows available (the remaining number available appears in the menu). Each additional window is associated with either DI1 or DI2, depending on which DI window menu was used to open it. There is a separate Setup dialog for each additional RX window, which is accessible from the menu bar at the top of the additional window. The first time an additional RX window is opened, its setup dialog will automatically be displayed. The decoder type (MMTTY, TNC or DXP38 - use MMTTY for 2Tone), and the path to the program or the COM port information for a TNC must be filled in before the additional RX window can be used. Once all of the additional RX windows you intend to open from either DI window have been set up and tested, you can use the Enable Attached RX Windows option to attach the additional windows to the main DI window
  • Interface
    • MMVARI - Select MMVARI as the interface (e.g. for PSK or other sound card digital modes)
      • No other installation required - the MMVARI engine is installed during the N1MM Logger install
    • Dxp38 - Select the DXP38 as the interface
  • TNC
    • TX - Switches the DXP38 into Transmit mode
    • RX - Switches the DXP38 back to Receive at the end of the current message
    • Abort - Switches the DXP38 back to Receive immediately
    • Tuning Indicator - DXP38 Tuning Indicator on/off
      • On - tuning indicator on
      • Off - tuning indicator off
    • Echo - DXP38 Echo on/off
      • On - echo on
      • Off - echo off
    • Tones - DXP38 Tones setup
      • Normal - normal mark/space tones
      • Reverse - reverse mark/space tones
    • RF Gain - DXP38 RF Gain setup
      • 0 - no amplification
      • +6 db - 6 db amplification selected
      • +12 db - 12 db amplification selected
    • Filter - DXP38 Filter setup
      • Narrow 55 hz - Selects narrow (55 Hz) filter
      • Mid 75 hz - Selects mid (75 Hz) filter
      • Wide 100 hz - Selects wide (100 Hz) filter
    • Setup TNC - Opens the DXP38 tab in the Digital Setup window for making adjustments to other DXP38 parameters
    • Hard Reset TNC - As it says - does a hard reset on the DXP38

  • Help - Shows help file

5. The Digital Interface - Setup

This setup dialog is for all interface types, but some settings are only for MMTTY or MMVARI. When selecting 'Setup | Settings' in the Digital Interface window a dialog like the one below will be shown. Any changes made in the setup form must be saved by clicking the Save Settings button located on the bottom of the form. Any changes made and saved will be changed as soon as the setup area closes.

5.1. Tab: General/MMTTY Setup

This interface has general setup information for ANY type of interface (Soundcard or external TNC) and some specific settings for MMTTY, MMVARI and Fldigi.

DigitalSetup GeneralTab

  • RX Windows add to Grab window - If this option is checked, callsigns detected in the Additional RX windows will be sent to the Grab window
  • Display Radio Freq and not Exact Freq in DI Caption
    • Check this option if you are using a radio mode that displays the actual transmitted frequency rather than the suppressed carrier frequency (e.g. FSK RTTY)
    • Note that this setup option only affects the frequency that is displayed in the DI window and that is returned by the {RDIGFQ} or {LDIGFQ} macro. To change the frequency that is sent to the Entry window and recorded in the log, see the DI window's Setup > Turn AutoTRXOffset On/Off menu item
  • Add Callsign to Bandmap on Alt+G - (MMTTY and PSK) Option to send callsign from station in callsign field (Alt+O) when doing a grab (Alt+G)
  • Send Space on Callsign Mouse Click - Sends a space to advance the entry window cursor after clicking on a call sign
  • (MMTTY) Send HamDefault on Run to S&P change - (MMTTY only) Ability to have Ham Default(MMTTY) sent when going from Run to S&P to reset Mark Frequency. Select to enable
  • (MMTTY-MMVARI) Turn AFC Off when switching to S&P - (MMTTY and PSK) Ability to Turn AFC Off when going from Run to S&P. Select to enable. Many people when in Running mode will leave the Net Off and turn on AFC to find people coming back to them a little off frequency. So to turn the AFC back off when you go to S&P (without forgetting) this setting comes in handy
  • Do Not add Dupes to Grab Window - Setting for adding dupes to Grab window or Not
  • Send Space on Using Grab - when doing a grab from the grab window it will also send a space press command to Entry window to advance the cursor
  • If QSY Wipes call is checked Clear Grab Window on QSY - If QSY Wipes and Spot call is checked then Clear the Grab window on wipe of callsign.
  • QSY will clear Grab Window - Changing frequency will clear the Grab window
  • Clear Grab Window On CQ - sending CQ will clear the Grab window
  • Only Grab Master.scp Calls and - Will only send calls that are found in Master.scp to the Grab window; if this is left unchecked, anything that passes the callsign validity check routines will be sent to the Grab window

  • On Top Settings
    • MMTTY always on Top - MMTTY is always in front of all other N1MM logger windows. A restart of N1MM logger is needed to activate this function. Minimizing the N1MM logger program will not minimize the MMTTY engine
    • MMVARI always on Top - MMVARI is always in front of all other N1MM logger windows. A restart of N1MM logger is needed to activate this function. Minimizing the N1MM logger program will not minimize the MMVARI engine
    • Fldigi always on Top - Fldigi is always in front of all other N1MM logger windows. A restart of N1MM logger is needed to activate this function. Minimizing the N1MM logger program will not minimize the Fldigi engine

  • Shift Frequency Compensation - for radios which use/need Shift Frequency Compensation
    • Enabled - Select to enable Shift Frequency Compensation
    • Offset Frequency - the frequency offset

  • Window Scroll
    • Window Scroll Type - You can choose between two scrolling behaviors in the RX window:
      • Scrolling - New text is always added at the bottom of the RX window. Each time a new line starts, previous text scrolls up one line to make room for the new line at the bottom of the window. The most recent text will always be near the bottom of the window, so you don't often need to move the mouse away from the bottom two lines or so, but if a newline character is received just as you want to click on something, the text you wish to click on will scroll upward
      • Non Scrolling - Previous text does not move when new text is added. The line where text is currently being entered is underlined, and each time a new line starts, the line immediately below the old current line is cleared and it becomes the new current line. If the previous current line was the bottom line of the display, the new current line will be the top line in the display, overwriting whatever was there before. Text does not move after it is entered, which can make it easier to click on than text in a scrolling window, but the most recent text can be anywhere in the window


  • Callsign Validity and Highlight Routines
    • Use Generic Routines - the generic routines will highlight anything that passes the check routines (and probably will look like a callsign), using the standard colors for multipliers, QSOs and dupes
    • Use these resources: - when selected, only call signs that are found in at least one of the selected resources will be highlighted
      • You can select any combination of the Master.scp file, the Call History file, calls that have been spotted on the cluster and appear in the Telnet window, and/or calls that have been logged in this contest
    • Use Combination of both - when selected there will be additional highlighting for callsigns that are not found in the selected resources. If the normal highlight is foreground, the background will be changed to yellow; if the normal highlight is background, the text color will be changed to yellow. The yellow color is not configurable
    • Use Search routine to find Master.scp in Garbage Text - turn checking for callsigns in garbage text in digital modes on or off. When this is turned on, callsigns that appear in the Master.scp file will be highlighted even if there are garbage characters before and after the call. Note that if a longer callsign is found that contains a callsign in Master.scp, only the callsign from Master.scp will be highlighted; you will have to enter the longer call sign by hand
    • Highlight Foreground Text - call sign text will be in the highlight color on the normal background
    • Highlight Background of Text - background color surrounding call sign will be changed to the highlight color

  • Alignment Frequency - frequency used by the Align button = preferred audio frequency. If you are using FSK RTTY, be sure to set the RTTY alignment frequency corresponding to your radio's transmit frequency (i.e. set Align frequency to your radio's Mark frequency in MMTTY, Mark frequency + 85 in MMVARI and Fldigi)
    • MMTTY - RTTY alignment frequency. This is the Mark frequency
    • MMVARI - Alignment frequencies for MMVARI
      • RTTY - RTTY alignment frequency in MMVARI
        • NB Add 85 to place MMVARI's Mark Frequency on desired frequency. Example: For 2125 Mark, enter 2210
      • Other - alignment frequency for other modes than RTTY (e.g. PSK)
    • FLdigi - Alignment frequencies for Fldigi
      • RTTY - RTTY alignment frequency in Fldigi
      • Other - alignment frequency for other modes than RTTY (e.g. PSK)

  • Default RTTY Interface - Select the preferred RTTY interface. Choices are: MMTTY, MMVARI, FLDIGI, TNC or DXP-38
  • Default PSK Interface - Select the preferred interface for PSK (and other sound card modes). Choices are MMVARI or FLDIGI

  • MMTTY Window Layout
    • Normal - The normal size MMTTY window is shown, including waterfall/spectrum, menu bar and control buttons
    • Small - The small size MMTTY window is shown, i.e. waterfall/spectrum display only
    • Control Menus - Shows waterfall/spectrum plus menu bar
    • Control Buttons - Shows waterfall/spectrum plus control buttons

  • Save Settings - Save the configuration changes you just made. If you want to back out without saving the changes, click on the X in the upper right corner to close the window; the program will ask you whether you are sure you don't want to save the changes

5.2. Tab: MMVARI Setup

DigitalSetup MMVARI WaterfallSetup

  • Waterfall/Spectrum Setup
    • Waterfall/Spectrum/Misc Color palette - The colors that make up the color palette can be changed to represent whatever colors you would like. The colors go from the weakest signal on the left to the strongest signal on the right. There is a color palette setting for the Waterfall, Spectrum and for Miscellaneous colors. The Default button changes the colors back to the default colors

    • AFC Search Range - This is how far in Hz the interface will track a drifting signal i.e the frequency sweeping width (+/-Hz) for the AFC
      • Sense Level - specifies the S/N level (dB) for the wide AFC. When the search range is less than or equal to 50 Hz, the wide AFC does not function. The sense level is applied to all the RX channels
    • Digital Output Level - specifies the digital output level in the range of 0 to 32767. The default value is 16384

    • Use TNC Software for control - When selected N1MM logger will release the serial port for the TNC so the soundboard in the TNC can have control. When using an external TNC the internal soundboard can be used

    • # of MMVARI channels - Number of MMVARI channels to use. Choices are 1, 2, 3 or 4
      • Note that if this is set to 1, you have the option to select the Multi-Channel Rx menu item in the MMVARI menu bar, but when it is set to 2, 3 or 4 this option is not available
    • MFSK (MFSK only)
      • Handling Center Frequency - When selected the center frequency is used for the carrier frequency. When not selected the base tone frequency is used for the carrier frequency
      • Use Metric Level Squelch - Select to use the metric level for the squelch. When not selected the S/N level is used for the squelch

    • Squelch Level - This level represents the noise level where you would like the interface to start copying signals. 0 indicates an open squelch and everything will be decoded
    • High Pass Filter - Select 'Use High Pass Filter' to use the internal high pass filter for RX. Although this is unnecessary with most soundcards, it sometimes is effective for eliminating hum in the input audio

    • Spectrum Lower Freq - the lower frequency to display when the Spectrum view or Waterfall is active
    • Spectrum Upper Freq - the upper frequency to display when the Spectrum view or Waterfall is active

    • CW ID
      • Enable - If this check box is checked (Enabled) the interface will send the string entered in the field (Enter CWID String) in CW after every transmission. A * will be substituted by SK, + by AR and = by BT

    • Save Settings - Save the configuration changes you just made. If you want to back out without saving the changes, click on the X in the upper right corner to close the window


DigitalSetup MMVARI SoundCard

  • Soundcard Setup
    • DI1/DI2 MMVARI Soundcard
      • Input Soundcard # - Select the input soundcard to be used
      • Input Channel - Select the input channel. Mono, Left channel or Right channel
      • Output Soundcard # - Select the output soundcard to be used)
    • FIFO
      • RX - specifies the depth of the RX FIFO buffer. Valid values are 4 to 32
      • TX - specifies the depth of the TX FIFO buffer. Valid values are 4 to 32
    • Clock - Soundcard Clock adjustment
      • RX Freq - specifies the sampling rate
      • TX Offset - the offset of the TX frequency compared to the RX frequency (some sound cards have an offset between record and playback)

    • Save Settings - Save the configuration changes you just made. If you want to back out without saving the changes, click on the X in the upper right corner to close the window

5.3. Tab: Message Setup

This tab is where you can edit the message buttons that are displayed in the lower part of the DI window. In addition to selecting this tab from the DI Setup window, you can also open this window by right-clicking on one of the buttons.

There are four separate sets of message buttons stored in the database, one for each type of digital interface (MMVARI, MMTTY/2Tone/Fldigi, TNC and DXP38). Before importing, exporting or editing buttons you need to select the particular message set you will be working on.

DigitalSetup Messages

  • Import - Once a message set has been selected under Digital Message Set, you can import buttons for that set from a .mc file using the Import button
  • Save - You can save the current message buttons in a .mc file in the N1MM Logger+ user files area by using the Save button

  • # of Messages - Select the number of message buttons to be displayed in the DI window. You can select 0, 8, 16 or 24

  • Digital Message Set -
    • Select an interface type from the drop down menu. Choices are:
      • MMVARI - messages for the MMVARI interface
      • MMTTY,Fldigi - messages for the MMTTY, 2Tone and Fldigi interfaces
      • Other - messages for a TNC (such as a PK-232 or KAM)
      • Dxp38 - messages for a DXP38
    • Click on the message button which is to be updated to transfer that button to the Message Setup area
    • The Macro buttons at the right are for TNC interfaces only. Enter the control codes that are needed to switch your TNC between RX and TX
      • Only visible when Other is selected
      • RX - Receive macro, i.e. the command(s) your TNC needs to put it into transmit. This will become the contents of the {RX} macro
      • TX - Transmit macro, i.e. the command(s) your TNC needs to put it back into receive at the end of a message. This will become the contents of the {TX} macro
      • ESC - Abort macro, i.e. the command(s) your TNC needs to abort an ongoing message immediately. This will be executed when you press the Escape key

  • Message Setup
    • Message Text - This is where the text of the message sent by the selected button is displayed and can be edited
    • Message Caption - This is where the caption that will appear on that button is displayed and can be edited
    • Available Macros - Shows the available macros that can be used in messages. Clicking on a macro will transfer it to the message text area
    • Save Message - Save the contents of the Message Text and Message Caption into the selected button

  • Save Settings - Save the configuration changes you just made, i.e. the entire set of 24 buttons. If you want to back out without saving the changes, click on the X in the upper right corner to close the window

5.4. Tab: DXP-38 Setup

This tab will only show when the DXP-38 TU has been selected under the Digital Modes tab in the Configurer.

DigitalSetup DXP38


The various settings in this window are for setting up DXP-38 parameters. Consult the DXP-38 manual for detailed instructions on setting them up.

  • Save Settings - Save the configuration changes you just made. If you want to back out without saving the changes, click on the X in the upper right corner to close the window

Last Modification: 19 August 2016 10:01:06 EDT by VE3KI.