¿ªÔÆÌåÓý

Date

Re: Anyone Using L76X GPS HAT?

 

Never used the L76X GPS hat, but if you give some configuration information, we might be able to help:
There appears to be 2 method of connecting the L76X to the Pi:
1. Simplest would be to set the Jumpers in position B (control through the Raspberry Pi) and
?? Make sure the serial port (typically /dev/ttyAMA0) is configured for normal use
?? Check for NMEA data with something like minicom with
?????? minicom -D /dev/ttyAMA0 -b9600
?? assumes default output is at 9600 baud 9per website)

If you see NMEA sentences, change the direwolf.conf accordingly.

2. Option 2 would be to set the jumpers to A and add a USB cable between the L76X USB out and the Pi USB in.
?? This would be the same as you are currently using an external USB GPS.
?? This may seem a bit strange, but should work.

Robert Giuliano
KB8RCO



On Sunday, September 24, 2023 at 05:13:26 PM EDT, Doug Kaye (K6DRK) <doug@...> wrote:


I've got my Pi Zero W running direwolf with an exernal USB-connected GPS receiver. Now I'm trying to get it working with a GPS hat to make it more compact. Has anyone successfully used a L76X GPS Hat? See?

? ?...doug


Re: Digipeater build.... not hearing packets

 

exact same USB sound card


Anyone Using L76X GPS HAT?

 

I've got my Pi Zero W running direwolf with an exernal USB-connected GPS receiver. Now I'm trying to get it working with a GPS hat to make it more compact. Has anyone successfully used a L76X GPS Hat? See?

? ?...doug


Re: Digipeater build.... not hearing packets

 

Did you use the exact same USB sound card or the laptop's sound card with UZ7HO?

If USB, definitely the alsamixer change should get you going.
If not, try that.? Get thd USB card working on the laptop (not the laptop's sound card).
? It still could be cable routing.

Robert Giuliano
KB8RCO


On Sun, Sep 24, 2023 at 14:28, Jon W7SEA
<jonw7sea@...> wrote:
Here's my to-date testing.? This will likely leave open some of Rob's points, but it's as far as I've gotten.

  • Headset (with 2.5mm and 3.5mm jacks) plugged directly into radio; hear packets.
  • I hooked up my audio cable (two-pin 2.5/3.5mm jack) from my Anytone to my laptop (with APRSISCE32 and UZ7HO installed) and it receives and decodes normally.
  • I added splitter to end of that cable and plugged one jack into USB sound card mic side; everything worked normally.
  • I booted up Direwolf.? Had both ends of splitter into USB sound card.? Same as before--show up on aprs.fi but not receiving packages.? USB sound card is blinking away as it does when receiving packets on laptop.

Let me know if I left off a test that might help diagnose.? I haven't had a chance to look up threads here on AT/Wouxun issues, but is it time for me to head down the Alsamixer path?? Is there any chance a line of code is wrong?


Re: RPi Direwolf packet station.

Mike Berg
 

Thanks again, John.?
I was experimenting today and was tickled to see your suggestion actually works well!

I have Direwolf running on a Pi 3b who's connected via a Signalink USB to a Yaesu FTM-6000 back in my shack.
I have easyterm49 running here on my Win7 machine. Under the TNC setup menu I entered the IP address of the Pi 3 in the HOST window.
Viola!? All over WiFi.
Connects and acts just like a TNC. One question, I notice easyterm uses 80 byte packet length by default. I think we usually default to 128 in the TNCs.?
Any reason I shouldn't change it in easyterm?

73
Mike N0QBH


Re: Digipeater build.... not hearing packets

 

Run alsamixer in a terminal, hit F6 key, move down to the soundcard you want, hit Enter.? Hit F5 key to show all settings.? The "Speaker" slider is obvious, audio-out.? Use up/down arrows keys to increase/decrease.? The next slider, "Mic", should be muted or at zero; it's for playback thru speakers what it hears on the mic-in, so that's no good for digital modes.? The next slider, "Capture, Mic", is audio-in from the radio, make sure it isn't muted and has some level indicated.? The last slider,"Auto Gain Control" should be muted.? Muting is toggled on/ff using the "M" key.? If a slider is muted, you'll see two "MM"s.? When finished, hit Escape to exit alsamixer.? The settings are saved automatically if you're using a Raspberry.? In other Linux flavors, run "sudo alsactl store" in a terminal to save the alsamixer settings.


Re: Digipeater build.... not hearing packets

 

Yep, check Alsmixer settings.? Maybe the capture input is actually muted.


Re: Digipeater build.... not hearing packets

 

¿ªÔÆÌåÓý


Yes.. I'm pretty sure you have incorrect mixer level settings.

--David
KI6ZHD


On 09/24/2023 11:28 AM, Jon W7SEA wrote:

Here's my to-date testing.? This will likely leave open some of Rob's points, but it's as far as I've gotten.

  • Headset (with 2.5mm and 3.5mm jacks) plugged directly into radio; hear packets.
  • I hooked up my audio cable (two-pin 2.5/3.5mm jack) from my Anytone to my laptop (with APRSISCE32 and UZ7HO installed) and it receives and decodes normally.
  • I added splitter to end of that cable and plugged one jack into USB sound card mic side; everything worked normally.
  • I booted up Direwolf.? Had both ends of splitter into USB sound card.? Same as before--show up on aprs.fi but not receiving packages.? USB sound card is blinking away as it does when receiving packets on laptop.

Let me know if I left off a test that might help diagnose.? I haven't had a chance to look up threads here on AT/Wouxun issues, but is it time for me to head down the Alsamixer path?? Is there any chance a line of code is wrong?


Re: Digipeater build.... not hearing packets

 

Here's my to-date testing.? This will likely leave open some of Rob's points, but it's as far as I've gotten.

  • Headset (with 2.5mm and 3.5mm jacks) plugged directly into radio; hear packets.
  • I hooked up my audio cable (two-pin 2.5/3.5mm jack) from my Anytone to my laptop (with APRSISCE32 and UZ7HO installed) and it receives and decodes normally.
  • I added splitter to end of that cable and plugged one jack into USB sound card mic side; everything worked normally.
  • I booted up Direwolf.? Had both ends of splitter into USB sound card.? Same as before--show up on aprs.fi but not receiving packages.? USB sound card is blinking away as it does when receiving packets on laptop.

Let me know if I left off a test that might help diagnose.? I haven't had a chance to look up threads here on AT/Wouxun issues, but is it time for me to head down the Alsamixer path?? Is there any chance a line of code is wrong?


Re: Digipeater build.... not hearing packets

 

Sorry if this was already mentioned. But ensure that "Auto Gain Control" is disabled on your device through the alsamixer tool.?

Open alsamixer
Press F6 to select your sound device
Press F5 to show all devices
Select "Auto Gain Control" and press m so that the Item entry on the top left shows [Off] next to Auto Gain Control.
You may need to turn the mic gain up or down after that.

Hope that helps,
73, Brent WG0A


Re: ADEVICE with USB on Raspberry Pi

 

Thanks, John. You're right. That's a much easier solution. Worked like a charm.

? ?...doug


Re: ADEVICE with USB on Raspberry Pi

 

On Sat, Sep 23, 2023 at 12:02 AM, Doug Kaye (K6DRK) wrote:
I guess I didn't explain the problem. Each time the Pi 4 boots, the USB audio device randomly comes up as card 0, 1, 2 or 3. I need a way to link ADEVICE to the vendor id, product id, or something similar.
There is an easy solution.

pages 35 and 36.

73,
John Wb2OSZ


Re: ADEVICE with USB on Raspberry Pi

 

¿ªÔÆÌåÓý

Win some, lose some!

The advice to remove PulseAudio has been superseded and not considered necessary anymore, but not having it certainly rules out Pulse grabbing anything!!

Ray vk2tv

On 23/9/23 14:39, Doug Kaye (K6DRK) wrote:

Thanks, Ray.

That's not it, since I removed pulseaudio per the Raspberry-Pi-APRS.pdf guide.

? ?...doug (K6DRK)


Re: ADEVICE with USB on Raspberry Pi

 

Thanks, Ray.

That's not it, since I removed pulseaudio per the Raspberry-Pi-APRS.pdf guide.

? ?...doug (K6DRK)


Re: ADEVICE with USB on Raspberry Pi

 

¿ªÔÆÌåÓý

Could it be that PulseAudio is grabbing the audio device in a random manner. It happened here so I blocked the affected devices from PulseAudio with a udev entry.

Create
/etc/udev/rules.d/89-pulseaudio.rules

use my content below as the starting point, suitably modified to fit your environment ...

Sample content ......

/etc/udev/rules.d/89-pulseaudio.rules
#Ignore SB Play in pulse audio. Required by Direwolf
ATTRS{idVendor}=="041e", ATTRS{idProduct}=="30d3", ENV{PULSE_IGNORE}="1"

#Ignore CM108 in pulse audio. Required by Direwolf
ATTRS{idVendor}=="0d8c", ATTRS{idProduct}=="013c", ENV{PULSE_IGNORE}="1"

Reboot or restart PulseAudio to activate.

Ray vk2tv

On 23/9/23 14:02, Doug Kaye (K6DRK) wrote:

Thanks, Rob.

I guess I didn't explain the problem. Each time the Pi 4 boots, the USB audio device randomly comes up as card 0, 1, 2 or 3. I need a way to link ADEVICE to the vendor id, product id, or something similar.

? ?...doug (K6DRK)


Re: Digipeater build.... not hearing packets

 

I had to tear down my makeshift test site, but I'll try and get the answer this weekend.? Thanks Jon


Re: ADEVICE with USB on Raspberry Pi

 

Thanks, Rob.

I guess I didn't explain the problem. Each time the Pi 4 boots, the USB audio device randomly comes up as card 0, 1, 2 or 3. I need a way to link ADEVICE to the vendor id, product id, or something similar.

? ?...doug (K6DRK)


Re: ADEVICE with USB on Raspberry Pi

 

since aplay -l and arecord -l show your USB sound card as "card 3:" I would just go with
???? ADEVICE plughw:3,0

If youy are plugging and unplugging USB sound devices, then I would worry about the other stuff.

Robert Giuliano
KB8RCO



On Friday, September 22, 2023 at 11:12:08 PM EDT, Doug Kaye (K6DRK) <doug@...> wrote:


I'm going crazy trying to figure out how to map a USB audio device properly to the ADEVICE config setting. I'm on a Raspberry Pi 4 running Direwolf 1.7. The (inexpensive) USB adaptor appears as follows, although the card $ changes randomly:

#aplay -l? [same for arecord -l]
card 3: Device [USB Audio Device], device 0: USB Audio [USB Audio]
? Subdevices: 1/1
? Subdevice #0: subdevice #0
#lsusb?
? Bus 001 Device 003: ID 0d8c:0014 C-Media Electronics, Inc. Audio Adapter (Unitek Y-247A)

I've tried this in?/etc/udev/rules.d/70-alsa-permanent.rules:
? ?SUBSYSTEM!="sound", GOTO="my_usb_audio_end"
? ?ACTION!="add", GOTO="my_usb_audio_end"
? ?ATTRS{idVendor}=="0x0d8c", ATTRS{idProduct}=="0x0014", ATTR{id}="MIC"
? ?ATTRS{idVendor}=="0x0d8c", ATTRS{idProduct}=="0x0014", ATTR{id}="SPEAKER"
? ?LABEL="my_usb_audio_end"

and in ~/.asoundrc:
pcm.!default {
type hw
card "MIC"
? ? device 0
}
ctl.!default {
type hw
card "MIC"
? ? device 0
}
...and so on...

I thought something like these might work, but no:
? ? ?ADEVICE "MIC:0","MIC:0"
or? ADEVICE "USB Audio Device"
etc.

I studied??but it's not at all clear how to use this in direwolf.conf.

Suggestions? (and thanks)





ADEVICE with USB on Raspberry Pi

 

I'm going crazy trying to figure out how to map a USB audio device properly to the ADEVICE config setting. I'm on a Raspberry Pi 4 running Direwolf 1.7. The (inexpensive) USB adaptor appears as follows, although the card $ changes randomly:

#aplay -l? [same for arecord -l]
card 3: Device [USB Audio Device], device 0: USB Audio [USB Audio]
? Subdevices: 1/1
? Subdevice #0: subdevice #0
#lsusb?
? Bus 001 Device 003: ID 0d8c:0014 C-Media Electronics, Inc. Audio Adapter (Unitek Y-247A)

I've tried this in?/etc/udev/rules.d/70-alsa-permanent.rules:
? ?SUBSYSTEM!="sound", GOTO="my_usb_audio_end"
? ?ACTION!="add", GOTO="my_usb_audio_end"
? ?ATTRS{idVendor}=="0x0d8c", ATTRS{idProduct}=="0x0014", ATTR{id}="MIC"
? ?ATTRS{idVendor}=="0x0d8c", ATTRS{idProduct}=="0x0014", ATTR{id}="SPEAKER"
? ?LABEL="my_usb_audio_end"

and in ~/.asoundrc:
pcm.!default {
type hw
card "MIC"
? ? device 0
}
ctl.!default {
type hw
card "MIC"
? ? device 0
}
...and so on...

I thought something like these might work, but no:
? ? ?ADEVICE "MIC:0","MIC:0"
or? ADEVICE "USB Audio Device"
etc.

I studied??but it's not at all clear how to use this in direwolf.conf.

Suggestions? (and thanks)





Re: Digipeater build.... not hearing packets

 

That isn't the question.? You don't use the HT speaker, so you need to know audio is coming through the cables you are adding.
There are many times these special cables don't make good contact or make "double contact" and cause the audio to not actually go through.

The pictures in the article you mention shows:
?? a) radio
?? b) cable that connects to the radio
?? c) Y-cable from that cable to the sound card mic input (radio speaker output) and headphone (radio mic)
?? d) USB sound card
So, troubleshooting RX would mean you have to follow the audio from radio to USB sound card.
??? Do you have a way of connecting headphones or speakers to the radio and cable that directly connects to the radio. Audio chain a) and b).
??????? This is typically a TRRS type connection, unless you cable has 2 ports (mic and speaker)
??? If there is audio there, including static, add the next cable [ audio chain a), b), and c) ]
??????? Is there audio on the cable that goes to the USB sound card Mic input.
?? If there is and you have those connections correct (as mentioned above), then
??????? the most likely issue for receive would be the Mic settings - use alsamixer to adjust the settings there.
???
-------
Robert Giuliano
KB8RCO