Packet Kantronics KPC-3+ help

[gytramr65]

Long-time ham here, off air for a while, trying to re-enter. I previously owned a Kantronics KPC-3 (pre-plus version) and a modest packet setup, had a bit of activity. I just purchased a used KPC-3+, version 8.2 (I think) firmware. Did a "RESTORE", got MYCALL and a few other basic parameters set successfully. Interacting with the TNC in "Command" mode seems all normal. Then, per manual I had downloaded, I tried connecting to my PBBS. Sent CONNECT (mycall) command, CON LED comes on, but no "welcome" message as described in the manual. I then tried a couple of PBBS commands, absolutely no response. Cntl-C brought back cmd: prompt, I sent DISCONNE, Con LED went out.

Also - thinking I could just "read the mail" and see some packet traffic, from the cmd: prompt I set MONITOR ON. Rcv LED flashes occasionally, but no text appears.

For context - KPC-3+ connected via a USB to RS-232 adapter to an iMac running Monterrey 12.7.6 with a third-party app, "Serial" as terminal software. (Could not get the native terminal app to consistently recognize the external port with the adapter.)

It seems to me that everything working OK in "command" mode indicates that I have RS-232 comms set up correctly, or at least acceptably. Is there some subtle parameter setting in the KPC-3+ that I've missed, or did I manage to purchase a broken TNC? Thanks in advance for any insight or suggestions!

DE W7LEJ (Marty)

 

[redbeard]

Take a look at the software DCD setting, that might make a difference depending on how the radio is wired along with volume and squelch. Ideally, you will be using a flat audio out from the radio with no squelch and the TNC will determine whether it hears traffic or not.

 

[kk9h]

The level of audio being fed to the KPC-3+ from your radio is a fairly important setting. First, with the CD parameter set to Internal, open the squelch on your radio with the volume control set all the way down. The DCD light should be off. Slowly bring up the volume level until the DCD light just begins to light up, then add just a tiny bit more volume. You now have the correct receive audio level set. You can leave the CD parameter set to Internal and adjust your squelch so the light just goes out, or you can set the CD parameter to Software (preferred) and leave the radio running in open squelch mode. With this done you have optimized the ability of your KPC-3+ to decode what it hears.

 

[gytramr65]

Take a look at the software DCD setting, that might make a difference depending on how the radio is wired along with volume and squelch. Ideally, you will be using a flat audio out from the radio with no squelch and the TNC will determine whether it hears traffic or not.

Thank you for your response and suggestions! A comment and a question, please.

I've been "experimenting" with setting CD to "Internal" and "Software" with no change in results. Also attempted changing volume settings on the radio, again no change. (Did I mention that the "Rev" LED does occasionally flash, and when it does, if I have the other receiver on, I hear what sounds like packet traffic, but no "decoded" text appears?) And - Isn't the detail that I'm not seeing any text back from when I've logged into my own PBBS an indication that maybe the issue(s) are "upstream" in the TNC or perhaps in settings for the link to the computer?

Thanks again!

 

[gytramr65]

The level of audio being fed to the KPC-3+ from your radio is a fairly important setting. First, with the CD parameter set to Internal, open the squelch on your radio with the volume control set all the way down. The DCD light should be off. Slowly bring up the volume level until the DCD light just begins to light up, then add just a tiny bit more volume. You now have the correct receive audio level set. You can leave the CD parameter set to Internal and adjust your squelch so the light just goes out, or you can set the CD parameter to Software (preferred) and leave the radio running in open squelch mode. With this done you have optimized the ability of your KPC-3+ to decode what it hears.

Thank you for the suggestions. If I may, the same question I asked the other responder - why no text response from my connection to my own PBBS? Doesn't that seem to point to a different issue than setting carrier detect? Thanks!