Help with TNC9k6 setup


Don Munson
 

First I am an operator and not a technician.  I can follow directions and to some extent do enough to get myself in trouble.  Having said that I purchased a TNC9k6 and have it running wiht a Raspberry PI 3B+.  Followed directions at (https://tnc-x.com/TNCPi.pdf) downloaded the pitnc files, set them in the directory and set permission to execute by owner.  Verified with ls -l that all permissions and owner/group ids as well as my logge din user are all setup per the text.

when I run the ./pitnc_getparams /dev/serial0 0 - I get the notation that RPi is using Serial 0 then Com Open Failed: permission denied.

I'm at a loss.  Searching here provides a slew of comm errors dated years back that are not trying serial but  ./pitnc_getparams 0 0 - when I try that it defaults to a TTY device (AAM0?) and simply repeats "retrying" which purportedly means a configuration issue.  But what configuration it is straight out of the setup - I've tweaked nothing in the RPI configuration.

Help?

Don, W4GFQ


steve.stroh@...
 

Don:

Just covering the obvious here but the TNC-Pi is a completely different product than the TNC-Pi9k6 and the instructions for the TNC-Pi are not applicable to the -Pi9k6. 

Steve N8GNJ

On Thu, Jun 25, 2020 at 23:01 Don Munson <w4gfq@...> wrote:
First I am an operator and not a technician.  I can follow directions and to some extent do enough to get myself in trouble.  Having said that I purchased a TNC9k6 and have it running wiht a Raspberry PI 3B+.  Followed directions at (https://tnc-x.com/TNCPi.pdf) downloaded the pitnc files, set them in the directory and set permission to execute by owner.  Verified with ls -l that all permissions and owner/group ids as well as my logge din user are all setup per the text.

when I run the ./pitnc_getparams /dev/serial0 0 - I get the notation that RPi is using Serial 0 then Com Open Failed: permission denied.

I'm at a loss.  Searching here provides a slew of comm errors dated years back that are not trying serial but  ./pitnc_getparams 0 0 - when I try that it defaults to a TTY device (AAM0?) and simply repeats "retrying" which purportedly means a configuration issue.  But what configuration it is straight out of the setup - I've tweaked nothing in the RPI configuration.

Help?

Don, W4GFQ

--
Steve Stroh (personal / general): stevestroh@...


Mark Griffith
 

Don,

First, you'll also need to use the raspi-config utility to enable the console serial port, but disable console login.

Run "sudo raspi-config"

Then go to menu 5, Interfacing Options, then menu P6, and disable the login shell over the serial port.

On the next screen, keep the serial port enabled.

Save these and finish.

Now try "sudo pitnc-getparams /dev/serial0 0"

This works the same with the TNC-Pi2 or the TNC-Pi9k6 and will be the same with the TNC-Pi3 once MFJ starts selling them.

Mark
KD0QYN


On Friday, June 26, 2020, 1:01:22 AM CDT, Don Munson <w4gfq@...> wrote:


First I am an operator and not a technician.  I can follow directions and to some extent do enough to get myself in trouble.  Having said that I purchased a TNC9k6 and have it running wiht a Raspberry PI 3B+.  Followed directions at (https://tnc-x.com/TNCPi.pdf) downloaded the pitnc files, set them in the directory and set permission to execute by owner.  Verified with ls -l that all permissions and owner/group ids as well as my logge din user are all setup per the text.

when I run the ./pitnc_getparams /dev/serial0 0 - I get the notation that RPi is using Serial 0 then Com Open Failed: permission denied.

I'm at a loss.  Searching here provides a slew of comm errors dated years back that are not trying serial but  ./pitnc_getparams 0 0 - when I try that it defaults to a TTY device (AAM0?) and simply repeats "retrying" which purportedly means a configuration issue.  But what configuration it is straight out of the setup - I've tweaked nothing in the RPI configuration.

Help?

Don, W4GFQ


Don Munson
 

That was my reaction as well, but every reference I can find looking for a “manual” points back to the TNC PI.  It was an impulse buy to see about getting a mobile packet station and the ability to have either 1200 or 9600 was attractive (as was working on a Pi).  But I was NOT prepared for the relative lack of instruction on what to do with it once I had it.

 

As I said I can follow instructions and extrapolate / learn as I go.  But learning from zero is a large row to hoe.

 

At this point I’d love to have a compilation of where/what/how, but my ability to find is running on empty.

 

Don

 

From: RaspberryPi-4-HamRadio@groups.io <RaspberryPi-4-HamRadio@groups.io> On Behalf Of steve.stroh@...
Sent: Friday, June 26, 2020 2:08 AM
To: RaspberryPi-4-HamRadio@groups.io
Subject: Re: [RaspberryPi-4-HamRadio] Help with TNC9k6 setup

 

Don:

 

Just covering the obvious here but the TNC-Pi is a completely different product than the TNC-Pi9k6 and the instructions for the TNC-Pi are not applicable to the -Pi9k6. 

 

Steve N8GNJ

 

On Thu, Jun 25, 2020 at 23:01 Don Munson <w4gfq@...> wrote:

First I am an operator and not a technician.  I can follow directions and to some extent do enough to get myself in trouble.  Having said that I purchased a TNC9k6 and have it running wiht a Raspberry PI 3B+.  Followed directions at (https://tnc-x.com/TNCPi.pdf) downloaded the pitnc files, set them in the directory and set permission to execute by owner.  Verified with ls -l that all permissions and owner/group ids as well as my logge din user are all setup per the text.

when I run the ./pitnc_getparams /dev/serial0 0 - I get the notation that RPi is using Serial 0 then Com Open Failed: permission denied.

I'm at a loss.  Searching here provides a slew of comm errors dated years back that are not trying serial but  ./pitnc_getparams 0 0 - when I try that it defaults to a TTY device (AAM0?) and simply repeats "retrying" which purportedly means a configuration issue.  But what configuration it is straight out of the setup - I've tweaked nothing in the RPI configuration.

Help?

Don, W4GFQ

--

Steve Stroh (personal / general): stevestroh@...


Don Munson
 

EXCELLENT!! 

 

So after six tries because it is early and I simply can’t type (and I have learned Linux is very unforgiving on typing!) I got the following:

 

Using Serial Port /dev/serial0 

retrying

 

and a presentation of the parameters.  

 

Now at least I know they are talking to each other 😊

 

I am not sure why it worked but it did.  I am going to presume that somehow the putty connection to the pi was using the serial port?  Although how it still connects (as does VNC) confuses me – but no matter.

 

The obvious next question is where do I go from here for reading about how to configure and use this board?

 

Don, W4GFQ

 

From: RaspberryPi-4-HamRadio@groups.io <RaspberryPi-4-HamRadio@groups.io> On Behalf Of Mark Griffith via groups.io
Sent: Friday, June 26, 2020 7:10 AM
To: RaspberryPi-4-HamRadio@groups.io
Subject: Re: [RaspberryPi-4-HamRadio] Help with TNC9k6 setup

 

Don,

 

First, you'll also need to use the raspi-config utility to enable the console serial port, but disable console login.

 

Run "sudo raspi-config"

 

Then go to menu 5, Interfacing Options, then menu P6, and disable the login shell over the serial port.

 

On the next screen, keep the serial port enabled.

 

Save these and finish.

 

Now try "sudo pitnc-getparams /dev/serial0 0"

 

This works the same with the TNC-Pi2 or the TNC-Pi9k6 and will be the same with the TNC-Pi3 once MFJ starts selling them.

 

Mark

KD0QYN

 

 

On Friday, June 26, 2020, 1:01:22 AM CDT, Don Munson <w4gfq@...> wrote:

 

 

First I am an operator and not a technician.  I can follow directions and to some extent do enough to get myself in trouble.  Having said that I purchased a TNC9k6 and have it running wiht a Raspberry PI 3B+.  Followed directions at (https://tnc-x.com/TNCPi.pdf) downloaded the pitnc files, set them in the directory and set permission to execute by owner.  Verified with ls -l that all permissions and owner/group ids as well as my logge din user are all setup per the text.

when I run the ./pitnc_getparams /dev/serial0 0 - I get the notation that RPi is using Serial 0 then Com Open Failed: permission denied.

I'm at a loss.  Searching here provides a slew of comm errors dated years back that are not trying serial but  ./pitnc_getparams 0 0 - when I try that it defaults to a TTY device (AAM0?) and simply repeats "retrying" which purportedly means a configuration issue.  But what configuration it is straight out of the setup - I've tweaked nothing in the RPI configuration.

Help?

Don, W4GFQ


Don Poaps
 

That is far as I got as well, I can see /dev/serial0 0 and /dev/serial1 0.
I need the 6 pin to work. I try the kissattach command. Shown on getpat,io.

73

Don va7dgp



On Fri., Jun. 26, 2020, 4:58 a.m. Don Munson <w4gfq@...> wrote:

EXCELLENT!! 

 

So after six tries because it is early and I simply can’t type (and I have learned Linux is very unforgiving on typing!) I got the following:

 

Using Serial Port /dev/serial0 

retrying

 

and a presentation of the parameters.  

 

Now at least I know they are talking to each other 😊

 

I am not sure why it worked but it did.  I am going to presume that somehow the putty connection to the pi was using the serial port?  Although how it still connects (as does VNC) confuses me – but no matter.

 

The obvious next question is where do I go from here for reading about how to configure and use this board?

 

Don, W4GFQ

 

From: RaspberryPi-4-HamRadio@groups.io <RaspberryPi-4-HamRadio@groups.io> On Behalf Of Mark Griffith via groups.io
Sent: Friday, June 26, 2020 7:10 AM
To: RaspberryPi-4-HamRadio@groups.io
Subject: Re: [RaspberryPi-4-HamRadio] Help with TNC9k6 setup

 

Don,

 

First, you'll also need to use the raspi-config utility to enable the console serial port, but disable console login.

 

Run "sudo raspi-config"

 

Then go to menu 5, Interfacing Options, then menu P6, and disable the login shell over the serial port.

 

On the next screen, keep the serial port enabled.

 

Save these and finish.

 

Now try "sudo pitnc-getparams /dev/serial0 0"

 

This works the same with the TNC-Pi2 or the TNC-Pi9k6 and will be the same with the TNC-Pi3 once MFJ starts selling them.

 

Mark

KD0QYN

 

 

On Friday, June 26, 2020, 1:01:22 AM CDT, Don Munson <w4gfq@...> wrote:

 

 

First I am an operator and not a technician.  I can follow directions and to some extent do enough to get myself in trouble.  Having said that I purchased a TNC9k6 and have it running wiht a Raspberry PI 3B+.  Followed directions at (https://tnc-x.com/TNCPi.pdf) downloaded the pitnc files, set them in the directory and set permission to execute by owner.  Verified with ls -l that all permissions and owner/group ids as well as my logge din user are all setup per the text.

when I run the ./pitnc_getparams /dev/serial0 0 - I get the notation that RPi is using Serial 0 then Com Open Failed: permission denied.

I'm at a loss.  Searching here provides a slew of comm errors dated years back that are not trying serial but  ./pitnc_getparams 0 0 - when I try that it defaults to a TTY device (AAM0?) and simply repeats "retrying" which purportedly means a configuration issue.  But what configuration it is straight out of the setup - I've tweaked nothing in the RPI configuration.

Help?

Don, W4GFQ


Mark Griffith
 

Don,

When you connect through PuTTY, is is through an SSH or Secure Shell TCP/IP connection port, not serial.  VNC is also through a direct connection at a non-serial port.

Where did you get the TNC-Pi9k6 from?  I've attached the docs from the old Coastal Chipworks site.  The board and procedure to build it is a little different than the other people selling this board, but the firmware configuration docs are still correct.

I'm getting ready to make a change in my website to reflect that the TNC-Pi9k6 is the choice for both the PiGate and PiGate RMS devices.  Is is a drop-in replacement for the TNC-Pi2.  I'm not too happy with the progress MFJ is making with building the new TNC-Pi3 board, and the West Virginia group that is now selling the TNC-Pi9k6 as an assembled board has a great price, which is probably going to be close to what MFJ sells the 1200 baud only board for.

Here's my web site in case you are interested in using your Pi and the TNC for communications with Winlink2000.

Mark
KD0QYN






Let me know if you have any more questions.

Mark
KD0QYN



On Friday, June 26, 2020, 6:58:46 AM CDT, Don Munson <w4gfq@...> wrote:


EXCELLENT!! 

 

So after six tries because it is early and I simply can’t type (and I have learned Linux is very unforgiving on typing!) I got the following:

 

Using Serial Port /dev/serial0 

retrying

 

and a presentation of the parameters.  

 

Now at least I know they are talking to each other 😊

 

I am not sure why it worked but it did.  I am going to presume that somehow the putty connection to the pi was using the serial port?  Although how it still connects (as does VNC) confuses me – but no matter.

 

The obvious next question is where do I go from here for reading about how to configure and use this board?

 

Don, W4GFQ

 

From: RaspberryPi-4-HamRadio@groups.io <RaspberryPi-4-HamRadio@groups.io> On Behalf Of Mark Griffith via groups.io
Sent: Friday, June 26, 2020 7:10 AM
To: RaspberryPi-4-HamRadio@groups.io
Subject: Re: [RaspberryPi-4-HamRadio] Help with TNC9k6 setup

 

Don,

 

First, you'll also need to use the raspi-config utility to enable the console serial port, but disable console login.

 

Run "sudo raspi-config"

 

Then go to menu 5, Interfacing Options, then menu P6, and disable the login shell over the serial port.

 

On the next screen, keep the serial port enabled.

 

Save these and finish.

 

Now try "sudo pitnc-getparams /dev/serial0 0"

 

This works the same with the TNC-Pi2 or the TNC-Pi9k6 and will be the same with the TNC-Pi3 once MFJ starts selling them.

 

Mark

KD0QYN

 

 

On Friday, June 26, 2020, 1:01:22 AM CDT, Don Munson <w4gfq@...> wrote:

 

 

First I am an operator and not a technician.  I can follow directions and to some extent do enough to get myself in trouble.  Having said that I purchased a TNC9k6 and have it running wiht a Raspberry PI 3B+.  Followed directions at (https://tnc-x.com/TNCPi.pdf) downloaded the pitnc files, set them in the directory and set permission to execute by owner.  Verified with ls -l that all permissions and owner/group ids as well as my logge din user are all setup per the text.

when I run the ./pitnc_getparams /dev/serial0 0 - I get the notation that RPi is using Serial 0 then Com Open Failed: permission denied.

I'm at a loss.  Searching here provides a slew of comm errors dated years back that are not trying serial but  ./pitnc_getparams 0 0 - when I try that it defaults to a TTY device (AAM0?) and simply repeats "retrying" which purportedly means a configuration issue.  But what configuration it is straight out of the setup - I've tweaked nothing in the RPI configuration.

Help?

Don, W4GFQ


Don Poaps
 

I got the Pi TNC from John Hanson a few years go. It's been sitting on a PI 3. Theres 2 modes I want to do. APRS and Pat Winlink. I know I have to do a Kissattach /dev/serial0 or something like that. I don't really want to load BPQ. I use vnc to log in via km4ack hotspot. 10.10.10.10:5900 for the vnc. I know how to create ssh before I run a fresh install of Buster etc. I then log in via putty on my Windown machine and the run raspi-config and setup the PI for SSH, VNC and SERIAL and the Resultion for getting way from that black screen for desktop display.
I have created the mkdir pitnc in /home/pi directory. I have run the setup. 
It's getting a script for APRS and a Script to run start Pat Winlink.

I'm learning but I'm clueless about how to set this up so when I log in via VNC and have a very small screen while I'm mobile. I can click on a icon and the script starts APRS. If I want Pat Winlink. I click on a Icon and the script fires up and I now can use Pat Winlink. 
As mentioned by Don (forget his USA call) he said the info is outdated. If there was a website created that had the command line where once could create the APRS and Pat Winlink for the PI tnc. 

I'll slip over to the site you mentioned and see If I can get this Pi to work.

73

Don va7dgp

Don Poaps
New Westminster, BC
VA7DGP DATA
VA7QU   VOICE


Winlink: va7qu@...
Subject://wl2k           



                    
  




 


On Fri, Jun 26, 2020 at 8:51 AM Mark Griffith via groups.io <mdgriffith2003=yahoo.com@groups.io> wrote:
Don,

When you connect through PuTTY, is is through an SSH or Secure Shell TCP/IP connection port, not serial.  VNC is also through a direct connection at a non-serial port.

Where did you get the TNC-Pi9k6 from?  I've attached the docs from the old Coastal Chipworks site.  The board and procedure to build it is a little different than the other people selling this board, but the firmware configuration docs are still correct.

I'm getting ready to make a change in my website to reflect that the TNC-Pi9k6 is the choice for both the PiGate and PiGate RMS devices.  Is is a drop-in replacement for the TNC-Pi2.  I'm not too happy with the progress MFJ is making with building the new TNC-Pi3 board, and the West Virginia group that is now selling the TNC-Pi9k6 as an assembled board has a great price, which is probably going to be close to what MFJ sells the 1200 baud only board for.

Here's my web site in case you are interested in using your Pi and the TNC for communications with Winlink2000.

Mark
KD0QYN






Let me know if you have any more questions.

Mark
KD0QYN



On Friday, June 26, 2020, 6:58:46 AM CDT, Don Munson <w4gfq@...> wrote:


EXCELLENT!! 

 

So after six tries because it is early and I simply can’t type (and I have learned Linux is very unforgiving on typing!) I got the following:

 

Using Serial Port /dev/serial0 

retrying

 

and a presentation of the parameters.  

 

Now at least I know they are talking to each other 😊

 

I am not sure why it worked but it did.  I am going to presume that somehow the putty connection to the pi was using the serial port?  Although how it still connects (as does VNC) confuses me – but no matter.

 

The obvious next question is where do I go from here for reading about how to configure and use this board?

 

Don, W4GFQ

 

From: RaspberryPi-4-HamRadio@groups.io <RaspberryPi-4-HamRadio@groups.io> On Behalf Of Mark Griffith via groups.io
Sent: Friday, June 26, 2020 7:10 AM
To: RaspberryPi-4-HamRadio@groups.io
Subject: Re: [RaspberryPi-4-HamRadio] Help with TNC9k6 setup

 

Don,

 

First, you'll also need to use the raspi-config utility to enable the console serial port, but disable console login.

 

Run "sudo raspi-config"

 

Then go to menu 5, Interfacing Options, then menu P6, and disable the login shell over the serial port.

 

On the next screen, keep the serial port enabled.

 

Save these and finish.

 

Now try "sudo pitnc-getparams /dev/serial0 0"

 

This works the same with the TNC-Pi2 or the TNC-Pi9k6 and will be the same with the TNC-Pi3 once MFJ starts selling them.

 

Mark

KD0QYN

 

 

On Friday, June 26, 2020, 1:01:22 AM CDT, Don Munson <w4gfq@...> wrote:

 

 

First I am an operator and not a technician.  I can follow directions and to some extent do enough to get myself in trouble.  Having said that I purchased a TNC9k6 and have it running wiht a Raspberry PI 3B+.  Followed directions at (https://tnc-x.com/TNCPi.pdf) downloaded the pitnc files, set them in the directory and set permission to execute by owner.  Verified with ls -l that all permissions and owner/group ids as well as my logge din user are all setup per the text.

when I run the ./pitnc_getparams /dev/serial0 0 - I get the notation that RPi is using Serial 0 then Com Open Failed: permission denied.

I'm at a loss.  Searching here provides a slew of comm errors dated years back that are not trying serial but  ./pitnc_getparams 0 0 - when I try that it defaults to a TTY device (AAM0?) and simply repeats "retrying" which purportedly means a configuration issue.  But what configuration it is straight out of the setup - I've tweaked nothing in the RPI configuration.

Help?

Don, W4GFQ


Mark Griffith
 

Don,

If you have the latest Raspbian Buster installed, AX.25 is already there and ready to go.  However, you need to edit a couple files to get it setup.  The PiGate software does this for you, but if you want to do it yourself:

Edit /etc/ax25/axports

It should have some lines in there like this:

# The format of this file is:
#portname       callsign        speed   paclen  window  description
tnc             KD0QYN-1        19200   128     2       TNC-Pi2 VHF
#uhfdrop        N0ONE-3         9600    128     2       443.425MHz+ 1200baud UHF Drop
#hfdrop         N0ONE-5         9600    32      2       40m HF Drop
#wtrunk         N0ONE-11        38400   253     2       UHF Trunk West
#etrunk         N0ONE-13        38400   253     2       UHF Trunk East
#axudp          N0ONE-8         115200  253     2       Linux (AX25<->UDP)

Notice that I changed one to have a port name of tnc, and added my call sign and a speed of 19200.  This is for the TNC-Pi.

Then edit /etc/default/ax25

There are three settings you need to change:

AXPORT=tnc (or whatever you called it)
HBAUD=19200
DEV=/dev/ttyserial0  (you can also try /dev/ttyAMA0)

Save both these files and run the command "sudo service ax25 start"

Then run the command "sudo service ax25 status"

You should see the service status and there should be a line saying it is loaded and active.

You can also run this command to see if kissattach has been successful:

"sudo ps -ef | grep kiss"  and it should return a line of two showing kissattach has been run on the serial port.

Now, pat or APRS will be able to connect to that port,  /dev/serial0, and access the KISS modem.

Let me know if you have any more questions.

NOTE: This is for Raspbian Buster.  Any other version may have the files in a different location, different file names, or different entries in the files.

Mark
KD0QYN



On Friday, June 26, 2020, 11:19:06 AM CDT, Don Poaps <va7dgp@...> wrote:


I got the Pi TNC from John Hanson a few years go. It's been sitting on a PI 3. Theres 2 modes I want to do. APRS and Pat Winlink. I know I have to do a Kissattach /dev/serial0 or something like that. I don't really want to load BPQ. I use vnc to log in via km4ack hotspot. 10.10.10.10:5900 for the vnc. I know how to create ssh before I run a fresh install of Buster etc. I then log in via putty on my Windown machine and the run raspi-config and setup the PI for SSH, VNC and SERIAL and the Resultion for getting way from that black screen for desktop display.
I have created the mkdir pitnc in /home/pi directory. I have run the setup. 
It's getting a script for APRS and a Script to run start Pat Winlink.

I'm learning but I'm clueless about how to set this up so when I log in via VNC and have a very small screen while I'm mobile. I can click on a icon and the script starts APRS. If I want Pat Winlink. I click on a Icon and the script fires up and I now can use Pat Winlink. 
As mentioned by Don (forget his USA call) he said the info is outdated. If there was a website created that had the command line where once could create the APRS and Pat Winlink for the PI tnc. 

I'll slip over to the site you mentioned and see If I can get this Pi to work.

73

Don va7dgp

Don Poaps
New Westminster, BC
VA7DGP DATA
VA7QU   VOICE


Winlink: va7qu@...
Subject://wl2k           



                    
  




 


On Fri, Jun 26, 2020 at 8:51 AM Mark Griffith via groups.io <mdgriffith2003=yahoo.com@groups.io> wrote:
Don,

When you connect through PuTTY, is is through an SSH or Secure Shell TCP/IP connection port, not serial.  VNC is also through a direct connection at a non-serial port.

Where did you get the TNC-Pi9k6 from?  I've attached the docs from the old Coastal Chipworks site.  The board and procedure to build it is a little different than the other people selling this board, but the firmware configuration docs are still correct.

I'm getting ready to make a change in my website to reflect that the TNC-Pi9k6 is the choice for both the PiGate and PiGate RMS devices.  Is is a drop-in replacement for the TNC-Pi2.  I'm not too happy with the progress MFJ is making with building the new TNC-Pi3 board, and the West Virginia group that is now selling the TNC-Pi9k6 as an assembled board has a great price, which is probably going to be close to what MFJ sells the 1200 baud only board for.

Here's my web site in case you are interested in using your Pi and the TNC for communications with Winlink2000.

Mark
KD0QYN






Let me know if you have any more questions.

Mark
KD0QYN



On Friday, June 26, 2020, 6:58:46 AM CDT, Don Munson <w4gfq@...> wrote:


EXCELLENT!! 

 

So after six tries because it is early and I simply can’t type (and I have learned Linux is very unforgiving on typing!) I got the following:

 

Using Serial Port /dev/serial0 

retrying

 

and a presentation of the parameters.  

 

Now at least I know they are talking to each other 😊

 

I am not sure why it worked but it did.  I am going to presume that somehow the putty connection to the pi was using the serial port?  Although how it still connects (as does VNC) confuses me – but no matter.

 

The obvious next question is where do I go from here for reading about how to configure and use this board?

 

Don, W4GFQ

 

From: RaspberryPi-4-HamRadio@groups.io <RaspberryPi-4-HamRadio@groups.io> On Behalf Of Mark Griffith via groups.io
Sent: Friday, June 26, 2020 7:10 AM
To: RaspberryPi-4-HamRadio@groups.io
Subject: Re: [RaspberryPi-4-HamRadio] Help with TNC9k6 setup

 

Don,

 

First, you'll also need to use the raspi-config utility to enable the console serial port, but disable console login.

 

Run "sudo raspi-config"

 

Then go to menu 5, Interfacing Options, then menu P6, and disable the login shell over the serial port.

 

On the next screen, keep the serial port enabled.

 

Save these and finish.

 

Now try "sudo pitnc-getparams /dev/serial0 0"

 

This works the same with the TNC-Pi2 or the TNC-Pi9k6 and will be the same with the TNC-Pi3 once MFJ starts selling them.

 

Mark

KD0QYN

 

 

On Friday, June 26, 2020, 1:01:22 AM CDT, Don Munson <w4gfq@...> wrote:

 

 

First I am an operator and not a technician.  I can follow directions and to some extent do enough to get myself in trouble.  Having said that I purchased a TNC9k6 and have it running wiht a Raspberry PI 3B+.  Followed directions at (https://tnc-x.com/TNCPi.pdf) downloaded the pitnc files, set them in the directory and set permission to execute by owner.  Verified with ls -l that all permissions and owner/group ids as well as my logge din user are all setup per the text.

when I run the ./pitnc_getparams /dev/serial0 0 - I get the notation that RPi is using Serial 0 then Com Open Failed: permission denied.

I'm at a loss.  Searching here provides a slew of comm errors dated years back that are not trying serial but  ./pitnc_getparams 0 0 - when I try that it defaults to a TTY device (AAM0?) and simply repeats "retrying" which purportedly means a configuration issue.  But what configuration it is straight out of the setup - I've tweaked nothing in the RPI configuration.

Help?

Don, W4GFQ


Don Poaps
 

see below






On Fri, Jun 26, 2020 at 10:16 AM Mark Griffith via groups.io <mdgriffith2003=yahoo.com@groups.io> wrote:
Don,

If you have the latest Raspbian Buster installed, AX.25 is already there and ready to go.  However, you need to edit a couple files to get it setup.  The PiGate software does this for you, but if you want to do it yourself:

Edit /etc/ax25/axports

It should have some lines in there like this:

wl2k VA7DGP 1200 255 7 Winlink
tnc VA7DGP 19200 128 2 TNC-Pi2 VHF

# The format of this file is:
#portname       callsign        speed   paclen  window  description
tnc             KD0QYN-1        19200   128     2       TNC-Pi2 VHF
#uhfdrop        N0ONE-3         9600    128     2       443.425MHz+ 1200baud UHF Drop
#hfdrop         N0ONE-5         9600    32      2       40m HF Drop
#wtrunk         N0ONE-11        38400   253     2       UHF Trunk West
#etrunk         N0ONE-13        38400   253     2       UHF Trunk East
#axudp          N0ONE-8         115200  253     2       Linux (AX25<->UDP)

Notice that I changed one to have a port name of tnc, and added my call sign and a speed of 19200.  This is for the TNC-Pi.

Then edit /etc/default/ax25

There are three settings you need to change:

AXPORT=tnc (or whatever you called it)
HBAUD=19200
DEV=/dev/ttyserial0  (you can also try /dev/ttyAMA0)

I didn't have this file in /dev/default/ac25

I added 

AXPORT=tnc
HBAUD=19200
DEV=/dev/serial0

as seen on my PI

pi@raspberrypi:~ $ ls /dev/serial*
/dev/serial0  /dev/serial1
pi@raspberrypi:~ $


Just for verification 

Don

Save both these files and run the command "sudo service ax25 start"

Then run the command "sudo service ax25 status"

You should see the service status and there should be a line saying it is loaded and active.

You can also run this command to see if kissattach has been successful:

"sudo ps -ef | grep kiss"  and it should return a line of two showing kissattach has been run on the serial port.

Now, pat or APRS will be able to connect to that port,  /dev/serial0, and access the KISS modem.

Let me know if you have any more questions.

NOTE: This is for Raspbian Buster.  Any other version may have the files in a different location, different file names, or different entries in the files.

Mark
KD0QYN



On Friday, June 26, 2020, 11:19:06 AM CDT, Don Poaps <va7dgp@...> wrote:


I got the Pi TNC from John Hanson a few years go. It's been sitting on a PI 3. Theres 2 modes I want to do. APRS and Pat Winlink. I know I have to do a Kissattach /dev/serial0 or something like that. I don't really want to load BPQ. I use vnc to log in via km4ack hotspot. 10.10.10.10:5900 for the vnc. I know how to create ssh before I run a fresh install of Buster etc. I then log in via putty on my Windown machine and the run raspi-config and setup the PI for SSH, VNC and SERIAL and the Resultion for getting way from that black screen for desktop display.
I have created the mkdir pitnc in /home/pi directory. I have run the setup. 
It's getting a script for APRS and a Script to run start Pat Winlink.

I'm learning but I'm clueless about how to set this up so when I log in via VNC and have a very small screen while I'm mobile. I can click on a icon and the script starts APRS. If I want Pat Winlink. I click on a Icon and the script fires up and I now can use Pat Winlink. 
As mentioned by Don (forget his USA call) he said the info is outdated. If there was a website created that had the command line where once could create the APRS and Pat Winlink for the PI tnc. 

I'll slip over to the site you mentioned and see If I can get this Pi to work.

73

Don va7dgp

Don Poaps
New Westminster, BC
VA7DGP DATA
VA7QU   VOICE


Winlink: va7qu@...
Subject://wl2k           



                    
  




 


On Fri, Jun 26, 2020 at 8:51 AM Mark Griffith via groups.io <mdgriffith2003=yahoo.com@groups.io> wrote:
Don,

When you connect through PuTTY, is is through an SSH or Secure Shell TCP/IP connection port, not serial.  VNC is also through a direct connection at a non-serial port.

Where did you get the TNC-Pi9k6 from?  I've attached the docs from the old Coastal Chipworks site.  The board and procedure to build it is a little different than the other people selling this board, but the firmware configuration docs are still correct.

I'm getting ready to make a change in my website to reflect that the TNC-Pi9k6 is the choice for both the PiGate and PiGate RMS devices.  Is is a drop-in replacement for the TNC-Pi2.  I'm not too happy with the progress MFJ is making with building the new TNC-Pi3 board, and the West Virginia group that is now selling the TNC-Pi9k6 as an assembled board has a great price, which is probably going to be close to what MFJ sells the 1200 baud only board for.

Here's my web site in case you are interested in using your Pi and the TNC for communications with Winlink2000.

Mark
KD0QYN






Let me know if you have any more questions.

Mark
KD0QYN



On Friday, June 26, 2020, 6:58:46 AM CDT, Don Munson <w4gfq@...> wrote:


EXCELLENT!! 

 

So after six tries because it is early and I simply can’t type (and I have learned Linux is very unforgiving on typing!) I got the following:

 

Using Serial Port /dev/serial0 

retrying

 

and a presentation of the parameters.  

 

Now at least I know they are talking to each other 😊

 

I am not sure why it worked but it did.  I am going to presume that somehow the putty connection to the pi was using the serial port?  Although how it still connects (as does VNC) confuses me – but no matter.

 

The obvious next question is where do I go from here for reading about how to configure and use this board?

 

Don, W4GFQ

 

From: RaspberryPi-4-HamRadio@groups.io <RaspberryPi-4-HamRadio@groups.io> On Behalf Of Mark Griffith via groups.io
Sent: Friday, June 26, 2020 7:10 AM
To: RaspberryPi-4-HamRadio@groups.io
Subject: Re: [RaspberryPi-4-HamRadio] Help with TNC9k6 setup

 

Don,

 

First, you'll also need to use the raspi-config utility to enable the console serial port, but disable console login.

 

Run "sudo raspi-config"

 

Then go to menu 5, Interfacing Options, then menu P6, and disable the login shell over the serial port.

 

On the next screen, keep the serial port enabled.

 

Save these and finish.

 

Now try "sudo pitnc-getparams /dev/serial0 0"

 

This works the same with the TNC-Pi2 or the TNC-Pi9k6 and will be the same with the TNC-Pi3 once MFJ starts selling them.

 

Mark

KD0QYN

 

 

On Friday, June 26, 2020, 1:01:22 AM CDT, Don Munson <w4gfq@...> wrote:

 

 

First I am an operator and not a technician.  I can follow directions and to some extent do enough to get myself in trouble.  Having said that I purchased a TNC9k6 and have it running wiht a Raspberry PI 3B+.  Followed directions at (https://tnc-x.com/TNCPi.pdf) downloaded the pitnc files, set them in the directory and set permission to execute by owner.  Verified with ls -l that all permissions and owner/group ids as well as my logge din user are all setup per the text.

when I run the ./pitnc_getparams /dev/serial0 0 - I get the notation that RPi is using Serial 0 then Com Open Failed: permission denied.

I'm at a loss.  Searching here provides a slew of comm errors dated years back that are not trying serial but  ./pitnc_getparams 0 0 - when I try that it defaults to a TTY device (AAM0?) and simply repeats "retrying" which purportedly means a configuration issue.  But what configuration it is straight out of the setup - I've tweaked nothing in the RPI configuration.

Help?

Don, W4GFQ


Don Poaps
 

AX 25 services issues

pi@raspberrypi:~ $ cd pitnc
pi@raspberrypi:~/pitnc $ sudo systemctl start ax25
Failed to start ax25.service: Unit ax25.service not found.
pi@raspberrypi:~/pitnc $ sudo systemctl enable ax25
Failed to enable unit: Unit file ax25.service does not exist.
pi@raspberrypi:~/pitnc $ 

Taking the XYL to her Mom's maybe when I back 30-40 minutes I'll have a better idea of whats going on.


Don Poaps
New Westminster, BC
VA7DGP DATA
VA7QU   VOICE


Winlink: va7qu@...
Subject://wl2k           



                    
  




 


On Fri, Jun 26, 2020 at 11:10 AM Don Poaps via groups.io <va7dgp=gmail.com@groups.io> wrote:
see below






On Fri, Jun 26, 2020 at 10:16 AM Mark Griffith via groups.io <mdgriffith2003=yahoo.com@groups.io> wrote:
Don,

If you have the latest Raspbian Buster installed, AX.25 is already there and ready to go.  However, you need to edit a couple files to get it setup.  The PiGate software does this for you, but if you want to do it yourself:

Edit /etc/ax25/axports

It should have some lines in there like this:

wl2k VA7DGP 1200 255 7 Winlink
tnc VA7DGP 19200 128 2 TNC-Pi2 VHF

# The format of this file is:
#portname       callsign        speed   paclen  window  description
tnc             KD0QYN-1        19200   128     2       TNC-Pi2 VHF
#uhfdrop        N0ONE-3         9600    128     2       443.425MHz+ 1200baud UHF Drop
#hfdrop         N0ONE-5         9600    32      2       40m HF Drop
#wtrunk         N0ONE-11        38400   253     2       UHF Trunk West
#etrunk         N0ONE-13        38400   253     2       UHF Trunk East
#axudp          N0ONE-8         115200  253     2       Linux (AX25<->UDP)

Notice that I changed one to have a port name of tnc, and added my call sign and a speed of 19200.  This is for the TNC-Pi.

Then edit /etc/default/ax25

There are three settings you need to change:

AXPORT=tnc (or whatever you called it)
HBAUD=19200
DEV=/dev/ttyserial0  (you can also try /dev/ttyAMA0)

I didn't have this file in /dev/default/ac25

I added 

AXPORT=tnc
HBAUD=19200
DEV=/dev/serial0

as seen on my PI

pi@raspberrypi:~ $ ls /dev/serial*
/dev/serial0  /dev/serial1
pi@raspberrypi:~ $


Just for verification 

Don

Save both these files and run the command "sudo service ax25 start"

Then run the command "sudo service ax25 status"

You should see the service status and there should be a line saying it is loaded and active.

You can also run this command to see if kissattach has been successful:

"sudo ps -ef | grep kiss"  and it should return a line of two showing kissattach has been run on the serial port.

Now, pat or APRS will be able to connect to that port,  /dev/serial0, and access the KISS modem.

Let me know if you have any more questions.

NOTE: This is for Raspbian Buster.  Any other version may have the files in a different location, different file names, or different entries in the files.

Mark
KD0QYN



On Friday, June 26, 2020, 11:19:06 AM CDT, Don Poaps <va7dgp@...> wrote:


I got the Pi TNC from John Hanson a few years go. It's been sitting on a PI 3. Theres 2 modes I want to do. APRS and Pat Winlink. I know I have to do a Kissattach /dev/serial0 or something like that. I don't really want to load BPQ. I use vnc to log in via km4ack hotspot. 10.10.10.10:5900 for the vnc. I know how to create ssh before I run a fresh install of Buster etc. I then log in via putty on my Windown machine and the run raspi-config and setup the PI for SSH, VNC and SERIAL and the Resultion for getting way from that black screen for desktop display.
I have created the mkdir pitnc in /home/pi directory. I have run the setup. 
It's getting a script for APRS and a Script to run start Pat Winlink.

I'm learning but I'm clueless about how to set this up so when I log in via VNC and have a very small screen while I'm mobile. I can click on a icon and the script starts APRS. If I want Pat Winlink. I click on a Icon and the script fires up and I now can use Pat Winlink. 
As mentioned by Don (forget his USA call) he said the info is outdated. If there was a website created that had the command line where once could create the APRS and Pat Winlink for the PI tnc. 

I'll slip over to the site you mentioned and see If I can get this Pi to work.

73

Don va7dgp

Don Poaps
New Westminster, BC
VA7DGP DATA
VA7QU   VOICE


Winlink: va7qu@...
Subject://wl2k           



                    
  




 


On Fri, Jun 26, 2020 at 8:51 AM Mark Griffith via groups.io <mdgriffith2003=yahoo.com@groups.io> wrote:
Don,

When you connect through PuTTY, is is through an SSH or Secure Shell TCP/IP connection port, not serial.  VNC is also through a direct connection at a non-serial port.

Where did you get the TNC-Pi9k6 from?  I've attached the docs from the old Coastal Chipworks site.  The board and procedure to build it is a little different than the other people selling this board, but the firmware configuration docs are still correct.

I'm getting ready to make a change in my website to reflect that the TNC-Pi9k6 is the choice for both the PiGate and PiGate RMS devices.  Is is a drop-in replacement for the TNC-Pi2.  I'm not too happy with the progress MFJ is making with building the new TNC-Pi3 board, and the West Virginia group that is now selling the TNC-Pi9k6 as an assembled board has a great price, which is probably going to be close to what MFJ sells the 1200 baud only board for.

Here's my web site in case you are interested in using your Pi and the TNC for communications with Winlink2000.

Mark
KD0QYN






Let me know if you have any more questions.

Mark
KD0QYN



On Friday, June 26, 2020, 6:58:46 AM CDT, Don Munson <w4gfq@...> wrote:


EXCELLENT!! 

 

So after six tries because it is early and I simply can’t type (and I have learned Linux is very unforgiving on typing!) I got the following:

 

Using Serial Port /dev/serial0 

retrying

 

and a presentation of the parameters.  

 

Now at least I know they are talking to each other 😊

 

I am not sure why it worked but it did.  I am going to presume that somehow the putty connection to the pi was using the serial port?  Although how it still connects (as does VNC) confuses me – but no matter.

 

The obvious next question is where do I go from here for reading about how to configure and use this board?

 

Don, W4GFQ

 

From: RaspberryPi-4-HamRadio@groups.io <RaspberryPi-4-HamRadio@groups.io> On Behalf Of Mark Griffith via groups.io
Sent: Friday, June 26, 2020 7:10 AM
To: RaspberryPi-4-HamRadio@groups.io
Subject: Re: [RaspberryPi-4-HamRadio] Help with TNC9k6 setup

 

Don,

 

First, you'll also need to use the raspi-config utility to enable the console serial port, but disable console login.

 

Run "sudo raspi-config"

 

Then go to menu 5, Interfacing Options, then menu P6, and disable the login shell over the serial port.

 

On the next screen, keep the serial port enabled.

 

Save these and finish.

 

Now try "sudo pitnc-getparams /dev/serial0 0"

 

This works the same with the TNC-Pi2 or the TNC-Pi9k6 and will be the same with the TNC-Pi3 once MFJ starts selling them.

 

Mark

KD0QYN

 

 

On Friday, June 26, 2020, 1:01:22 AM CDT, Don Munson <w4gfq@...> wrote:

 

 

First I am an operator and not a technician.  I can follow directions and to some extent do enough to get myself in trouble.  Having said that I purchased a TNC9k6 and have it running wiht a Raspberry PI 3B+.  Followed directions at (https://tnc-x.com/TNCPi.pdf) downloaded the pitnc files, set them in the directory and set permission to execute by owner.  Verified with ls -l that all permissions and owner/group ids as well as my logge din user are all setup per the text.

when I run the ./pitnc_getparams /dev/serial0 0 - I get the notation that RPi is using Serial 0 then Com Open Failed: permission denied.

I'm at a loss.  Searching here provides a slew of comm errors dated years back that are not trying serial but  ./pitnc_getparams 0 0 - when I try that it defaults to a TTY device (AAM0?) and simply repeats "retrying" which purportedly means a configuration issue.  But what configuration it is straight out of the setup - I've tweaked nothing in the RPI configuration.

Help?

Don, W4GFQ


N5XMT
 

I also don't have those on my Pi running the HamPi V1.0


On Fri, Jun 26, 2020 at 11:17 AM Don Poaps <va7dgp@...> wrote:
AX 25 services issues

pi@raspberrypi:~ $ cd pitnc
pi@raspberrypi:~/pitnc $ sudo systemctl start ax25
Failed to start ax25.service: Unit ax25.service not found.
pi@raspberrypi:~/pitnc $ sudo systemctl enable ax25
Failed to enable unit: Unit file ax25.service does not exist.
pi@raspberrypi:~/pitnc $ 

Taking the XYL to her Mom's maybe when I back 30-40 minutes I'll have a better idea of whats going on.


Don Poaps
New Westminster, BC
VA7DGP DATA
VA7QU   VOICE


Winlink: va7qu@...
Subject://wl2k           



                    
  




 


On Fri, Jun 26, 2020 at 11:10 AM Don Poaps via groups.io <va7dgp=gmail.com@groups.io> wrote:
see below






On Fri, Jun 26, 2020 at 10:16 AM Mark Griffith via groups.io <mdgriffith2003=yahoo.com@groups.io> wrote:
Don,

If you have the latest Raspbian Buster installed, AX.25 is already there and ready to go.  However, you need to edit a couple files to get it setup.  The PiGate software does this for you, but if you want to do it yourself:

Edit /etc/ax25/axports

It should have some lines in there like this:

wl2k VA7DGP 1200 255 7 Winlink
tnc VA7DGP 19200 128 2 TNC-Pi2 VHF

# The format of this file is:
#portname       callsign        speed   paclen  window  description
tnc             KD0QYN-1        19200   128     2       TNC-Pi2 VHF
#uhfdrop        N0ONE-3         9600    128     2       443.425MHz+ 1200baud UHF Drop
#hfdrop         N0ONE-5         9600    32      2       40m HF Drop
#wtrunk         N0ONE-11        38400   253     2       UHF Trunk West
#etrunk         N0ONE-13        38400   253     2       UHF Trunk East
#axudp          N0ONE-8         115200  253     2       Linux (AX25<->UDP)

Notice that I changed one to have a port name of tnc, and added my call sign and a speed of 19200.  This is for the TNC-Pi.

Then edit /etc/default/ax25

There are three settings you need to change:

AXPORT=tnc (or whatever you called it)
HBAUD=19200
DEV=/dev/ttyserial0  (you can also try /dev/ttyAMA0)

I didn't have this file in /dev/default/ac25

I added 

AXPORT=tnc
HBAUD=19200
DEV=/dev/serial0

as seen on my PI

pi@raspberrypi:~ $ ls /dev/serial*
/dev/serial0  /dev/serial1
pi@raspberrypi:~ $


Just for verification 

Don

Save both these files and run the command "sudo service ax25 start"

Then run the command "sudo service ax25 status"

You should see the service status and there should be a line saying it is loaded and active.

You can also run this command to see if kissattach has been successful:

"sudo ps -ef | grep kiss"  and it should return a line of two showing kissattach has been run on the serial port.

Now, pat or APRS will be able to connect to that port,  /dev/serial0, and access the KISS modem.

Let me know if you have any more questions.

NOTE: This is for Raspbian Buster.  Any other version may have the files in a different location, different file names, or different entries in the files.

Mark
KD0QYN



On Friday, June 26, 2020, 11:19:06 AM CDT, Don Poaps <va7dgp@...> wrote:


I got the Pi TNC from John Hanson a few years go. It's been sitting on a PI 3. Theres 2 modes I want to do. APRS and Pat Winlink. I know I have to do a Kissattach /dev/serial0 or something like that. I don't really want to load BPQ. I use vnc to log in via km4ack hotspot. 10.10.10.10:5900 for the vnc. I know how to create ssh before I run a fresh install of Buster etc. I then log in via putty on my Windown machine and the run raspi-config and setup the PI for SSH, VNC and SERIAL and the Resultion for getting way from that black screen for desktop display.
I have created the mkdir pitnc in /home/pi directory. I have run the setup. 
It's getting a script for APRS and a Script to run start Pat Winlink.

I'm learning but I'm clueless about how to set this up so when I log in via VNC and have a very small screen while I'm mobile. I can click on a icon and the script starts APRS. If I want Pat Winlink. I click on a Icon and the script fires up and I now can use Pat Winlink. 
As mentioned by Don (forget his USA call) he said the info is outdated. If there was a website created that had the command line where once could create the APRS and Pat Winlink for the PI tnc. 

I'll slip over to the site you mentioned and see If I can get this Pi to work.

73

Don va7dgp

Don Poaps
New Westminster, BC
VA7DGP DATA
VA7QU   VOICE


Winlink: va7qu@...
Subject://wl2k           



                    
  




 


On Fri, Jun 26, 2020 at 8:51 AM Mark Griffith via groups.io <mdgriffith2003=yahoo.com@groups.io> wrote:
Don,

When you connect through PuTTY, is is through an SSH or Secure Shell TCP/IP connection port, not serial.  VNC is also through a direct connection at a non-serial port.

Where did you get the TNC-Pi9k6 from?  I've attached the docs from the old Coastal Chipworks site.  The board and procedure to build it is a little different than the other people selling this board, but the firmware configuration docs are still correct.

I'm getting ready to make a change in my website to reflect that the TNC-Pi9k6 is the choice for both the PiGate and PiGate RMS devices.  Is is a drop-in replacement for the TNC-Pi2.  I'm not too happy with the progress MFJ is making with building the new TNC-Pi3 board, and the West Virginia group that is now selling the TNC-Pi9k6 as an assembled board has a great price, which is probably going to be close to what MFJ sells the 1200 baud only board for.

Here's my web site in case you are interested in using your Pi and the TNC for communications with Winlink2000.

Mark
KD0QYN






Let me know if you have any more questions.

Mark
KD0QYN



On Friday, June 26, 2020, 6:58:46 AM CDT, Don Munson <w4gfq@...> wrote:


EXCELLENT!! 

 

So after six tries because it is early and I simply can’t type (and I have learned Linux is very unforgiving on typing!) I got the following:

 

Using Serial Port /dev/serial0 

retrying

 

and a presentation of the parameters.  

 

Now at least I know they are talking to each other 😊

 

I am not sure why it worked but it did.  I am going to presume that somehow the putty connection to the pi was using the serial port?  Although how it still connects (as does VNC) confuses me – but no matter.

 

The obvious next question is where do I go from here for reading about how to configure and use this board?

 

Don, W4GFQ

 

From: RaspberryPi-4-HamRadio@groups.io <RaspberryPi-4-HamRadio@groups.io> On Behalf Of Mark Griffith via groups.io
Sent: Friday, June 26, 2020 7:10 AM
To: RaspberryPi-4-HamRadio@groups.io
Subject: Re: [RaspberryPi-4-HamRadio] Help with TNC9k6 setup

 

Don,

 

First, you'll also need to use the raspi-config utility to enable the console serial port, but disable console login.

 

Run "sudo raspi-config"

 

Then go to menu 5, Interfacing Options, then menu P6, and disable the login shell over the serial port.

 

On the next screen, keep the serial port enabled.

 

Save these and finish.

 

Now try "sudo pitnc-getparams /dev/serial0 0"

 

This works the same with the TNC-Pi2 or the TNC-Pi9k6 and will be the same with the TNC-Pi3 once MFJ starts selling them.

 

Mark

KD0QYN

 

 

On Friday, June 26, 2020, 1:01:22 AM CDT, Don Munson <w4gfq@...> wrote:

 

 

First I am an operator and not a technician.  I can follow directions and to some extent do enough to get myself in trouble.  Having said that I purchased a TNC9k6 and have it running wiht a Raspberry PI 3B+.  Followed directions at (https://tnc-x.com/TNCPi.pdf) downloaded the pitnc files, set them in the directory and set permission to execute by owner.  Verified with ls -l that all permissions and owner/group ids as well as my logge din user are all setup per the text.

when I run the ./pitnc_getparams /dev/serial0 0 - I get the notation that RPi is using Serial 0 then Com Open Failed: permission denied.

I'm at a loss.  Searching here provides a slew of comm errors dated years back that are not trying serial but  ./pitnc_getparams 0 0 - when I try that it defaults to a TTY device (AAM0?) and simply repeats "retrying" which purportedly means a configuration issue.  But what configuration it is straight out of the setup - I've tweaked nothing in the RPI configuration.

Help?

Don, W4GFQ


Don Munson
 

Two Dons – go figure 😊

 

I use Putty as SSH as well as VNC – which is why I was sort of curious why turning off Secure Shell seemed to work as I didn’t connect that way.  Unless it reserved it somehow?

 

I got my 9k6 from WVC ARC via Etsy.  I saw the Coastal site.  That is where (I believe) I go the ‘manual’ to follow that was the TNC-Pi originally.  I did find a link I had stuck away (and forgotten) to a ‘manual’ to assemble the WVC board.  That had some additional information in it as well.  That was here: https://www.wvcarc.com/p/tnc-96k-resources.html

 

And your PiGate site was the genesis of my intent to get packet working in my Go Kit 😊  Easy and smooth operation with my V71A to a WinLink node was appealing – but there were NO TNC boards except the 9K6 available.  And since the V71A can do 9600 I said WTH – another arrow in the quiver in addition to standard 1200.

 

My hang up at the moment is the WVC manual which states (implies?) that the Teensy board needs to be loaded with software.  I need to read and digest that a little bit to figure out what that means.  But at the moment all I have “loaded” directly is the Pi itself.  I did see later in this string (or earlier in time) about the AX25 files and I have to go see if those are on the board or not. 

 

It will be steps but as long as I know the steps I should be OK overall.  The challenge to me is finding and understanding the steps 😊

 

Don, W4GFQ

 

From: RaspberryPi-4-HamRadio@groups.io <RaspberryPi-4-HamRadio@groups.io> On Behalf Of Mark Griffith via groups.io
Sent: Friday, June 26, 2020 11:51 AM
To: RaspberryPi-4-HamRadio@groups.io
Subject: Re: [RaspberryPi-4-HamRadio] Help with TNC9k6 setup

 

Don,

 

When you connect through PuTTY, is is through an SSH or Secure Shell TCP/IP connection port, not serial.  VNC is also through a direct connection at a non-serial port.

 

Where did you get the TNC-Pi9k6 from?  I've attached the docs from the old Coastal Chipworks site.  The board and procedure to build it is a little different than the other people selling this board, but the firmware configuration docs are still correct.

 

I'm getting ready to make a change in my website to reflect that the TNC-Pi9k6 is the choice for both the PiGate and PiGate RMS devices.  Is is a drop-in replacement for the TNC-Pi2.  I'm not too happy with the progress MFJ is making with building the new TNC-Pi3 board, and the West Virginia group that is now selling the TNC-Pi9k6 as an assembled board has a great price, which is probably going to be close to what MFJ sells the 1200 baud only board for.

 

Here's my web site in case you are interested in using your Pi and the TNC for communications with Winlink2000.

 

Mark

KD0QYN

 

 

 

 


Pigate - Emergency Communication System, Emergency Radio, Emergency Resp...

An emergency communication system to provide emergency e-mail communications in a disaster scenario.

 

 

 

Let me know if you have any more questions.

 

Mark

KD0QYN

 

 

 

On Friday, June 26, 2020, 6:58:46 AM CDT, Don Munson <w4gfq@...> wrote:

 

 

EXCELLENT!! 

 

So after six tries because it is early and I simply can’t type (and I have learned Linux is very unforgiving on typing!) I got the following:

 

Using Serial Port /dev/serial0 

retrying

 

and a presentation of the parameters.  

 

Now at least I know they are talking to each other 😊

 

I am not sure why it worked but it did.  I am going to presume that somehow the putty connection to the pi was using the serial port?  Although how it still connects (as does VNC) confuses me – but no matter.

 

The obvious next question is where do I go from here for reading about how to configure and use this board?

 

Don, W4GFQ

 

From: RaspberryPi-4-HamRadio@groups.io <RaspberryPi-4-HamRadio@groups.io> On Behalf Of Mark Griffith via groups.io
Sent: Friday, June 26, 2020 7:10 AM
To: RaspberryPi-4-HamRadio@groups.io
Subject: Re: [RaspberryPi-4-HamRadio] Help with TNC9k6 setup

 

Don,

 

First, you'll also need to use the raspi-config utility to enable the console serial port, but disable console login.

 

Run "sudo raspi-config"

 

Then go to menu 5, Interfacing Options, then menu P6, and disable the login shell over the serial port.

 

On the next screen, keep the serial port enabled.

 

Save these and finish.

 

Now try "sudo pitnc-getparams /dev/serial0 0"

 

This works the same with the TNC-Pi2 or the TNC-Pi9k6 and will be the same with the TNC-Pi3 once MFJ starts selling them.

 

Mark

KD0QYN

 

 

On Friday, June 26, 2020, 1:01:22 AM CDT, Don Munson <w4gfq@...> wrote:

 

 

First I am an operator and not a technician.  I can follow directions and to some extent do enough to get myself in trouble.  Having said that I purchased a TNC9k6 and have it running wiht a Raspberry PI 3B+.  Followed directions at (https://tnc-x.com/TNCPi.pdf) downloaded the pitnc files, set them in the directory and set permission to execute by owner.  Verified with ls -l that all permissions and owner/group ids as well as my logge din user are all setup per the text.

when I run the ./pitnc_getparams /dev/serial0 0 - I get the notation that RPi is using Serial 0 then Com Open Failed: permission denied.

I'm at a loss.  Searching here provides a slew of comm errors dated years back that are not trying serial but  ./pitnc_getparams 0 0 - when I try that it defaults to a TTY device (AAM0?) and simply repeats "retrying" which purportedly means a configuration issue.  But what configuration it is straight out of the setup - I've tweaked nothing in the RPI configuration.

Help?

Don, W4GFQ


N5XMT
 

For loading the Teensy, go to the old Pi-TNC site and look at the manual for the PiTNC-9k6 there.  It has instructions for compiling and loading


On Fri, Jun 26, 2020 at 11:54 AM Don Munson <w4gfq@...> wrote:

Two Dons – go figure 😊

 

I use Putty as SSH as well as VNC – which is why I was sort of curious why turning off Secure Shell seemed to work as I didn’t connect that way.  Unless it reserved it somehow?

 

I got my 9k6 from WVC ARC via Etsy.  I saw the Coastal site.  That is where (I believe) I go the ‘manual’ to follow that was the TNC-Pi originally.  I did find a link I had stuck away (and forgotten) to a ‘manual’ to assemble the WVC board.  That had some additional information in it as well.  That was here: https://www.wvcarc.com/p/tnc-96k-resources.html

 

And your PiGate site was the genesis of my intent to get packet working in my Go Kit 😊  Easy and smooth operation with my V71A to a WinLink node was appealing – but there were NO TNC boards except the 9K6 available.  And since the V71A can do 9600 I said WTH – another arrow in the quiver in addition to standard 1200.

 

My hang up at the moment is the WVC manual which states (implies?) that the Teensy board needs to be loaded with software.  I need to read and digest that a little bit to figure out what that means.  But at the moment all I have “loaded” directly is the Pi itself.  I did see later in this string (or earlier in time) about the AX25 files and I have to go see if those are on the board or not. 

 

It will be steps but as long as I know the steps I should be OK overall.  The challenge to me is finding and understanding the steps 😊

 

Don, W4GFQ

 

From: RaspberryPi-4-HamRadio@groups.io <RaspberryPi-4-HamRadio@groups.io> On Behalf Of Mark Griffith via groups.io
Sent: Friday, June 26, 2020 11:51 AM
To: RaspberryPi-4-HamRadio@groups.io
Subject: Re: [RaspberryPi-4-HamRadio] Help with TNC9k6 setup

 

Don,

 

When you connect through PuTTY, is is through an SSH or Secure Shell TCP/IP connection port, not serial.  VNC is also through a direct connection at a non-serial port.

 

Where did you get the TNC-Pi9k6 from?  I've attached the docs from the old Coastal Chipworks site.  The board and procedure to build it is a little different than the other people selling this board, but the firmware configuration docs are still correct.

 

I'm getting ready to make a change in my website to reflect that the TNC-Pi9k6 is the choice for both the PiGate and PiGate RMS devices.  Is is a drop-in replacement for the TNC-Pi2.  I'm not too happy with the progress MFJ is making with building the new TNC-Pi3 board, and the West Virginia group that is now selling the TNC-Pi9k6 as an assembled board has a great price, which is probably going to be close to what MFJ sells the 1200 baud only board for.

 

Here's my web site in case you are interested in using your Pi and the TNC for communications with Winlink2000.

 

Mark

KD0QYN

 

 

 

 


Pigate - Emergency Communication System, Emergency Radio, Emergency Resp...

An emergency communication system to provide emergency e-mail communications in a disaster scenario.

 

 

 

Let me know if you have any more questions.

 

Mark

KD0QYN

 

 

 

On Friday, June 26, 2020, 6:58:46 AM CDT, Don Munson <w4gfq@...> wrote:

 

 

EXCELLENT!! 

 

So after six tries because it is early and I simply can’t type (and I have learned Linux is very unforgiving on typing!) I got the following:

 

Using Serial Port /dev/serial0 

retrying

 

and a presentation of the parameters.  

 

Now at least I know they are talking to each other 😊

 

I am not sure why it worked but it did.  I am going to presume that somehow the putty connection to the pi was using the serial port?  Although how it still connects (as does VNC) confuses me – but no matter.

 

The obvious next question is where do I go from here for reading about how to configure and use this board?

 

Don, W4GFQ

 

From: RaspberryPi-4-HamRadio@groups.io <RaspberryPi-4-HamRadio@groups.io> On Behalf Of Mark Griffith via groups.io
Sent: Friday, June 26, 2020 7:10 AM
To: RaspberryPi-4-HamRadio@groups.io
Subject: Re: [RaspberryPi-4-HamRadio] Help with TNC9k6 setup

 

Don,

 

First, you'll also need to use the raspi-config utility to enable the console serial port, but disable console login.

 

Run "sudo raspi-config"

 

Then go to menu 5, Interfacing Options, then menu P6, and disable the login shell over the serial port.

 

On the next screen, keep the serial port enabled.

 

Save these and finish.

 

Now try "sudo pitnc-getparams /dev/serial0 0"

 

This works the same with the TNC-Pi2 or the TNC-Pi9k6 and will be the same with the TNC-Pi3 once MFJ starts selling them.

 

Mark

KD0QYN

 

 

On Friday, June 26, 2020, 1:01:22 AM CDT, Don Munson <w4gfq@...> wrote:

 

 

First I am an operator and not a technician.  I can follow directions and to some extent do enough to get myself in trouble.  Having said that I purchased a TNC9k6 and have it running wiht a Raspberry PI 3B+.  Followed directions at (https://tnc-x.com/TNCPi.pdf) downloaded the pitnc files, set them in the directory and set permission to execute by owner.  Verified with ls -l that all permissions and owner/group ids as well as my logge din user are all setup per the text.

when I run the ./pitnc_getparams /dev/serial0 0 - I get the notation that RPi is using Serial 0 then Com Open Failed: permission denied.

I'm at a loss.  Searching here provides a slew of comm errors dated years back that are not trying serial but  ./pitnc_getparams 0 0 - when I try that it defaults to a TTY device (AAM0?) and simply repeats "retrying" which purportedly means a configuration issue.  But what configuration it is straight out of the setup - I've tweaked nothing in the RPI configuration.

Help?

Don, W4GFQ


Mark Griffith
 

Don,

/etc/default/ax25, NOT

"I didn't have this file in /dev/default/ac25"

Make sure you are editing the correct files.

Mark
KD0QYN


On Friday, June 26, 2020, 1:10:37 PM CDT, Don Poaps <va7dgp@...> wrote:


see below






On Fri, Jun 26, 2020 at 10:16 AM Mark Griffith via groups.io <mdgriffith2003=yahoo.com@groups.io> wrote:
Don,

If you have the latest Raspbian Buster installed, AX.25 is already there and ready to go.  However, you need to edit a couple files to get it setup.  The PiGate software does this for you, but if you want to do it yourself:

Edit /etc/ax25/axports

It should have some lines in there like this:

wl2k VA7DGP 1200 255 7 Winlink
tnc VA7DGP 19200 128 2 TNC-Pi2 VHF

# The format of this file is:
#portname       callsign        speed   paclen  window  description
tnc             KD0QYN-1        19200   128     2       TNC-Pi2 VHF
#uhfdrop        N0ONE-3         9600    128     2       443.425MHz+ 1200baud UHF Drop
#hfdrop         N0ONE-5         9600    32      2       40m HF Drop
#wtrunk         N0ONE-11        38400   253     2       UHF Trunk West
#etrunk         N0ONE-13        38400   253     2       UHF Trunk East
#axudp          N0ONE-8         115200  253     2       Linux (AX25<->UDP)

Notice that I changed one to have a port name of tnc, and added my call sign and a speed of 19200.  This is for the TNC-Pi.

Then edit /etc/default/ax25

There are three settings you need to change:

AXPORT=tnc (or whatever you called it)
HBAUD=19200
DEV=/dev/ttyserial0  (you can also try /dev/ttyAMA0)

I didn't have this file in /dev/default/ac25

I added 

AXPORT=tnc
HBAUD=19200
DEV=/dev/serial0

as seen on my PI

pi@raspberrypi:~ $ ls /dev/serial*
/dev/serial0  /dev/serial1
pi@raspberrypi:~ $


Just for verification 

Don

Save both these files and run the command "sudo service ax25 start"

Then run the command "sudo service ax25 status"

You should see the service status and there should be a line saying it is loaded and active.

You can also run this command to see if kissattach has been successful:

"sudo ps -ef | grep kiss"  and it should return a line of two showing kissattach has been run on the serial port.

Now, pat or APRS will be able to connect to that port,  /dev/serial0, and access the KISS modem.

Let me know if you have any more questions.

NOTE: This is for Raspbian Buster.  Any other version may have the files in a different location, different file names, or different entries in the files.

Mark
KD0QYN



On Friday, June 26, 2020, 11:19:06 AM CDT, Don Poaps <va7dgp@...> wrote:


I got the Pi TNC from John Hanson a few years go. It's been sitting on a PI 3. Theres 2 modes I want to do. APRS and Pat Winlink. I know I have to do a Kissattach /dev/serial0 or something like that. I don't really want to load BPQ. I use vnc to log in via km4ack hotspot. 10.10.10.10:5900 for the vnc. I know how to create ssh before I run a fresh install of Buster etc. I then log in via putty on my Windown machine and the run raspi-config and setup the PI for SSH, VNC and SERIAL and the Resultion for getting way from that black screen for desktop display.
I have created the mkdir pitnc in /home/pi directory. I have run the setup. 
It's getting a script for APRS and a Script to run start Pat Winlink.

I'm learning but I'm clueless about how to set this up so when I log in via VNC and have a very small screen while I'm mobile. I can click on a icon and the script starts APRS. If I want Pat Winlink. I click on a Icon and the script fires up and I now can use Pat Winlink. 
As mentioned by Don (forget his USA call) he said the info is outdated. If there was a website created that had the command line where once could create the APRS and Pat Winlink for the PI tnc. 

I'll slip over to the site you mentioned and see If I can get this Pi to work.

73

Don va7dgp

Don Poaps
New Westminster, BC
VA7DGP DATA
VA7QU   VOICE


Winlink: va7qu@...
Subject://wl2k           



                    
  




 


On Fri, Jun 26, 2020 at 8:51 AM Mark Griffith via groups.io <mdgriffith2003=yahoo.com@groups.io> wrote:
Don,

When you connect through PuTTY, is is through an SSH or Secure Shell TCP/IP connection port, not serial.  VNC is also through a direct connection at a non-serial port.

Where did you get the TNC-Pi9k6 from?  I've attached the docs from the old Coastal Chipworks site.  The board and procedure to build it is a little different than the other people selling this board, but the firmware configuration docs are still correct.

I'm getting ready to make a change in my website to reflect that the TNC-Pi9k6 is the choice for both the PiGate and PiGate RMS devices.  Is is a drop-in replacement for the TNC-Pi2.  I'm not too happy with the progress MFJ is making with building the new TNC-Pi3 board, and the West Virginia group that is now selling the TNC-Pi9k6 as an assembled board has a great price, which is probably going to be close to what MFJ sells the 1200 baud only board for.

Here's my web site in case you are interested in using your Pi and the TNC for communications with Winlink2000.

Mark
KD0QYN






Let me know if you have any more questions.

Mark
KD0QYN



On Friday, June 26, 2020, 6:58:46 AM CDT, Don Munson <w4gfq@...> wrote:


EXCELLENT!! 

 

So after six tries because it is early and I simply can’t type (and I have learned Linux is very unforgiving on typing!) I got the following:

 

Using Serial Port /dev/serial0 

retrying

 

and a presentation of the parameters.  

 

Now at least I know they are talking to each other 😊

 

I am not sure why it worked but it did.  I am going to presume that somehow the putty connection to the pi was using the serial port?  Although how it still connects (as does VNC) confuses me – but no matter.

 

The obvious next question is where do I go from here for reading about how to configure and use this board?

 

Don, W4GFQ

 

From: RaspberryPi-4-HamRadio@groups.io <RaspberryPi-4-HamRadio@groups.io> On Behalf Of Mark Griffith via groups.io
Sent: Friday, June 26, 2020 7:10 AM
To: RaspberryPi-4-HamRadio@groups.io
Subject: Re: [RaspberryPi-4-HamRadio] Help with TNC9k6 setup

 

Don,

 

First, you'll also need to use the raspi-config utility to enable the console serial port, but disable console login.

 

Run "sudo raspi-config"

 

Then go to menu 5, Interfacing Options, then menu P6, and disable the login shell over the serial port.

 

On the next screen, keep the serial port enabled.

 

Save these and finish.

 

Now try "sudo pitnc-getparams /dev/serial0 0"

 

This works the same with the TNC-Pi2 or the TNC-Pi9k6 and will be the same with the TNC-Pi3 once MFJ starts selling them.

 

Mark

KD0QYN

 

 

On Friday, June 26, 2020, 1:01:22 AM CDT, Don Munson <w4gfq@...> wrote:

 

 

First I am an operator and not a technician.  I can follow directions and to some extent do enough to get myself in trouble.  Having said that I purchased a TNC9k6 and have it running wiht a Raspberry PI 3B+.  Followed directions at (https://tnc-x.com/TNCPi.pdf) downloaded the pitnc files, set them in the directory and set permission to execute by owner.  Verified with ls -l that all permissions and owner/group ids as well as my logge din user are all setup per the text.

when I run the ./pitnc_getparams /dev/serial0 0 - I get the notation that RPi is using Serial 0 then Com Open Failed: permission denied.

I'm at a loss.  Searching here provides a slew of comm errors dated years back that are not trying serial but  ./pitnc_getparams 0 0 - when I try that it defaults to a TTY device (AAM0?) and simply repeats "retrying" which purportedly means a configuration issue.  But what configuration it is straight out of the setup - I've tweaked nothing in the RPI configuration.

Help?

Don, W4GFQ


Mark Griffith
 

Don,

If you will be using the PiGate image, there is nothing for you to do except plug the TNC into the Pi, load the image to an SD card, insert it about boot.

I don't know how the TNC-Pi9k6 from WVARC comes configured, you should talk with them, but the procedures to setup the board in the doc I attached are correct.  I don't currently support that particular board, but probably will in the near future.

Mark
KD0QYN


On Friday, June 26, 2020, 1:54:19 PM CDT, Don Munson <w4gfq@...> wrote:


Two Dons – go figure 😊

 

I use Putty as SSH as well as VNC – which is why I was sort of curious why turning off Secure Shell seemed to work as I didn’t connect that way.  Unless it reserved it somehow?

 

I got my 9k6 from WVC ARC via Etsy.  I saw the Coastal site.  That is where (I believe) I go the ‘manual’ to follow that was the TNC-Pi originally.  I did find a link I had stuck away (and forgotten) to a ‘manual’ to assemble the WVC board.  That had some additional information in it as well.  That was here: https://www.wvcarc.com/p/tnc-96k-resources.html

 

And your PiGate site was the genesis of my intent to get packet working in my Go Kit 😊  Easy and smooth operation with my V71A to a WinLink node was appealing – but there were NO TNC boards except the 9K6 available.  And since the V71A can do 9600 I said WTH – another arrow in the quiver in addition to standard 1200.

 

My hang up at the moment is the WVC manual which states (implies?) that the Teensy board needs to be loaded with software.  I need to read and digest that a little bit to figure out what that means.  But at the moment all I have “loaded” directly is the Pi itself.  I did see later in this string (or earlier in time) about the AX25 files and I have to go see if those are on the board or not. 

 

It will be steps but as long as I know the steps I should be OK overall.  The challenge to me is finding and understanding the steps 😊

 

Don, W4GFQ

 

From: RaspberryPi-4-HamRadio@groups.io <RaspberryPi-4-HamRadio@groups.io> On Behalf Of Mark Griffith via groups.io
Sent: Friday, June 26, 2020 11:51 AM
To: RaspberryPi-4-HamRadio@groups.io
Subject: Re: [RaspberryPi-4-HamRadio] Help with TNC9k6 setup

 

Don,

 

When you connect through PuTTY, is is through an SSH or Secure Shell TCP/IP connection port, not serial.  VNC is also through a direct connection at a non-serial port.

 

Where did you get the TNC-Pi9k6 from?  I've attached the docs from the old Coastal Chipworks site.  The board and procedure to build it is a little different than the other people selling this board, but the firmware configuration docs are still correct.

 

I'm getting ready to make a change in my website to reflect that the TNC-Pi9k6 is the choice for both the PiGate and PiGate RMS devices.  Is is a drop-in replacement for the TNC-Pi2.  I'm not too happy with the progress MFJ is making with building the new TNC-Pi3 board, and the West Virginia group that is now selling the TNC-Pi9k6 as an assembled board has a great price, which is probably going to be close to what MFJ sells the 1200 baud only board for.

 

Here's my web site in case you are interested in using your Pi and the TNC for communications with Winlink2000.

 

Mark

KD0QYN

 

 

 

 


Pigate - Emergency Communication System, Emergency Radio, Emergency Resp...

An emergency communication system to provide emergency e-mail communications in a disaster scenario.

 

 

 

Let me know if you have any more questions.

 

Mark

KD0QYN

 

 

 

On Friday, June 26, 2020, 6:58:46 AM CDT, Don Munson <w4gfq@...> wrote:

 

 

EXCELLENT!! 

 

So after six tries because it is early and I simply can’t type (and I have learned Linux is very unforgiving on typing!) I got the following:

 

Using Serial Port /dev/serial0 

retrying

 

and a presentation of the parameters.  

 

Now at least I know they are talking to each other 😊

 

I am not sure why it worked but it did.  I am going to presume that somehow the putty connection to the pi was using the serial port?  Although how it still connects (as does VNC) confuses me – but no matter.

 

The obvious next question is where do I go from here for reading about how to configure and use this board?

 

Don, W4GFQ

 

From: RaspberryPi-4-HamRadio@groups.io <RaspberryPi-4-HamRadio@groups.io> On Behalf Of Mark Griffith via groups.io
Sent: Friday, June 26, 2020 7:10 AM
To: RaspberryPi-4-HamRadio@groups.io
Subject: Re: [RaspberryPi-4-HamRadio] Help with TNC9k6 setup

 

Don,

 

First, you'll also need to use the raspi-config utility to enable the console serial port, but disable console login.

 

Run "sudo raspi-config"

 

Then go to menu 5, Interfacing Options, then menu P6, and disable the login shell over the serial port.

 

On the next screen, keep the serial port enabled.

 

Save these and finish.

 

Now try "sudo pitnc-getparams /dev/serial0 0"

 

This works the same with the TNC-Pi2 or the TNC-Pi9k6 and will be the same with the TNC-Pi3 once MFJ starts selling them.

 

Mark

KD0QYN

 

 

On Friday, June 26, 2020, 1:01:22 AM CDT, Don Munson <w4gfq@...> wrote:

 

 

First I am an operator and not a technician.  I can follow directions and to some extent do enough to get myself in trouble.  Having said that I purchased a TNC9k6 and have it running wiht a Raspberry PI 3B+.  Followed directions at (https://tnc-x.com/TNCPi.pdf) downloaded the pitnc files, set them in the directory and set permission to execute by owner.  Verified with ls -l that all permissions and owner/group ids as well as my logge din user are all setup per the text.

when I run the ./pitnc_getparams /dev/serial0 0 - I get the notation that RPi is using Serial 0 then Com Open Failed: permission denied.

I'm at a loss.  Searching here provides a slew of comm errors dated years back that are not trying serial but  ./pitnc_getparams 0 0 - when I try that it defaults to a TTY device (AAM0?) and simply repeats "retrying" which purportedly means a configuration issue.  But what configuration it is straight out of the setup - I've tweaked nothing in the RPI configuration.

Help?

Don, W4GFQ


Ray Wells
 



On 27/6/20 4:17 am, Don Poaps wrote:
AX 25 services issues

pi@raspberrypi:~ $ cd pitnc
pi@raspberrypi:~/pitnc $ sudo systemctl start ax25
Failed to start ax25.service: Unit ax25.service not found.
pi@raspberrypi:~/pitnc $ sudo systemctl enable ax25
Failed to enable unit: Unit file ax25.service does not exist.
pi@raspberrypi:~/pitnc $ 

Taking the XYL to her Mom's maybe when I back 30-40 minutes I'll have a better idea of whats going on.

I didn't know you can take them back :-)


Ray vk2tv


Mat Murdock
 

Depending on which board you purchase the appropriate firmware is pre loaded.  For instance if you get a TNC configured with the Raspberry PI headers then it has firmware loaded to interact with the PI using the GPIO pins set aside for serial communications (19200 baud btw).  If you get the "stand alone" TNC then the firmware loaded is for that specific configuration.

I have tested our TNC's with Mark's PiGate image and I don't recall having to change any settings.

One other item.  You can find pre-compiled binary's for the TNC9k6 on our site: http://www.wvcarc.com/p/tnc-96k-resources.html

Mat


Don Munson
 

Mat

 

I purchased the pre-built board off Etsey that is intended to be a “hat” to the Pi.  It is on the GPIO pins and lights up properly when the PI boots.  I can get the parameters from the board so I know it is connected and communicating at least at that level.  But my question becomes – now what?

 

I can’t find any references to how it gets configured, what software to use, how to use it, etc.  I have put the KM4ACK Build a Pi on a card and have pieces of it working, but frankly I don’t know (or can’t find?) enough information on how to connect APRS (for example) to the TNC board.  I tried to list serial ports on the board and get nothing back (as in there are no serial ports?) But I have serial ports enabled.

 

At this point I’m looking for how I could connect YAAC (for example) from the PI and set up a serial connection to the TNC in an attempt to get an APRS signal to a radio and audio back.

 

Also from your comment the Teensy board is loaded, how to I look at those directories to see that software from the RPI interface? I’m assuming the TNC talks to the Pi to permit viewing those directories somehow?

 

As you can see I’m relatively lost.

 

Don, W4GFQ

 

From: RaspberryPi-4-HamRadio@groups.io <RaspberryPi-4-HamRadio@groups.io> On Behalf Of Mat Murdock
Sent: Saturday, June 27, 2020 8:15 PM
To: RaspberryPi-4-HamRadio@groups.io
Subject: Re: [RaspberryPi-4-HamRadio] Help with TNC9k6 setup

 

Depending on which board you purchase the appropriate firmware is pre loaded.  For instance if you get a TNC configured with the Raspberry PI headers then it has firmware loaded to interact with the PI using the GPIO pins set aside for serial communications (19200 baud btw).  If you get the "stand alone" TNC then the firmware loaded is for that specific configuration.

I have tested our TNC's with Mark's PiGate image and I don't recall having to change any settings.

One other item.  You can find pre-compiled binary's for the TNC9k6 on our site: http://www.wvcarc.com/p/tnc-96k-resources.html

Mat


Mark Griffith
 

Don,

The TNC-Pi9k6 appears on the serial port as a KISS TNC modem.  Only software that "speaks" the KISS protocol can us it.  That would be one of the packet software suites, like Pat, linbpq, PiGate, APRS, etc.

Use one of those programs to unlock the "secrets" of the TNC.

Mark
KD0QYN


On Tuesday, June 30, 2020, 9:08:43 PM CDT, Don Munson <w4gfq@...> wrote:


Mat

 

I purchased the pre-built board off Etsey that is intended to be a “hat” to the Pi.  It is on the GPIO pins and lights up properly when the PI boots.  I can get the parameters from the board so I know it is connected and communicating at least at that level.  But my question becomes – now what?

 

I can’t find any references to how it gets configured, what software to use, how to use it, etc.  I have put the KM4ACK Build a Pi on a card and have pieces of it working, but frankly I don’t know (or can’t find?) enough information on how to connect APRS (for example) to the TNC board.  I tried to list serial ports on the board and get nothing back (as in there are no serial ports?) But I have serial ports enabled.

 

At this point I’m looking for how I could connect YAAC (for example) from the PI and set up a serial connection to the TNC in an attempt to get an APRS signal to a radio and audio back.

 

Also from your comment the Teensy board is loaded, how to I look at those directories to see that software from the RPI interface? I’m assuming the TNC talks to the Pi to permit viewing those directories somehow?

 

As you can see I’m relatively lost.

 

Don, W4GFQ

 

From: RaspberryPi-4-HamRadio@groups.io <RaspberryPi-4-HamRadio@groups.io> On Behalf Of Mat Murdock
Sent: Saturday, June 27, 2020 8:15 PM
To: RaspberryPi-4-HamRadio@groups.io
Subject: Re: [RaspberryPi-4-HamRadio] Help with TNC9k6 setup

 

Depending on which board you purchase the appropriate firmware is pre loaded.  For instance if you get a TNC configured with the Raspberry PI headers then it has firmware loaded to interact with the PI using the GPIO pins set aside for serial communications (19200 baud btw).  If you get the "stand alone" TNC then the firmware loaded is for that specific configuration.

I have tested our TNC's with Mark's PiGate image and I don't recall having to change any settings.

One other item.  You can find pre-compiled binary's for the TNC9k6 on our site: http://www.wvcarc.com/p/tnc-96k-resources.html

Mat