¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

Re: [direwolf] Problems with DINAH on Raspberry PI 3+


 

You open an interesting question.? And I believe the answer is nuanced based on:

- application?of the soundcard interface
- the details of the transceiver

I am going to give my best understanding?based on my work with Echolink and a variety of digital modes including Direwolf.

My belief is that the DINAH and other Allstar type interfaces are designed for the Allstar modes which are basically voice modes of which?Echolink is a subset.

My experience with Echolink has been that the signal needs to have squelch applied at the radio end because it is difficult?to discriminate in software between a voice signal?and noise.? As such if squelch is off the software believes that the radio is always receiving?a signal and will not allow transmission.

When I use digital?modes as you note in general?one wants to have squelch off to allow detection of low level digital signals and the software?can discriminate the digital signals out of the noise.

As AllStar is a voice mode predominantly the carrier on signal implemented in hardware is an excellent design choice.

However when a sound interface with hardware implemented?COS is used for digital modes, the COS line is now potentially problematic.? If the squelch?signal is high indicating receive then COS will disable the transmission and I have had systems effectively?lock up in receive only mode.

I have two different configurations for my signallink?interfaces depending on whether it is used for voice or digital modes to work?around this problem.

In my present implementation:

- I am providing a radio only link to a digipeater about?0.6 miles away which does not have internet access:? I don't need to decode weak signals, the digipeater will do that
- my present transceiver?will have Squelch high all the time if squelch is disabled
o so I must either have squelch enabled OR I must disable the hardware COS

Disabling hardware COS is the simplest solution, but having squelch on for this?use of Direwolf is not a problem for this application and reduces software load for random signals.

This is a more general question?of how to have a multipurpose voice and digital mode? sound interface which I am still muttering on.? And? this is compounded by different delay latencies for the PTT line depending on the details of the mode.

But thanks for the observation: in general you are correct, for Direwold?one would not want squelch on.

Thanks!


On Wed, Dec 16, 2020 at 3:20 PM David Ranch <direwolf-groupsio@...> wrote:

Hello Don,

Your email has me confused.? Direwolf should be operated with a radio with OPEN squelch.? This ensures that even the weakest signals are heard and potentially decoded.? Next, Direwolf doesn't care about COS signals but it does offer a DCD signal when it detects a potentially legit packet coming in.? Beyond that, Direwolf doesn't do any muting, etc.

Maybe you're using some other application here?? Are you running the same Rapberry Pi OS and patch level on your two different Rasberry Pis?

--David
KI6ZHD


On 12/16/2020 06:11 AM, Don Rolph wrote:
I am using a DINAH and either a Raspberry PI 2 or 3+ using the Direwolf 1.6 software

When I connect a DINAH to a Raspberry PI 2, the DINAH card output is silenced when Squelch is enabled and then returns to the prior?setting and will transmit properly.

When I connect?the DINAH? to a Raspberry PI 3+, an incoming?signal enables Squelch, the volume of the DINAH output goes down but does not return to normal?when Squelch is dropped.

This means I can receive?fine but can not send.

This actually mirrors a problem I saw on Windows.

I can obviously cut the COS line, but this disables?the hardware check for channel busy.

Thoughts?

Thanks!

--

73,
AB1PH
Don Rolph



--

73,
AB1PH
Don Rolph

Join [email protected] to automatically receive all group messages.