On Jan 2, 2022, at 2:12 PM, Rob Giuliano via <kb8rco@...> wrote:

I know thus is off topic.

I find the inoTNC very interesting.? Since the device appears to use the MCP2221 by MicroChip.

Section 2.0 USB ENUMERATION PROCESS

This section explains how to set certain parameters (like S/N) which could be used in the UDEV rules to identify each device, which would be easier to identify multiple devices connected to different radios.

Have you looked into this options?

Rob KB8RCO

On Sun, Jan 2, 2022 at 12:51, Tadd KA2DEW in NC via

<tadd@...> wrote:

David and Charles,?

?The NinoTNC was designed to make the process of a multi-port Raspberry PI station easy to set up and maintain.?

Our local network was using 50 of the TNC-PI. ?We’d even come up with a customized PCB that Coastal Chipworks was making for us that made it a little easier than his standard PCB. ?However, with Coastal going away we created our own TNC and fixed all of the problems we’d had with the TNC-PI including implementing a modem that is almost at Direwolf levels of performance, and adding in 3 more bit-rates plus firmware based forward error correction. ?

In the middle of all of this we made a go of using Direwolf in place of the TNC-PI. ?There were three considerations (probably unique to our project) which had us go with the home-grown firmware TNC project instead of Direwolf. ? 1: The Direwolf configuration was not very easy when dealing with > 3 port systems. 2: We still had to come up with a hardware piece to interface the Raspberry PI to the radios, because we did not want a home-brew element to be a requirement for system construction. 3: we had engineers in the group who wanted to do a firmware TNC. ?

Over the past 2 years we’ve completely eliminated the TNC-PI from the network in favor of the NinoTNC because NinoTNC is so much easier to maintain and support, and?NinoTNC’s modem is much better. ?It’s also more fun to watch. ?The only rough part remaining is recognizing which USB /dev goes to which radio. ?This comes down to hooking up the USB cables in a particular order, or figuring out the arrangement after system startup. ?I’m not totally happy with that but it’s a crap-ton easier than dealing with the TNC-PI! ? ? I’m pretty sure Direwolf multi-port users have this problem as well. ?

We came up with a team of volunteer labor to produce and deliver the NinoTNC and we take no labor costs or profit to ship and support the TNC as parts. ?So $40 as a solder kit gets you a TNC-PI/KPC-3 compatible DE9 socket on a USB-KISS TNC with outstanding performance, diagnostic and configuration features against which no other hardware TNC has ever compared, at any price. ?

?

? ?

Tadd - KA2DEW -

<ninotnc-a4-model-for-webpage16b-x1348x1562.jpeg>

<ninotnc-a4-model-for-webpage16b-x1348x1562.jpeg>

On Jan 2, 2022, at 2:12 PM, Rob Giuliano via <kb8rco@...> wrote:

I know thus is off topic.

I find the inoTNC very interesting.? Since the device appears to use the MCP2221 by MicroChip.

Section 2.0 USB ENUMERATION PROCESS

This section explains how to set certain parameters (like S/N) which could be used in the UDEV rules to identify each device, which would be easier to identify multiple devices connected to different radios.

Have you looked into this options?

Rob KB8RCO

On Sun, Jan 2, 2022 at 12:51, Tadd KA2DEW in NC via

<tadd@...> wrote:

David and Charles,?

?The NinoTNC was designed to make the process of a multi-port Raspberry PI station easy to set up and maintain.?

Our local network was using 50 of the TNC-PI. ?We’d even come up with a customized PCB that Coastal Chipworks was making for us that made it a little easier than his standard PCB. ?However, with Coastal going away we created our own TNC and fixed all of the problems we’d had with the TNC-PI including implementing a modem that is almost at Direwolf levels of performance, and adding in 3 more bit-rates plus firmware based forward error correction. ?

In the middle of all of this we made a go of using Direwolf in place of the TNC-PI. ?There were three considerations (probably unique to our project) which had us go with the home-grown firmware TNC project instead of Direwolf. ? 1: The Direwolf configuration was not very easy when dealing with > 3 port systems. 2: We still had to come up with a hardware piece to interface the Raspberry PI to the radios, because we did not want a home-brew element to be a requirement for system construction. 3: we had engineers in the group who wanted to do a firmware TNC. ?

Over the past 2 years we’ve completely eliminated the TNC-PI from the network in favor of the NinoTNC because NinoTNC is so much easier to maintain and support, and?NinoTNC’s modem is much better. ?It’s also more fun to watch. ?The only rough part remaining is recognizing which USB /dev goes to which radio. ?This comes down to hooking up the USB cables in a particular order, or figuring out the arrangement after system startup. ?I’m not totally happy with that but it’s a crap-ton easier than dealing with the TNC-PI! ? ? I’m pretty sure Direwolf multi-port users have this problem as well. ?

We came up with a team of volunteer labor to produce and deliver the NinoTNC and we take no labor costs or profit to ship and support the TNC as parts. ?So $40 as a solder kit gets you a TNC-PI/KPC-3 compatible DE9 socket on a USB-KISS TNC with outstanding performance, diagnostic and configuration features against which no other hardware TNC has ever compared, at any price. ?

?

? ?

Tadd - KA2DEW -

<ninotnc-a4-model-for-webpage16b-x1348x1562.jpeg>

<ninotnc-a4-model-for-webpage16b-x1348x1562.jpeg>

?

DCD questions:

David and Charles,
?The NinoTNC was designed to make the process of a multi-port Raspberry PI station easy to set up and maintain.
Our local network was using 50 of the TNC-PI. ?We’d even come up with a customized PCB that Coastal Chipworks was making for us that made it a little easier than his standard PCB. ?However, with Coastal going away we created our own TNC and fixed all of the problems we’d had with the TNC-PI including implementing a modem that is almost at Direwolf levels of performance, and adding in 3 more bit-rates plus firmware based forward error correction.
In the middle of all of this we made a go of using Direwolf in place of the TNC-PI. ?There were three considerations (probably unique to our project) which had us go with the home-grown firmware TNC project instead of Direwolf. ? 1: The Direwolf configuration was not very easy when dealing with
> 3 port systems. 2: We still had to come up with a hardware piece to interface the Raspberry PI to
the radios, because we did not want a home-brew element to be a requirement for system construction. 3: we had engineers in the group who wanted to do a firmware TNC.
Over the past 2 years we’ve completely eliminated the TNC-PI from the network in favor of the NinoTNC because NinoTNC is so much easier to maintain and support, and?NinoTNC’s modem is much better. ?It’s also more fun to watch. ?The only rough part remaining is recognizing which USB /dev goes to which radio. ?This comes down to hooking up the USB cables in a particular order, or figuring out the arrangement after system startup. ?I’m not totally happy with that but it’s a crap-ton easier than dealing with the TNC-PI! ? ? I’m pretty sure Direwolf multi-port users have this problem as well.
We came up with a team of volunteer labor to produce and deliver the NinoTNC and we take no labor costs or profit to ship and support the TNC as parts. ?So $40 as a solder kit gets you a TNC-PI/KPC-3 compatible DE9 socket on a USB-KISS TNC with outstanding performance, diagnostic and configuration features against which no other hardware TNC has ever compared, at any price.

Tadd - KA2DEW -

On Jan 2, 2022, at 12:30 PM, David Ranch <direwolf-groupsio@... <mailto:direwolf-groupsio@...>> wrote:


Hello Charles,

Ok, thanks for clearing those points up though as John mentioned, Direwolf will outperform that TNC-Pi on weak signals by a large margin.? There isn't much point continuing the discussion here since it's outside the topic of Direwolf but I had played with the TNC-Pis some time ago and have a write up here that might help you:



NOTE:? That section of my documentation brings up the TNC via the I2C bus and not using the Pi's internal hardware serial UART. That document also focuses on using the LInux AX.25 stack but since you're using JNOS's stack, you'll need to translate some of those steps into JNOS's configuration.

--David
KI6ZHD

I am replacing the old PC with the RPi and the KPC3 with the TNC-Pi.
This will be running on the local 220Mhz lan to inject connectivity
to the current flexnet group in NJ near my home (Staten Island). They
have dropped off of the flexnet destination lists because of connection
issues. That is why I am going to be running Xnet to talk "flexnet".
My current JNOS bbs is not going to be affected. I will be using this
RPi setup at my home as a bridge between NJ flexnet and N2KGC in NY
via AXIP. This is only a temporary link.

On 1/1/2022 2:19 PM, David Ranch wrote:

Hello Charles,

What is your goal here?? Do you just want to replace the KPC3 with the TNC-Pi?? That's possible but you won't use Direwolf here as Direwolf and the TNC-Pi do the same function.? Pick one. Next, maybe you want to replace the 386 PC?? That's also possible as Raspberry Pi 3B can do this as well and is orders of magnitude faster than a 386.? Finally, Xnet is possible (recently pointed out to me) to natively run on the Raspberry Pi but there is little documentation.

I would recommend to join the UroNode email list ( ) to get get help there as that's far removed from anything Direwolf.

--David
KI6ZHD

On Sun, Jan 2, 2022 at 12:51, Tadd KA2DEW in NC via groups.io

<tadd@...> wrote:

David and Charles,?

?The NinoTNC was designed to make the process of a multi-port Raspberry PI station easy to set up and maintain.?

Our local network was using 50 of the TNC-PI. ?We’d even come up with a customized PCB that Coastal Chipworks was making for us that made it a little easier than his standard PCB. ?However, with Coastal going away we created our own TNC and fixed all of the problems we’d had with the TNC-PI including implementing a modem that is almost at Direwolf levels of performance, and adding in 3 more bit-rates plus firmware based forward error correction. ?

In the middle of all of this we made a go of using Direwolf in place of the TNC-PI. ?There were three considerations (probably unique to our project) which had us go with the home-grown firmware TNC project instead of Direwolf. ? 1: The Direwolf configuration was not very easy when dealing with > 3 port systems. 2: We still had to come up with a hardware piece to interface the Raspberry PI to the radios, because we did not want a home-brew element to be a requirement for system construction. 3: we had engineers in the group who wanted to do a firmware TNC. ?

Over the past 2 years we’ve completely eliminated the TNC-PI from the network in favor of the NinoTNC because NinoTNC is so much easier to maintain and support, and?NinoTNC’s modem is much better. ?It’s also more fun to watch. ?The only rough part remaining is recognizing which USB /dev goes to which radio. ?This comes down to hooking up the USB cables in a particular order, or figuring out the arrangement after system startup. ?I’m not totally happy with that but it’s a crap-ton easier than dealing with the TNC-PI! ? ? I’m pretty sure Direwolf multi-port users have this problem as well. ?

We came up with a team of volunteer labor to produce and deliver the NinoTNC and we take no labor costs or profit to ship and support the TNC as parts. ?So $40 as a solder kit gets you a TNC-PI/KPC-3 compatible DE9 socket on a USB-KISS TNC with outstanding performance, diagnostic and configuration features against which no other hardware TNC has ever compared, at any price. ?

?

? ?

Tadd - KA2DEW -

I just added the DCD function on Direwolf 1.7
Since then, when my beacon transmits, I only have the carrier, and I don't have the text of my beacon. Why ?
in Direwolf I put:
PTT GPIO 26

#DCD COM1 -DTR
 DCD GPIO 24
Is it correct ?
Thanks for your help.

On Jan 2, 2022, at 12:30 PM, David Ranch <direwolf-groupsio@...> wrote:

Hello Charles,

Ok, thanks for clearing those points up though as John mentioned, Direwolf will outperform that TNC-Pi on weak signals by a large margin.? There isn't much point continuing the discussion here since it's outside the topic of Direwolf but I had played with the TNC-Pis some time ago and have a write up here that might help you:

??

NOTE:? That section of my documentation brings up the TNC via the I2C bus and not using the Pi's internal hardware serial UART.? That document also focuses on using the LInux AX.25 stack but since you're using JNOS's stack, you'll need to translate some of those steps into JNOS's configuration.

--David
KI6ZHD

I am replacing the old PC with the RPi and the KPC3 with the TNC-Pi.
This will be running on the local 220Mhz lan to inject connectivity
to the current flexnet group in NJ near my home (Staten Island). They
have dropped off of the flexnet destination lists because of connection
issues. That is why I am going to be running Xnet to talk "flexnet".
My current JNOS bbs is not going to be affected. I will be using this
RPi setup at my home as a bridge between NJ flexnet and N2KGC in NY
via AXIP. This is only a temporary link.

On 1/1/2022 2:19 PM, David Ranch wrote:

Hello Charles,

What is your goal here?? Do you just want to replace the KPC3 with the TNC-Pi?? That's possible but you won't use Direwolf here as Direwolf and the TNC-Pi do the same function.? Pick one.? Next, maybe you want to replace the 386 PC?? That's also possible as Raspberry Pi 3B can do this as well and is orders of magnitude faster than a 386.? Finally, Xnet is possible (recently pointed out to me) to natively run on the Raspberry Pi but there is little documentation.

I would recommend to join the UroNode email list ( ) to get get help there as that's far removed from anything Direwolf.

--David
KI6ZHD

I don't understand why we tolerate this issue? It's clear that RFI alone is not the issue. I've done extensive testing with APRS and AllStar, using the same equipement. AllStar can transmit for hours on end and I have never seen the sound card or any part of the USB system or software stop working.

If I run direwolf, the failure rate varies, but always happens. I assume there's something with the RFI that does prevent minor blips in the comms of the system, but direwolf can't bounce back, whereas AllStar doesn't even noticeable get phased by it.?

I think this is something to be looked at.

I am replacing the old PC with the RPi and the KPC3 with the TNC-Pi.
This will be running on the local 220Mhz lan to inject connectivity
to the current flexnet group in NJ near my home (Staten Island). They
have dropped off of the flexnet destination lists because of connection
issues. That is why I am going to be running Xnet to talk "flexnet".
My current JNOS bbs is not going to be affected. I will be using this
RPi setup at my home as a bridge between NJ flexnet and N2KGC in NY
via AXIP. This is only a temporary link.

On 1/1/2022 2:19 PM, David Ranch wrote:

Hello Charles,

What is your goal here?? Do you just want to replace the KPC3 with the TNC-Pi?? That's possible but you won't use Direwolf here as Direwolf and the TNC-Pi do the same function.? Pick one.? Next, maybe you want to replace the 386 PC?? That's also possible as Raspberry Pi 3B can do this as well and is orders of magnitude faster than a 386.? Finally, Xnet is possible (recently pointed out to me) to natively run on the Raspberry Pi but there is little documentation.

I would recommend to join the UroNode email list ( ) to get get help there as that's far removed from anything Direwolf.

--David
KI6ZHD

On Sun, Jan 2, 2022 at 10:38, F6GDL

<om.f6gdl@...> wrote:

I just added the DCD function on Direwolf 1.7
Since then, when my beacon transmits, I only have the carrier, and I don't have the text of my beacon. Why ?
in Direwolf I put:
PTT GPIO 26

#DCD COM1 -DTR
 DCD GPIO 24
Is it correct ?
Thanks for your help.

Hello Charles,
What is your goal here?? Do you just want to replace the KPC3 with the TNC-Pi?? That's possible but you won't use Direwolf here as Direwolf and the TNC-Pi do the same function.? Pick one.? Next, maybe you want to replace the 386 PC?? That's also possible as Raspberry Pi 3B can do this as well and is orders of magnitude faster than a 386.? Finally, Xnet is possible (recently pointed out to me) to natively run on the Raspberry Pi but there is little documentation.
I would recommend to join the UroNode email list ( ) to get get help there as that's far removed from anything Direwolf.
--David
KI6ZHD

Hei,

I found this DW's transmit inhibit very useful. I'm running SvxLink and Direwolf in a RPi 3 which is connected to a Motorola GM340 transceiver with RIM-Maxtrac. Both FM and APRS are two-way Internet gateways. The FM transmission has priority.

If some one is interested the modified SvxLink Tcl-codes resides in a repository at The branch is aprs_inhibit

73, Veijo