Kantronics

[bodnarp]

I have a Kantronics 3+ and using outpost all of a sudden I am getting this ÀÀS00À along with checking tnc.

Help Please

 

[AK9R]

Check speed, parity, stop bits.

 

[bodnarp]

Check speed, parity, stop bits.

Speed 9600,8,none,1

 

[AK9R]

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]

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]

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?

 

[bodnarp]

Yes they match I even tried it on a windows 10 machine and got the same

 

[AK9R]

Other than cycle power on the KPC3+ and check all your settings, I'm stumped.

 

[bodnarp]

Me too lol Thanks for the help

 

[bodnarp]

Other than cycle power on the KPC3+ and check all your settings, I'm stumped.

According to Kantronics the tnc is in host mode trying to figure out how to get it out of host mode

 

[jeepsandradios]

Try removing the internal battery and let it sit for a bit. You'll loose all settings in the TNC but it should put it back in normal mode.

 

[bodnarp]

Try removing the internal battery and let it sit for a bit. You'll loose all settings in the TNC but it should put it back in normal mode.

Yep that is what Kantronics had me do. Everything is back to normal. Thanks everyone for the help

 

[AK9R]

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.