Pages: [1]   Go Down

Author Topic: Software only vs hardware TNC with Winlink for reliability  (Read 312 times)

KK4GMU

  • Member
  • Posts: 366
Software only vs hardware TNC with Winlink for reliability
« on: February 12, 2022, 06:40:03 AM »

What are some pros and cons for hardware TNC vs software only when using Winlink for EmComms?

Two specific setups:

1) Hardware: Mobilinkd3 TNC with a multi-use computer to do packet email with Winlink.

2) Software: UZ7HO with a multi-use computer to do packet email with Winlink.

Which is easiest to set up?
Which is most likely to stay properly configured?
Which will be most reliable and not subject to glitches?
Which would be easiest to troubleshoot if something doesn't work?


Logged
IC-7100, RSPdx, AT-D878UVII-Plus HT, TGIF Spot

WA3SKN

  • Member
  • Posts: 8126
Re: Software only vs hardware TNC with Winlink for reliability
« Reply #1 on: February 12, 2022, 07:23:39 AM »

Does your computer have a serial port or do you plan to use USB or connect via LAN?

-Mike.
Logged

KK4GMU

  • Member
  • Posts: 366
Re: Software only vs hardware TNC with Winlink for reliability
« Reply #2 on: February 12, 2022, 08:35:52 AM »

Planning to use USB - simplest?

Is there any advantage to RS232?
Logged
IC-7100, RSPdx, AT-D878UVII-Plus HT, TGIF Spot

W1VT

  • Member
  • Posts: 6071
Re: Software only vs hardware TNC with Winlink for reliability
« Reply #3 on: February 12, 2022, 12:20:48 PM »

Hardware RS-232 numbers don't change.
USB to serial port numbers can change if you unplug the adapter, which means you may need to reconfigure the software to fix that.

Logged

KB8VUL

  • Member
  • Posts: 654
Re: Software only vs hardware TNC with Winlink for reliability
« Reply #4 on: February 22, 2022, 09:13:14 PM »

Both. 
One is easier to deploy, but requires the specific PC it's configured on. 
A TNC can be connected to any radio and controlled from any computer with a terminal program.  Obviously the terminal setup is harder to use, but it's not impossible.  A lot of that is going to depend on what you are connecting to, and what functionality it has. If it's fully featured, it will have a mail program that will run from the terminal interface and NOT require a piece of specific software to operate. 
Logged

K8TB

  • Member
  • Posts: 9
Re: Software only vs hardware TNC with Winlink for reliability
« Reply #5 on: May 03, 2022, 12:10:16 PM »

How about a very simple and cheap hardware solution, with no additional software needed?

Build or buy a Nino TNC, made by the TARPN group: http://tarpn.net/t/nino-tnc/nino-tnc.html
Build your own, or buy built units on Etsy for about $ 65.
This modem is USB powered, and runs off your Windows computer. Bring up your Winlink program, click on "Open Session>Packet Winlink, then click on settings. For the "Packet Type" box, select "KISS". The "Packet TNC Model is "Normal", and the comm port will be that USB comm port picked by your CPU for the modem, and the Serial Port Baud will be 57,600. Make sure your dip switches on the Nino are where they should be, then all you need to do is calibrate the tranmit level to a proper value, and you are on the air. It takes longer to tell how to do it than it does to do.

We are changing all of our counties packet go kits to this modem. Easy peazy and it works.   
Logged

G4AON

  • Member
  • Posts: 2178
Re: Software only vs hardware TNC with Winlink for reliability
« Reply #6 on: May 04, 2022, 01:10:01 AM »

Although I no longer use packet, I do use Winlink via HF and an SCS Pactor modem. I also have a KAM Plus and a KPC3+ that can be pressed into use, but they are mainly used for test purposes and to watch Navtex with the KAM Plus.

Hardware modems, especially RS232 connected ones, “just work” once you have configured them. You can even leave them turned on with the mailbox set, so locals can leave you messages, without needing to leave a computer running.

73 Dave
Logged

KK4GMU

  • Member
  • Posts: 366
Re: Software only vs hardware TNC with Winlink for reliability
« Reply #7 on: July 26, 2022, 06:07:08 AM »

I ended up getting a Kantronics PacketCommunicator 3+.  It's the first one that worked pretty much right away for me (probably because after trying a couple others - software-only and Mobilinkd 3 - I finally figured out what I was doing :-X).  Easy enough to change com port if it changes, which it only did once in 3 months.

The Mobilinkd 3 was cheapest by a hundred bucks, but for me it didn't seem as straight forward and goof proof as the Kantronics.
Logged
IC-7100, RSPdx, AT-D878UVII-Plus HT, TGIF Spot

VE7JMR

  • Member
  • Posts: 2
Re: Software only vs hardware TNC with Winlink for reliability
« Reply #8 on: October 05, 2022, 05:01:46 PM »

It may be worth considering that a software modem like Direwolf or UZ7HO Soundmodem should have much better receive performance than a hardware TNC, especially compared to something as ancient as a Kantronics KCP-3+.
Logged

KT4WO

  • Member
  • Posts: 425
    • homeURL
Re: Software only vs hardware TNC with Winlink for reliability
« Reply #9 on: October 06, 2022, 07:18:08 AM »

1st - The Mobilinkd is NOT a "TNC"(unless something has changed) it is a KISS modem.

2nd - UZ7HO or Direwolf will decode better than any hardware TNC/modem.

Been on packet(HF and VHF) for 30 years and have a stack of TNC's on the shelf.
NONE in use... All software based now.
I still run 2 nodes and a gateway, all in software.
Logged
Pages: [1]   Go Up