ssh and vnc are already turned on. It's described in the pigate20 pdf. Worked fine hear. I only logged in so I could see how it was built but to run Pigate you don't need ssh or vnc. As Mark says, jus

I "solved" my audio out problem. For some reason, the PITNC-9k6 is not working with my FT-8900. It is working with my FT-817. Thanks for all the help from the group.

The pitnc-9k6 is hearing well be appears to me mute. I have sent the calibration command sudo ./pitnc_setparams /dev/serial0 0 15 3 and listened on another radio and the radio keys but no audio tones.

Thanks to N5XMT - ./pitnc_getparams 1 30 worked. Thanks, Mat - your suggestion worked really well, I am now copying APRS packets. Next step is to get Pat working. Tomorrow I have a RPi 3+ coming so I

A year ago I had my Coastal Chipworks tncpi-96k running fine. I think I may have converted it to ARDOP but I can't remember for sure. I have been trying to reload the packet software onto the Teensy 3

I had a problem that pitnc_getparams would not work if the ax.25 service was running. Since I have ax.25 set to autostart, I have to stop the service before I run pitnc_getparams.

This link will provide a script that will create a bpq32.cfg file you can use to get started. I solved my problems when I started with linbpq. Once you have a working bpq32.cfg you can move on to modi

The PI96K is connected to linbpq, correct? If so, shouldn't you be using the telnet transport in PAT to talk to linbpq, not the PAT ARDOP transport?

I have one RPi running linbpq as a Winlink Packet RMS and another for experimenting with RPi Winlink Client software. I also have Pi Zero as a DMR Hotspot and and old B+ as a D-Star hotspot. The later

I could be wrong but I don't think the PI-Star image supports VNC since it has no shell, i.e. user interface other than HTML. Bob

The command is: chmod +x pitnc_getparams chmod +x pitnc_setparams It is adding the "executable" bit to the file permissions for pitnc_getparams and pitnc_setparams. You are missing the "x". Bob AF9W F

cd /home/pi chmod +x pitnc_getparams chmod +x pitnc_setparams This will make the programs executable. In my case, ./pitnc_getparams /dev/serial0 0 shows me the current settings. I am using AX25 (https

Ok, I am feeling stupid. AX25 had the serial port. Once I stopped that, all is well - almost. Still can't receive packets but that is a simpler problem.

I am trying to get a TNC-PI96K running with PAT to create a 9600 baud Winlink. When I first installed this I could run .pitnc_getparams and pitnc_setparams and I would get results. I turned off the Pi