Date   

Re: CAT Control Options

Craig Davidson
 

If you ever want to control your Icom radio via the ci-v port using a
Raspberry Pi running your own linux scripts, I have figured out how to
turn on the Pi serial port (header pins 8 and 10) and send ascii/hex
data to the radio. The ci-v bus is the same as the old com port
(RS232) except the voltage levels are 5 volts and ground. I would be
happy to share my scripts and what I have learned about the interface.
One of the GPIO pins could be used for PTT on the radio.

Here are some notes about turning on the serial port on the Raspberry Pi.

http://experimental.irlp.net/IRLP_Projects/INSTRUCTIONS%20for%20Pi%20serial%20port%20setup.txt

Here is a diagram of my interface to a chinese transceiver board.
Similar wiring could interface to an Icom radio.

http://experimental.irlp.net/IRLP_Projects/SCHEMATIC_Pi_to_China_Transceiver_Board.png

On 4/21/20, Ed Bloom, KD9FRQ wrote:
I look forward to learning what you learn on making the link from the Pi
to the 718.

On 4/20/2020 10:15 PM, Bill Lamm wrote:
I have a Icom 718 and a ci-v cable.. I am setting up raspi4 following
KM4ACK's wonderful work..
Tge CI-V cable works but doesn't control PTT.. I am using Gordon
Gibby's digital interface kit to isolate raspi4 and radio. That will
require a sound card dongle and ?USB? connection to the ACC jack on
the rear.


Re: Now that coastal Chipworks is gone

Dean Smith
 

Not sure about copyright issues, but if someone has blown their TncPI,i have the hexfile.
I keep it incase mine throws a hissy fit!


Re: CAT Control Options

Ed Bloom, KD9FRQ
 

I look forward to learning what you learn on making the link from the Pi to the 718.

On 4/20/2020 10:15 PM, Bill Lamm wrote:
I have a Icom 718 and a ci-v cable.. I am setting up raspi4 following KM4ACK's wonderful work.. 
Tge CI-V cable works but doesn't control PTT.. I am using Gordon Gibby's digital interface kit to isolate raspi4 and radio.  That will require a sound card dongle and ?USB? connection to the ACC jack on the rear. 



Re: CAT Control Options

Bill Lamm
 
Edited

I have a Icom 718 and a ci-v cable.. I am setting up raspi4 following KM4ACK's wonderful work.. 
The CI-V cable works but doesn't control PTT.. I am using Gordon Gibby's digital interface kit to isolate raspi4 and radio.  That will require a sound card dongle and ?USB? connection to the ACC jack on the rear.


Re: CAT Control Options

 



On Mon, Apr 20, 2020 at 12:44 PM Ed Bloom, KD9FRQ via groups.io <ewbloom=verizon.net@groups.io> wrote:
Mike,

I know the FT-450 does and I have a plain serial to serial cable on it now to my big PC.

So you are saying that as along as I order a CAT-62 equivalent, I should be able to plug
it into a USB port on the Pi and be good to go (once all the settings are in place?

That is what I have done.  I use this one
https://smile.amazon.com/gp/product/B0041LNISK  

 
I just don't want to spend the money on a cable someone else has already tried and found
to be lacking in functionality.

In the example of Jason, KM4ACK, his rig had a direct USB port so he does not need anything
special just a USB-A to USB-B.

I think the FT-897 will be the same serial port as the FT-450. I will need to check as it has
been boxed in the Go Case for a while.  the ICOM 718 is is new enough to me that I have not
fully reached the point yet.

I don't have an IC-718 but it looks like it takes a standard Icom style CI-V cable.

Here is the Icom version I have - https://smile.amazon.com/gp/product/B004L0T4UM

 I like these versions because they use FTDI USB to serial chips which are better supported.  You may find lower cost options.  For Linux, FTDI may not be as important.

There are a lot of counterfeit Prolific chips, which may not work with Windows. 

--
John D. Hays
Kingston, WA
K7VE

 


Re: CAT Control Options

Mike B
 

I have the 857D.   There is no official USB cable for it...but there are some available on ebay/amazon (I don't remember where I bought mine.) in any case...the cable did talk the radio but I could not transmit with it.  

So I had to buy the correct serial CAT cable for the Yaesu (meaning the not cheap one)...AND a generic USB to serial cable...and that combo is plug and play on both Windows and the Pi. 

I got a USB to serial cable like this one...and like I said, it worked for Windows and the Pi.


 

Mike

On 4/20/2020 2:43 PM, Ed Bloom, KD9FRQ via groups.io wrote:
Mike,

I know the FT-450 does and I have a plain serial to serial cable on it now to my big PC.

So you are saying that as along as I order a CAT-62 equivalent, I should be able to plug
it into a USB port on the Pi and be good to go (once all the settings are in place?

I just don't want to spend the money on a cable someone else has already tried and found
to be lacking in functionality.

In the example of Jason, KM4ACK, his rig had a direct USB port so he does not need anything
special just a USB-A to USB-B.

I think the FT-897 will be the same serial port as the FT-450. I will need to check as it has
been boxed in the Go Case for a while.  the ICOM 718 is is new enough to me that I have not
fully reached the point yet.

I stilled asked the question, so I could go ahead and order the "I have successfully used "cables
even if they do sit a month or two on the bench.

Ed Bloom, KD9FRQ
ewbloom@...
Sent from Webmail access


-----Original Message-----
From: Mike B <kf5dey@...>
To: RaspberryPi-4-HamRadio <RaspberryPi-4-HamRadio@groups.io>
Sent: Mon, Apr 20, 2020 1:42 pm
Subject: Re: [RaspberryPi-4-HamRadio] CAT Control Options

I am pretty sure all of those radios have available serial cables to CAT.

From there you use a USB to serial adapter...I use a generic one I got on Amazon... it is plug and play on the Pi basically.

Mike


On Mon, Apr 20, 2020 at 11:12 AM Ed Bloom, KD9FRQ via groups.io <ewbloom=verizon.net@groups.io> wrote:
In working on using the Build A Pi script from Jason, KM4ACK, I have come across the need for assistance.

I need some guidance on identifying available cables to allow FLRIG to control the RIG via CAT as built in the
script / setup.

I own an older FT-450 (currently my main Base HF Rig using a SignaLink), an FT-897 (my target HF Rig for
mobile / portable ops) and an ICOM 718 (currently planned to be my back shack rig with a SignaLink and also
connected to my 80m dipole).

The reason I am looking for cable for all three rigs is that I will eventually want to move away from the big PC
I am using in my shack and move the PI and totally 12v operation.

Thank you in advance for your help in locating cable options for CAT control on the PI for these rigs.

Ed Bloom, KD9FRQ
ewbloom@...
Sent from Webmail access


--
John D. Hays
Kingston, WA
K7VE

 




Re: TNC-Pi connection problem

Mark Griffith
 

Carlos,

I developed the PiGate system.  No one else here is going to help you any more than me, not because I'm so smart, but because I know the software better than anyone else and have spent years supporting it.

First, get rid of the Baofeng.  If you can't get any other radio, then you will continue to have problems.  There is nothing more I can say about that.

Second, you have not posted a packet log, so it is difficult to help.

Third, trying to make changes in the software or firmware is only going to get you more confused.  All the parameters for the TNC are set to support the vast majority of radios (except the Baofeng) and none of them need changing.  By messing around with the parameters you have put yourself in a bad position.  Put them all back to the default settings and the two pots to the middle settings (half way open/closed).

If you want to get a more detailed log, you'll have to login to the PiGate though SSH or some other method, and run a command line program to decode all the packets.  To do this:

First from the admin interface, clear the packet log.

SSH in as user "pi" with the password of "PiGate12"

Get to a command line interface or terminal window.  If you don't know how to do these things search the Internet.  There are lots and lots of help pages.

sudo listen -a

Let this run and start a RMS station poll from the admin interface.  When the poll is finished, the output of listen will also be finished.  Post that here.  Please do not do a screen shot.  Cut the text and paste it here.  Same with the packet log.

I can promise you, except in VERY RARE instances, everyone that has contacted my trying to run a Baofeng has fixed their problems by getting a better radio.

Let me know if you need any more help.

Mark
KD0QYN


On Monday, April 20, 2020, 11:47:39 AM CDT, KC3CCD <kc3ccd@...> wrote:


I assume is not using VOX because it is disabled in the radio’s menu and is the cable the manufacturer of the TNC recommended to be used with the radio. 

I do hear the tone on another radio. I had followed the manufacture’s direction setting the level as you described. Starting from zero and increasing until it wouldn’t increase more stayed fairly close to the minimum (about 1/8 turn). I kept going and another point was reached where it increased again near the max. It stayed constant from there. Which of the two points should I use? I tested with both and still does not connect. 

That said, using the lowest of the two, I noticed the radio was transmitting longer and it seemed like some comms occurred but the software still tells me it fails. The packet log does not say much. Maybe is a sanitized log version that gets saved with the rms connect script used by the PiGate?

Is there some log that shows the connection transaction similar to what  soundmodem does? 

Hard to tell if actual two tones are happening or not. I do hear a difference but can’t differentiate. I’ll setup my SDR later today and capture the transmission and look closer. 

Using PiGate version 2.1. I am using the same settings that soundmodem works with: 500 ms delay and 5 tail but I think the TNC likes 0 on tail. Have not really been able to narrow that one. 

Thanks for the help!

v/r,
Carlos

PS. I’m avoiding the radio discussion and was hoping to avoid with the statement of “always work with my PC”. It really does. I don’t know how to blame the radio when it reliably works with soundmodem. I will try my FT-2DR as soon as I make a DB9 to RJ45 adapter. If it ends up working, it may be time to switch to direwolf and ditching my two TNCs (oops, another hot topic <ducking>). 


Sent from my 📲

On Apr 19, 2020, at 10:15 PM, Tadd KA2DEW in NC via groups.io <tadd@...> wrote:


Make sure you aren’t using VOX to key up the radio.  Set up the radio with PTT and wire PTT back to the TNC-PI.  
If you start a connect from your piGate to a station over the radio, do you hear the packets go out on another receiver?  
If so, turn the TXlevel on the TNC all the way down and start walking it up.  There will be a threshold where turning it up doesn’t make it louder.  Set it below that threshold.  Set the TXDELAY up until you can hear the change in tone in each packet as the TXdelay expires.  There are two tones, before the data, and during the data.  You want the before the data to be notice-able, at least for the start and TXdelay controls the length of that before-the-data period.  

The Chinese-brand radios are not to be trusted.  They have been shown to be unsafe and to not meet the USA rules, by a wide margin.  They make dandy test equipment since you can type in a receive frequency, but they are certainly not something to hook up to a real antenna or to transmit in places where other transceivers might be operated, like planet Earth.  They can do all sorts of damage to ham radio credibility in the US by impacting other services that we spend much of our time trying to impress, like the cops, fire department, federal agencies etc..   They also are not particularly selective or able to survive jamming from out-of-band signals.  That means another transmitter near you can turn off your receiver even though that other transmitter isn’t even in the ham band.  It’s really interesting when mountain climbing that as soon as you get to anywhere near the peak (where the big antennas are) your radio goes deaf.  A good radio won’t be as susceptible. The Chinese radios use the cheapest part that will even seem to work.  Earphone plugs that only survive a few dozen insertions, or beak off in the connector, and etc..    Plus the Chinese radios are really hard to operate.  Life’s too short. 

   Tadd



Tadd Torborg 




On Apr 19, 2020, at 9:51 PM, Mark Griffith via groups.io <mdgriffith2003@...> wrote:

Carlos,

The first problem is the Baofeng.  If you want packet to work, don't use a cheap radio.  It may work sometimes, and sometimes it won't.

The TXDelay is not that important, set it to 40 (400ms) and that should work for most situations.  That may be too fast for a Baofeng.  Don't mess with the other parameters.  You're problem is the radio.

What version of the PiGate software are you using?  Ver. 2.1?

Mark
KD0QYN



On Sunday, April 19, 2020, 5:02:26 PM CDT, KC3CCD <kc3ccd@...> wrote:


I have a TNC-Pi (rev 2.3) on a Pi3B+ that can't connect to any packet station. No issues via telnet. This is a PiGate setup. I can connect reliably with the same radio (UV-5RE+) using a signalink with my laptop. I experimented with the TXDelay and TXTail with no luck. TXTail was 0 or 5, TXDelay went from 18-50.  

Can anyone help?

Thanks in advance.

Carlos
N3RDR

Settings of the TNC:

pi@PiGate:~/pitnc $ ./pitnc_getparams 0 0

 

   PIC Software Version           1

01 TXDelay - Zero means use ADC   0

02 Persistance                   63

03 Slottime (in 10 mS)           10

04 TXTail                         0

05 Full Duplex - Not used       255

06 Our Channel (Hex)             00

07 I2C Address (0 = async) Hex   00

   ADC Value                     45

8 1 0 3f a 0 ff 0 0 2d ee c0 sum 0 



Re: CAT Control Options

Ed Bloom, KD9FRQ
 

Mike,

I know the FT-450 does and I have a plain serial to serial cable on it now to my big PC.

So you are saying that as along as I order a CAT-62 equivalent, I should be able to plug
it into a USB port on the Pi and be good to go (once all the settings are in place?

I just don't want to spend the money on a cable someone else has already tried and found
to be lacking in functionality.

In the example of Jason, KM4ACK, his rig had a direct USB port so he does not need anything
special just a USB-A to USB-B.

I think the FT-897 will be the same serial port as the FT-450. I will need to check as it has
been boxed in the Go Case for a while.  the ICOM 718 is is new enough to me that I have not
fully reached the point yet.

I stilled asked the question, so I could go ahead and order the "I have successfully used "cables
even if they do sit a month or two on the bench.

Ed Bloom, KD9FRQ
ewbloom@...
Sent from Webmail access


-----Original Message-----
From: Mike B <kf5dey@...>
To: RaspberryPi-4-HamRadio <RaspberryPi-4-HamRadio@groups.io>
Sent: Mon, Apr 20, 2020 1:42 pm
Subject: Re: [RaspberryPi-4-HamRadio] CAT Control Options

I am pretty sure all of those radios have available serial cables to CAT.

From there you use a USB to serial adapter...I use a generic one I got on Amazon... it is plug and play on the Pi basically.

Mike


On Mon, Apr 20, 2020 at 11:12 AM Ed Bloom, KD9FRQ via groups.io <ewbloom=verizon.net@groups.io> wrote:
In working on using the Build A Pi script from Jason, KM4ACK, I have come across the need for assistance.

I need some guidance on identifying available cables to allow FLRIG to control the RIG via CAT as built in the
script / setup.

I own an older FT-450 (currently my main Base HF Rig using a SignaLink), an FT-897 (my target HF Rig for
mobile / portable ops) and an ICOM 718 (currently planned to be my back shack rig with a SignaLink and also
connected to my 80m dipole).

The reason I am looking for cable for all three rigs is that I will eventually want to move away from the big PC
I am using in my shack and move the PI and totally 12v operation.

Thank you in advance for your help in locating cable options for CAT control on the PI for these rigs.

Ed Bloom, KD9FRQ
ewbloom@...
Sent from Webmail access


--
John D. Hays
Kingston, WA
K7VE

 



Re: TNC-Pi connection problem

 

Carlos, check out the NinoTNC. http://tarpn.net/d 
 — Tadd KA2DEW

On Apr 20, 2020, at 1:36 PM, KC3CCD <kc3ccd@...> wrote:

Oh!No! Regardless of how great these sw TNCs are, the effort to make these work on a Pi is not trivial. I have another Pi that I am configuring for that. I had to add audio this, control radio for that, and I’m still waiting for some parts since I am trying to make it compact. 

It is not as elegant as the TNC-Pi. A single “hat” the radio plugs into at a great price point. I was sorry to see coastal chip works go but is good to see someone else picking the project up. 

Carlos
N3RDR

Sent from my 📲

On Apr 20, 2020, at 1:22 PM, John Wiseman <john.wiseman@...> wrote:

 If you are looking for a software TNC there is now also a Linux port of UZ7HO's Soundmodem

https://www.cantab.net/users/john.wiseman/Documents/QtSoundModem.html

73,
John G8BPQ

On 20/04/2020 17:47, KC3CCD wrote:
I assume is not using VOX because it is disabled in the radio’s menu and is the cable the manufacturer of the TNC recommended to be used with the radio. 

I do hear the tone on another radio. I had followed the manufacture’s direction setting the level as you described. Starting from zero and increasing until it wouldn’t increase more stayed fairly close to the minimum (about 1/8 turn). I kept going and another point was reached where it increased again near the max. It stayed constant from there. Which of the two points should I use? I tested with both and still does not connect. 

That said, using the lowest of the two, I noticed the radio was transmitting longer and it seemed like some comms occurred but the software still tells me it fails. The packet log does not say much. Maybe is a sanitized log version that gets saved with the rms connect script used by the PiGate?

Is there some log that shows the connection transaction similar to what  soundmodem does? 

Hard to tell if actual two tones are happening or not. I do hear a difference but can’t differentiate. I’ll setup my SDR later today and capture the transmission and look closer. 

Using PiGate version 2.1. I am using the same settings that soundmodem works with: 500 ms delay and 5 tail but I think the TNC likes 0 on tail. Have not really been able to narrow that one. 

Thanks for the help!

v/r,
Carlos

PS. I’m avoiding the radio discussion and was hoping to avoid with the statement of “always work with my PC”. It really does. I don’t know how to blame the radio when it reliably works with soundmodem. I will try my FT-2DR as soon as I make a DB9 to RJ45 adapter. If it ends up working, it may be time to switch to direwolf and ditching my two TNCs (oops, another hot topic <ducking>). 


Sent from my 📲

On Apr 19, 2020, at 10:15 PM, Tadd KA2DEW in NC via groups.io <tadd@...> wrote:

 Make sure you aren’t using VOX to key up the radio.  Set up the radio with PTT and wire PTT back to the TNC-PI.  
If you start a connect from your piGate to a station over the radio, do you hear the packets go out on another receiver?  
If so, turn the TXlevel on the TNC all the way down and start walking it up.  There will be a threshold where turning it up doesn’t make it louder.  Set it below that threshold.  Set the TXDELAY up until you can hear the change in tone in each packet as the TXdelay expires.  There are two tones, before the data, and during the data.  You want the before the data to be notice-able, at least for the start and TXdelay controls the length of that before-the-data period.  

The Chinese-brand radios are not to be trusted.  They have been shown to be unsafe and to not meet the USA rules, by a wide margin.  They make dandy test equipment since you can type in a receive frequency, but they are certainly not something to hook up to a real antenna or to transmit in places where other transceivers might be operated, like planet Earth.  They can do all sorts of damage to ham radio credibility in the US by impacting other services that we spend much of our time trying to impress, like the cops, fire department, federal agencies etc..   They also are not particularly selective or able to survive jamming from out-of-band signals.  That means another transmitter near you can turn off your receiver even though that other transmitter isn’t even in the ham band.  It’s really interesting when mountain climbing that as soon as you get to anywhere near the peak (where the big antennas are) your radio goes deaf.  A good radio won’t be as susceptible. The Chinese radios use the cheapest part that will even seem to work.  Earphone plugs that only survive a few dozen insertions, or beak off in the connector, and etc..    Plus the Chinese radios are really hard to operate.  Life’s too short. 

   Tadd



Tadd Torborg 




On Apr 19, 2020, at 9:51 PM, Mark Griffith via groups.io <mdgriffith2003@...> wrote:

Carlos,

The first problem is the Baofeng.  If you want packet to work, don't use a cheap radio.  It may work sometimes, and sometimes it won't.

The TXDelay is not that important, set it to 40 (400ms) and that should work for most situations.  That may be too fast for a Baofeng.  Don't mess with the other parameters.  You're problem is the radio.

What version of the PiGate software are you using?  Ver. 2.1?

Mark
KD0QYN



On Sunday, April 19, 2020, 5:02:26 PM CDT, KC3CCD <kc3ccd@...> wrote:


I have a TNC-Pi (rev 2.3) on a Pi3B+ that can't connect to any packet station. No issues via telnet. This is a PiGate setup. I can connect reliably with the same radio (UV-5RE+) using a signalink with my laptop. I experimented with the TXDelay and TXTail with no luck. TXTail was 0 or 5, TXDelay went from 18-50.  

Can anyone help?

Thanks in advance.

Carlos
N3RDR

Settings of the TNC:

pi@PiGate:~/pitnc $ ./pitnc_getparams 0 0

 

   PIC Software Version           1

01 TXDelay - Zero means use ADC   0

02 Persistance                   63

03 Slottime (in 10 mS)           10

04 TXTail                         0

05 Full Duplex - Not used       255

06 Our Channel (Hex)             00

07 I2C Address (0 = async) Hex   00

   ADC Value                     45

8 1 0 3f a 0 ff 0 0 2d ee c0 sum 0 





Re: CAT Control Options

Mike B
 

"I need some guidance on identifying available cables to allow FLRIG to control the RIG via CAT as built in the
script / setup."

A specific question...just because ebay has a CAT cable, doesn't mean it will work...how do I know?   I bought an ebay usb CAT cable...it recognized the radio...but would not allow radio to transmit.

So I gave a specific answer...there are serial to CAT cables available...and from there you can use a generic USB to serial adapter.

And that adapter will be plug and play with the Pi.

Mike



I have to ask...is that how you mentor other amateurs trying to learn something new in the hobby?



On 4/20/2020 1:48 PM, John D Hays - K7VE wrote:
That was not a mean answer.  It was a link that will help you get to a search.

The search lists a number of places to get the cables at different price points.

You don't need a USB to serial cable, if the cable is USB to the proper CAT connection.


On Mon, Apr 20, 2020 at 11:42 AM Mike B <kf5dey@...> wrote:
If you are going to give a mean answer...why answer at all.

I am pretty sure all of those radios have available serial cables to CAT.

From there you use a USB to serial adapter...I use a generic one I got on Amazon... it is plug and play on the Pi basically.

Mike

On 4/20/2020 1:34 PM, John D Hays - K7VE wrote:
I use these USB cables on Raspberry Pi to do CAT control on Yaesu and on Icom
 

On Mon, Apr 20, 2020 at 11:12 AM Ed Bloom, KD9FRQ via groups.io <ewbloom=verizon.net@groups.io> wrote:
In working on using the Build A Pi script from Jason, KM4ACK, I have come across the need for assistance.

I need some guidance on identifying available cables to allow FLRIG to control the RIG via CAT as built in the
script / setup.

I own an older FT-450 (currently my main Base HF Rig using a SignaLink), an FT-897 (my target HF Rig for
mobile / portable ops) and an ICOM 718 (currently planned to be my back shack rig with a SignaLink and also
connected to my 80m dipole).

The reason I am looking for cable for all three rigs is that I will eventually want to move away from the big PC
I am using in my shack and move the PI and totally 12v operation.

Thank you in advance for your help in locating cable options for CAT control on the PI for these rigs.

Ed Bloom, KD9FRQ
ewbloom@...
Sent from Webmail access


--
John D. Hays
Kingston, WA
K7VE

 




--
John D. Hays
Kingston, WA
K7VE

 



Re: CAT Control Options

 

That was not a mean answer.  It was a link that will help you get to a search.

The search lists a number of places to get the cables at different price points.

You don't need a USB to serial cable, if the cable is USB to the proper CAT connection.


On Mon, Apr 20, 2020 at 11:42 AM Mike B <kf5dey@...> wrote:
If you are going to give a mean answer...why answer at all.

I am pretty sure all of those radios have available serial cables to CAT.

From there you use a USB to serial adapter...I use a generic one I got on Amazon... it is plug and play on the Pi basically.

Mike

On 4/20/2020 1:34 PM, John D Hays - K7VE wrote:
I use these USB cables on Raspberry Pi to do CAT control on Yaesu and on Icom
 

On Mon, Apr 20, 2020 at 11:12 AM Ed Bloom, KD9FRQ via groups.io <ewbloom=verizon.net@groups.io> wrote:
In working on using the Build A Pi script from Jason, KM4ACK, I have come across the need for assistance.

I need some guidance on identifying available cables to allow FLRIG to control the RIG via CAT as built in the
script / setup.

I own an older FT-450 (currently my main Base HF Rig using a SignaLink), an FT-897 (my target HF Rig for
mobile / portable ops) and an ICOM 718 (currently planned to be my back shack rig with a SignaLink and also
connected to my 80m dipole).

The reason I am looking for cable for all three rigs is that I will eventually want to move away from the big PC
I am using in my shack and move the PI and totally 12v operation.

Thank you in advance for your help in locating cable options for CAT control on the PI for these rigs.

Ed Bloom, KD9FRQ
ewbloom@...
Sent from Webmail access


--
John D. Hays
Kingston, WA
K7VE

 




--
John D. Hays
Kingston, WA
K7VE

 


Re: CAT Control Options

Mike B
 

If you are going to give a mean answer...why answer at all.

I am pretty sure all of those radios have available serial cables to CAT.

From there you use a USB to serial adapter...I use a generic one I got on Amazon... it is plug and play on the Pi basically.

Mike

On 4/20/2020 1:34 PM, John D Hays - K7VE wrote:
I use these USB cables on Raspberry Pi to do CAT control on Yaesu and on Icom
 

On Mon, Apr 20, 2020 at 11:12 AM Ed Bloom, KD9FRQ via groups.io <ewbloom=verizon.net@groups.io> wrote:
In working on using the Build A Pi script from Jason, KM4ACK, I have come across the need for assistance.

I need some guidance on identifying available cables to allow FLRIG to control the RIG via CAT as built in the
script / setup.

I own an older FT-450 (currently my main Base HF Rig using a SignaLink), an FT-897 (my target HF Rig for
mobile / portable ops) and an ICOM 718 (currently planned to be my back shack rig with a SignaLink and also
connected to my 80m dipole).

The reason I am looking for cable for all three rigs is that I will eventually want to move away from the big PC
I am using in my shack and move the PI and totally 12v operation.

Thank you in advance for your help in locating cable options for CAT control on the PI for these rigs.

Ed Bloom, KD9FRQ
ewbloom@...
Sent from Webmail access


--
John D. Hays
Kingston, WA
K7VE

 



Re: CAT Control Options

 

I use these USB cables on Raspberry Pi to do CAT control on Yaesu and on Icom
 


On Mon, Apr 20, 2020 at 11:12 AM Ed Bloom, KD9FRQ via groups.io <ewbloom=verizon.net@groups.io> wrote:
In working on using the Build A Pi script from Jason, KM4ACK, I have come across the need for assistance.

I need some guidance on identifying available cables to allow FLRIG to control the RIG via CAT as built in the
script / setup.

I own an older FT-450 (currently my main Base HF Rig using a SignaLink), an FT-897 (my target HF Rig for
mobile / portable ops) and an ICOM 718 (currently planned to be my back shack rig with a SignaLink and also
connected to my 80m dipole).

The reason I am looking for cable for all three rigs is that I will eventually want to move away from the big PC
I am using in my shack and move the PI and totally 12v operation.

Thank you in advance for your help in locating cable options for CAT control on the PI for these rigs.

Ed Bloom, KD9FRQ
ewbloom@...
Sent from Webmail access



--
John D. Hays
Kingston, WA
K7VE

 


CAT Control Options

Ed Bloom, KD9FRQ
 

In working on using the Build A Pi script from Jason, KM4ACK, I have come across the need for assistance.

I need some guidance on identifying available cables to allow FLRIG to control the RIG via CAT as built in the
script / setup.

I own an older FT-450 (currently my main Base HF Rig using a SignaLink), an FT-897 (my target HF Rig for
mobile / portable ops) and an ICOM 718 (currently planned to be my back shack rig with a SignaLink and also
connected to my 80m dipole).

The reason I am looking for cable for all three rigs is that I will eventually want to move away from the big PC
I am using in my shack and move the PI and totally 12v operation.

Thank you in advance for your help in locating cable options for CAT control on the PI for these rigs.

Ed Bloom, KD9FRQ
ewbloom@...
Sent from Webmail access


Re: TNC-Pi connection problem

N3RDR
 

Oh!No! Regardless of how great these sw TNCs are, the effort to make these work on a Pi is not trivial. I have another Pi that I am configuring for that. I had to add audio this, control radio for that, and I’m still waiting for some parts since I am trying to make it compact. 

It is not as elegant as the TNC-Pi. A single “hat” the radio plugs into at a great price point. I was sorry to see coastal chip works go but is good to see someone else picking the project up. 

Carlos
N3RDR

Sent from my 📲

On Apr 20, 2020, at 1:22 PM, John Wiseman <john.wiseman@...> wrote:

 If you are looking for a software TNC there is now also a Linux port of UZ7HO's Soundmodem

https://www.cantab.net/users/john.wiseman/Documents/QtSoundModem.html

73,
John G8BPQ

On 20/04/2020 17:47, KC3CCD wrote:
I assume is not using VOX because it is disabled in the radio’s menu and is the cable the manufacturer of the TNC recommended to be used with the radio. 

I do hear the tone on another radio. I had followed the manufacture’s direction setting the level as you described. Starting from zero and increasing until it wouldn’t increase more stayed fairly close to the minimum (about 1/8 turn). I kept going and another point was reached where it increased again near the max. It stayed constant from there. Which of the two points should I use? I tested with both and still does not connect. 

That said, using the lowest of the two, I noticed the radio was transmitting longer and it seemed like some comms occurred but the software still tells me it fails. The packet log does not say much. Maybe is a sanitized log version that gets saved with the rms connect script used by the PiGate?

Is there some log that shows the connection transaction similar to what  soundmodem does? 

Hard to tell if actual two tones are happening or not. I do hear a difference but can’t differentiate. I’ll setup my SDR later today and capture the transmission and look closer. 

Using PiGate version 2.1. I am using the same settings that soundmodem works with: 500 ms delay and 5 tail but I think the TNC likes 0 on tail. Have not really been able to narrow that one. 

Thanks for the help!

v/r,
Carlos

PS. I’m avoiding the radio discussion and was hoping to avoid with the statement of “always work with my PC”. It really does. I don’t know how to blame the radio when it reliably works with soundmodem. I will try my FT-2DR as soon as I make a DB9 to RJ45 adapter. If it ends up working, it may be time to switch to direwolf and ditching my two TNCs (oops, another hot topic <ducking>). 


Sent from my 📲

On Apr 19, 2020, at 10:15 PM, Tadd KA2DEW in NC via groups.io <tadd@...> wrote:

 Make sure you aren’t using VOX to key up the radio.  Set up the radio with PTT and wire PTT back to the TNC-PI.  
If you start a connect from your piGate to a station over the radio, do you hear the packets go out on another receiver?  
If so, turn the TXlevel on the TNC all the way down and start walking it up.  There will be a threshold where turning it up doesn’t make it louder.  Set it below that threshold.  Set the TXDELAY up until you can hear the change in tone in each packet as the TXdelay expires.  There are two tones, before the data, and during the data.  You want the before the data to be notice-able, at least for the start and TXdelay controls the length of that before-the-data period.  

The Chinese-brand radios are not to be trusted.  They have been shown to be unsafe and to not meet the USA rules, by a wide margin.  They make dandy test equipment since you can type in a receive frequency, but they are certainly not something to hook up to a real antenna or to transmit in places where other transceivers might be operated, like planet Earth.  They can do all sorts of damage to ham radio credibility in the US by impacting other services that we spend much of our time trying to impress, like the cops, fire department, federal agencies etc..   They also are not particularly selective or able to survive jamming from out-of-band signals.  That means another transmitter near you can turn off your receiver even though that other transmitter isn’t even in the ham band.  It’s really interesting when mountain climbing that as soon as you get to anywhere near the peak (where the big antennas are) your radio goes deaf.  A good radio won’t be as susceptible. The Chinese radios use the cheapest part that will even seem to work.  Earphone plugs that only survive a few dozen insertions, or beak off in the connector, and etc..    Plus the Chinese radios are really hard to operate.  Life’s too short. 

   Tadd



Tadd Torborg 




On Apr 19, 2020, at 9:51 PM, Mark Griffith via groups.io <mdgriffith2003@...> wrote:

Carlos,

The first problem is the Baofeng.  If you want packet to work, don't use a cheap radio.  It may work sometimes, and sometimes it won't.

The TXDelay is not that important, set it to 40 (400ms) and that should work for most situations.  That may be too fast for a Baofeng.  Don't mess with the other parameters.  You're problem is the radio.

What version of the PiGate software are you using?  Ver. 2.1?

Mark
KD0QYN



On Sunday, April 19, 2020, 5:02:26 PM CDT, KC3CCD <kc3ccd@...> wrote:


I have a TNC-Pi (rev 2.3) on a Pi3B+ that can't connect to any packet station. No issues via telnet. This is a PiGate setup. I can connect reliably with the same radio (UV-5RE+) using a signalink with my laptop. I experimented with the TXDelay and TXTail with no luck. TXTail was 0 or 5, TXDelay went from 18-50.  

Can anyone help?

Thanks in advance.

Carlos
N3RDR

Settings of the TNC:

pi@PiGate:~/pitnc $ ./pitnc_getparams 0 0

 

   PIC Software Version           1

01 TXDelay - Zero means use ADC   0

02 Persistance                   63

03 Slottime (in 10 mS)           10

04 TXTail                         0

05 Full Duplex - Not used       255

06 Our Channel (Hex)             00

07 I2C Address (0 = async) Hex   00

   ADC Value                     45

8 1 0 3f a 0 ff 0 0 2d ee c0 sum 0 




Re: TNC-Pi connection problem

John Wiseman
 

If you are looking for a software TNC there is now also a Linux port of UZ7HO's Soundmodem

https://www.cantab.net/users/john.wiseman/Documents/QtSoundModem.html

73,
John G8BPQ

On 20/04/2020 17:47, KC3CCD wrote:
I assume is not using VOX because it is disabled in the radio’s menu and is the cable the manufacturer of the TNC recommended to be used with the radio. 

I do hear the tone on another radio. I had followed the manufacture’s direction setting the level as you described. Starting from zero and increasing until it wouldn’t increase more stayed fairly close to the minimum (about 1/8 turn). I kept going and another point was reached where it increased again near the max. It stayed constant from there. Which of the two points should I use? I tested with both and still does not connect. 

That said, using the lowest of the two, I noticed the radio was transmitting longer and it seemed like some comms occurred but the software still tells me it fails. The packet log does not say much. Maybe is a sanitized log version that gets saved with the rms connect script used by the PiGate?

Is there some log that shows the connection transaction similar to what  soundmodem does? 

Hard to tell if actual two tones are happening or not. I do hear a difference but can’t differentiate. I’ll setup my SDR later today and capture the transmission and look closer. 

Using PiGate version 2.1. I am using the same settings that soundmodem works with: 500 ms delay and 5 tail but I think the TNC likes 0 on tail. Have not really been able to narrow that one. 

Thanks for the help!

v/r,
Carlos

PS. I’m avoiding the radio discussion and was hoping to avoid with the statement of “always work with my PC”. It really does. I don’t know how to blame the radio when it reliably works with soundmodem. I will try my FT-2DR as soon as I make a DB9 to RJ45 adapter. If it ends up working, it may be time to switch to direwolf and ditching my two TNCs (oops, another hot topic <ducking>). 


Sent from my 📲

On Apr 19, 2020, at 10:15 PM, Tadd KA2DEW in NC via groups.io <tadd@...> wrote:

 Make sure you aren’t using VOX to key up the radio.  Set up the radio with PTT and wire PTT back to the TNC-PI.  
If you start a connect from your piGate to a station over the radio, do you hear the packets go out on another receiver?  
If so, turn the TXlevel on the TNC all the way down and start walking it up.  There will be a threshold where turning it up doesn’t make it louder.  Set it below that threshold.  Set the TXDELAY up until you can hear the change in tone in each packet as the TXdelay expires.  There are two tones, before the data, and during the data.  You want the before the data to be notice-able, at least for the start and TXdelay controls the length of that before-the-data period.  

The Chinese-brand radios are not to be trusted.  They have been shown to be unsafe and to not meet the USA rules, by a wide margin.  They make dandy test equipment since you can type in a receive frequency, but they are certainly not something to hook up to a real antenna or to transmit in places where other transceivers might be operated, like planet Earth.  They can do all sorts of damage to ham radio credibility in the US by impacting other services that we spend much of our time trying to impress, like the cops, fire department, federal agencies etc..   They also are not particularly selective or able to survive jamming from out-of-band signals.  That means another transmitter near you can turn off your receiver even though that other transmitter isn’t even in the ham band.  It’s really interesting when mountain climbing that as soon as you get to anywhere near the peak (where the big antennas are) your radio goes deaf.  A good radio won’t be as susceptible. The Chinese radios use the cheapest part that will even seem to work.  Earphone plugs that only survive a few dozen insertions, or beak off in the connector, and etc..    Plus the Chinese radios are really hard to operate.  Life’s too short. 

   Tadd



Tadd Torborg 




On Apr 19, 2020, at 9:51 PM, Mark Griffith via groups.io <mdgriffith2003@...> wrote:

Carlos,

The first problem is the Baofeng.  If you want packet to work, don't use a cheap radio.  It may work sometimes, and sometimes it won't.

The TXDelay is not that important, set it to 40 (400ms) and that should work for most situations.  That may be too fast for a Baofeng.  Don't mess with the other parameters.  You're problem is the radio.

What version of the PiGate software are you using?  Ver. 2.1?

Mark
KD0QYN



On Sunday, April 19, 2020, 5:02:26 PM CDT, KC3CCD <kc3ccd@...> wrote:


I have a TNC-Pi (rev 2.3) on a Pi3B+ that can't connect to any packet station. No issues via telnet. This is a PiGate setup. I can connect reliably with the same radio (UV-5RE+) using a signalink with my laptop. I experimented with the TXDelay and TXTail with no luck. TXTail was 0 or 5, TXDelay went from 18-50.  

Can anyone help?

Thanks in advance.

Carlos
N3RDR

Settings of the TNC:

pi@PiGate:~/pitnc $ ./pitnc_getparams 0 0

 

   PIC Software Version           1

01 TXDelay - Zero means use ADC   0

02 Persistance                   63

03 Slottime (in 10 mS)           10

04 TXTail                         0

05 Full Duplex - Not used       255

06 Our Channel (Hex)             00

07 I2C Address (0 = async) Hex   00

   ADC Value                     45

8 1 0 3f a 0 ff 0 0 2d ee c0 sum 0 




Re: TNC-Pi connection problem

 

Carlos,  the txdelay May be sent by software or it may be set by potentiometer.  The pitnc-getparams will tell you TXDELAY is 0 of the TNC-PI is using the A2D input and potentiometer to set txdelay.  

Tadd --- Sent from Planet X

On Apr 20, 2020, at 12:47 PM, KC3CCD <kc3ccd@...> wrote:

I assume is not using VOX because it is disabled in the radio’s menu and is the cable the manufacturer of the TNC recommended to be used with the radio. 

I do hear the tone on another radio. I had followed the manufacture’s direction setting the level as you described. Starting from zero and increasing until it wouldn’t increase more stayed fairly close to the minimum (about 1/8 turn). I kept going and another point was reached where it increased again near the max. It stayed constant from there. Which of the two points should I use? I tested with both and still does not connect. 

That said, using the lowest of the two, I noticed the radio was transmitting longer and it seemed like some comms occurred but the software still tells me it fails. The packet log does not say much. Maybe is a sanitized log version that gets saved with the rms connect script used by the PiGate?

Is there some log that shows the connection transaction similar to what  soundmodem does? 

Hard to tell if actual two tones are happening or not. I do hear a difference but can’t differentiate. I’ll setup my SDR later today and capture the transmission and look closer. 

Using PiGate version 2.1. I am using the same settings that soundmodem works with: 500 ms delay and 5 tail but I think the TNC likes 0 on tail. Have not really been able to narrow that one. 

Thanks for the help!

v/r,
Carlos

PS. I’m avoiding the radio discussion and was hoping to avoid with the statement of “always work with my PC”. It really does. I don’t know how to blame the radio when it reliably works with soundmodem. I will try my FT-2DR as soon as I make a DB9 to RJ45 adapter. If it ends up working, it may be time to switch to direwolf and ditching my two TNCs (oops, another hot topic <ducking>). 


Sent from my 📲

On Apr 19, 2020, at 10:15 PM, Tadd KA2DEW in NC via groups.io <tadd@...> wrote:

Make sure you aren’t using VOX to key up the radio.  Set up the radio with PTT and wire PTT back to the TNC-PI.  
If you start a connect from your piGate to a station over the radio, do you hear the packets go out on another receiver?  
If so, turn the TXlevel on the TNC all the way down and start walking it up.  There will be a threshold where turning it up doesn’t make it louder.  Set it below that threshold.  Set the TXDELAY up until you can hear the change in tone in each packet as the TXdelay expires.  There are two tones, before the data, and during the data.  You want the before the data to be notice-able, at least for the start and TXdelay controls the length of that before-the-data period.  

The Chinese-brand radios are not to be trusted.  They have been shown to be unsafe and to not meet the USA rules, by a wide margin.  They make dandy test equipment since you can type in a receive frequency, but they are certainly not something to hook up to a real antenna or to transmit in places where other transceivers might be operated, like planet Earth.  They can do all sorts of damage to ham radio credibility in the US by impacting other services that we spend much of our time trying to impress, like the cops, fire department, federal agencies etc..   They also are not particularly selective or able to survive jamming from out-of-band signals.  That means another transmitter near you can turn off your receiver even though that other transmitter isn’t even in the ham band.  It’s really interesting when mountain climbing that as soon as you get to anywhere near the peak (where the big antennas are) your radio goes deaf.  A good radio won’t be as susceptible. The Chinese radios use the cheapest part that will even seem to work.  Earphone plugs that only survive a few dozen insertions, or beak off in the connector, and etc..    Plus the Chinese radios are really hard to operate.  Life’s too short. 

   Tadd



Tadd Torborg 




On Apr 19, 2020, at 9:51 PM, Mark Griffith via groups.io <mdgriffith2003@...> wrote:

Carlos,

The first problem is the Baofeng.  If you want packet to work, don't use a cheap radio.  It may work sometimes, and sometimes it won't.

The TXDelay is not that important, set it to 40 (400ms) and that should work for most situations.  That may be too fast for a Baofeng.  Don't mess with the other parameters.  You're problem is the radio.

What version of the PiGate software are you using?  Ver. 2.1?

Mark
KD0QYN



On Sunday, April 19, 2020, 5:02:26 PM CDT, KC3CCD <kc3ccd@...> wrote:


I have a TNC-Pi (rev 2.3) on a Pi3B+ that can't connect to any packet station. No issues via telnet. This is a PiGate setup. I can connect reliably with the same radio (UV-5RE+) using a signalink with my laptop. I experimented with the TXDelay and TXTail with no luck. TXTail was 0 or 5, TXDelay went from 18-50.  

Can anyone help?

Thanks in advance.

Carlos
N3RDR

Settings of the TNC:

pi@PiGate:~/pitnc $ ./pitnc_getparams 0 0

 

   PIC Software Version           1

01 TXDelay - Zero means use ADC   0

02 Persistance                   63

03 Slottime (in 10 mS)           10

04 TXTail                         0

05 Full Duplex - Not used       255

06 Our Channel (Hex)             00

07 I2C Address (0 = async) Hex   00

   ADC Value                     45

8 1 0 3f a 0 ff 0 0 2d ee c0 sum 0 



Re: TNC-Pi connection problem

N3RDR
 

I assume is not using VOX because it is disabled in the radio’s menu and is the cable the manufacturer of the TNC recommended to be used with the radio. 

I do hear the tone on another radio. I had followed the manufacture’s direction setting the level as you described. Starting from zero and increasing until it wouldn’t increase more stayed fairly close to the minimum (about 1/8 turn). I kept going and another point was reached where it increased again near the max. It stayed constant from there. Which of the two points should I use? I tested with both and still does not connect. 

That said, using the lowest of the two, I noticed the radio was transmitting longer and it seemed like some comms occurred but the software still tells me it fails. The packet log does not say much. Maybe is a sanitized log version that gets saved with the rms connect script used by the PiGate?

Is there some log that shows the connection transaction similar to what  soundmodem does? 

Hard to tell if actual two tones are happening or not. I do hear a difference but can’t differentiate. I’ll setup my SDR later today and capture the transmission and look closer. 

Using PiGate version 2.1. I am using the same settings that soundmodem works with: 500 ms delay and 5 tail but I think the TNC likes 0 on tail. Have not really been able to narrow that one. 

Thanks for the help!

v/r,
Carlos

PS. I’m avoiding the radio discussion and was hoping to avoid with the statement of “always work with my PC”. It really does. I don’t know how to blame the radio when it reliably works with soundmodem. I will try my FT-2DR as soon as I make a DB9 to RJ45 adapter. If it ends up working, it may be time to switch to direwolf and ditching my two TNCs (oops, another hot topic <ducking>). 


Sent from my 📲

On Apr 19, 2020, at 10:15 PM, Tadd KA2DEW in NC via groups.io <tadd@...> wrote:

Make sure you aren’t using VOX to key up the radio.  Set up the radio with PTT and wire PTT back to the TNC-PI.  
If you start a connect from your piGate to a station over the radio, do you hear the packets go out on another receiver?  
If so, turn the TXlevel on the TNC all the way down and start walking it up.  There will be a threshold where turning it up doesn’t make it louder.  Set it below that threshold.  Set the TXDELAY up until you can hear the change in tone in each packet as the TXdelay expires.  There are two tones, before the data, and during the data.  You want the before the data to be notice-able, at least for the start and TXdelay controls the length of that before-the-data period.  

The Chinese-brand radios are not to be trusted.  They have been shown to be unsafe and to not meet the USA rules, by a wide margin.  They make dandy test equipment since you can type in a receive frequency, but they are certainly not something to hook up to a real antenna or to transmit in places where other transceivers might be operated, like planet Earth.  They can do all sorts of damage to ham radio credibility in the US by impacting other services that we spend much of our time trying to impress, like the cops, fire department, federal agencies etc..   They also are not particularly selective or able to survive jamming from out-of-band signals.  That means another transmitter near you can turn off your receiver even though that other transmitter isn’t even in the ham band.  It’s really interesting when mountain climbing that as soon as you get to anywhere near the peak (where the big antennas are) your radio goes deaf.  A good radio won’t be as susceptible. The Chinese radios use the cheapest part that will even seem to work.  Earphone plugs that only survive a few dozen insertions, or beak off in the connector, and etc..    Plus the Chinese radios are really hard to operate.  Life’s too short. 

   Tadd



Tadd Torborg 




On Apr 19, 2020, at 9:51 PM, Mark Griffith via groups.io <mdgriffith2003@...> wrote:

Carlos,

The first problem is the Baofeng.  If you want packet to work, don't use a cheap radio.  It may work sometimes, and sometimes it won't.

The TXDelay is not that important, set it to 40 (400ms) and that should work for most situations.  That may be too fast for a Baofeng.  Don't mess with the other parameters.  You're problem is the radio.

What version of the PiGate software are you using?  Ver. 2.1?

Mark
KD0QYN



On Sunday, April 19, 2020, 5:02:26 PM CDT, KC3CCD <kc3ccd@...> wrote:


I have a TNC-Pi (rev 2.3) on a Pi3B+ that can't connect to any packet station. No issues via telnet. This is a PiGate setup. I can connect reliably with the same radio (UV-5RE+) using a signalink with my laptop. I experimented with the TXDelay and TXTail with no luck. TXTail was 0 or 5, TXDelay went from 18-50.  

Can anyone help?

Thanks in advance.

Carlos
N3RDR

Settings of the TNC:

pi@PiGate:~/pitnc $ ./pitnc_getparams 0 0

 

   PIC Software Version           1

01 TXDelay - Zero means use ADC   0

02 Persistance                   63

03 Slottime (in 10 mS)           10

04 TXTail                         0

05 Full Duplex - Not used       255

06 Our Channel (Hex)             00

07 I2C Address (0 = async) Hex   00

   ADC Value                     45

8 1 0 3f a 0 ff 0 0 2d ee c0 sum 0 



Re: TNC-Pi connection problem

Mark Griffith
 

This is completely true.  I have spent years working with people that have tried to use the Baofengs for digital packet.  In every case that I know of, when they switched to a better radio, their connection problems magically disappeared.  I have two Baofengs, and I used them extensively during the initial PiGate development.  They only worked with a lot of messing around to coax them into submission.  Most of the time, they would fail for no reason.  Switching to a better radio made all the difference.

So if you want to work with haphazard equipment and maybe connect sometimes and maybe not, that is your choice.

And 1200 baud packet is not forgiving.  You must have a good signal, with low noise and good frequency response for RELIABLE communications.

Mark
KD0QYN


On Sunday, April 19, 2020, 10:55:32 PM CDT, John Tetreault (WA1OKB) <john.h.tetreault@...> wrote:


That's not even remotely true.... Plenty have packet working just fine with a Baofeng.... I get it, they're not a top of the line radio.... But 1200 baud communication is pretty darn forgiving.

On Sun, Apr 19, 2020, 9:52 PM Mark Griffith via groups.io <mdgriffith2003=yahoo.com@groups.io> wrote:
Carlos,

The first problem is the Baofeng.  If you want packet to work, don't use a cheap radio.  It may work sometimes, and sometimes it won't.

The TXDelay is not that important, set it to 40 (400ms) and that should work for most situations.  That may be too fast for a Baofeng.  Don't mess with the other parameters.  You're problem is the radio.

What version of the PiGate software are you using?  Ver. 2.1?

Mark
KD0QYN



On Sunday, April 19, 2020, 5:02:26 PM CDT, KC3CCD <kc3ccd@...> wrote:


I have a TNC-Pi (rev 2.3) on a Pi3B+ that can't connect to any packet station. No issues via telnet. This is a PiGate setup. I can connect reliably with the same radio (UV-5RE+) using a signalink with my laptop. I experimented with the TXDelay and TXTail with no luck. TXTail was 0 or 5, TXDelay went from 18-50.  

Can anyone help?

Thanks in advance.

Carlos
N3RDR

Settings of the TNC:

pi@PiGate:~/pitnc $ ./pitnc_getparams 0 0

 

   PIC Software Version           1

01 TXDelay - Zero means use ADC   0

02 Persistance                   63

03 Slottime (in 10 mS)           10

04 TXTail                         0

05 Full Duplex - Not used       255

06 Our Channel (Hex)             00

07 I2C Address (0 = async) Hex   00

   ADC Value                     45

8 1 0 3f a 0 ff 0 0 2d ee c0 sum 0 


Re: TNC-Pi connection problem

Mat Murdock
 

While a Baofeng would not be my first choice to do packet, I have got it to work.  They just are not very selective or sensitive so your millage will vary.  I have had the best results by adding a resistor on the PTT wire as show here: https://www.tnc-x.com/Baofeng.htm.  Good luck!

Mat