|
There appears to?be a problem with GPSD support in Direwolf 1.6
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.
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.
Configuration is:
- Rasperry PI 3 - Raspian?with Pulse?audio removed per Raspberry instructions - Direwolf 1.6
This behavior occurs with both a DINAH usb sound adapter with JP3 cut and with a Signalink sound adapter, so it appears to be sound adapter independent.
Direwolf is quite usable as a static digipeater system.
At this point I have not been able to get Direwolf to be stable as a GPS tracker.
I am unsure what to do next, since it appears to be a function?of the Direwolf software.
What options do I have for assistance here?
Thanks in advance!
|
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
|
Btw... as an experiment, try the following:
?? 1. Have your receiving radio on 144.390
?? 2. disable gpsd
?? 3. disconnect your GPS
?? 4. open up the receive squelch and turn up the volume so you can
hear the FM static
?? 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.
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:
toggle quoted message
Show quoted text
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
|
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.
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
--
|
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?
-?
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.
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
--
|
This is very strange. Let's start with no nogpsd recording.?? The first thing we notice is a beep at the beginning and end.  The beep near the beginning has a frequency of about 782 Hz.?  It looks like the amplitude might be so high that it is clipping and distorting the signal. The beep near the end is very strange.  The fundamental frequency is about 440 Hz with very strong harmonics. The packet has amplitude fluctuating all over.  The with gpsd recording is even stranger but let's get the no gps case working correctly first. Where is this coming from??? Is the recording directly from the soundcard or after a transmitter and receiver?
|
The center portion is the only portion of the packet. ?I am recording from a microphone so I have ambient noise.
toggle quoted message
Show quoted text
On Sep 13, 2021, at 8:34 PM, WB2OSZ <wb2osz@...> wrote:
?This is very strange. Let's start with no nogpsd recording.?? The first thing we notice is a beep at the beginning and end. <dummyfile.0.part> The beep near the beginning has a frequency of about 782 Hz.? <dummyfile.1.part> It looks like the amplitude might be so high that it is clipping and distorting the signal. The beep near the end is very strange. <dummyfile.2.part> The fundamental frequency is about 440 Hz with very strong harmonics. The packet has amplitude fluctuating all over. <dummyfile.3.part> The with gpsd recording is even stranger but let's get the no gps case working correctly first. Where is this coming from??? Is the recording directly from the soundcard or after a transmitter and receiver?
|
The no gpsd packet is successfully decoded by nearly all systems.
As you note the gpsd recording is stranger: the sound is typically quite distorted.
And this seems to occur as soon Direwolf has a gpsd daemon which it starts connecting to.
toggle quoted message
Show quoted text
On Sep 13, 2021, at 8:34 PM, WB2OSZ <wb2osz@...> wrote:
?This is very strange. Let's start with no nogpsd recording.?? The first thing we notice is a beep at the beginning and end. <dummyfile.0.part> The beep near the beginning has a frequency of about 782 Hz.? <dummyfile.1.part> It looks like the amplitude might be so high that it is clipping and distorting the signal. The beep near the end is very strange. <dummyfile.2.part> The fundamental frequency is about 440 Hz with very strong harmonics. The packet has amplitude fluctuating all over. <dummyfile.3.part> The with gpsd recording is even stranger but let's get the no gps case working correctly first. Where is this coming from??? Is the recording directly from the soundcard or after a transmitter and receiver?
|
Hello Don,
A few other tests to try:
1. gpsd running and puck connected; In direwolf.conf GPSD
disabled but have cgps or xgps running in another window which
will enable the GPS puck and make sure it has a lock.? How are the
resulting transmitted packets sounding?
2. no transmitter:
?? - disable gpsd
?? - turn off the radio and connect the audio output from the
Direwolf soundcard to a speaker
?? - Send a beacon from Direwolf and see how it sounds through the
speaker
?? - Enable gpsd and send a beacon from
Direwolf and see how it sounds through the speaker?
--David
KI6ZHD
On 09/13/2021 03:33 PM, Don Rolph
wrote:
toggle quoted message
Show quoted text
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?
-?
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.
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
--
--
|
Ok I was working to establish a test setup to run the tests David Ranch and John Langer WB2OSZ had suggested.
But I was having trouble establishing a clean test scenario in which to confirm the success of the proposed tests.? Someone had mentioned RFI from a GPS puck so I through a ferrite choke around the USB lead fomr the GPS [puck.
And Iam now faced with a major problem in running the propsoed?tests: ?I have been running for 24 hours so far and I can't get it to fail so I can run the tests to see if they fizx?it.
So based on the test data to date:
- ?it appears to be RFI causing failure when using GPSD
- ?putting a choke on the GPS puck wire seems to suppress the issue
I am still puzzled that Direwofl works when the gps puck is attached, gpsd is running and I am monitoring the gps using cgps.
But this is engineering not science and:
- putting the choke on the GPS lead suppresses the problem
I have ordered more chokes and will put them on all the leads: ?there is a general issue that Raspberry PIs seem quite sensitive RFI in general.
My thanks in particular to David and John for their?help and to the members of the Direwolf discussion group for their patience with me!
Hello Don,
A few other tests to try:
1. gpsd running and puck connected; In direwolf.conf GPSD
disabled but have cgps or xgps running in another window which
will enable the GPS puck and make sure it has a lock.? How are the
resulting transmitted packets sounding?
2. no transmitter:
?? - disable gpsd
?? - turn off the radio and connect the audio output from the
Direwolf soundcard to a speaker
?? - Send a beacon from Direwolf and see how it sounds through the
speaker
?? - Enable gpsd and send a beacon from
Direwolf and see how it sounds through the speaker?
--David
KI6ZHD
On 09/13/2021 03:33 PM, Don Rolph
wrote:
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?
-?
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.
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
--
--
|
