https://docs.win-test.com/w/api.php?action=feedcontributions&user=DL8NAS&feedformat=atomWin-Test Wiki - User contributions [en]2024-03-29T14:56:18ZUser contributionsMediaWiki 1.35.0https://docs.win-test.com/w/index.php?title=DX_Cluster/Packet&diff=2207DX Cluster/Packet2006-09-25T19:33:33Z<p>DL8NAS: </p>
<hr />
<div>== TNC pre-test ==<br />
<br />
Before you can use a TNC with Win-Test, it should be tested first with a simple terminal program, not PAXON! Some TNC have different operating systems. Popularly are <tt>''"The Firmware"''</tt> (TF) and <tt>''"KISS"''</tt> mode. In Kiss mode, normally no connection is possible. I didn't find any successful way. If there is one, please let me know.<br />
<br />
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 the TNC on.<br />
If your TNC has the TF OS, a message should appear in the terminal program after reset of the TNC like <tt>"The Firmware Ver. 2.1.."</tt>. <br />
If not, check cable and set-up. If the pre-test was successful, then set-up the TNC in Win-Test it can now be carried out.<br />
<br />
== Win-Test TNC set-up ==<br />
<br />
To set-up TNC, open <tt>menu - options - configure interfaces</tt>. Setting up the right COM port parameters, the same as before in the terminal program.<br />
<br />
[[image:Config_TNC.jpg|center]]<br />
<br />
== Checking that the set-up works ==<br />
<br />
To check that the TNC set-up and the connection are correct, open DX-Cluster monitor window (<tt>Alt+O</tt>). After resetting the TNC, the same message should appear as before in the terminal program. If it doesn't work, set-up or cable is wrong.<br />
<br />
== Connecting node ==<br />
<br />
Once you have configured the appropriate COM port for your TNC in Win-Test, you should be able to connect to your local node.<br />
<br />
Open the DX cluster window by using <tt>Alt+T</tt> to send a command to the TNC.<br />
[[Image:dx-cluster.png]]<br />
To control the TNC, you need control sequences.<br />
TNC control sequences always start with '''ESC'''!<br />
<br />
Pressing ESC in the DX-Cluster window is not possible, the window will close.<br />
<br />
To achieve an '''ESC control''', you must press <tt>CTRL+E</tt> followed by the TNC command!<br />
<br />
Check your call sign first, whether this is stored in the TNC correctly. If not, no connection is possible. To check your call sign type in DX cluster window: <tt>CTRL+E I</tt><br />
<br />
You can see the TNC answer in the monitor window, e.g.: NO CALL or CALL DL8NAS.<br />
<br />
If your call sign is wrong, type: <tt>CTRL+E I <call></tt> (<tt>CTRL+I DL8NAS</tt>)<br />
<br />
After reset, the TNC is normally in channel 0, no connection is possible, only viewing mode. The command to change to channel 1 is: <tt>CTRL+E S1</tt><br />
<br />
Message in monitor window: <tt>CHANNEL NOT CONNECTED</tt><br />
<br />
The connect command to your local node: <tt>CTRL+E C<node></tt> where <node> is the callsign of your local node.<br />
<br />
You can follow the connection in the DX-cluster monitor window. When connection is made, then connect to your preferred DX-Cluster:<br />
It is important, that all commands after connecting are WITHOUT ESC!<br />
These are normal inputs in the DX-cluster window, e.g.: <tt>C DB0SDF-7</tt> where C is the connect command to your local node, to connect to the DX cluster DB0SDF-7.<br />
<br />
After connection to your preferred DX-cluster, you can use the buttons of the DX-CL window to show DX announcements.<br />
<br />
You can use the packet monitor window (<tt>Alt+O</tt>) to check the connection status and to see data are coming in from the TNC. Spots should begin filling up the bandmap at this stage.<br />
<br />
If no DX announcements come into the window, check also DX-Cluster options set-up:<br />
[[Image:dx-cluster-syntax.png]]<br />
<br />
== Disconnecting node ==<br />
<br />
To leave the DX cluster, use <tt>bye</tt> command in the DX-Cluster window. After reconnect to your local node, type the TNC command <tt>CTRL+E D</tt> to disconnect from your local node.<br />
<br />
Other important TNC commands are:<br />
<br />
<tt>CTRL+E T16</tt>: set TX delay, normally around 16 (12..20)<br />
<br />
A summary of TNC commands set with TF OS can be found here: [http://www.ralfzimmermann.de/tf26_2.html The Firmware TF 2.6 Commands] <br />
<br />
Sep. 25. 06, DL8NAS, Sigi<br />
<br />
== See also == <br />
<br />
* [[DX Cluster/Telnet|Connecting via telnet to a DX cluster]]<br />
* ...</div>DL8NAShttps://docs.win-test.com/w/index.php?title=Keys&diff=1833Keys2006-07-31T20:27:47Z<p>DL8NAS: /* Other keys */</p>
<hr />
<div>==Cursor's movement in the log==<br />
<br />
* Left arrow : Moves the cursor one character to the left<br />
* Right arrow : Moves the cursor one character to the right<br />
* Home (or Ctrl - Left arrow) : Moves the cursor to the left of the field<br />
* End (or Ctrl - Right arrow) : Moves the cursor to the beginning of the field<br />
* Backspace : Deletes the character located just before the cursor<br />
* Shift - Backspace : Deletes all the characters located before the cursor<br />
* Del : Deletes the character located under the cursor<br />
* Shift - Del : Deletes all the characters located after and under the cursor<br />
* Ctrl - W : Deletes the current field<br />
* F11 : Deletes all the fields of the current QSO, and locates the cursor in the callsign logging field<br />
<br />
==Movement between the different QSO fields==<br />
<br />
* Space bar : Toggles the cursor between the principal fields (Callsign and received report in HF; Callsign, received report and gridsquare in VHF)<br />
* Tab or < or > : Toggles the cursor between the possible logging fields<br />
<br />
==Movement in the log==<br />
<br />
Warning : Any movement in the log validates the QSO where the cursor was located before the movement !<br />
<br />
* Up arrow : Moves the cursor one QSO up in the log<br />
* Down arrow : Moves the cursor one QSO down in the log<br />
* PageUp : Moves the cursor 10 QSO up in the log<br />
* PageDown : Moves the cursor 10 QSO down in the log<br />
* Ctrl - Home : Moves the cursor to the first QSO of the log<br />
* Ctrl - End : Moves the cursor to the last QSO of the log<br />
<br />
==CW and SSB keyer==<br />
<br />
* F1 : Plays message n°1 (CW or Phone). Normally, this message is the CQ<br />
* F2 : Plays message n°2 (CW or Phone). Normally, this message is the report sent (full)<br />
* F3 : Plays message n°3 (CW or Phone). Normally, this message is the serial number sent<br />
* F4 : Plays message n°4 (CW or Phone). Normally, this message is your call<br />
* F5 : Plays message n°5 (CW or Phone). Normally, this message is the logged callsign<br />
* F6 : Plays message n°6 (CW only)<br />
* F7 : Plays message n°7 (CW only)<br />
* Insert : Plays the message definied for this key (CW only) : Normally, this message is the logged callsign the full sent report<br />
* + [Numerical pad] : Plays the message definied for this key (CW only) : Normally, this message sends a TU, then your callsign and automatically validates the logged QSO<br />
* Esc : Stops the output message being sent<br />
<br />
* Shift - F1 to Shift - F7 : Records the messages n°1 to n°7 (CW or Phone)<br />
* Shift - Insert : Records the message associated to the Insert key<br />
* Shift - + : Records the message associated to the + key<br />
<br />
* Alt - F9 : Decreases the speed by 2 WPM (CW only)<br />
* Alt - F10 : Increases the speed by 2 WPM (CW only)<br />
<br />
==Other keys==<br />
<br />
* - [Numerical pad] : Equivalent to Commands / Split frequency<br />
* * [Numerical pad] : Equivalent to Commands / Radio active / Active radio<br />
* F8 : Equivalent to Windows / Check partials<br />
* F9 : Equivalent to Windows / Check call<br />
* F10 : Equivalent to Windows / Check multipliers<br />
* shift-F10 : Display worked stations with that Multiplier by band in checkpartial window<br />
* F11 : Equivalent to Edit / Initialize QSO (see before)<br />
* F12 : Equivalent to Windows / Check partials<br />
<br />
* Alt - 1...9 : Grab nth call in partner window<br />
* Alt - Enter : Add call to partner window<br />
* Alt - : : Equivalent to Commands / Radio active / Active radio<br />
* Alt - A : Equivalent to Windows / DX-Cluster aanouncements<br />
* Alt - B : Equivalent to Windows / Skeds<br />
* Alt - C : Equivalent to Options / CW / Modify additional messages<br />
* Alt - D : Equivalent to Commands / Pass a station<br />
* Alt - E : Equivalent to Commands / Take a sked<br />
* Alt - F : Equivalent to Edit / QSO and time<br />
* Alt - G : Equivalent to Messages / Send a gab<br />
* Alt - I : Equivalent to Windows / Gab<br />
* Alt - J : Equivalent to Windows / Status<br />
* Alt - K : Equivalent to Commands / Keyboard mode<br />
* Alt - L : only in [[WAEDC]] - [[WAEDC|open QTC RX window]]<br />
* Alt - M : Equivalent to Windows / Worked DXCC<br />
* Alt - N : Equivalent to Messages / Write a note regarding this QSO<br />
* Alt - O : Equivalent to Windows / DX-Cluster monitor<br />
* Alt - R : Equivalent to Windows / Rate<br />
* Alt - S : Equivalent to Windows / Summary<br />
* Alt - T : Equivalent to Commands / DX-Cluster<br />
* Alt - W : Equivalent to Edit / Initialize QSO (see before)<br />
* Alt - Y : Toggles the current QSO from RUN to MULT in M/S category or from RUN1 to RUN2 in M/2 category and vice versa<br />
* Alt - Z : Equivalent to Windows / Worked zones<br />
* Alt - F1 : Equivalent to Commands / QSY / One band up<br />
* Alt - F2 : Equivalent to Commands / QSY / One band down<br />
* Alt - F3 : Equivalent to Commands / Spot<br />
* Alt - F4 : Equivalent to Commands / QSY to run frequency<br />
* Alt - F8 : Equivalent to Edit / Initialize QSO (see before)<br />
* Alt - Up arrow : Copy the previous QSO in the log<br />
<br />
* Ctrl - Enter : Equivalent to Commands / Insert into BandMap<br />
* Ctrl - Del : Deletes the spot of the current frequency in the active bandmap<br />
* Ctrl - G : Equivalent to Edit / Goto QSO<br />
* Ctrl - J : Equivalent to Commands / Insert into BandMap<br />
* Ctrl - L : only in [[WAEDC]] - [[WAEDC|open QTC TX window]]<br />
* Ctrl - F1 et Ctrl - F2 : Mode toggle (when the contest permits)<br />
* Ctrl - F3 : Toggles the current QSO from RUN to MULT in M/S category or from RUN1 to RUN2 in M/2 category and vice versa<br />
* Ctrl - F9 : Equivalent to Windows / Rate sheet<br />
* Ctrl - Up arrow : Grabs the first upper spot in the active bandmap (in frequency regarding the active radio)<br />
* Ctrl - Shift - Up arrow : Grabs the first upper spot in the active bandmap (in frequency regarding the active radio), even if it is a 0-point station<br />
* Ctrl - Down arrow : Grabs the first lower spot in the active bandmap (in frequency regarding the active radio)<br />
* Ctrl - Shift - Down arrow : Grabs the first lower spot in the active bandmap (in frequency regarding the active radio), even if it is a 0-point station<br />
<br />
<br />
<br />
[[Main Page|Back to Main Page]]</div>DL8NAShttps://docs.win-test.com/w/index.php?title=DX_Cluster/Packet&diff=1650DX Cluster/Packet2006-07-27T17:47:51Z<p>DL8NAS: </p>
<hr />
<div>== TNC pre-test ==<br />
<br />
Before you can use a TNC with Win-Test, it should be tested first with a simple terminal program, not PAXON! Some TNC have different operating systems. Popularly are <tt>''"The Firmware"''</tt> (TF) and <tt>''"KISS"''</tt> mode. In Kiss mode, normally no connection is possible. I didn't find any successful way. If there is, please let me know.<br />
<br />
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.<br />
If your TNC has the TF OS, after reset TNC a message should appear in the terminal program like <tt>"The Firmware Ver. 2.1.."</tt>. <br />
If not, check cable and set-up. If the pre-test was successful, then set-up the TNC in Win-Test it can now be carried out.<br />
<br />
== Win-Test TNC set-up ==<br />
<br />
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.<br />
<br />
[[image:Config_TNC.jpg|center]]<br />
<br />
== Checking that the set-up works ==<br />
<br />
To check that the TNC set-up and connection is correct, open DX-Cluster monitor window (<tt>Alt+O</tt>). After resetting TNC, the same message should appear as before in the terminal program. If it doesn't work, set-up or cable is wrong.<br />
<br />
== Connecting node ==<br />
<br />
Once you have configured the appropriate COM port for your TNC in Win-Test, you should be able to connect to your local node.<br />
<br />
Open DX cluster window by using <tt>Alt+T</tt> to send a command to the TNC.<br />
[[Image:dx-cluster.png]]<br />
To control the TNC, you need control sequences.<br />
TNC control sequences always starts with '''ESC'''!<br />
<br />
Pressing ESC in DX-Cluster window is not possible, the window will close.<br />
<br />
To achieve an '''ESC control''', you must press <tt>CTRL+E</tt> followed by the TNC command!<br />
<br />
Check your call sign first, whether this is stored in the TNC correctly. If not, no connection is possible. To check your call sign type in DX cluster window: <tt>CTRL+E I</tt><br />
<br />
You can see the TNC answer in the monitor window, e.g.: NO CALL or CALL DL8NAS.<br />
<br />
If your call sign is wrong, type: <tt>CTRL+E I <call></tt> (<tt>CTRL+I DL8NAS</tt>)<br />
<br />
After reset, TNC is normally in channel 0, no connection is possible, only viewing mode. The command to change to channel 1 is: <tt>CTRL+E S1</tt><br />
<br />
Message in monitor window: <tt>CHANNEL NOT CONNECTED</tt><br />
<br />
The connect command to your local node: <tt>CTRL+E C<node></tt> where <node> is the callsign of your local node.<br />
<br />
You can follow the connection in the DX-cluster monitor window. When connection is made, then connect to your preferred DX-Cluster:<br />
It is important, that all commands after connecting are WITHOUT ESC!<br />
These are normal inputs in the DX-cluster window, e.g.: <tt>C DB0SDF-7</tt> where C is the connect command to your local node, to connect to the DX cluster DB0SDF-7.<br />
<br />
After connection to your preferred DX-cluster, you can use the buttons of the DX-CL window to show DX announcements.<br />
<br />
You can use the packet monitor window (<tt>Alt+O</tt>) to check the connection status and to see data inbound from the TNC. Spots should begin filling up the bandmap at this stage.<br />
<br />
If not DX announcements come into the window, check also DX-Cluster options set-up:<br />
[[Image:dx-cluster-syntax.png]]<br />
<br />
== Disconnecting node ==<br />
<br />
To leave the DX cluster, use <tt>bye</tt> command in DX-Cluster window. After reconnect to your local node, TNC command <tt>CTRL+E D</tt> to disconnect from your local node.<br />
<br />
Other important TNC commands are:<br />
<br />
<tt>CTRL+E T16</tt>: set TX delay, normally around 16 (12..20)<br />
<br />
A summary of TNC commands set with TF OS can be found here: [http://www.ralfzimmermann.de/tf26_2.html The Firmware TF 2.6 Commands] <br />
<br />
Jul. 27. 06, DL8NAS, Sigi<br />
<br />
== See also == <br />
<br />
* [[DX Cluster/Telnet|Connecting via telnet to a DX cluster]]<br />
* ...</div>DL8NAShttps://docs.win-test.com/w/index.php?title=DX_Cluster/Packet&diff=1609DX Cluster/Packet2006-07-26T18:55:57Z<p>DL8NAS: </p>
<hr />
<div>== TNC pre-test ==<br />
<br />
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 <tt>''"The Firmware"''</tt> (TF) and <tt>''"KISS"''</tt> mode. In Kiss mode, normally no connection is possible, I found now way. If it is, please let me know.<br />
<br />
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.<br />
If your TNC has the TF OS, after reset TNC a message should appear in the terminal program like <tt>"The Firmware Ver. 2.1.."</tt>. <br />
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.<br />
<br />
== Win-Test TNC set-up ==<br />
<br />
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.<br />
<br />
[[image:Config_TNC.jpg|center]]<br />
<br />
== Checking the set-up works ==<br />
<br />
To check, the TNC set-up and connection is correct, open DX-Cluster monitor window (<tt>Alt+O</tt>). 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.<br />
<br />
== Connecting node ==<br />
<br />
Once you have configured the appropriate COM port for your TNC in Win-Test, you should be able to connect to your local node.<br />
<br />
Open DX cluster window by using <tt>Alt+T</tt> to send a command to the TNC.<br />
<br />
To control the TNC, you need control sequences.<br />
TNC control sequences always starts with '''ESC'''!<br />
<br />
Pressing ESC in DX-Cluster window is not possible, the window will close.<br />
<br />
To achieve a '''ESC control''', you must press <tt>CTRL+E</tt> followed by the TNC command!<br />
<br />
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: <tt>CTRL+E I</tt><br />
<br />
You can see the TNC answer in the monitor window like: NO CALL or CALL DL8NAS.<br />
<br />
If your call is wrong, type: <tt>CTRL+E I <call></tt> (<tt>CTRL+I DL8NAS</tt>)<br />
<br />
After reset, TNC is normally in cannel 0, no connection is possible, only viewing mode. The command to change to cannel 1 is: <tt>CTRL+E S1</tt><br />
<br />
Message in monitor window: <tt>CHANNEL NOT CONNECTED</tt><br />
<br />
The connect command to your local node: <tt>CTRL+E C<node></tt> where <node> is the callsign of your local node.<br />
<br />
You can follow the connection in the DX-cluster monitor window. When connection is made, than connect to your preferred DX-Cluster:<br />
It is important, that all commands after connecting are WITHOUT ESC!<br />
These are normal inputs in the DX-cluster window like: <tt>C DB0SDF-7</tt> where C is the connect command to your local node, to connect to the DX cluster DB0SDF-7.<br />
<br />
After connection to your preferred DX-cluster, you can use the buttons of the DX-CL window to show DX announcements.<br />
<br />
You can use the packet monitor window (<tt>Alt+O</tt>) to check the connection status and to see data inbound from the TNC. Spots should begin filling up the bandmap at this stage.<br />
<br />
If not DX announcements comes into, check also DX-Cluster options set-up:<br />
<br />
<tt>Options> DX CLuster shortcuts> Syntax> DXSpider</TT><br />
<br />
or<br />
<br />
<tt>Options> DX CLuster shortcuts> Syntax> DXNet, AK1A..</TT> <br />
<br />
== Disconnecting node ==<br />
<br />
To leave the DX cluster, normally <tt>bye</tt> command in DX-Cluster window. After reconnect to your local node, TNC command <tt>CTRL+E D</tt> disconnect from your local node.<br />
<br />
Other important TNC commands are:<br />
<br />
<tt>CTRL+E T16</tt>: set TX delay, normally around 16 (12..20)<br />
<br />
A summary of TNC command set with TF OS can found here: [http://www.ralfzimmermann.de/tf26_2.html The Firmware TF 2.6 Commands] <br />
<br />
26. Jul. 06<br />
DL8NAS, Sigi<br />
<br />
== See also == <br />
<br />
* [[DX Cluster/Telnet|Connecting via telnet to a DX cluster]]<br />
* ...</div>DL8NAShttps://docs.win-test.com/w/index.php?title=DX_Cluster/Packet&diff=1608DX Cluster/Packet2006-07-26T18:36:49Z<p>DL8NAS: </p>
<hr />
<div>== TNC pre-test ==<br />
<br />
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 <tt>''"The Firmware"''</tt> (TF) and <tt>''"KISS"''</tt> mode. In Kiss mode, normally no connection is possible, I found now way. If it is, please let me know.<br />
<br />
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.<br />
If your TNC has the TF OS, after reset TNC a message should appear in the terminal program like <tt>"The Firmware Ver. 2.1.."</tt>. <br />
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.<br />
<br />
== Win-Test TNC set-up ==<br />
<br />
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.<br />
<br />
[[image:Config_TNC.jpg|center]]<br />
<br />
== Checking the set-up works ==<br />
<br />
To check, the TNC set-up and connection is correct, open DX-Cluster monitor window (<tt>Alt+O</tt>). 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.<br />
<br />
== Connecting node ==<br />
<br />
Once you have configured the appropriate COM port for your TNC in Win-Test, you should be able to connect to your local node.<br />
<br />
Open DX cluster window by using <tt>Alt+T</tt> to send a command to the TNC.<br />
<br />
To control the TNC, you need control sequences.<br />
TNC control sequences always starts with '''ESC'''!<br />
<br />
Pressing ESC in DX-Cluster window is not possible, the window will close.<br />
<br />
To achieve a '''ESC control''', you must press <tt>CTRL+E</tt> followed by the TNC command!<br />
<br />
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: <tt>CTRL+E I</tt><br />
<br />
You can see the TNC answer in the monitor window like: NO CALL or CALL DL8NAS.<br />
<br />
If your call is wrong, type: <tt>CTRL+E I <call></tt> (<tt>CTRL+I DL8NAS</tt>)<br />
<br />
After reset, TNC is normally in cannel 0, no connection is possible, only viewing mode. The command to change to cannel 1 is: <tt>CTRL+E S1</tt><br />
<br />
Message in monitor window: <tt>CHANNEL NOT CONNECTED</tt><br />
<br />
The connect command to your local node: <tt>CTRL+E C<node></tt> where <node> is the callsign of your local node.<br />
<br />
You can follow the connection in the DX-cluster monitor window. When connection is made, than connect to your preferred DX-Cluster:<br />
It is important, that all commands after connecting are WITHOUT ESC!<br />
These are normal inputs in the DX-cluster window like: <tt>C DB0SDF-7</tt> where C is the connect command to your local node, to connect to the DX cluster DB0SDF-7.<br />
<br />
After connection to your preferred DX-cluster, you can use the buttons of the DX-CL window to show DX announcements.<br />
<br />
You can use the packet monitor window (<tt>Alt+O</tt>) to check the connection status and to see data inbound from the TNC. Spots should begin filling up the bandmap at this stage.<br />
<br />
== Disconnecting node ==<br />
<br />
To leave the DX cluster, normally <tt>bye</tt> command in DX-Cluster window. After reconnect to your local node, TNC command <tt>CTRL+E D</tt> disconnect from your local node.<br />
<br />
Other important TNC commands are:<br />
<br />
<tt>CTRL+E T16</tt>: set TX delay, normally around 16 (12..20)<br />
<br />
A summary of TNC command set with TF OS can found here: [http://www.ralfzimmermann.de/tf26_2.html The Firmware TF 2.6 Commands] <br />
<br />
26. Jul. 06<br />
DL8NAS, Sigi<br />
<br />
== See also == <br />
<br />
* [[DX Cluster/Telnet|Connecting via telnet to a DX cluster]]<br />
* ...</div>DL8NAShttps://docs.win-test.com/w/index.php?title=File:Config_TNC.jpg&diff=1607File:Config TNC.jpg2006-07-26T18:27:22Z<p>DL8NAS: </p>
<hr />
<div></div>DL8NAShttps://docs.win-test.com/w/index.php?title=DX_Cluster/Packet&diff=1606DX Cluster/Packet2006-07-26T18:18:42Z<p>DL8NAS: </p>
<hr />
<div>== TNC pre-test ==<br />
<br />
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 <tt>''"The Firmware"''</tt> (TF) and <tt>''"KISS"''</tt> mode. In Kiss mode, normally no connection is possible, I found now way. If it is, please let me know.<br />
<br />
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.<br />
If your TNC has the TF OS, after reset TNC a message should appear in the terminal program like <tt>"The Firmware Ver. 2.1.."</tt>. <br />
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.<br />
<br />
== Win-Test TNC set-up ==<br />
<br />
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.<br />
<br />
== Checking the set-up works ==<br />
<br />
To check, the TNC set-up and connection is correct, open DX-Cluster monitor window (<tt>Alt+O</tt>). 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.<br />
<br />
== Connecting node ==<br />
<br />
Once you have configured the appropriate COM port for your TNC in Win-Test, you should be able to connect to your local node.<br />
<br />
Open DX cluster window by using <tt>Alt+T</tt> to send a command to the TNC.<br />
<br />
To control the TNC, you need control sequences.<br />
TNC control sequences always starts with '''ESC'''!<br />
<br />
Pressing ESC in DX-Cluster window is not possible, the window will close.<br />
<br />
To achieve a '''ESC control''', you must press <tt>CTRL+E</tt> followed by the TNC command!<br />
<br />
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: <tt>CTRL+E I</tt><br />
<br />
You can see the TNC answer in the monitor window like: NO CALL or CALL DL8NAS.<br />
<br />
If your call is wrong, type: <tt>CTRL+E I <call></tt> (<tt>CTRL+I DL8NAS</tt>)<br />
<br />
After reset, TNC is normally in cannel 0, no connection is possible, only viewing mode. The command to change to cannel 1 is: <tt>CTRL+E S1</tt><br />
<br />
Message in monitor window: <tt>CHANNEL NOT CONNECTED</tt><br />
<br />
The connect command to your local node: <tt>CTRL+E C<node></tt> where <node> is the callsign of your local node.<br />
<br />
You can follow the connection in the DX-cluster monitor window. When connection is made, than connect to your preferred DX-Cluster:<br />
It is important, that all commands after connecting are WITHOUT ESC!<br />
These are normal inputs in the DX-cluster window like: <tt>C DB0SDF-7</tt> where C is the connect command to your local node, to connect to the DX cluster DB0SDF-7.<br />
<br />
After connection to your preferred DX-cluster, you can use the buttons of the DX-CL window to show DX announcements.<br />
<br />
You can use the packet monitor window (<tt>Alt+O</tt>) to check the connection status and to see data inbound from the TNC. Spots should begin filling up the bandmap at this stage.<br />
<br />
== Disconnecting node ==<br />
<br />
To leave the DX cluster, normally <tt>bye</tt> command in DX-Cluster window. After reconnect to your local node, TNC command <tt>CTRL+E D</tt> disconnect from your local node.<br />
<br />
Other important TNC commands are:<br />
<br />
<tt>CTRL+E T16</tt>: set TX delay, normally around 16 (12..20)<br />
<br />
A summary of TNC command set with TF OS can found here: [http://www.ralfzimmermann.de/tf26_2.html The Firmware TF 2.6 Commands] <br />
<br />
26. Jul. 06<br />
DL8NAS, Sigi<br />
<br />
== See also == <br />
<br />
* [[DX Cluster/Telnet|Connecting via telnet to a DX cluster]]<br />
* ...</div>DL8NAShttps://docs.win-test.com/w/index.php?title=DX_Cluster/Packet&diff=1605DX Cluster/Packet2006-07-26T18:13:43Z<p>DL8NAS: </p>
<hr />
<div>== TNC pre-test ==<br />
<br />
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 <tt>''"The Firmware"''</tt> (TF) and <tt>''"KISS"''</tt> mode. In Kiss mode, normally no connection is possible, I found now way. If it is, please let me know.<br />
<br />
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.<br />
If your TNC has the TF OS, after reset TNC a message should appear in the terminal program like <tt>"The Firmware Ver. 2.1.."</tt>. <br />
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.<br />
<br />
== Win-Test TNC set-up ==<br />
<br />
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.<br />
<br />
== Checking the set-up works ==<br />
<br />
To check, the TNC set-up and connection is correct, open DX-Cluster monitor window (<tt>Alt+O</tt>). 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.<br />
<br />
== Connecting node ==<br />
<br />
Once you have configured the appropriate COM port for your TNC in Win-Test, you should be able to connect to your local node.<br />
<br />
Open DX cluster window by using <tt>Alt+T</tt> to send a command to the TNC.<br />
<br />
To control the TNC, you need control sequences.<br />
TNC control sequences always starts with '''ESC'''!<br />
<br />
Pressing ESC in DX-Cluster window is not possible, the window will close.<br />
<br />
To achieve a '''ESC control''', you must press <tt>CTRL+E</tt> followed by the TNC command!<br />
<br />
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: <tt>CTRL+E I</tt><br />
<br />
You can see the answer in the monitor window like: NO CALL or CALL DL8NAS.<br />
<br />
If your call is wrong, type: <tt>CTRL+E I <call></tt> (<tt>CTRL+I DL8NAS</tt>)<br />
<br />
After reset, TNC is normally in cannel 0, no connection is possible, only viewing mode. The command to change to cannel 1 is: <tt>CTRL+E S1</tt><br />
<br />
Message in monitor window: <tt>CHANNEL NOT CONNECTED</tt><br />
<br />
The connect command to your local node: <tt>CTRL+E C<node></tt> where <node> is the callsign of your local node.<br />
<br />
You can follow the connection in the DX-cluster monitor window. When connection is made, than connect to your preferred DX-Cluster:<br />
It is important, that all commands after connecting are WITHOUT ESC!<br />
These are normal inputs in the DX-cluster window like: <tt>C DB0SDF-7</tt> where C is the connect command to your local node, to connect to the DX cluster DB0SDF-7.<br />
<br />
After connection to your preferred DX-cluster, you can use the buttons of the DX-CL window to show DX announcements.<br />
<br />
You can use the packet monitor window (<tt>Alt+O</tt>) to check the connection status and to see data inbound from the TNC. Spots should begin filling up the bandmap at this stage.<br />
<br />
== Disconnecting node ==<br />
<br />
To leave the DX cluster, normally <tt>bye</tt> command in DX-Cluster window. After reconnect to your local node, TNC command <tt>CTRL+E D</tt> disconnect from your local node.<br />
<br />
Other important TNC commands are:<br />
<br />
<tt>CTRL+E T16</tt>: set TX delay, normally around 16 (12..20)<br />
<br />
A summary of TNC command set with TF OS can found here: [http://www.ralfzimmermann.de/tf26_2.html The Firmware TF 2.6 Commands] <br />
<br />
26. Jul. 06<br />
DL8NAS, Sigi<br />
<br />
== See also == <br />
<br />
* [[DX Cluster/Telnet|Connecting via telnet to a DX cluster]]<br />
* ...</div>DL8NAShttps://docs.win-test.com/w/index.php?title=DX_Cluster/Packet&diff=1604DX Cluster/Packet2006-07-26T18:09:12Z<p>DL8NAS: </p>
<hr />
<div>== TNC pre-test ==<br />
<br />
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 <tt>''"The Firmware"''</tt> (TF) and <tt>''"KISS"''</tt> mode. In Kiss mode, normally no connection is possible, I found now way. If it is, please let me know.<br />
<br />
To make sure your TNC has the correct OS, use a simple terminal program, connect to a COM port, setting the right baud rate and switch on the TNC.<br />
If your TNC has the TF OS, after reset TNC a message should appear in the terminal program like <tt>"The Firmware Ver. 2.1.."</tt>. <br />
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.<br />
<br />
== Win-Test TNC set-up ==<br />
<br />
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.<br />
<br />
== Checking the set-up works ==<br />
<br />
To check, the TNC set-up and connection is correct, open DX-Cluster monitor window (<tt>Alt+O</tt>). 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.<br />
<br />
== Connecting node ==<br />
<br />
Once you have configured the appropriate COM port for your TNC in Win-Test, you should be able to connect to your local node.<br />
<br />
Open DX cluster window by using <tt>Alt+T</tt> to send a command to the TNC.<br />
<br />
To control the TNC, you need control sequences.<br />
TNC control sequences always starts with '''ESC'''!<br />
<br />
Pressing ESC in DX-Cluster window is not possible, the window will close.<br />
<br />
To achieve a '''ESC control''', you must press <tt>CTRL+E</tt> followed by the TNC command!<br />
<br />
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: <tt>CTRL+E I</tt><br />
<br />
You can see the answer in the monitor window like: NO CALL or CALL DL8NAS.<br />
<br />
If your call is wrong, type: <tt>CTRL+E I <call></tt> (<tt>CTRL+I DL8NAS</tt>)<br />
<br />
After reset, TNC is normally in cannel 0, no connection is possible, only viewing mode. The command to change to cannel 1 is: <tt>CTRL+E S1</tt><br />
<br />
Message in monitor window: <tt>CHANNEL NOT CONNECTED</tt><br />
<br />
The connect command to your local node: <tt>CTRL+E C<node></tt> where <node> is the callsign of your local node.<br />
<br />
You can follow the connection in the DX-cluster monitor window. When connection is made, than connect to your preferred DX-Cluster:<br />
It is important, that all commands after connecting are WITHOUT ESC!<br />
These are normal inputs in the DX-cluster window like: <tt>C DB0SDF-7</tt> where C is the connect command to your local node, to connect to the DX cluster DB0SDF-7.<br />
<br />
After connection to your preferred DX-cluster, you can use the buttons of the DX-CL window to show DX announcements.<br />
<br />
You can use the packet monitor window (<tt>Alt+O</tt>) to check the connection status and to see data inbound from the TNC. Spots should begin filling up the bandmap at this stage.<br />
<br />
== Disconnecting node ==<br />
<br />
To leave the DX cluster, normally <tt>bye</tt> command in DX-Cluster window. After reconnect to your local node, TNC command <tt>CTRL+E D</tt> disconnect from your local node.<br />
<br />
Other important TNC commands are:<br />
<br />
<tt>CTRL+E T16</tt>: set TX delay, normally around 16 (12..20)<br />
<br />
A summary of TNC command set with TF OS can found here: [http://www.ralfzimmermann.de/tf26_2.html The Firmware TF 2.6 Commands] <br />
<br />
26. Jul. 06<br />
DL8NAS, Sigi<br />
<br />
== See also == <br />
<br />
* [[DX Cluster/Telnet|Connecting via telnet to a DX cluster]]<br />
* ...</div>DL8NAShttps://docs.win-test.com/w/index.php?title=DX_Cluster/Packet&diff=1457DX Cluster/Packet2006-07-23T18:08:10Z<p>DL8NAS: </p>
<hr />
<div>== TNC pre-test ==<br />
<br />
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 <tt>''"The Firmware"''</tt> (TF) and <tt>''"KISS"''</tt> mode. In Kiss mode, no connection is possible.<p><br />
To make sure your TNC has the correct OS, use a simple terminal program, connect to a COM port, setting the right baud rate and switch on the TNC.<br />
If your TNC has the TF OS, after reset TNC a message should appear in the terminal program like <tt>"The Firmware Ver. 2.1.."</tt>. <br />
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.<br />
<br />
== Win-Test TNC set-up ==<br />
<br />
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.<br />
<br />
== Checking the set-up works ==<br />
<br />
To check, the TNC set-up and connection is correct, open DX-Cluster monitor window (<tt>Alt+O</tt>). 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.<br />
<br />
== Connecting node ==<br />
<br />
Once you have configured the appropriate COM port for your TNC in Win-Test, you should be able to connect to your local node.<br />
<br />
Open DX cluster window by using <tt>Alt+T</tt> to send a command to the TNC.<br />
<br />
To control the TNC, you need control sequences.<br />
TNC control sequences always starts with '''ESC'''!<br />
<br />
Pressing ESC in DX-Cluster window is not possible, the window will close.<br />
<br />
To achieve a '''ESC control''', you must press <tt>CTRL+E</tt> followed by the TNC command!<br />
<br />
After reset, TNC is normally in cannel 0, no connection is possible, only viewing mode. The command to change to cannel 1 is: <tt>CTRL+E S1</tt><br />
<br />
Message in monitor window: <tt>CHANNEL NOT CONNECTED</tt><br />
<br />
The connect command to your local node: <tt>CTRL+E C<node></tt> where <node> is the callsign of your local node.<br />
<br />
You can follow the connection in the DX-cluster monitor window. When connection is made, than connect to your preferred DX-Cluster:<br />
It is important, that all commands after connecting are WITHOUT ESC!<br />
These are normal inputs in the DX-cluster window like: <tt>C DB0SDF-7</tt> where C is the connect command for your local node, to connect to the DX cluster DB0SDF-7.<br />
<br />
After connection to your preferred DX-cluster, you can use the buttons of the DX-CL window to show DX announcements.<br />
<br />
You can use the packet monitor window (<tt>Alt+O</tt>) to check the connection status and to see data inbound from the TNC. Spots should begin filling up the bandmap at this stage.<br />
<br />
== Disconnecting node ==<br />
<br />
To leave the DX cluster, normally <tt>bye</tt> command in DX-Cluster window. After reconnect to your local node, TNC command <tt>CTRL+E D</tt> disconnect from your local node.<br />
<br />
Other important TNC commands are:<br />
<br />
<tt>CTRL+E I</tt>: set your own call to TNC (<tt>CTRL+E I DL8NAS</tt>)<br />
<br />
<tt>CTRL+E T16</tt>: set TX delay, normally around 16 (12..20)<br />
<br />
A summary of TNC command set with TF OS can found here: [http://www.ralfzimmermann.de/tf26_2.html The Firmware TF 2.6 Commands]<br />
<br />
<br />
06 Jul. 23, DL8NAS, Sigi<br />
<br />
== See also == <br />
<br />
* [[DX Cluster/Telnet|Connecting via telnet to a DX cluster]]<br />
* ...</div>DL8NAShttps://docs.win-test.com/w/index.php?title=DX_Cluster/Packet&diff=1456DX Cluster/Packet2006-07-23T18:02:19Z<p>DL8NAS: </p>
<hr />
<div>== TNC pre-test ==<br />
<br />
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 <tt>''"The Firmware"''</tt> (TF) and <tt>''"KISS"''</tt> mode. In Kiss mode, no connection is possible.<p><br />
To make sure your TNC has the correct OS, use a simple terminal program, connect to a COM port, setting the right baud rate and switch on the TNC.<br />
If your TNC has the TF OS, after reset TNC a message should appear in the terminal program like <tt>"The Firmware Ver. 2.1.."</tt>. <br />
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.<br />
<br />
== Win-Test TNC set-up ==<br />
<br />
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.<br />
<br />
== Checking the set-up works ==<br />
<br />
To check, the TNC set-up and connection is correct, open DX-Cluster monitor window (<tt>Alt+O</tt>). 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.<br />
<br />
== Connecting node ==<br />
<br />
Once you have configured the appropriate COM port for your TNC in Win-Test, you should be able to connect to your local node.<br />
<br />
Open DX cluster window by using <tt>Alt+T</tt> to send a command to the TNC.<br />
<br />
To control the TNC, you need control sequences.<br />
TNC control sequences always starts with '''ESC'''!<br />
<br />
Pressing ESC in DX-Cluster window is not possible, the window will close.<br />
<br />
To achieve a '''ESC control''', you must press <tt>CTRL+E</tt> followed by the TNC command!<br />
<br />
After reset, TNC is normally in cannel 0, no connection is possible, only viewing mode. The command to change to cannel 1 is: <tt>CTRL+E S1</tt><br />
<br />
Message in monitor window: <tt>CHANNEL NOT CONNECTED</tt><br />
<br />
The connect command to your local node: <tt>CTRL+E C<node></tt> where <node> is the callsign of your local node.<br />
<br />
You can follow the connection in the DX-cluster monitor window. When connection is made, than connect to your preferred DX-Cluster:<br />
It is important, that all commands after connecting are WITHOUT ESC!<br />
These are normal inputs in the DX-cluster window like: <tt>C DB0SDF-7</tt> where C is the connect command to your local node, to connect to the DX cluster DB0SDF-7.<br />
<br />
After connection to your preferred DX-cluster, you can use the buttons of the DX-CL window to show DX announcements.<br />
<br />
You can use the packet monitor window (<tt>Alt+O</tt>) to check the connection status and to see data inbound from the TNC. Spots should begin filling up the bandmap at this stage.<br />
<br />
== Disconnecting node ==<br />
<br />
To leave the DX cluster, normally <tt>bye</tt> command in DX-Cluster window. After reconnect to your local node, TNC command <tt>CTRL+E D</tt> disconnect from your local node.<br />
<br />
Other important TNC commands are:<br />
<br />
<tt>CTRL+E I</tt>: set your own call to TNC (<tt>CTRL+E I DL8NAS</tt>)<br />
<br />
<tt>CTRL+E T16</tt>: set TX delay, normally around 16 (12..20)<br />
<br />
A summary of TNC command set with TF OS can found here: [http://www.ralfzimmermann.de/tf26_2.html The Firmware TF 2.6 Commands]<br />
<br />
<br />
06 Jul. 23, DL8NAS, Sigi<br />
<br />
== See also == <br />
<br />
* [[DX Cluster/Telnet|Connecting via telnet to a DX cluster]]<br />
* ...</div>DL8NAShttps://docs.win-test.com/w/index.php?title=DX_Cluster/Packet&diff=1455DX Cluster/Packet2006-07-23T17:50:51Z<p>DL8NAS: </p>
<hr />
<div>== TNC pre-test ==<br />
<br />
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 <tt>''"The Firmware"''</tt> (TF) and <tt>''"KISS"''</tt> mode. In Kiss mode, no connection is possible.<p><br />
To make sure your TNC has the correct OS, use a simple terminal program, connect to a COM port, setting the right baud rate and switch on the TNC.<br />
If your TNC has the TF OS, after reset TNC a message should appear in the terminal program like <tt>"The Firmware Ver. 2.1.."</tt>. <br />
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.<br />
<br />
== Win-Test TNC set-up ==<br />
<br />
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.<br />
<br />
== Checking the set-up works ==<br />
<br />
To check, the TNC set-up and connection is correct, open DX-Cluster monitor window (<tt>Alt+O</tt>). 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.<br />
<br />
== Connecting node ==<br />
<br />
Once you have configured the appropriate COM port for your TNC in Win-Test, you should be able to connect to your local node.<br />
<br />
Open DX cluster window by using <tt>Alt+T</tt> to send a command to the TNC.<br />
<br />
To control the TNC, you need control sequences.<br />
TNC control sequences always starts with '''ESC'''!<br />
<br />
Pressing ESC in DX-Cluster window is not possible, the window will close.<br />
<br />
To achieve a '''ESC control''', you must press <tt>CTRL+E</tt> followed by the TNC command!<br />
<br />
After reset, TNC is normally in cannel 0, no connection is possible, only viewing mode. The command to change to cannel 1 is: <tt>CTRL+E S1</tt><br />
<br />
Message in monitor window: <tt>CHANNEL NOT CONNECTED</tt><br />
<br />
The connect command to your local node: <tt>CTRL+E C<node></tt> where <node> is the callsign of your local node.<br />
<br />
You can follow the connection in the DX-cluster monitor window. When connection is made, than connect to your preferred DX-Cluster:<br />
It is important, that all commands after connecting are WITHOUT ESC!<br />
These are normal inputs in the DX-cluster window like: <tt>C DB0SDF-7</tt> where C is the connect command to your local node, to connect to the DX cluster DB0SDF-7.<br />
<br />
After connection to your preferred DX-cluster, you can use the buttons of the DX-CL window to show DX announcements.<br />
<br />
You can use the packet monitor window (<tt>Alt+O</tt>) to check the connection status and to see data inbound from the TNC. Spots should begin filling up the bandmap at this stage.<br />
<br />
== Disconnecting node ==<br />
<br />
To leave the DX cluster, normally <tt>bye</tt> command in DX-Cluster window. After reconnect to your local node, TNC command <tt>CTRL+E D</tt> disconnect from your local node.<br />
<br />
Other important TNC commands are:<br />
<br />
<tt>CTRL+E I</tt>: set your own call to TNC (<tt>CTRL+E I DL8NAS</tt>)<br />
<br />
<tt>CTRL+E T16</tt>: set TX delay, normally around 16 (12..20)<br />
<br />
<br />
23. Jul. 06<br />
DL8NAS, Sigi<br />
<br />
== See also == <br />
<br />
* [[DX Cluster/Telnet|Connecting via telnet to a DX cluster]]<br />
* ...</div>DL8NAShttps://docs.win-test.com/w/index.php?title=DX_Cluster/Packet&diff=1454DX Cluster/Packet2006-07-23T17:33:06Z<p>DL8NAS: /* Disconnecting node */</p>
<hr />
<div>== TNC pre-test ==<br />
<br />
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 <tt>''"The Firmware"''</tt> (TF) and <tt>''"KISS"''</tt> mode. In Kiss mode, no connection is possible.<p><br />
To make sure your TNC has the correct OS, use a simple terminal program, connect to a COM port, setting the right baud rate and switch on the TNC.<br />
If your TNC has the TF OS, after reset TNC a message should appear in the terminal program like <tt>"The Firmware Ver. 2.1.."</tt>. <br />
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.<br />
<br />
== Win-Test TNC set-up ==<br />
<br />
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.<br />
<br />
== Checking the set-up works ==<br />
<br />
To check, the TNC set-up and connection is correct, open DX-Cluster monitor window (<tt>Alt+O</tt>). 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.<br />
<br />
== Connecting node ==<br />
<br />
Once you have configured the appropriate COM port for your TNC in Win-Test, you should be able to connect to your local node.<br />
<br />
Open DX cluster window by using <tt>Alt+T</tt> to send a command to the TNC.<br />
<br />
To control the TNC, you need control sequences.<br />
TNC control sequences always starts with '''ESC'''!<br />
<br />
Pressing ESC in DX-Cluster window is not possible, the window will close.<br />
<br />
To achieve a '''ESC control''', you must press <tt>CTRL+E</tt> followed by the TNC command!<br />
<br />
After reset, TNC is normally in cannel 0, no connection is possible, only viewing mode. The command to change to cannel 1 is: <tt>CTRL+E S1</tt><br />
<br />
Message in monitor window: <tt>CHANNEL NOT CONNECTED</tt><br />
<br />
The connect command to your local node: <tt>CTRL+E C<node></tt> where <node> is the callsign of your local node.<br />
<br />
You can follow the connection in the DX-cluster monitor window. When connection is made, than connect to your preferred DX-Cluster:<br />
It is important, that all commands after connecting are WITHOUT ESC!<br />
These are normal inputs in the DX-cluster window like: <tt>C DB0SDF-7</tt> where C is the connect command to your local node, to connect to the DX cluster DB0SDF-7.<br />
<br />
After connection to your preferred DX-cluster, you can use the buttons of the DX-CL window to show DX announcements.<br />
<br />
You can use the packet monitor window (<tt>Alt+O</tt>) to check the connection status and to see data inbound from the TNC. Spots should begin filling up the bandmap at this stage.<br />
<br />
== Disconnecting node ==<br />
<br />
To leave the DX cluster, normally <tt>bye</tt> command in DX-Cluster window. After reconnect to your local node, TNC command <tt>CTRL+E D</tt> disconnect from your local node.<br />
<br />
Other important TNC commands are:<br />
<br />
<tt>CTRL+E I</tt>: set your own call to TNC (<tt>CTRL+E I DL8NAS</tt>)<br />
<br />
<tt>CTRL+E T16</tt>: set TX delay, normally around 16 (12..20)<br />
<br />
<br />
23. Jul. 06<br />
DL8NAS, Sigi<br />
<br />
== See also == <br />
<br />
* [[DX Cluster/Telnet|Connecting via telnet to a DX cluster]]<br />
* ...<br />
<br />
{{stub}}</div>DL8NAShttps://docs.win-test.com/w/index.php?title=DX_Cluster/Packet&diff=1453DX Cluster/Packet2006-07-23T17:25:58Z<p>DL8NAS: </p>
<hr />
<div>== TNC pre-test ==<br />
<br />
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 <tt>''"The Firmware"''</tt> (TF) and <tt>''"KISS"''</tt> mode. In Kiss mode, no connection is possible.<p><br />
To make sure your TNC has the correct OS, use a simple terminal program, connect to a COM port, setting the right baud rate and switch on the TNC.<br />
If your TNC has the TF OS, after reset TNC a message should appear in the terminal program like <tt>"The Firmware Ver. 2.1.."</tt>. <br />
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.<br />
<br />
== Win-Test TNC set-up ==<br />
<br />
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.<br />
<br />
== Checking the set-up works ==<br />
<br />
To check, the TNC set-up and connection is correct, open DX-Cluster monitor window (<tt>Alt+O</tt>). 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.<br />
<br />
== Connecting node ==<br />
<br />
Once you have configured the appropriate COM port for your TNC in Win-Test, you should be able to connect to your local node.<br />
<br />
Open DX cluster window by using <tt>Alt+T</tt> to send a command to the TNC.<br />
<br />
To control the TNC, you need control sequences.<br />
TNC control sequences always starts with '''ESC'''!<br />
<br />
Pressing ESC in DX-Cluster window is not possible, the window will close.<br />
<br />
To achieve a '''ESC control''', you must press <tt>CTRL+E</tt> followed by the TNC command!<br />
<br />
After reset, TNC is normally in cannel 0, no connection is possible, only viewing mode. The command to change to cannel 1 is: <tt>CTRL+E S1</tt><br />
<br />
Message in monitor window: <tt>CHANNEL NOT CONNECTED</tt><br />
<br />
The connect command to your local node: <tt>CTRL+E C<node></tt> where <node> is the callsign of your local node.<br />
<br />
You can follow the connection in the DX-cluster monitor window. When connection is made, than connect to your preferred DX-Cluster:<br />
It is important, that all commands after connecting are WITHOUT ESC!<br />
These are normal inputs in the DX-cluster window like: <tt>C DB0SDF-7</tt> where C is the connect command to your local node, to connect to the DX cluster DB0SDF-7.<br />
<br />
After connection to your preferred DX-cluster, you can use the buttons of the DX-CL window to show DX announcements.<br />
<br />
You can use the packet monitor window (<tt>Alt+O</tt>) to check the connection status and to see data inbound from the TNC. Spots should begin filling up the bandmap at this stage.<br />
<br />
== Disconnecting node ==<br />
<br />
To leave the DX cluster, normally <tt>bye</tt> command in DX-Cluster window. After reconnect to your local node, TNC command <tt>CTRL+E D</tt> disconnect from your local node.<br />
<br />
Other important TNC commands are:<br />
<br />
<tt>CTRL+E I</tt>: set your own call to TNC (<tt>CTRL+I DL8NAS</tt>)<br />
<br />
<tt>CTRL+E T16</tt>: set TX delay, normally around 16 (12..20)<br />
<br />
<br />
23. Jul. 06<br />
DL8NAS, Sigi<br />
<br />
== See also == <br />
<br />
* [[DX Cluster/Telnet|Connecting via telnet to a DX cluster]]<br />
* ...<br />
<br />
{{stub}}</div>DL8NAS