Jump to content

Terminal node controller

From Wikipedia, the free encyclopedia
(Redirected from Terminal Node Controller)
AEA (Advanced Electronic Applications Inc.) PK-232MBX, circa 1991

A terminal node controller (TNC) is a device used by amateur radio operators to participate in AX.25 packet radio networks. It is similar in function to the Packet Assembler/Disassemblers used on X.25 networks, with the addition of a modem to convert baseband digital signals to audio tones.[1]

The first TNC, the VADCG board, was originally developed by Doug Lockhart, VE7APU, of Vancouver, British Columbia.[2]

Amateur Radio TNCs were first developed in 1978 in Canada by the Montreal Amateur Radio Club and the Vancouver Area Digital Communications group. These never gained much popularity because only a bare printed circuit board was made available and builders had to gather up a large number of components.[specify]

In 1983, the Tucson Amateur Packet Radio (TAPR) association produced complete kits for their TNC-1 design. This was later available as the Heathkit HD-4040. A few years later, the improved TNC-2 became available, and it was licensed to commercial manufacturers such as MFJ.

In 1986, the improved "TNC+" was designed to run programs and protocols developed for the original TNC board. TNC+ also included an assembler and a version of Forth (STOIC), which runs on the TNC+ itself, to support developing new programs and protocols.[3]

In 2018 Nino Carillo (KK4HEJ) developed and produced a TNC (the NinoTNC)[4] with (currently) 16 different data modes, from 300 baud AFSK to 19,200 C4FSK.It has a KISS interface to the compute device, and implements IL2P (Improved Layer 2 Protocol)[5] for Forward Error Correction (FEC) in some modes.

Description

[edit]
The Kantronics 9612+ was implemented around an 8-bit Motorola microcontroller.

A typical model consists of a microprocessor, a modem, and software (in EPROM) that implements the AX.25 protocol and provides a command line interface to the user. (Commonly, this software provides other functionality as well, such as a basic bulletin board system to receive messages while the operator is away.) Because the TNC contains all the intelligence needed to communicate over an AX.25 network, no external computer is required. All of the network's resources can be accessed using a dumb terminal.

The TNC connects to the terminal and a radio transceiver. Data from the terminal is formatted into AX.25 packets and modulated into audio signals (in traditional applications) for transmission by the radio. Received signals are demodulated, the data unformatted, and the output sent to the terminal for display. In addition to these functions, the TNC manages the radio channel according to guidelines in the AX.25 specification.

Early usage was mostly one-to-one communication, either between two people or a person to an automated Bulletin Board or E-mail system.

Current status

[edit]


Since the late 1990s, most AX.25 usage has shifted to a different one-to-many communication paradigm with the Automatic Packet Reporting System (APRS).

The TNCs of the 1980s and 1990s were complete solutions that only needed a radio and an optional dumb terminal. As home computers made their way into ham "shacks," there was a movement toward simpler, cheaper "KISS" (Keep It Simple, Stupid) devices. These have a modem and minimal processing of the AX.25 protocol. Most of the processing is moved to the personal computer.

The next logical step in the evolution is to eliminate the specialized hardware and move all of the processing to a computer. A "soundcard" is used for audio to and from the radio. Everything else is done in software.[6]

Some of the earlier attempts performed poorly, giving this approach a bad reputation. Modern software TNCs, using digital signal processing (DSP) techniques, can successfully decode poor quality signals that the older equipment can't.[7]

Some handheld and mobile VHF radios currently on the market incorporate TNC abilities within the radio itself in support of the APRS protocol.

Many TNCs are still in use, especially in unattended stations where reliability is important. The importance of location to the APRS system has fueled development of a new generation of small low-power TNCs often integrated with a GPS module for use in mobile tracking stations. Not all AX.25 activity is APRS: Some AX.25 data networks exist, including the EastNet Packet Network mostly in the Northeastern United States[8] and TARPN Network mostly in North Carolina.[9]

APRS digipeating protocols require specific naming conventions, and older TNCs may not have the required support to be used as a digipeater. However, almost any TNC can be pressed into service for Home or Tracker use. TNCs that were clones of the popular TAPR TNC-2 may be upgradeable via the UIDIGI firmware project.


TNC/Radio data ports

[edit]

Although typically described as data ports, the interface between a radio and a TNC is almost entirely analog audio (plus lines for PTT and squelch). The connectors used for this purpose vary widely across TNC manufacturers, but modern radios that offer data ports have widely adopted the Mini-DIN 6-pin connector.

Also used are full-size DIN connectors, DE-9 (D-sub) connectors,[10] modular telephone (RJ) connectors, and combinations of mini- and micro-headphone connectors (typically on handheld radios).

  • 6-pin Mini-DIN

Terminal data port

[edit]

TNCs were originally designed to accept messages from a human typing on a dumb terminal. TNCs had a DB-25 or DE-9 connector carrying asynchronous start-stop bytes with RS-232 signal levels. This could also be used with the serial port of a personal computer. Serial ports are now pretty much extinct, but USB-to-serial converter cables are available.

However, typically a human uses a more sophisticated software package running on a personal computer that sends messages to the TNC using the KISS (TNC) protocol or the 6PACK protocol.[11]

Modern Software TNCs provide TCP/IP interfaces that can be accessed across computer networks. For example, it is possible to run a software TNC on a Raspberry Pi near the radio and access it from a laptop computer in another location. Software TNCs also provide "pseudo terminals" so they can be used with old applications that only know how to use serial ports.


See also

[edit]

References

[edit]
  1. ^ R. Dean Straw, ed. (2005). The ARRL Handbook for Radio Communications 2006. American Radio Relay League. pp. 9.14–9.15. ISBN 0-87259-948-5.
  2. ^ Larry Kenney. "Introduction to packet radio".
  3. ^ Douglas Lockhart. (1986). "Features of the VADCG TNC+". Vancouver Amateur Digital Communications Group.
  4. ^ "TARPN -- NinoTNC info for Builders". tarpn.net. Retrieved 2024-09-01.
  5. ^ "TARPN: Improved Layer-2 Protocol". tarpn.net. Retrieved 2024-09-01.
  6. ^ "Dire Wolf Software TNC". GitHub. 10 May 2021.
  7. ^ "WA8LMF TNC Test CD Results a.k.a. Battle of the TNCs" (PDF). GitHub.
  8. ^ "EastNet Packet Radio Group Welcome". www.qsl.net. Retrieved 2024-09-01.
  9. ^ "TARPN Network Page". tarpn.net. Retrieved 2024-09-01.
  10. ^ "TARPN -- NinoTNC info for Builders". tarpn.net. Retrieved 2024-09-01.
  11. ^ Welwarsky, Matthias. "6PACK a "real time" PC to TNC protocol". Translated by Sailer, Tom. Retrieved 2013-05-19.
[edit]
Retrieved from "https://en.wikipedia.org/w/index.php?title=Terminal_node_controller&oldid=1250335050"