Did a retest of one configuration.

- enable GPSD in direwolf.conf

- kill gpsd?

- unplug gps

Start direwolf:? all works.? Log messages state that there is no gps data.

Now plug in gps puck.

- gpsd restarts

- gps data starts flowing

-? direwolf fails to produce good packets.

Since simply having gpsd running with a puck plugged in does not cause a failure, this would seem to suggest that the issue is the polling of gpsd by direwolf which is causing the trouble:? when there is no gpsd to poll. everything seems to work.

Thoughts?

-?

On Mon, Sep 13, 2021 at 5:41 PM Don Rolph via <don.rolph=[email protected]> wrote:

See below.

System works fine with gpsd running and puck connected.? In direwolf.conf GPSD disabled.

System works fine with gpsd running and no puck connected.? In direwolf.conf GPSD disabled.

System works fine with gpsd not running and no puck connected.?? In direwolf.conf GPSD disabled.

System fails with puck connected, gpsd running and GPSD enabled in direwolf.conf.

On Mon, Sep 13, 2021 at 11:41 AM David Ranch <direwolf-groupsio@...> wrote:

Btw... as an experiment, try the following:

?? 1. Have your receiving radio on 144.390

check?

?? 2. disable gpsd

check?

?? 3. disconnect your GPS

check?

?? 4. open up the receive squelch and turn up the volume so you can hear the FM static

check?

?? 5. connect the GPS.? Did you hear any difference in the FM static?? You might not as you really need to be listening when there is is some other active transmitter on frequency.?

?? 6. enable gpsd.? Did you hear any difference in the FM static?? Did you hear any difference in the FM static?? You might not as you really need to be listening when there is is some other active transmitter on frequency.? Maybe try QSYing the radio to an active analog FM repeater with an ongoing conversation that's near 144.390.

no change in statuic?

Btw, I had a very similar "receive sensitivity" issue on an APRS setup when using an Ambicom USB GPS:

??

I had to stop using that GPS due to the various interference it would create on 144.390.

--David
KI6ZHD

On 09/13/2021 08:25 AM, David Ranch wrote:

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

--

73,

AB1PH

Don Rolph

--

73,

AB1PH

Don Rolph