Работа RTTY

The interface will operate with MMTTY , HAL DXP38 and ANY TNC because the commands for the TNC are not hard coded into the program. This has to be done by the user of the program :-)
When having troubles please first check the Digital Modes part of the chapter Frequently Asked Questions.

Цифровой интерфейс

Цифровой интерфейс можно использовать как с внешним TNC, так и с MMTTY. При работе с TNC интерфейс выглядит так:

 

При работе с MMTTY появляется два окна, ядро MMTTY (рисунок вверху) и Цифровой интерфейс (рисунок ниже).

The Digital Interface is shown when it is selected under Window in the Entry Window. If a second RTTY port is configured a menu item will appear on the top of the Digital Interface allowing you to open the second RTTY interface.. The exact frequency is displayed in Digital Interface caption (rig(+/-)audio).

The interface has two windows :

It is possible to have 2 Digital Interface windows open at the same time. Open your first interface then click again on the menu item called 'Open 2nd RTTY Window'. This feature can be used to copy both the TNC and MMTTY to pick up on callsigns you might have missed etc. Or if you have 2 radios and 2 separate TNC's you can switch between the 2 of them. Note: The macros for the second Interface window you open up will not be the same as they are for the first window you open.

If the callsign in the callsign field in the Entry window is equal to the callsign in the received text, the call in the Entry window does not get placed into the call list.

Focus is automatically returned back to the Entry window when clicking a callsign in the Receive window

Setup Menu Selections

Selection: MMTTY

Selection: OTHER

Keyboard Assignments

Insert key Assignments

    Mode    
Enter Sends Message
(ESM mode)
    INSERT key or ; key does the following:

RUN

and

S&P

OFF
  1. Grab Callsign from call list if callsign field empty otherwise use call in callsign field.
  2. Prefilles Exchange Boxes
  3. NO DUPE: Sends F5 (Hiscall) + F2 (Exchange)
    or
    DUPE: Sends Nothing
  4. Places cursor in next exchange field (Example: Sect)
RUN
ON
  1. Grab Callsign from call list if callsign field empty otherwise use call in callsign field.
  2. Prefilles Exchange Boxes
  3. NO DUPE: Sends F5 (Hiscall) + F2 (Exchange)
    or
    DUPE
    WorkDupes checked: Sends F5 (Hiscall) + F2 (Exchange)
    WorkDupes not checked:Sends F6(Dupe)
  4. Places cursor in next exchange field (Example: Sect)
  5. Highlights F8 button
S&P
ON
  1. Grab Callsign from call list if callsign field empty otherwise use call in callsign field.
  2. Prefilles Exchange Boxes
  3. NO DUPE: Sends F4 (Mycall)
    or
    DUPE
    WorkDupes checked: Sends F5 (Hiscall) + F2 (Exchange)
    WorkDupes not checked:Sends F6(Dupe)
  4. Once exchange entered INSERT sends F5-F2
    • Pressing INSERTagain will continue to send F5-F2
  5. Places cursor in next exchange field (Example: Sect)

Mouse Assignments

Configuring the Entry window function keys

Macro keys

The TNC interface

The TNC Interface will accept all of the Macro keywords that can be used in the Packet window and other places in the Logger and will also accept the following:

Macro keywords can be used in any of the macro buttons or the Logger function keys..

The TX window will accept all control key commands except for the Esc key, this must be sent as a Shift+Escape combination.

There is one special macro key on the TNC interface. The very first macro button must be setup to send the abort transmission command. As you see in the above picture I have this marked as Abort and have it colored RED. If at any time you press the ESC key while transmitting it will send this macro to the TNC to stop transmission immediately.

Remember that when to set up a macro key that is not a TNC command you will need to include the sequence to key the TNC before it sends. If you click on the macro without the TNC transmitting, your TNC will think it is a command being sent to it and not know how to process it.

TNC users have to enter in what ever CTRL characters are needed to turn on and off your specific TNC....

To use the free form typing in the TX window you need to create a macro that will key your TNC and another to Turn it off. Click the macro that starts transmitting and then click in the TX window. Whatever you type will be sent out… then click the macro to turn things off after you are done.

The MMTTY interface

Setting up the Digital Interface

This setup dialog is for both MMTTY and PSK, thismeans that some setings are only for PSK, MMTTY or both. When selecting 'Setup | Settings' in the Digital Interface window will show a dialog like the one below.

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.

Test your External TNC

Make sure your radio and TNC work on your computers serial port by testing them with an existing terminal program. Connect your TNC/Radio into your computers serial port. The Hyperterm terminal program is included with Windows and works well. Make sure you note all COM port parameters. You should be able to tune in a RTTY signal and print it on the Hyperterm terminal program.

The interface has been tested with the three mentioned TNC's below and work fine with them. Any other TNC should also work as long as you place the right commands for that TNC in the macros.

KAM

Below some RTTY settings for the KAM TNC

AUTOCR 0 AUTOLF ON AUTOSTRT OFF
BKONDEL ON CD SOFTWARE CRADD OFF
DIDDLE ON ECHO ON FILTER OFF
FSKINV OFF INVERT OFF LFSUP OFF
LOWTONES OFF MARK 2125HZ RBAUD 45
SHIFT 170 SPACE 2295HZ USOS ON
XFLOW ON XMITECHO ON    

SCS PTC

PK-232

Настройки PK-232

By John VK4WPX / VK4CEJ

Настройка PK-232 для работы RTTY весьма проста.

Setting up macros and the main logging window "F" keys for the PK-232 is also really very simple.

Настройки KAM

There are three parts in setting up N1MM logger to work with the KAM.

  1. Port configuration
  2. Digital configuration
  3. Macro Creation required to control the KAM

Настройки HAL DXP38

By Brian, K3KO

The following instructions will get the HAL DXP38 TNC up and running for FSK in N1MMLogger. I admit to not trying AFSK but it should work. This implementation is not elegant but does work with some 'features' of its own. There is a built-in tuning indicator accessible through macro toggles. The implementation is very basic but is working, there are other programs around if you want all the bells and whistles. Thanks go to N2AMG for making the program changes necessary to accommodate HAL commands.

Since there is essentially only one way communication between N1MMlogger and the DXP38 in the command mode, don't expect error checking or error detection. It is assumed that turning on the DXP38 properly loads the internal software. No capability exists here to do such. No capability exists to update the internal programs. This must be done with the HAL software. My unit uses the latest update .LOD and .S28 files from the HAL websitehttp://www.halcomm.com .It is not clear that the updated files are needed here. However, the reason given for the update was to fix a PTT error with another program. So if you are having problems with PTT activation, these updates may be appropriate. Unless you alter the attached initialization macro, you must use LSB RTTY for FSK or LSB for AFSK..

There are three distinct phases - Hardware setup, Software Setup, and Use. The last section discusses two problems that have cropped up and solutions found.

Hardware Set-up

It is recommended that one first get the DXP38 running with WF1B, HAL or a known 'tried and true' software package first. Doing so eliminates the need to troubleshoot both hardware and software when configuring N1MMLogger. Hardware setup:

  1. Connect the PTT and FSK lines to the rig
  2. Connect the COM port (1 for HAL software) to the TNC
  3. Connect audio input to the DXP-38
  4. Connecting the power.
  5. Connecting AFSK output to the rig (AFSK only)
  6. Consult the DXP-38 manuals for the details. The rig must be set FSK RTTY (LSB) or LSB for AFSK.

Software Setup in N1MM logger

There are three parts in setting up N1MM logger to work with the HAL DSP38. Make sure the version of N1MMLogger being used supports the DXP38 hexidecimal commands (version 3.0.187 and later).

Port configuration

Digital configuration

Macro Creation required to initialize and control the DXP38

Example Macro file (other 1.mc). This macro is available for download from the N1MM website (Other files)

*,-
INIZE,{H8084}{H8085}{H80D1}{H80C0}{H80DB}{H80D3}{H805B}{H8089}{H80E3}{H8002}{H80ED}{H8001}
                     {H80E8}{H8037}{H8000}{H805D}{H8059}{H800E}
*,-
RXinv,{H804C}
RXnorm,{H805C}
Echo y,{H8059}
*,-
*,-
SQlow,{H80E8}{H8015}
SQmid,{H80E8}{H8037}
SQhigh,{H80E8}{H8045}
B45,{H80E4}{H8000}{H800E}
*,-
Echo n,{H8049}
*,-
Tun Off,{H804D}
Fnar,{H80EB}{H8000}
Fmid,{H80EB}{H8001}
Fwide,{H80EB}{H8002}
*,-
*,-
*,-
*,-
Tun On,{H805D}
TX,{H800D}
RX,{H800E}
ESC,{H8006}

First time startup

Known problems

I have experienced some occasional problems on start-up and shutdown.

Startup - Sometimes the DXP38 and N1MM logger just don't want to communicate. The TNC won't accept the initialization commands. The cure is to shut off the TNC and wait about 45 seconds. Shutdown N1MM logger. Start up the TNC and wait until it has finished its internal initialization. (LED indicators have stopped flashing). Restart N1MMLogger. This may be a problem I have with the COM3 port here and you may never see it.

Shutdown - About half the time the DXP38 will go into the transmit mode when N1MMLogger is shutdown. The cure is to turn off the DXP38. Hopefully a more graceful shutdown can be developed.

Конфигурирование MMTTY

Получение дистрибутива MMTTY

Configure MMTTY

FSK KEYING

  1. In Main Config area 'Digital' tab.
  2. In Main Config area 'Hardware' tab.
  3. Save and exit If MMTTY is already loaded you will probably get an Error message about not being able to open port xxxx.
  4. Open the 'Digital Interface' and when MMTTY loads select: Settings/Setup MMTTY.
  5. Click the TX Settings pane in the MMTTY Setup area and set your serial port that you will be using for FSK keying and Data.
  6. Close the Setup Window and then close the Digital Interface to have MMTTY save the settings.
  7. From this point every time the Digital Interface loads It will NOT pass the port info to MMTTY. MMTTY will load the the serial settings from it's own settings file.

Using the RIGblaster interface for FSK with N1MM/MMTTY combo.

The default for FSK via MMTTY is TXD. You'll need to change the jumpers when using a Rigblaster. Also, make sure you get MMTTY working as a standalone first. Then you should just be able to specify MMTTY in the Digital Interface config in N1MM and it should take off. If you are lucky enough to have a radio where PTT is asserted via radio control ( Kenwood is one) then leave the PTT unchecked in the port setup and checked in the PTT via rig control portion.

AFSK KEYING

  1. In Main Config area 'Digital' tab.
  2. In Main Config area Hardware pane

SO2R : In order to use 2 copies of MMTTY you need to have 2 different keying comports setup for MMTTY to use. Also the second serial port must be a higher number than the first.. More info can be found in the SO2R chapter.

Testing MMTTY

MMTTY is also a stand alone application. So testing can be done outside N1MM logger.

Советы по использованию MMTTY

Как настроиться на RTTY сигнал

Периодически в окне MMTTY пропадает принимаемый сигнал, а N1MM logger аварийно завершает работу с сообщением об ошибке RTTY.

When should I use AFC

When should I use the NET option: NET On/Off with Run Change

Why to use "Auto Update TRX Offset w/Mark Freq."

Configure and test using a TNC

Configure the TNC

  1. Start the N1MM Logger application.
  2. On the Logger Main Window do a 'Config> Configure Ports, Telnet Address, Other'
  3. In Digital Setup
  4. Load the Digital Interface from the window menu.
  5. Create your Abort macro (This should be in the upper left corner) by right clicking on it. This will open up the RTTY setup area. Click on the same macro and enter what ever key sequence you need to abort transmission and save the macro.
    Example PK-232: {CTRL-C}R{ENTER}    and save the macro.
  6. You should be ready to copy RTTY make sure your interface is set to copy 45 baud and 170 shift. You can configure a macro key to change this or you can type the key sequence needed in the transmit window and it will get sent to the TNC.

That should be it. You will need to add the CTRL keys that turn on and off the TNC
Example CQ macro for the PK-232:    X{ENTER} CQ CQ CQ TEST DE {MYCALL} {MYCALL} K {CTRL-D}

Testing the TNC

Make a RTTY transmission

Name lookup

The program has the possibility to lookup the name from a station entered in the Callsign field. For this to happen the following has to be done.

Example how to import the Friend.ini file from the WF1B program.

Outputting RX data to a text file

Outputting your RX data to a text file can be done in N1MM logger and in MMTTY.

SO2R

N1MM logger also supports SO2R for RTTY. You can use any combination of either 2 MMTTY windows, 2 TNC windows or a combination of MMTTY and a TNC for SO2R operation. Info about MMTTY soundcard setup and SO2R can be found in the N1MM logger Help file in the SO2R chapter

Other Features

To get auto-CQ to work correctly with a TNC set you repeat time to at least 9 or 10 seconds. It may need to be longer if you have a longer CQ macro. This will stop the TNC buffer from receiving the next string before it finishes sending the last one.
It is best to add the command that your TNC uses to clear the transmit buffer to the end of your Abort Macro. If not, the transmit buffer still holds the remaining characters that were left in the sent string and will get sent the next time the TNC sends.
When using a TNC turn off Stop Sending CQ when Callsign changed this is located in the configuration area under function keys. If not every time you stop an auto-CQ and you type a callsign in the box it will send the abort string to the TNC.