RTTY Ver 3, Pt II: Packet DxCluster by Dick Stevens N1RCT

For most of us, the Dx Cluster will be of interest, even if we do not have two rigs networked for a separate multiplier station. If you have not used the cluster before, there is a nice article by Neal, ON9CNC on Jim's Gazette at http://www.n2hos.com/digital/cluster.html     If you already have the DxCluster set up for normal use, RTTY Ver 3 can probably use it directly. All that is needed is the port number in RTTY.INI. Here is mine:

;------------------ your packet info here ----------------------
[CLUSTER]
ComPort=6
Beep-ok=Yes
Beep-Frequency=1200
Beep-Duration=500

;------------------ your computer serial port info here --------
[COM6]
BaseAddr=$180
IrqNumber=12
HandShake=Xon/Xoff
BaudRate=9600
Parity=None
DataBits=8
StopBits=1
BuffersSize=1000
Delay=0

    If the COM port specification seems a little exotic, we will talk about expansion serial cards in Part III. The cluster TNC I am using is a KPC-3 into an Alinco DR-119 at 50 watts which uses a Cushcraft beam at 25 feet into the only cluster in my area, W1AO about 33 miles (53 KM) away. This results in a very solid connection; since you will want to connect for long periods "unattended", a solid link is very desirable. Do you have to connect? No, but then RTTY will sense each and every spot sent to each person that is connected to the cluster; say 5 or 20. This will make for a whole lot of beeping going on, fill up the call queue, make a big save file, and other boring things. If you are connected, the TNC will only relay messages for you to RTTY.

   Under the [Cluster]  specification, you can set the tone that will beep when a RTTY spot is made .. you might want to make this a very different tone than the normal beeps going on when a new callsign is spotted on baudot.

     You probably will not be able to use a dual-port TNC like the Kam-Plus or the PK 900 for both Baudot and VHF packet at the same time, at least not the PK 900. However, K6STI for baudot and the PK 900 for cluster works fine; I hooked up the KPC-3 so I have the PK-900 available as a back-up.

       By the way, if you using a multi-purpose TNC, you don't really have to hook to packet. The "packet page" will show baudot and allow you to send manual commands to the TNC. For instance, you could run the same sound from the radio to a P38 and a PK-232, specify the PK 232 as the packet cluster, and actually put the PK 232 into the HF baudot mode. The result will be dual print and two text files saved, one for the P38 and one for the PK-232, which can then be compared for print quality, etc. In fact, my PK-900 being used for packet also collected all the baudot it was hearing on the other port. So how about the great shootout between RITTY and ST-8000?? The software is in place!

OK, let's assume you have a packet TNC and radio hooked up and the RTTY.INI modified to reflect what you want. Start up RTTY Ver. 3, click on the top line, network, packet. (  `pa is the quick route). For my KPC-3, the linking is done for me by  typing   CONNECT W1AO      on the command line. RTTY is being a dumb terminal here so any command the TNC recognizes could be typed here. You have a fully functioning TNC with all it's capabilities available. Note that the propagation indexes are available on the cluster; new ones come out every three hours and will appear at the bottom left of the main screen. The resulting screen is:

Now go back to the main screen; you should not have to touch the cluster again unless you lose the link or want to see the CW spots coming in to help judge band openings. Which brings us to a sticky point: For single operators, unassisted (the vast majority of us),  when is using the DxCluster legal? I know of two contests that says it is illegal (the CQWW & Roundup) and one that says it is legal (the WPX). The other 15 or so make no explicit mention. The general consensus I think I hear is that clusters are legal if they are not declared illegal by the rules. Many will argue that is not sporting or unfair as the quality of the cluster varies greatly around the country / world; but I have not heard of anyone being disqualified although there are checks being made for the CQWW Phone/CW contests apparently. There are also issues of a "friend" making a lot of spots of YOU and even self-spotting when QSYing or things are getting slow. As usual, the technical problem is a lot easier than the legal hassles. I think this new Ver. 3 capability will encourage event rules to be explicit about cluster usage, a simple YES or NO. (Please, Sir, does that include the internet?    If I just use Telnet?     How about if it is my cluster and I have to see that all is working well?    How about if I don't actually connect?      May I send in spots as long as I don't look at any? That includes spots of myself, right?). I predict WF1B Ver 8 will have an internet connection !

    OK! You have connected to the DxCluster and returned to the main screen. When spots come in, they are displayed on the right and the latest is displayed on the bottom left. The "latest" may include general announcements posted on the cluster.

Since we are already on 20 meters, we can turn the VFO to 14085.8 FSK and we should hear ON4AGT nearby. If the spot was LSB and you are using FSK, just subtract 2.2 from the spot, and visa-versa. If you have rig control ( another COM port and set in RTTY.INI), you switch to the spot automatically by using the alt-A key. This brings up a screen that can be clicked on>>>>>>>
The rig will automatically switch to that frequency and band. Most of us will now have to select the correct antenna, reset the antenna tuner, move the beam around, and set the amp up, put up a tune signal, and then find the spot, but it is kind of slick to see the radio change magically. Of course, you pushed A=B on the radio before you QSYed so you could find your way back home .......

So how did RTTY Ver 3 just show the RTTY spots when there were many other spots for CW and Phone sent out by the cluster? Let's quote the manual:    "The rules for determining a RTTY spot are ...
if comment contains "RTTY", "TTY", "FSK", or "TEST"
if comment is empty but frequency is in range of 14070..14105, 21070..21105, or 28070..28105 " This leads to the explanation of where the W0IR spot came from ... looking back at the packet cluster screen, we see what the complete spot was:


As we gain experience, there may well be some changes to the logic used to determine which spots will be shown on the main screen. An occasional quick look at the packet screen ( `np ) will keep you confident until perfection is reached.             29 May '97