Kantronics

AK9R

Lead Wiki Manager and almost an Awesome Moderator
Super Moderator
Joined
Jul 18, 2004
Messages
9,678
Location
Central Indiana
Speed 9600,8,none,1
That appears to be correct. Are both the TNC and computer set the same?

What software are you running on the computer?

How are the computer and TNC connected?
 

bodnarp

Member
Premium Subscriber
Joined
Sep 6, 2003
Messages
381
Location
Allendale, Michigan
That appears to be correct. Are both the TNC and computer set the same?

What software are you running on the computer?

How are the computer and TNC connected?
Running outpost tnc and computer connected to pc via usb, tnc connected to ftm 400 via the radio cable for it. It woked a month ago then stopped
 

AK9R

Lead Wiki Manager and almost an Awesome Moderator
Super Moderator
Joined
Jul 18, 2004
Messages
9,678
Location
Central Indiana
computer connected to pc via usb
Whether you are using a UBS-to-serial adapter or you have a newer KPC3+ with USB on board, when you connect the TNC to the computer, the driver should create a virtual COM port. Have you checked to see if that COM port number matches the COM port setting in Outpost?
 

AK9R

Lead Wiki Manager and almost an Awesome Moderator
Super Moderator
Joined
Jul 18, 2004
Messages
9,678
Location
Central Indiana
Other than cycle power on the KPC3+ and check all your settings, I'm stumped.
 

AK9R

Lead Wiki Manager and almost an Awesome Moderator
Super Moderator
Joined
Jul 18, 2004
Messages
9,678
Location
Central Indiana
Don't take this the wrong way, but if removing/replacing the internal battery fixed the problem, then something got set in the TNC that caused the communications failure. Kantronics' firmware is pretty solid, so that leaves a power glitch or...

As I recall, Outpost has a terminal window where you can send commands to the TNC and watch the results. The Kantronics TNC firmware has a handy command called "DISP" for DISPlay. If you type DISP in the terminal window and watch the output, you'll see every setting in the TNC scroll by. If there's a way to capture that dump in the Outpost terminal window, you could save that information as a file and use it as a touch stone to go back to if problems develop in the future.
 
Top