Introduction to Packetcluster


by Neal Campbell ON9CNC

In case you have not used a Packetcluster node, let be introduce you to one of the biggest sources of pleasure in amateur radio! Packetcluster is a software system written by Dick Newell, AK1A, that broadcasts announcements of where DX stations are located. Usually, Packetcluster stations (usually called nodes) are connected to each other.

To explain how a Packetcluster works, lets assume someone in New Hampshire detects ON4UN on 160 meters and alerts their local Packetcluster node. The Packetcluster node immediately notifies everyone connected to that Packetcluster node about the DX, specifying the frequency, callsign of the DX station, callsign of the station alerting everyone, and the time of the alert.

Simultaneously, the Packetcluster node is telling all other Packetcluster nodes that are connected to it that ON4UN was spotted on 160meters. These Packetcluster nodes alert all of the stations connected to them of the alert, and likewise tell all Packetcluster nodes connected to it.

It is amazing how quickly these alerts are send around the world. While I lived in Virginia, I was the sysop of a Packetcluster node. It literally took only 5 minutes for a DX spot originating in Massachusetts to reach Virginia. I plan to write much more on Packetcluster in the coming months, as not only is it a convenient way to keep abreast of DX, but it is a very powerful system of databases and mail that can assist you in many ways.

Surf the Internet to a Packetcluster?


Now, on face value, this seems like a ridiculous prospect. After all, we love using ham radio for any and all things possible (and sometimes for things not very possible). What is the value of using the Internet to connect to something that you can access via amateur radio? The easy answer is none! Of course, this assumes that you have a very reliable connection to a Packetcluster node that has spots originating from every region that you desire.

There are many Packetcluster nodes located throughout the world, but as a sysop I can tell you many people have problems connecting to them. Some of these problems are related to packet radio parameters, low VHF/UHF antennas, long distances, or inappropriately adjusted 2 meter or 440 mHz radios. Weather can play havoc with connections. An acceptable link in the winter can be unacceptable in the summer.

Many hams like seeing what DX stations are being heard at different locations in the world. This is a very controversial topic, in fact, as many hams also do not want to know. With the global reach of Packetclusters interconnected via Internet, it is not unusual to see someone in another continent "spot" DX on your local Packetcluster. I assist in ON7PC running the ON4DXB Packetcluster node in Brussels. Routinely I see spots for DX coming from the US.

Why is this so controversial? The main reason is that propagation is different everywhere in the world at a given time. At 0900 GMT I can hear Asian stations from Belgium. I am sure that these stations cannot be heard in the eastern part of the US at that time. Many people do not like seeing spots for stations they cannot hear. Other stations like knowing what is being heard so they can follow the effects of propagation around the world. Unless your Packetcluster node is very well connected via Internet to other parts of the world, you will not be able to follow the propagation, if you are interested.

Another great reason is that many times you are not near your shack , but would like to watch what is occurring on the bands. I would not suggest that some of us might keep an eye out for DX while at work, but I am sure it has happened at least once! The final reason you might want to access a Packetcluster node via the Internet is that it is pure fun! It is comforting to see something so familiar as Packetcluster on the Internet.

Your Internet Packetcluster Station


To connect to your local Packetcluster node, you need a VHF/UHF radio and antenna, a TNC, a terminal program, and the frequency of where Packetcluster users connect. To connect to a Packetcluster node, you need similar equipment, but if you currently can connect to the Internet, you already have most of what you need. To utilize the Packetcluster fully, you need a phone modem, an account with an Internet-capable service provider, and a Telnet program.

Telnet programs provide you with the capability to log onto remote Internet hosts. This method of connection is older than connecting to a Web page, and you usually need a separate program to communicate with a Telnet host. Where can you get a Telnet program? From the Internet, of course! If you use a Macintosh, the most popular Telnet program is NCSA Telnet. You can download it from many sites. For the PC, I use NTCRT, which is also available from many sites. If you have problems finding these programs, let me know and I will help you. (Note: Win95 includes Telnet among its many tools. Merely go to the DOS prompt and type Telnet—Ed).

If you are using a Web browser such as Microsoft Explorer or Netscape, you can tell these programs what program to use when attempting a Telnet connection. Going to the Preferences section of these programs will show you where to specify the name of your Telnet program.

From Here to There


Once you have a Telnet program, and have told your Web browser where it is, accessing the Packetcluster is very easy!

One very easy way to access a Packetcluster node is to visit a Web page that has a link created. For instance, I regularly visit KA9FOX's page, as he has links to so many places about amateur radio. He has a small section of his web page dedicated to Packetcluster nodes accessible, and gives easy instructions.

Figure 1

If you want to visit the KA9FOX web page, enter "HTTP://www.qth.com/KA9FOX" into your browser program.

Otherwise, from your web browser, type "TELNET://migate.ampr.org". This will cause your Web browser to start up your Telnet program and point it to MIGATE. MIGATE is a TCP/IP bridge between the Internet and amateur radio.

Once you connect to MIGATE, the system will prompt you for your user name. Enter your callsign. It will them ask you for a password. Usually, I enter my Internet address as my password, but the system does not validate it so you need not remember what you enter.

Sometimes, the system will ask you to register. To do this, type Register and then answer what ever questions the system might ask you. If you do not know the answer to these questions, type something and it will usually accept it.

Once you have successfully connected to MIGATE, you are talking with a node not unlike TheNet or any digipeater that you are used to. You can enter commands to see what nodes are available by typing NO (which stands for nodes).

When you type NO, you will receive a listing of many nodes available (I will guess almost 100 nodes are accessible by MIGATE). As with most digipeaters, each node is known by a callsign/SSID (like ON9CNC-9) and an alias (such as NCNODE). You can connect to any node in this list by either specifying the callsign/SSID or the alias.

There is a normal naming convention for alias used to access Packetclusters. They usually start with DX. If you look at the nodes connected to MIGATE, you may see the following Packetcluster stations accessible:

  KI3V (DX2400)   VE3CDX (DXGATE) WD5B (DXCNWY)
  NO4J (DXFLA)   KC8FT (DXIT)   IK5QGO (DXCPC)
  WD5B (DXARK) IK5PWJ (DXCPCL).

One of the first Packetcluster nodes accessible via Internet was VE3CDX, so lets try that one.

Enter "C DXGATE". You will next see a message saying that a connection is in progress and if you change your mind to type CTRL T. With any luck, in 5-20 seconds you will be connected to a node that will tell you what to type to connect to the Packetcluster node.

Figure 2


Assuming this is the first time you have ever connected to VE3CDX's node, it will ask you for your name. It will confirm that you have typed the correct name, and repeat this process for your address.

Once you have told the Packetcluster who you are, you are now a regular user of the VE3CDX node.

Figure 3

Type "SHOW/USERS" and you will see the call sign of everyone connected to VE3CDX. Likely, you will see 6 or more Canadian amateurs, but also visitors like you from all around the work. Last week, I saw stations from Italy, Belgium, Brazil and Portugal.

Figure 4


Basic Packetcluster Commands

If you are new to Packetcluster, let me introduce you to a few commands that can get you going quickly.

If you know your latitude/longitude coordinates, type "SET/LOCATION". For instance, for my QTH, I would enter "SET/LOCATION 50 51 N 04 41 E". By doing this, you are telling the Packetcluster node exactly where you are located. Once it has this information, it can tell you where to point your beam for short-path directionality. You can find this information by typing "SHOW/HEAD" followed by a prefix. This feature is very handy if you do not get this information from your logging program, or it is not readily available.

While you are connected to the Packetcluster node, you will see spots appear as other amateurs post them. If you would like to see the last 10 spots broadcast, type "SHOW/DX/10". If you would like to see all spots from a certain country that were posted in the last 2 days, enter "SHOW/DX/D2" followed by the country prefix. If you would like to see the last 5 spots for RTTY, type "SHOW/DX 'RTTY". This command usually works because people usually type RTTY as a comment when spotting a RTTY station.

What if you would like to announce some juicy DX that you just found on 30 meters? As we are all supposed to be monitoring 30 meters each day for digital action, lets assume you just discovered N2HOS on 10133 mHz. As Jim is considered very rare DX here in Europe, many people would love the opportunity to work him (getting a QSO with the founder of The Copper Dipole in the Attic Association is always very exciting HI). Type "DX 10133.0 N2HOS RTTY JIM". In a few seconds, you will receive a spot from the alert that you just entered.

Built into the Packetcluster system is a mail system. Hams use mail just like on a regular PBBS. You can address mail to specific amateurs (if the Packetcluster system knows where they are) or to generic addresses like ALL. Each cluster system has a set of rules on how to use mail, so please make sure you understand the etiquette before you try to send mail. Many of the Packetcluster nodes that are accessible will not allow you to send mail, since there are better and more efficient ways to do that on the Internet.

To see what mail has been posted to the general community, type DI. You will then see the last 5 mail messages posted to the general community. When you look at the listings of the mail messages, you will see that each has a unique number at the beginning of each line. Just as with any PBBS, to read the mail message, type "R " followed by the mail message number.

Packetcluster - The Easy Way!


If the above method of connecting to a Packetcluster node is too intensive for you, you can browse the 'cluster by point your browser at "HTTP://www.clinet.fi/~jukka/webcluster.html". Jukka has provided a web-style access to the Packetcluster that lets you submit certain command.

Figure 5


You will not be able to experience the full power of the Packetcluster by this method. You will not be automatically notified when a new DX station is spotted. This method is very easy, however, and if you are not familiar with Packetcluster, it is a nice introduction.

I plan to cover Packetcluster operations in more detail for the future. Otherwise, if you have access to one locally, experiment! If you have any questions about how to use it, contact the sysop, as they are always willing to help.

Until next month, 73

Neal

Neal ON9CNC needs your comments and questions