Date   

Re: TT4 delays about 15 seconds as KISS modem

Mark Griffith
 

It's just grabbing the call sign, so just replace $ADMIN with your call sign.

Mark
KD0QYN


On Friday, September 4, 2020, 5:59:06 PM CDT, Bill AA6BD <bill@...> wrote:


Mark,
In your little program, I understand substituting my callsign and tnc name in axports.  I don't have a file wl2k.conf.  I have a directory /etc/ax25 which is where axports and a bunch of ax25....conf files are stored but there is no wl2k.conf file in that directory.  What is this file?
--
Bill AA6BD


Re: New participant and new with the Raspi

K6AEA@...
 

Did you right-click the speaker icon, and select the appropriate output?


Re: TT4 delays about 15 seconds as KISS modem

Bill AA6BD
 

Mark,
In your little program, I understand substituting my callsign and tnc name in axports.  I don't have a file wl2k.conf.  I have a directory /etc/ax25 which is where axports and a bunch of ax25....conf files are stored but there is no wl2k.conf file in that directory.  What is this file?
--
Bill AA6BD


Re: Dual purpose DMR hotspot and HF digimodes

Bryan Waller
 

Just ordered the least expensive dual band, dual timeslot MMDVM with decent reviews from Amazon and reviews confirming that it runs on the PI4b. I'll likely first set it up with its own SD card image since I have never run a DMR hotspot before, then try to incorporate it in with my KM4ACK build a pi setup on a separate SD. Since the single timeslots have long run on the original pi, I would think that the 4b would have plenty of processing power to do DMR hotspot and HF digital duty at the same time, even running dual timeslots. We shall see. If it doesn't work, I'll order another PI and set them up separately.


Re: Dual purpose DMR hotspot and HF digimodes

 

I would think a Pi with a HAT (like DRAWS™) for HF/Digital Data such as Packet and an attached USB MMDVM for digital voice modes would be a good combination.

On Fri, Sep 4, 2020 at 7:48 AM Bryan Waller <bryanw55@...> wrote:
I may give it a roll in the near future. Worst case is that I'd have to buy another pi if it doesn't work.



--
John D. Hays
Kingston, WA
K7VE

 


Re: Dual purpose DMR hotspot and HF digimodes

Bryan Waller
 

I may give it a roll in the near future. Worst case is that I'd have to buy another pi if it doesn't work.


Re: Dual purpose DMR hotspot and HF digimodes

thegadget techie
 

That would be interesting.  All the DMR stuff is just a process on the pi being it's derived from Debian.  Limits maybe imposed by the mem/cpu capabilities, in that can it perform efficient enough under the various load that the apps place on the unit.  All the GUI-based stuff will put a higher demand on the processing capabilities vs. the DMR "conversion".

Would be an interesting POC.


Re: TT4 delays about 15 seconds as KISS modem

Mark Griffith
 

I'm not sure if it the kissattach or just starting the AX.25 service.  This may have appeared in early kernels, it wasn't in Wheezy, but when Buster was released, this delay showed up.  May have been in Stretch too.  Annoying, but that is what you get with open sourced software.  I notice it as every time AX.25 is started.

My answer was every time I start the AX.25 service, I run a little program to wake it up.

#!/bin/sh

ADMIN=`grep ^mycall /usr/local/etc/wl2k.conf | cut -d\= -f2`
/usr/sbin/beacon tnc $ADMIN -s -t1 "Test"
/usr/sbin/beacon tnc $ADMIN -s -t1 "Test"
/usr/sbin/beacon tnc $ADMIN -s -t1 "Test"

This just sends a very small beacon signal and every AX.25 transmission after that will not have a delay.  The first two "tests" are not normally transmitted, but the third will.

You would have to modify the script for your call sign and the tnc name in axports.

Mark
KD0QYN


On Thursday, September 3, 2020, 1:20:53 PM CDT, David Ranch <rpi4hamradio-groupsio@...> wrote:



This is a known behavior of the mkiss kernel module creating a one-time delay.  There are a few ways to address this (crc_force=1) this be it just be patient for your first connection attempt OR change the options used when the mkiss kernel module is installed.  This later approach is the way I do it on my system via my packetrig.sh startup script:

   http://www.trinityos.com/HAM/CentosDigitalModes/usr/local/sbin/packetrig.sh
   --

   #Attempt to set the crcmode to NONE :: this can also be done with kissparm's -c option
   echo -e "\nLoading mkiss kernel module with CRC-mode: none" >> $LOG 2>&1
   $MODPROBE -q mkiss crc_force=1 >> $LOG 2>&1
   --

--David
KI6ZHD


On 09/03/2020 10:26 AM, Bill AA6BD wrote:
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


Re: TT4 delays about 15 seconds as KISS modem

David Ranch
 


This is a known behavior of the mkiss kernel module creating a one-time delay.  There are a few ways to address this (crc_force=1) this be it just be patient for your first connection attempt OR change the options used when the mkiss kernel module is installed.  This later approach is the way I do it on my system via my packetrig.sh startup script:

   http://www.trinityos.com/HAM/CentosDigitalModes/usr/local/sbin/packetrig.sh
   --

   #Attempt to set the crcmode to NONE :: this can also be done with kissparm's -c option
   echo -e "\nLoading mkiss kernel module with CRC-mode: none" >> $LOG 2>&1
   $MODPROBE -q mkiss crc_force=1 >> $LOG 2>&1
   --

--David
KI6ZHD


On 09/03/2020 10:26 AM, Bill AA6BD wrote:
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


TT4 delays about 15 seconds as KISS modem

Bill AA6BD
 

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


FoxTelem using USB Sound

Suryono Adisoemarta
 

Has anybody use a USB soundcard to decode using FoxTelem ?

On mine I can see it detected on starting FoxTelem.jar, but not shown / available on the dropdown source menu.

This is on Rpi 3B running headless

73 de Yono - YD0NXX


Dual purpose DMR hotspot and HF digimodes

Bryan Waller
 

Has anyone seen a build that uses say a Pi4b to work simultaneously as a DMR radio hotspot and to work HF digital modes? If not, can you think of any reason it would not work or would not be a good idea to attempt?

Bryan/KN4EBW


New participant and new with the Raspi

Julio Paredes - KW4WA
 

Hello everyone.
I'm using for the first time a Raspberry-Pi 4 that I want to use to do all the digital modes I'm involved with: Winlink, JS8, PSK31.
On learning how to use the Raspbian environment I encountered a problem:  I connected a set of earphones, connected to YouTube and opened a music video, but there is no sound.  Is there a need for High Z phones or something in the software that I need to do?
Thanks and 73,
JP, KW4WA


Re: Accessing USB devices in .net core

Brus-Per
 

Charles,

Are you trying to localize/find the USB ports and the devices connected to them or are you attempting to read/write to a specific port? I assume you already know that Raspbian (Debian/Linux) treats USB ports as any tty-device.

I'm sorry but when it comes to RPi:s I'm only using Golang so I can not be of much help when it comes to .net on the RPi.

Best,
Brus-Per, SM6EIK


Re: Direwolf - Audio Writer Error

David Ranch
 


Hello Fushigi,

I already replied to you back on Fri, 28 Aug 2020 09:41:16 -0700 about this issue.  Are you saying that with this .asoundrc file in place but having direwolf STILL configured to use "plughw:1,0", DIrewolf breaks?  Remember, you cannot run say Direwolf and another soundcard program using the same sound device at the same time.

--David
KI6ZHD



On 09/01/2020 09:45 PM, Ada via groups.io wrote:
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


Direwolf - Audio Writer Error

Ada <fushigi_aries@...>
 

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


Re: Reducing size of fldigi display to fit small screen on raspberry pi

Bill P.
 

I’m sorry I don’t have the exact file name for you but there is a TXT file in /boot that contains the display parameters to adjust. Also, if you go to adafruit.com and look at any of their 5” or 7” hdmi displays there is a reference on the page to the same file with the parameters to adjust. I have a Pi-3 running WSJT-X and was able to adjust the parameters for a proper display on a WIMAXIT 10” hdmi.
Bill acj


Re: Screen size of fldigi on a small (3.5") gpio display

Mark Griffith
 

There is probably a minimum size for the application and the 3.5 inch screen is just too small.

You might get more help asking the FLDIGI application team.

Mark
KD0QYN


On Tuesday, September 1, 2020, 1:56:27 PM CDT, Charles Albert <mrcwa2@...> wrote:


I have properly installed a small display on the pi zero; it displays
perfectly on boot up and all the standard apps in raspian display
well; however, when I installed fldigi on the zero, the display is
oversized and only about 25% of the fldigi screen can be seen. Moving
the screen around I can see part of the top of the screen, but can't
see the bottom third.  This seems like a setting on fldigi needs to be
changed.  fldigi displays perfectly on a 5" hdmi screen on the pi 3B+
an on a 7" hdmi display. The fldigi loaded on the zero with no
problem. Any thoughts??




Screen size of fldigi on a small (3.5") gpio display

Charles Albert
 

I have properly installed a small display on the pi zero; it displays
perfectly on boot up and all the standard apps in raspian display
well; however, when I installed fldigi on the zero, the display is
oversized and only about 25% of the fldigi screen can be seen. Moving
the screen around I can see part of the top of the screen, but can't
see the bottom third. This seems like a setting on fldigi needs to be
changed. fldigi displays perfectly on a 5" hdmi screen on the pi 3B+
an on a 7" hdmi display. The fldigi loaded on the zero with no
problem. Any thoughts??


Re: None of my Pi's are showing on network _ HELP

N5XMT
 

Also edit config.text and uncomment "hdmi_force_hotplug=1"

Get BlueMail for Android
On Sep 1, 2020, at 04:18, km4ack <jason.oleham@...> wrote:

(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

1141 - 1160 of 13266