¿ªÔÆÌåÓý

Re: Apparent problem with GPSD support in Direwolf 1.6


 

¿ªÔÆÌåÓý


Hello Don,

If GPSD is not enabled and I use PBEACON and digipeating Direwolf is functioning, packets are received?by a wide variety of stations.? A capture of the sound is below as nogpsd.m4a.

This sounds ok though I'm guessing your using a Kenwood radio right?? Why am I hearing a beep before the AFSK-1200bps packet and then another beep after the packet.? That should NOT be happening.



If GPSD is enabled, and I use PBEACON?and digipeating, Direwolf packets are in general not?decoded by any system. ?(sometimes one gets lucky but success is at best intermittent).? A capture of the sound is attached as gpsd.m4a.

To me, it sounds like you're missing the begining of the packet here.? Have you 100% opened the squelch on your radio?? This is how Direwolf is intended to run.?? If this turns out to be your issue, maybe starting up gpsd and thus powering up your GPS is creating some interference on the VHF receiver and it's hurting your current squelch setting.? Again.. open it up 100%.?? Also.. the Kenwood beeps are there which should NOT be there.


- Rasperry PI 3
- Raspian?with Pulse?audio removed per Raspberry instructions
- Direwolf 1.6

Please note that the recommendation to remove PulseAudio is no longer required as this only applied to older versions of Raspberry Pi OS.? There is an open Github issue on this:

???

Your existing setup should work perfectly fine with it removed but of you're using Xwindows on this Raspberry Pi and want to use say system sounds via a different soundcard, things probably won't work.


--David
KI6ZHD

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