I have a TT4 connected to a Raspberry Pi running PAT Winlink client and ax.25 and kissattach.  I can connect the TT4 to PAT client when I use the kissattach command.  After I power up my Raspberry Pi, the first time that I try to connect PAT to a gateway, there is about a 15 second delay when it seems nothing is happening, and then the TT4 issues a PTT and the radio connects to the gateway and all works as expected.

If I try again to connect PAT to the gateway, there is no delay.  The PTT happens almost immediately and the session proceeds.

Is there some setting in the TT4 or in the Raspberry Pi (PAT or ax.25 or kissattach?) that can reduce or eliminate the 15 second delay the first time?
--
Bill AA6BD

Hello! I am using direwolf with xastir,  Firts I was using plughw:1,0 configuration and direwolf worked without any problem, but the problem is Alsa don't let me use the soundcard with other application like sox or qsstv then I change the setting in .asoundrc with dmix, direwolf starts normal same xastir but only let me transmit once and the second time I get this error:

 

Audio Writer Error: File descriptor in bad state

Audio write error: retry count exeeded

  

.asound file:

 

pcm.dmixer {
    type dmix
    ipc_key 1024
    slave.pcm "hw:1,0"
}
pcm.dsnooped {
    type dsnoop
    ipc_key 1025
    slave.pcm "hw:1,0"
}

pcm.duplex {
    type asym
    playback.pcm "dmixer"
    capture.pcm "dsnooped"
}

 

pcm.usb {

                 type plug

                 slave.pcm "duplex"

}

I think is a alsa problem and I need a configuration for my usb soundcard, I don't know

(The only small remaining issue is that VNC Connect says it can't display the desktop - more investigation to be done.)

SSH into the pi and run sudo raspi-config Under the advanced options, set the resolution and it should solve this issue.

73, de KM4ACK

YouTube

On 1/9/20 1:32 am, David Ranch wrote:

Hello Phil,

Going back to your first post, it seems you're doing this on "a Linux laptop" which I assume is running PulseAudio.

Thanks again David for your reply,

No, the laptop uses Alsa audio. Perhaps there's no reason for me to be concerned about the audio input level to the Raspberry pi? I just thought that others might be using a Raspberry pi and an FT-991A together and had found a way to create a level control.

By the way, the laptop runs under Kubuntu and the Raspberry runs under the standard Raspberry OS.

On 31/8/20 3:37 am, David Ranch wrote:

Different sound devices will have different names so that's perfectly fine.  I assume you're using Raspbian here but what does commands like "aplay -l" and "arecord -l" say?  Are you using vanilla ALSA or are you trying to use say PulseAudio, etc?

Thank you for your reply David,

I had already listed the Alsa audio devices but only the default device was shown. I decided to do an update and then turned the Raspberry pi off for the night. The next day and now the Burr-Brown codecs are listed so at least I can select the codecs that I previously had.

However I have a new problem, no capture control only an output control which does vary the transmitter power. AlsaMixer reports that "This device does not have any capture controls" . JS8CALL and Fldigi (as well as WSJTX, which I don't use) function but the input is a little high at 60dB. As I type this I now remember that was the case previously but the interface had it's own control which solved the problem.

So the question now is, how do I create a capture control? More Internet searching has not revealed an answer.