Re:N1MM Digital mode setup

[HL2UOK]

• Jump to Content

 

 

Contest Logging Software

Free Software for Phone, CW, and Digital Modes

• Home
  • Features
  • PC Requirements
  • -----
  • Program Development
• Files
  • Full Install
  • Latest Updates
  • Update History 2007-2010
  • Update History 2011-present
  • Alternate Download Site
  • -----
  • LP1H Callsign Database
  • Experimental Versions
  • -----
  • Sample Function Key Files
  • User Defined Contests (UDC)
  • Call History Files
  • Additional Support Files
  • -----
  • Documentation Downloads (pdf)
  • Documentation Translations (pdf)
• Documents
  • All Documentation (1 - 4)
  • - 1. Getting Started
  • - 2. Digging Deeper
  • - 3. References
  • - 4. Frequently Asked Questions
  • -----
  • Hot Topics (most hits)
    • Download and Install
    • Download Latest Updates
    • QSO Entry Window
    • The Configurer
    • Function Keys, Messages and Macros
    • Hotkeys (Keyboard Shortcuts)
    • Hotkey Short List
    • Supported Radios
    • Supported Contests
    • Contest Setup Instructions
    • Instructional Videos
  • -----
  • Translations (pdf files)
  • -----
  • Print Current Documentation
• Support
  • Email Support Groups
  • Instructional Videos
  • Feature Requests
  • Bug Reports
• Website
  • Website Users Guide
  • Website Authors Guide
  • -----
  • Overview All Pages
  • Last Changes
  • Sitemap (Doc Structures)
  • -----
  • Website Problem Reports
  • -----
  • Register
  • Login

• 
  • Digging Deeper N1MM Logger Documentation

2.7.3 Digital Setup

• 2.7.3 Digital Setup
  • 1. Setup Overview
    • 1.1. Downloading and Installing MMTTY
    • 1.2. Downloading and Installing 2Tone
    • 1.3. Downloading and Installing Fldigi
    • 1.4. Setting Up the Configurer
  • 2. The Digital Interface - Window
    • 2.1. Receive Window Callsign Colors
    • 2.2. Mouse Assignments
      • 2.2.1. Keyboard Assignments
  • 3. The Digital Interface - Menu Selections
    • 3.1. Configurer Selection: Soundcard
    • 3.2. Configurer Selection: OTHER
    • 3.3. Configurer Selection: DXP38
  • 4. The Digital Interface - Setup
    • 4.1. Tab: General/MMTTY Setup
    • 4.2. Tab: MMVARI Setup
    • 4.3. Tab: Message Setup
    • 4.4. Tab: WAE RTTY Configuration
    • 4.5. Tab: DXP-38 Setup

1. Setup Overview

Setting up an interface involves 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. If you are using MMTTY for FSK RTTY, you will also have to perform some configuration from within MMTTY. If you use Fldigi, there is some configuration that must be done from within Fldigi.

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, 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). 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 plugin. If you are using MMVARI for RTTY using FSK keying, select the appropriate plugin (FSK8250 for true serial ports, EXTFSK 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), 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 or Fldigi, but not 2Tone), or from N1MM Logger itself. To use serial port PTT from the digital engine, 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, you should 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.

Setting Sound Card Levels

If you are using a computer sound card, you will need to pay some attention to level settings.

On receive, to make best use of the sound card's available dynamic range you would adjust the sound card's record 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 record 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 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 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 adding hum and noise 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.

1.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\ .

Note for users of Windows Vista and Windows 7 and 8: 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.

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 program 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 file if you are using EXTFSK for FSK keying). MMTTY will create a separate 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 and DI2RX2 so that you can run up to six copies of MMTTY simultaneously; one for each main DI window, plus up to 4 additional RX windows (e.g. two additional windows for each DI window). Into each of these windows, you need only copy the MMTTY.exe and UserPara.ini files from the main MMTTY program folder created when you first installed it. Each copy will then be configured to use the appropriate sound card and channel. The "Additional RX" copies 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. two or three different decoding methods used on the same receive audio.

Once MMTTY has been downloaded and installed, you can proceed to use the Configurer to set up N1MM Logger to use it.

1.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 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. in 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 updates, 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.

AA5AU has posted a tutorial on setting up N1MM Logger with 2Tone here; #4 in the list gives step-by-step instructions for downloading, installing and setting up 2Tone.

1.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. If you intend never to use Fldigi, you can skip the rest of this section.

If you do not have a copy of Fldigi, then before continuing with the digital setup it is recommended that you 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.

Note that Fldigi cannot be configured to use a single channel of a stereo sound card; Fldigi always uses its sound card in mono mode on receive. If you want to use Fldigi in a two-receiver configuration, either SO2V or SO2R, you will have to use two separate sound cards. You will also need to install two separate copies of Fldigi in separate folders, one for each DI window, in order to be able to configure each one for a separate sound card. It is suggested that you do a full install for each copy, but do not create Start menu or Desktop shortcuts for the second copy. As with MMTTY, users of Windows Vista and Windows 7 may find it necessary to install one or both of these copies outside the Program Files path.

You do not need to install separate copies of Fldigi for additional RX windows, because this feature is not implemented for Fldigi or MMVARI engines, only for MMTTY, 2Tone and hardware TUs/TNCs.

1.4. 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.

• The Digital box in the main Configurer window indicates to the Logger that this port is used for digital mode control.
  • Use this to indicate a port that is used for an external TNC
  • Use this to indicate a port that is used for FSK keying with MMTTY, but not if EXTFSK is being used
    • A port that is used for FSK must also be configured inside the MMTTY setup, regardless of whether the Digital box is checked or not; this includes ports used with EXTFSK
    • It is possible to use a port in the range COM9-COM16 for FSK with MMTTY. In this case, there is no Digital box to be checked; the port must be configured entirely within MMTTY
    • It is possible to use an otherwise unused port in the range COM1-COM8 with EXTFSK; such ports must be configured within MMTTY and EXTFSK, but not in the Configurer
  • Use the Digital box to indicate a port that is used by the digital engine for PTT in AFSK RTTY or other digital modes with MMTTY, MMVARI or Fldigi
    • Exception: If PTT is done by EXTFSK or if PTT is done by the main N1MM Logger program, e.g. from a radio control port or from a Winkeyer, do not check the Digital box for that port
    • If you are using 2Tone as your transmitting interface for RTTY, PTT must be done by the main N1MM Logger program, so do not check the Digital check box for that port
  • It is possible to share a port (sequentially, not simultaneously) for both serial port CW keying (e.g. on DTR) and for PTT and FSK using MMTTY for RTTY (e.g. on RTS and TxD of the same port). In this case, 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) that determine how the port is used. However, if you want to leave the DI window open with the program and radio in CW mode (e.g. to use the Fldigi CW decoder), you cannot share the CW port with the digital engine; do not check the Digital check box on a port that will be used for CW with the DI window open

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 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.

• MMTTY (if used; use this selection for 2Tone as well)
  • Digital Interface 1/2 (left part of window)
    • TU Type: Soundcard
  • DI-1/2 MMTTY Setup (upper right part of window)
    • 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)
      • The path does not need to be in the N1MM Logger program directory
      • The paths for the two DI windows do not need to be the same

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, you should 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 can get confused due to a glitch in MMTTY, which means the port assignments may be wrong the next time the Logger is started up.

• MMVARI (if used)
  • Digital Interface 1/2 (left part of window)
    • TU Type: Soundcard
  • 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

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.

• Fldigi (if used)
  • Digital Interface 1/2 (left part of window)
    • TU Type: Soundcard
  • DI-1/2 Fldigi Setup (lower right part of window)
    • Fldigi Path: Select path to fldigi.exe (complete path, including the name of the executable file)
      • The paths for the two DI windows do not need to be the same

SO2V/SO2R Limitation in Fldigi

There is a basic limitation in the Fldigi engine which can make it harder to use in dual-receiver situations (SO2R and SO2V). Fldigi always receives in mono mode. If you are using a stereo sound card to decode two receivers, with one receiver in the left channel and the other receiver in the right channel, Fldigi will combine the two receivers in its waterfall. It doesn't matter whether Fldigi is the interface engine in DI1 or DI2, it will see the audio from both receivers. Therefore, if you want to use Fldigi with both receivers in a two-receiver setup, you will need to use two separate sound cards for the two receivers. You will also need to install two copies of Fldigi in two separate program folders in order to allow a different sound card to be configured in each copy.

• External TNC (if used)
  • Digital Interface 1/2 (left part of window)
    • TU Type: Other
    • Set other parameters appropriately for the TNC in use (Example settings: 9600, 8, N, 1, Xon-Xoff)

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.

The available 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. For PSK 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. The Digital Interface - Window

The Digital Interface window is nearly the same regardless of which type of interface (MMTTY, MMVARI, FLDIGI or TNC) is being used. Its appearance (foreground and background font colors) can be customized using the Settings > Setup menu item.

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 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. This is the window used for making QSOs. There are 2 ways of placing a callsign into the callsign window of the Logger. 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. 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 what ever 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 change settings etc.
• Callsign Textbox and Grab - When a callsign is encountered in one of the receive windows it will be placed 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 - These buttons on the Digital Interface are (max.) 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)
• Align (MMTTY and Fldigi only) - This is used to move the signal that you are copying into the pass band of your filters. Set the frequency in the setup area. For example, if your filters are centred 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 such a signal to decode it, 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
• AFC (MMTTY only) - Can be used to turn MMTTY's AFC on or off (colored background means AFC is on)
• HAM (MMTTY only) - Restore the MMTTY frequency and shift settings to the HAM default
• 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 (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 window. Once the callsign is filled, whatever you click on next will fill the next box to have info entered in. When the Digital Interface is in transmit, calls are not added to the Grab window
• CLR - Clear the Grab list

2.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.dta 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.dta 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.

The determination of what is a valid callsign is affected by two things: the Callsign Validity and Highlight option chosen in the Digital Setup window, and whether or not there is a file named LP1H_Calls.mdb in the N1MM Logger program folder.

If the "Use Generic Routines" option is chosen in the Digital Setup, anything that looks like a callsign (i.e. passes the check routines - see next paragraph) 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.dta File" option is chosen, only call signs in the Master.dta file will be colored according to the multiplier status; callsigns that are not in the Master.dta file will be given a different highlight color to indicate that they were not found in Master.dta. Regardless of which option is chosen, any callsign that passes the check routines will be placed in the Grab window.

There are two separate check routines. The first is based on a database of all call signs that are known to have been issued by licensing authorities. This database, called LP1H_Calls.mdb, has been compiled by LU5DX. It contains approximately 1.7 million callsigns, and is updated five times a year. A zip file containing this database can be downloaded from the Files menu on the N1MM Logger web site and unzipped into the N1MM Logger program folder. If this database is found, any text string that is neither a number nor a gridsquare reference nor too long to be a callsign is checked against this database, and if it is found there, it is considered to be a valid callsign. If this database is not present, or if the text string is not found in the callsign database, then it is checked using the second check routine, which is a pattern-matching routine that looks for patterns that match amateur callsigns (national prefix, number, suffix). If the database is present and a callsign that matches the pattern-matching routine but is not found in the database is entered into the Entry window, a warning message is displayed in the Check window to indicate that the callsign was not found in the database.

2.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. grabs it and places it in the Exchange field on the Entry Window dialog
    • NB. The callsign field must be filled first!
  • 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 Entry window. (Must click first in Entry window 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

2.2.1. 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 displays the CW/Digital Keyboard window to send manual information using the keyboard
• 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

3. 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.

3.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
  • Receive Mixer - Shows the Record control mixer dialog from the Windows operating system. Only for Windows versions XP and earlier
  • Transmit 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
• 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, 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 N1MM Logger program folder. 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 as controlled by the next option. 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
  • Layout
    • Single Over Each Other - Each additional attached RX Window displays a single line of text. If there is more than one additional window, the attached windows are stacked vertically above the main RX window
    • Double Over Each Other - Similar, except each additional attached RX Window displays two lines of text. The DI window must be sized large enough vertically to make sufficient room for the main RX window as well as the additional attached RX window(s)
    • Side by Side - Additional attached RX Windows are arranged in two columns above the main RX window, with two lines of text in each
  • 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
  • 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
  • MMVARI - Select MMVARI as the interface
    • No other installation required - the MMVARI engine is installed during the N1MM Logger install
  • 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

3.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 N1MM Logger program folder. 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 as controlled by the next option. 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
  • Layout
    • Single Over Each Other - Each additional attached RX Window displays a single line of text. If there is more than one additional window, the attached windows are stacked vertically above the main RX window
    • Double Over Each Other - Similar, except each additional attached RX Window displays two lines of text. The DI window must be sized large enough vertically to make sufficient room for the main RX window as well as the additional attached RX window(s)
    • Side by Side - Additional attached RX Windows are arranged in two columns above the main RX window, with two lines of text in each
  • 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

3.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 N1MM Logger program folder. 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 as controlled by the next option. 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
  • Layout
    • Single Over Each Other - Each additional attached RX Window displays a single line of text. If there is more than one additional window, the attached windows are stacked vertically above the main RX window
    • Double Over Each Other - Similar, except each additional attached RX Window displays two lines of text. The DI window must be sized large enough vertically to make sufficient room for the main RX window as well as the additional attached RX window(s)
    • Side by Side - Additional attached RX Windows are arranged in two columns above the main RX window, with two lines of text in each
  • 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

4. 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 shown. Any changes made in the setup form must be saved by clicking the Save Configuration Button located on the bottom of the form. Any changes made and saved will be changed as soon as the setup area closes.

4.1. Tab: General/MMTTY Setup

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

• 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)
• Remove Excess Linefeeds from RX Window - Ability to strip excess linefeeds from RX Window
• 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

• Callsign Validity Routines
  • Use Generic Routines - the generic routines will highlight anything that passes the check routines (and probably will look like a callsign)
  • Use master.dta File - when selected only the callsigns in the master.dta file will be highlighted
    • Highlight Color for non-Master.dta calls will be shown in the shown color.
  • Use Search routine to find Master.dta in Garbage Text - ability to turn off checking for callsigns in garbage text in digital modes
  • 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

• Digital Interface Window Colors
  • The RTTY receive and transmit window background colors, RX text color and own callsign color in RX window can be changed here. Click on one of the colored boxes to change its color. Note that the highlight colors for validated callsigns corresponding to their worked/multiplier status (red/green/blue/grey) are the same as in the bandmap and cannot be changed

• Digital Interface RX Window Font Selection - Change the font and character size for the RX channels. Press the 'Set Font' button to get a selection window
  • You must close the Digital Window and reopen it so the changes can take effect

• MMTTY Window Settings
  • 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 Menu's - Shows waterfall/spectrum plus menu bar
  • Control Button's - Shows waterfall/spectrum plus control buttons
  • Give MMTTY Help Starting - Turn MMTTY kick-starts off and on

Having trouble getting MMTTY to start?

If you are having trouble getting MMTTY to initialize when the DI window starts up, here are some things to try: First, upgrade to the latest version of MMTTY. Several cases of failure to start have been solved by updating to version 1.68A. Next, if that doesn't work, try checking the Give MMTTY Help Starting check box. If this box is already checked, try unchecking it.

• Preferred RTTY Interface - Select the preferred RTTY interface. Choices are: MMTTY, MMVARI, TNC or Fldigi
• Preferred PSK Interface - Select the preferred interface for PSK (and other sound card modes). Choices are MMVARI and Fldigi
• 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

• 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 Mark Frequency on desired frequency. Example: For 2125 Mark, enter 2210
    • Other - alignment frequency for other modes than RTTY
  • FLdigi - Alignment frequencies for Fldigi
    • RTTY - RTTY alignment frequency in Fldigi
      • NB Add 85 to place Mark Frequency on desired frequency. Example: For 2125 Mark, enter 2210
    • Other - alignment frequency for other modes than RTTY

• Save Configuration - 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

4.2. Tab: MMVARI Setup

• MMVARI Engine
  • 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
  • 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 Frq - the lower frequency to display when the Spectrum view or Waterfall is active
  • Spectrum Upper Frq - 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
  • 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
  • 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
  • Digital Output Level - specifies the digital output level in the range of 0 to 32767. The default value is 16384

• DI1/DI2 MMVARI Soundcard
  • MMVARI Soundcard #
    • Input Soundcard# - Select the input soundcard to be used when there is more than one soundcard in your computer (maximum 4)
    • Input Channel - Select the input channel. Mono, Left channel or Right channel
    • Output Soundcard# - Select the output soundcard to be used when there is more than one soundcard in your computer (maximum 4)
  • FIFO
    • RX - specifies the depth of the RX FIFO. Valid values are 4 to 32
    • TX - specifies the depth of the TX FIFO. Valid values are 4 to 32
  • Clock - Soundcard Clock adjustment
    • RX - specifies the tuning parameters of the RX clock adjustment function
    • TX Offset - the offset of the TX frequency compared to the RX frequency
    • Graphical Adjustment - Graphical RX clock adjustment
      • The computer clock itself is not very accurate (+- 100 ppm); that is why to use WWV or another precision source to calibrate the soundcard
      • 1. Tune to WWV or another Time Mark; adjust so tick is on 1000 Hz in Spectrum of MMVARI
      • 2. Wait for line to appear in display and adjust Clock Freq so line appears straight and not at an angle
      • 3. Click button to save new frequency when line is straight up and down

• 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
• # 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
• Save Configuration - 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

4.3. Tab: Message Setup

• Digital Message Set Select Interface Type and Window Number to begin - Update the message definitions and button caption texts
  • Select an interface (TNC or soundcard DI) from the drop down menu. Choices are:
    • MMVARI - messages for the MMVARI interface
    • MMTTY,Fldigi - messages for the MMTTY and Fldigi interfaces
    • Other - messages for the TNC
    • Dxp38 - messages for a DXP38
  • Click on the message button which has to be updated
  • Type the message text in the field 'Message Text'
  • Type the button caption text in the field 'Message Caption'
  • Click on the 'Save Message' button when satisfied
  • The selected message caption text will be shown on the button
  • Available macros for use in messages are shown in the box 'Available Macros'. First select a message button to see them all
  • The Macro buttons below (for TNC use only) have to be configured as TX/RX buttons. Enter the control codes that are needed to turn on and off your TNC
    • 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
• Load Messages - Load saved messages from a saved file (*.mc) to the selected Digital Message Set
• Save Messages - Save messages from the Digital Macro Set to a file (*.mc)
• # of Messages - Select the number of message buttons. You can select 0, 8, 16 or 24
• Message Setup
  • Message Text - Area where to create the message text for the selected message
  • Message Caption - Message caption from the button
  • 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 created message
• Save Configuration - 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

4.4. Tab: WAE RTTY Configuration

This tab will only show when the WAE RTTY contest has been selected and the information in this tab is only valid for the WAE RTTY contest.

• RQTC - Under RQTC are the 4 messages to send when receiving a QTC
• SQTC - Under SQTC are the 4 messages to send when sending a QTC
• Default Number of QTC to Send - maximum of 10 QTC's
• When sending request for single QTC do what?
  • Clear all data for that QTC
  • Clear only Bad Data
  • Do nothing just send request
• Save Configuration - 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

4.5. 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.

The various settings in this window are for setting up DXP-38 parameters.

• Save Configuration - 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 December 2013 08:24:16 EST by VE3KI.

© Copyright 2004-2013 - N1MM Logger. All rights reserved