Difference between revisions of "DX Cluster/Packet"

From Win-Test Wiki
Jump to navigation Jump to search
Line 10: Line 10:
To set-up TNC, open <tt>menu - options - configure interfaces</tt>. Setting up the right COM port parameters, the same as before in terminal program.
To set-up TNC, open <tt>menu - options - configure interfaces</tt>. Setting up the right COM port parameters, the same as before in terminal program.
== Checking the set-up works ==
== Checking the set-up works ==

Revision as of 19:36, 26 July 2006

TNC pre-test

Before you can use a TNC with Win-Test, it should tested before with a simple terminal program, not PAXON! Some TNC have different operating systems. Popularly are "The Firmware" (TF) and "KISS" mode. In Kiss mode, normally no connection is possible, I found now way. If it is, please let me know.

To make sure your TNC has the correct OS, use a simple terminal program, connect your TNC to a COM port, setting the right baud rate in the terminal program and switch on the TNC. If your TNC has the TF OS, after reset TNC a message should appear in the terminal program like "The Firmware Ver. 2.1..". If not, check cable and set-up. If the pre-test was successful, then set-up the TNC in Win-Test can be carried out now.

Win-Test TNC set-up

To set-up TNC, open menu - options - configure interfaces. Setting up the right COM port parameters, the same as before in terminal program.

Config TNC.jpg

Checking the set-up works

To check, the TNC set-up and connection is correct, open DX-Cluster monitor window (Alt+O). After resetting TNC, the same message must appear as before in the terminal program. If it doesn't works, set-up or cable is wrong.

Connecting node

Once you have configured the appropriate COM port for your TNC in Win-Test, you should be able to connect to your local node.

Open DX cluster window by using Alt+T to send a command to the TNC.

To control the TNC, you need control sequences. TNC control sequences always starts with ESC!

Pressing ESC in DX-Cluster window is not possible, the window will close.

To achieve a ESC control, you must press CTRL+E followed by the TNC command!

Check your call at first, whether this is stored in the TNC correctly. If not, no connection is possible. To check your call type in DX cluster window: CTRL+E I

You can see the TNC answer in the monitor window like: NO CALL or CALL DL8NAS.

If your call is wrong, type: CTRL+E I <call> (CTRL+I DL8NAS)

After reset, TNC is normally in cannel 0, no connection is possible, only viewing mode. The command to change to cannel 1 is: CTRL+E S1

Message in monitor window: CHANNEL NOT CONNECTED

The connect command to your local node: CTRL+E C<node> where <node> is the callsign of your local node.

You can follow the connection in the DX-cluster monitor window. When connection is made, than connect to your preferred DX-Cluster: It is important, that all commands after connecting are WITHOUT ESC! These are normal inputs in the DX-cluster window like: C DB0SDF-7 where C is the connect command to your local node, to connect to the DX cluster DB0SDF-7.

After connection to your preferred DX-cluster, you can use the buttons of the DX-CL window to show DX announcements.

You can use the packet monitor window (Alt+O) to check the connection status and to see data inbound from the TNC. Spots should begin filling up the bandmap at this stage.

Disconnecting node

To leave the DX cluster, normally bye command in DX-Cluster window. After reconnect to your local node, TNC command CTRL+E D disconnect from your local node.

Other important TNC commands are:

CTRL+E T16: set TX delay, normally around 16 (12..20)

A summary of TNC command set with TF OS can found here: The Firmware TF 2.6 Commands

26. Jul. 06 DL8NAS, Sigi

See also