I recently purchased a digirig lite, from Amazon, and have been having issues with RX. It will TX but for whatever reason it will not hear any packets coming in. I am hoping I am just missing something silly and that the unit is not faulty.
I first experienced the issue trying to send APRS messages between 2 devices:
Station 1: APRS Droid > Pixel 7 Pro > digirig lite > FT3DR
Station 2: APRS Droid > Samsung Galaxy Tab Active5 > digirig mobile > BaoFeng UV5R
I could RX packets on the Active5, but not on the Pixel. I searched and saw some reports of Pixel users having audio issues. I tried a few different options without resolve and ended up purchasing a BTech UV-Pro. Now I have a known working station.
I tested between the UV-Pro and digirig mobile, this works flawlessly, you can see the configs and the RX packet in direwolf below.
I also tested the same radio, same direwolf config, same UV-Pro, but with the digirig lite and no packet RX.
I love digirig products and the only reason that I purchased the UV-Pro was to have a known working station to troubleshoot this issue with the digirig lie. It has some quirks that I still dont like but I will probably keep it as it seems to be pretty much plug and play for my applications.
I am approaching returning the digirig lite, but I would like to understand am I doing something wrong here or is this unit faulty? Any suggestions/help would be greatly appreciated!
$ lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 0d8c:0012 C-Media Electronics, Inc. USB Audio Device
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 007: ID 10c4:ea60 Silicon Labs CP210x UART Bridge
Bus 001 Device 006: ID 0d8c:013c C-Media Electronics, Inc. CM108 Audio Controller
Bus 001 Device 005: ID 0424:2412 Microchip Technology, Inc. (formerly SMSC) Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
$ cat /etc/udev/rules.d/99-direwolf-cmedia.rules | grep -iv “#”
SUBSYSTEM==“hidraw”, ATTRS{idVendor}==“0d8c”, GROUP=“audio”, MODE=“0660”
SUBSYSTEM==“hidraw”, ATTRS{idVendor}==“1209”, ATTRS{idProduct}==“7388”, GROUP=“audio”, MODE=“0660”
$ cat /etc/udev/rules.d/99-graywolf-cm108.rules | grep -iv “#”
SUBSYSTEM==“hidraw”, ATTRS{idVendor}==“0d8c”, MODE=“0660”, GROUP=“plugdev”
SUBSYSTEM==“hidraw”, ATTRS{idVendor}==“1209”, ATTRS{idProduct}==“7388”, MODE=“0660”, GROUP=“plugdev”
SUBSYSTEM==“hidraw”, ATTRS{idVendor}==“0c76”, MODE=“0660”, GROUP=“plugdev”
$ arecord -l
**** List of CAPTURE Hardware Devices ****
card 2: Device_1 [USB PnP Sound Device], device 0: USB Audio [USB Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 3: Device [USB Audio Device], device 0: USB Audio [USB Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0
$ cat test_slim.conf && direwolf -c test_slim.conf
ADEVICE plughw:3,0
ADEVICE1 plughw:2,0
CHANNEL 0
MYCALL KO4PWQ
MODEM 1200
Dire Wolf version 1.7Includes optional support for: gpsd hamlib cm108-ptt dns-sd
Reading config file test_slim.confAudio device for both receive and transmit: plughw:3,0 (channel 0)Audio device for both receive and transmit: plughw:2,0 (channel 2)Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, A+, 44100 sample rate.Channel 2: 1200 baud, AFSK 1200 & 2200 Hz, A+, 44100 sample rate.Note: PTT not configured for channel 0. (Ignore this if using VOX.)Note: PTT not configured for channel 2. (Ignore this if using VOX.)Ready to accept AGW client application 0 on port 8000 …Ready to accept KISS TCP client application 0 on port 8001 …DNS-SD: Avahi: Announcing KISS TCP on port 8001 as ‘Dire Wolf on hampi-5’DNS-SD: Avahi: Service ‘Dire Wolf on hampi-5’ successfully registered.
KO4PWQ-5 audio level = 196(72/69) |||||__Audio input level is too high. Reduce so most stations are around 50.[2.3] KO4PWQ-5>APDR17,WIDE1-1,WIDE2-1::ALL :Testing RX via digirig mobile {1APRS Message, number “1”, from “KO4PWQ-5” to “ALL”, APRSdroid Android App http://aprsdroid.org/Testing RX via digirig mobile<0x20>