Hi Steven,
The lite does work. You have to get and build Martin’s version because it hasn’t been merged into the main branch yet.?
One word of caution. I spent much of today trying to troubleshoot a failure with it and found that it’s very susceptible to rfi so you will likely either need to put ferries on the usb cable or put an external antenna on the radio.?
73 de K6EF
toggle quoted message
Show quoted text
On Apr 17, 2025, at 3:51?PM, Steven via groups.io <stevene1@...> wrote:
? There are two versions, now, of the Digirig sound card...one called "mobile" and the other captioned as "Lite".? I learned, here, that the "mobile" version (mine) doesn't support COM108 PTT.
?
In digging around, I was able to identify two separate serial numbers on these devices:
?
5e375fc11987ed118f4329d7a603910e
f0a610ace98bee1189aefe018acbdcd8
?
however, I don't fully understand how to rename them with that information.? Currently they're named ttyUSB0 and ttyUSB1 under /dev.??
|
There are two versions, now, of the Digirig sound card...one called "mobile" and the other captioned as "Lite".? I learned, here, that the "mobile" version (mine) doesn't support COM108 PTT.
?
In digging around, I was able to identify two separate serial numbers on these devices:
?
5e375fc11987ed118f4329d7a603910e
f0a610ace98bee1189aefe018acbdcd8
?
however, I don't fully understand how to rename them with that information.? Currently they're named ttyUSB0 and ttyUSB1 under /dev.??
|
Hi Martin,?
Apologies for getting this muddled up!
My experience so far (which might apply to Tim)
1. The Digirig (standard) works perfectly fine with Direwolf and does not need CM108 support. It works by both setting the Audio Device and the PTT to the serial device with RTS..?
2. The Digirig Lite using the CM108 does not work with PTT CM108. The error is a “failure to write to the device” (Could not open DevSrvsID:4294980973 for write)
3. The AIOC (URC Universal Radio Controller) works without erroring other than a message stating “Transmit timing error: PTT is on 1288 mSec too long”
If you like, please send me an email directly and we can separate these discussions, am very sorry for muddling things up.
73 de K6EF
toggle quoted message
Show quoted text
On Apr 17, 2025, at 1:00?PM, Martin Cooper via groups.io <mfncooper@...> wrote:
Hi Tim,
We have two intertwined conversations going on here, with both you and Mark looking to get up and running on Mac. My "Hmm" reply was in response to Mark's message.
As I understand it from other discussions on this list related to Digirig (I don't have one), there are two flavours, one of which uses a CM108 device, the other of which does not. Given the PTT line you cited that is working for you, I have to assume you have the Digirig?that does *not* have the CM108 in it.
I'm not clear as to whether you have a second device with a CM108 that you want to get working as well. If you do, you'll first need to rebuild Direwolf so that you have CM108 support, since your current Direwolf build does not?have that. (On startup, it says "Includes optional support for:??gpsd hamlib", where you want to see "cm108" included in that line.) To build it, see the discussion with Mark here. Once you have that, use the 'cm108' command line tool to see what you need to specify in your direwolf.conf.
Incidentally, from your earlier quote from Direwolf startup, it looks like you have some bad lines in your config file. (I'm looking at the 2 lines with "Unrecognized command" in them.) You'll want to clean those up.
Hope that helps.
Martin. KD6YAM On Thu, Apr 17, 2025 at 12:34?PM Tim Huffaker via ??<thuffaker= [email protected]> wrote: Martin, ? I wish I knew, but Direwolf is feeding YAAC with an AGWPE port, and that is working with PTT /dev/ttyusbaudo-221220 RTS.? The PPT makes sense since it points to the serial port.? I am sure CM08 does the same, but I do not know how. ? ? I am not sure how Direwolf finds audio devices on a Mac because my experience on Linux is long, and I know how it works.? I have three devices with a Raspberry Pi running.? One is permanent, and two are for a bike event we support. ? ? I do not know how the audio ports work on the Mac, so I have no idea. ? Tim? ? ?
|
Hi Tim,
We have two intertwined conversations going on here, with both you and Mark looking to get up and running on Mac. My "Hmm" reply was in response to Mark's message.
As I understand it from other discussions on this list related to Digirig (I don't have one), there are two flavours, one of which uses a CM108 device, the other of which does not. Given the PTT line you cited that is working for you, I have to assume you have the Digirig?that does *not* have the CM108 in it.
I'm not clear as to whether you have a second device with a CM108 that you want to get working as well. If you do, you'll first need to rebuild Direwolf so that you have CM108 support, since your current Direwolf build does not?have that. (On startup, it says "Includes optional support for:??gpsd hamlib", where you want to see "cm108" included in that line.) To build it, see the discussion with Mark here. Once you have that, use the 'cm108' command line tool to see what you need to specify in your direwolf.conf.
Incidentally, from your earlier quote from Direwolf startup, it looks like you have some bad lines in your config file. (I'm looking at the 2 lines with "Unrecognized command" in them.) You'll want to clean those up.
Hope that helps.
Martin. KD6YAM
On Thu, Apr 17, 2025 at 12:34?PM Tim Huffaker via <thuffaker= [email protected]> wrote: Martin,
?
I wish I knew, but Direwolf is feeding YAAC with an AGWPE port, and that is working with PTT /dev/ttyusbaudo-221220 RTS.? The PPT makes sense since it points to the serial port.? I am sure CM08 does the same, but I do not know how. ?
?
I am not sure how Direwolf finds audio devices on a Mac because my experience on Linux is long, and I know how it works.? I have three devices with a Raspberry Pi running.? One is permanent, and two are for a bike event we support. ?
?
I do not know how the audio ports work on the Mac, so I have no idea.
?
Tim
?
?
|
Martin,
?
I wish I knew, but Direwolf is feeding YAAC with an AGWPE port, and that is working with PTT /dev/ttyusbaudo-221220 RTS. ?The PPT makes sense since it points to the serial port. ?I am sure CM08 does the same, but I do not know how. ?
?
I am not sure how Direwolf finds audio devices on a Mac because my experience on Linux is long, and I know how it works. ?I have three devices with a Raspberry Pi running. ?One is permanent, and two are for a bike event we support. ?
?
I do not know how the audio ports work on the Mac, so I have no idea.
?
Tim
?
?
|
Hmm, I don't recall having to make any permission changes. The first time I plugged in one of my devices, macOS did ask for permission,?via the usual popup, but appears to have remembered that and no longer asks. I'm running on Sequoia (and originally tested on Ventura and High Sierra), and running the cm108 command gives me the following relevant lines:
? ? VID ?PID ? Product ? ? ? ? ? ? ? ? ? ? ? ? ?HID [ptt]
? ? --- ?--- ? ------- ? ? ? ? ? ? ? ? ? ? ? ? ?---------
** ?0d8c 0012 ?USB Audio Device ? ? ? ? ? ? ? ? DevSrvsID:4315917197
** ?0d8c 000c ?C-Media USB Headphone Set ? ? ? ?DevSrvsID:4315917396
The first is my Dinah and the second is my homebrew CM108 device.
In my direwolf.conf, I just have (relevant lines only):
ADEVICE "USB Audio Device" PTT CM108
That all works. I wonder what's different about your device and / or Mac. Odd.
Martin. KD6YAM
Hi Martin,?
Well, made some progress but the OS doesn’t seem to want me to access the device. (Seems like a typical group permission to a device error, I just don’t know *yet* how to resolve it..)
Ready to accept KISS TCP client application 1 on port 8001 ... [0L] K6EF-4>APFII0,WIDE1-1,WIDE2-1:@174818h3733.39N/12216.72W$ for iOS!wSc! Transmit timing error: PTT is on 328 mSec too long. Could not open DevSrvsID:4295872346 for write ERROR: ?PTT for channel 0 has failed.? See User Guide for troubleshooting tips.
-Mark
Hi Martin,?
Actually, it seems that there was an issue with the make install.. It wasn’t actually copying over the re-built direwolf binary. (No errors produced.)?
I ran from the src directory ./direwolf -c ~/direwolf.conf and finally saw the cm108-ptt in the support line. It seems to start now and I’ll do a quick APRS / Winlink test with this setup.?
Thanks again for all of your work on this. I really wish the changes were merged.. We need better non linux / non windows support in Direwolf (and better documentation!)?
Mark
Hi Mark,
Sorry, I should have mentioned before - while the changes are still in my fork, you'll need to build from the 'dev' branch and not 'master' to get the Mac CM108 changes. I'm guessing that the problem you're seeing is because you built?from 'master', which doesn't include the necessary changes.
Martin. Hi Martin!?
Great to see you here.
I just built from your branch and all seems to have built, but I get an error when trying to use a CM108 device..?
Reading config file direwolf.conf Config file line 196: PTT with CM108 is only available when USB Audio GPIO support is enabled. You must rebuild direwolf with CM108 Audio Adapter GPIO PTT support. See Interface Guide for details. See online documentation: ? ??stable release: ? ? ? ??development version: ? ? ? ??additional topics: ? ?
I looked over the doc but it seems to lack information on building with GPIO on any platforms other than Linux. Am I missing something?
73 de K6EF
One clarification to Mark's comments: If you build from my fork or apply my PR, you do get the cm108 tool as well. As with Windows and Linux, running the tool will show you which devices are available to use for 'PTT CM108'.
The changes in the PR were "approved" by John, WB2OSZ, in July 2024, but have never been applied to the main Direwolf repo. I don't know why that is, but you can still run from what I have. I do, and run with both a Dinah and a homebrew CM108 solution.
Martin. KD6YAM As an aside, I re-pulled the source and built direwolf..?
Some thoughts :?
1. The MacOSX instructions are lacking. Ports is far out of support and Homebrew is the replacement.? 2. The Additions that Martin added need to be documented better, specifically around?brew install hidapi.? 3. The CM108 tools are not there in OSX, so there is no documented method of seeing the sound card and building Direwolf with PTT support with GPIO.. The end user gets an error when trying to enable PTT CM108.
As for the sound device, upon starting Direwolf on a Mac, you are given the available sound devices. In the case of Digirig (standard), you get?"USB PnP Sound Device” .. So ADEVICE?"USB PnP Sound Device”?"USB PnP Sound Device” works (on my system) Then you need to determine the serial device. For me, I ls -lart /dev/ and see the last cu and tty devices. In the case of my Digirig, it’s?/dev/tty.usbserial-13120 so the line to enable PTT is :?PTT /dev/tty.usbserial-13120 RTS
I was able to successfully test APRS and Packet (Winlink) with this setup. Direwolf presents AGW and KISS ports and apps on my phone like??and RadioMail both see the dns-sd share of the TNC.? The caveat on Mac is that you will need to adjust the volume for the input/output device in the Sound settings AND the radio’s volume knob to alleviate the errors/warnings about volume.
What I would like to see is better support for the CM108 device in OSX, this means a working cm108 tool to determine the device and capabilities as well as better documentation in Direwolf for enabling this device. It USED to work and in the past I was able to get the AIOC and Digirig Lite to work, but these days these devices are not working on my updated M4 Mac (ARM processor)
Hope this helps and I’m absolutely open to help if I missed something around building Direwolf for CM108/Digirig Lite etc..
73 de K6EF
?Hi Tim,?
Arecord is part of the Alsa toolset and not present on the Mac.?
Try using ADEVICE?"USB Audio Device”?"USB Audio Device”
For the Digirig, (depending on which one you have) it could be PTT CM108 but I’ve not played with Direwolf on the Mac in a while, I’ve been using it on Linux hosts mostly. I’ll check and see, since I have both the Digirig and the Digirig Lite
Mark K6EF
Hello, ? I am trying to find the audio codec for Direwolf with a Digirig on my Mac.? I do not know a command like ?arecord -l to get the sound cards for ADEVICE? "USB Audio Codec:6"? "USB Audio Codec:5".?I believe the PPT is /dev/tty.usbmodem223101 RTS?cards I know this is different from Linux. ? Tim KM4ESU ?
|
I found the problem, and now I am seeing APRS on YAAC with direwolf audio working. ?Warning to Mac users with Parallels or similar, Windows can grab your USB ports without you knowing. ?I use this radio for VARAFM email, and Windows grabbed the PnP audio. ?
?
Now to fix the PTT.
?
Thank you for all the help in getting Direwolf working on a Mac. ?Please publish this for others like me to find. ?
?
Tim?
|
I ran the command direwolf -x a? ?This is what I got. Looks like I cannot use USB PnP Sound Device for the audio. ?I will try using the "USB AUDIO CODEC"
?
Tim ?
?
Dire Wolf version 1.6
Includes optional support for:? gpsd hamlib
?
Reading config file direwolf.conf
Config file: Unrecognized command '0\xb8\xb1\xe0\xb8\x84\xe0\xb8\xa3\xe0\xb9\x80\xe0\xb8\xa5\xe0\xb9\x88\xe0\xb8\x99' on line 294.
Config file: Unrecognized command '4\xce\xb5\xcf\x87\xce\xbd\xce\xb9\xcf\x83\xce\xbc\xcf\x8c\xcf\x82' on line 296.
Audio input device for receive: a? (channels 0 & 1)
Audio out device for transmit: USB PnP Sound Device? (channels 0 & 1)
Number of devices = 12
--------------------------------------- device #0
Name? ? ? ? = "LG ULTRAWIDE"
Host API? ? = Core Audio
Max inputs? = 0
Max outputs = 2
--------------------------------------- device #1
Name? ? ? ? = "LG ULTRAWIDE"
Host API? ? = Core Audio
Max inputs? = 0
Max outputs = 2
--------------------------------------- device #2
Name? ? ? ? = "iPhone (14) Microphone"
Host API? ? = Core Audio
Max inputs? = 1
Max outputs = 0
--------------------------------------- device #3
Name? ? ? ? = "USB AUDIO? CODEC"
Host API? ? = Core Audio
Max inputs? = 0
Max outputs = 2
--------------------------------------- device #4
Name? ? ? ? = "USB AUDIO? CODEC"
Host API? ? = Core Audio
Max inputs? = 2
Max outputs = 0
--------------------------------------- device #5
Name? ? ? ? = "USB 3.0 Dual 4K Displayport adapter"
Host API? ? = Core Audio
Max inputs? = 0
Max outputs = 0
--------------------------------------- device #6
Name? ? ? ? = "USB Digital Audio"
Host API? ? = Core Audio
Max inputs? = 1
Max outputs = 0
--------------------------------------- device #7
[ Default Output ]
Name? ? ? ? = "Mac mini Speakers"
Host API? ? = Core Audio
Max inputs? = 0
Max outputs = 2
--------------------------------------- device #8
Name? ? ? ? = "Microsoft Teams Audio"
Host API? ? = Core Audio
Max inputs? = 2
Max outputs = 2
--------------------------------------- device #9
Name? ? ? ? = "VB-Cable"
Host API? ? = Core Audio
Max inputs? = 2
Max outputs = 2
--------------------------------------- device #10
[ Default Input ]
Name? ? ? ? = "K4 USB Audo Input"
Host API? ? = Core Audio
Max inputs? = 2
Max outputs = 0
--------------------------------------- device #11
Name? ? ? ? = "K4 USB Audo Output"
Host API? ? = Core Audio
Max inputs? = 0
Max outputs = 2
Requested Input Audio Device not found a.
Pointless to continue without audio device.
timhuffaker@Mac-mini direwolf %?
|
Hi Martin,?
Well, made some progress but the OS doesn’t seem to want me to access the device. (Seems like a typical group permission to a device error, I just don’t know *yet* how to resolve it..)
Ready to accept KISS TCP client application 1 on port 8001 ... [0L] K6EF-4>APFII0,WIDE1-1,WIDE2-1:@174818h3733.39N/12216.72W$aprs.fi for iOS!wSc! Transmit timing error: PTT is on 328 mSec too long. Could not open DevSrvsID:4295872346 for write ERROR: ?PTT for channel 0 has failed. ?See User Guide for troubleshooting tips.
-Mark
toggle quoted message
Show quoted text
On Apr 17, 2025, at 10:36?AM, Mark C via groups.io <k6ef@...> wrote:
Hi Martin,?
Actually, it seems that there was an issue with the make install.. It wasn’t actually copying over the re-built direwolf binary. (No errors produced.)?
I ran from the src directory ./direwolf -c ~/direwolf.conf and finally saw the cm108-ptt in the support line. It seems to start now and I’ll do a quick APRS / Winlink test with this setup.?
Thanks again for all of your work on this. I really wish the changes were merged.. We need better non linux / non windows support in Direwolf (and better documentation!)?
Mark On Apr 17, 2025, at 10:21?AM, Martin Cooper via groups.io <mfncooper@...> wrote:
Hi Mark,
Sorry, I should have mentioned before - while the changes are still in my fork, you'll need to build from the 'dev' branch and not 'master' to get the Mac CM108 changes. I'm guessing that the problem you're seeing is because you built?from 'master', which doesn't include the necessary changes.
Martin. Hi Martin!?
Great to see you here.
I just built from your branch and all seems to have built, but I get an error when trying to use a CM108 device..?
Reading config file direwolf.conf Config file line 196: PTT with CM108 is only available when USB Audio GPIO support is enabled. You must rebuild direwolf with CM108 Audio Adapter GPIO PTT support. See Interface Guide for details. See online documentation: ? ??stable release: ? ? ? ??development version: ? ? ? ??additional topics: ? ?
I looked over the doc but it seems to lack information on building with GPIO on any platforms other than Linux. Am I missing something?
73 de K6EF
One clarification to Mark's comments: If you build from my fork or apply my PR, you do get the cm108 tool as well. As with Windows and Linux, running the tool will show you which devices are available to use for 'PTT CM108'.
The changes in the PR were "approved" by John, WB2OSZ, in July 2024, but have never been applied to the main Direwolf repo. I don't know why that is, but you can still run from what I have. I do, and run with both a Dinah and a homebrew CM108 solution.
Martin. KD6YAM As an aside, I re-pulled the source and built direwolf..?
Some thoughts :?
1. The MacOSX instructions are lacking. Ports is far out of support and Homebrew is the replacement.? 2. The Additions that Martin added need to be documented better, specifically around?brew install hidapi.? 3. The CM108 tools are not there in OSX, so there is no documented method of seeing the sound card and building Direwolf with PTT support with GPIO.. The end user gets an error when trying to enable PTT CM108.
As for the sound device, upon starting Direwolf on a Mac, you are given the available sound devices. In the case of Digirig (standard), you get?"USB PnP Sound Device” .. So ADEVICE?"USB PnP Sound Device”?"USB PnP Sound Device” works (on my system) Then you need to determine the serial device. For me, I ls -lart /dev/ and see the last cu and tty devices. In the case of my Digirig, it’s?/dev/tty.usbserial-13120 so the line to enable PTT is :?PTT /dev/tty.usbserial-13120 RTS
I was able to successfully test APRS and Packet (Winlink) with this setup. Direwolf presents AGW and KISS ports and apps on my phone like??and RadioMail both see the dns-sd share of the TNC.? The caveat on Mac is that you will need to adjust the volume for the input/output device in the Sound settings AND the radio’s volume knob to alleviate the errors/warnings about volume.
What I would like to see is better support for the CM108 device in OSX, this means a working cm108 tool to determine the device and capabilities as well as better documentation in Direwolf for enabling this device. It USED to work and in the past I was able to get the AIOC and Digirig Lite to work, but these days these devices are not working on my updated M4 Mac (ARM processor)
Hope this helps and I’m absolutely open to help if I missed something around building Direwolf for CM108/Digirig Lite etc..
73 de K6EF
?Hi Tim,?
Arecord is part of the Alsa toolset and not present on the Mac.?
Try using ADEVICE?"USB Audio Device”?"USB Audio Device”
For the Digirig, (depending on which one you have) it could be PTT CM108 but I’ve not played with Direwolf on the Mac in a while, I’ve been using it on Linux hosts mostly. I’ll check and see, since I have both the Digirig and the Digirig Lite
Mark K6EF
Hello, ? I am trying to find the audio codec for Direwolf with a Digirig on my Mac.? I do not know a command like ?arecord -l to get the sound cards for ADEVICE? "USB Audio Codec:6"? "USB Audio Codec:5".?I believe the PPT is /dev/tty.usbmodem223101 RTS?cards I know this is different from Linux. ? Tim KM4ESU ?
|
Hi Martin,?
Actually, it seems that there was an issue with the make install.. It wasn’t actually copying over the re-built direwolf binary. (No errors produced.)?
I ran from the src directory ./direwolf -c ~/direwolf.conf and finally saw the cm108-ptt in the support line. It seems to start now and I’ll do a quick APRS / Winlink test with this setup.?
Thanks again for all of your work on this. I really wish the changes were merged.. We need better non linux / non windows support in Direwolf (and better documentation!)?
toggle quoted message
Show quoted text
On Apr 17, 2025, at 10:21?AM, Martin Cooper via groups.io <mfncooper@...> wrote:
Hi Mark,
Sorry, I should have mentioned before - while the changes are still in my fork, you'll need to build from the 'dev' branch and not 'master' to get the Mac CM108 changes. I'm guessing that the problem you're seeing is because you built?from 'master', which doesn't include the necessary changes.
Martin. Hi Martin!?
Great to see you here.
I just built from your branch and all seems to have built, but I get an error when trying to use a CM108 device..?
Reading config file direwolf.conf Config file line 196: PTT with CM108 is only available when USB Audio GPIO support is enabled. You must rebuild direwolf with CM108 Audio Adapter GPIO PTT support. See Interface Guide for details. See online documentation: ? ??stable release: ? ? ? ??development version: ? ? ? ??additional topics: ? ?
I looked over the doc but it seems to lack information on building with GPIO on any platforms other than Linux. Am I missing something?
73 de K6EF
One clarification to Mark's comments: If you build from my fork or apply my PR, you do get the cm108 tool as well. As with Windows and Linux, running the tool will show you which devices are available to use for 'PTT CM108'.
The changes in the PR were "approved" by John, WB2OSZ, in July 2024, but have never been applied to the main Direwolf repo. I don't know why that is, but you can still run from what I have. I do, and run with both a Dinah and a homebrew CM108 solution.
Martin. KD6YAM As an aside, I re-pulled the source and built direwolf..?
Some thoughts :?
1. The MacOSX instructions are lacking. Ports is far out of support and Homebrew is the replacement.? 2. The Additions that Martin added need to be documented better, specifically around?brew install hidapi.? 3. The CM108 tools are not there in OSX, so there is no documented method of seeing the sound card and building Direwolf with PTT support with GPIO.. The end user gets an error when trying to enable PTT CM108.
As for the sound device, upon starting Direwolf on a Mac, you are given the available sound devices. In the case of Digirig (standard), you get?"USB PnP Sound Device” .. So ADEVICE?"USB PnP Sound Device”?"USB PnP Sound Device” works (on my system) Then you need to determine the serial device. For me, I ls -lart /dev/ and see the last cu and tty devices. In the case of my Digirig, it’s?/dev/tty.usbserial-13120 so the line to enable PTT is :?PTT /dev/tty.usbserial-13120 RTS
I was able to successfully test APRS and Packet (Winlink) with this setup. Direwolf presents AGW and KISS ports and apps on my phone like??and RadioMail both see the dns-sd share of the TNC.? The caveat on Mac is that you will need to adjust the volume for the input/output device in the Sound settings AND the radio’s volume knob to alleviate the errors/warnings about volume.
What I would like to see is better support for the CM108 device in OSX, this means a working cm108 tool to determine the device and capabilities as well as better documentation in Direwolf for enabling this device. It USED to work and in the past I was able to get the AIOC and Digirig Lite to work, but these days these devices are not working on my updated M4 Mac (ARM processor)
Hope this helps and I’m absolutely open to help if I missed something around building Direwolf for CM108/Digirig Lite etc..
73 de K6EF
?Hi Tim,?
Arecord is part of the Alsa toolset and not present on the Mac.?
Try using ADEVICE?"USB Audio Device”?"USB Audio Device”
For the Digirig, (depending on which one you have) it could be PTT CM108 but I’ve not played with Direwolf on the Mac in a while, I’ve been using it on Linux hosts mostly. I’ll check and see, since I have both the Digirig and the Digirig Lite
Mark K6EF
Hello, ? I am trying to find the audio codec for Direwolf with a Digirig on my Mac.? I do not know a command like ?arecord -l to get the sound cards for ADEVICE? "USB Audio Codec:6"? "USB Audio Codec:5".?I believe the PPT is /dev/tty.usbmodem223101 RTS?cards I know this is different from Linux. ? Tim KM4ESU ?
|
Hi Mark,
Sorry, I should have mentioned before - while the changes are still in my fork, you'll need to build from the 'dev' branch and not 'master' to get the Mac CM108 changes. I'm guessing that the problem you're seeing is because you built?from 'master', which doesn't include the necessary changes.
Martin.
Hi Martin!?
Great to see you here.
I just built from your branch and all seems to have built, but I get an error when trying to use a CM108 device..?
Reading config file direwolf.conf Config file line 196: PTT with CM108 is only available when USB Audio GPIO support is enabled. You must rebuild direwolf with CM108 Audio Adapter GPIO PTT support. See Interface Guide for details. See online documentation: ? ? stable release: ? ? ? ? development version: ? ? ? ? additional topics: ? ?
I looked over the doc but it seems to lack information on building with GPIO on any platforms other than Linux. Am I missing something?
73 de K6EF
One clarification to Mark's comments: If you build from my fork or apply my PR, you do get the cm108 tool as well. As with Windows and Linux, running the tool will show you which devices are available to use for 'PTT CM108'.
The changes in the PR were "approved" by John, WB2OSZ, in July 2024, but have never been applied to the main Direwolf repo. I don't know why that is, but you can still run from what I have. I do, and run with both a Dinah and a homebrew CM108 solution.
Martin. KD6YAM As an aside, I re-pulled the source and built direwolf..?
Some thoughts :?
1. The MacOSX instructions are lacking. Ports is far out of support and Homebrew is the replacement.? 2. The Additions that Martin added need to be documented better, specifically around?brew install hidapi.? 3. The CM108 tools are not there in OSX, so there is no documented method of seeing the sound card and building Direwolf with PTT support with GPIO.. The end user gets an error when trying to enable PTT CM108.
As for the sound device, upon starting Direwolf on a Mac, you are given the available sound devices. In the case of Digirig (standard), you get?"USB PnP Sound Device” .. So ADEVICE?"USB PnP Sound Device”?"USB PnP Sound Device” works (on my system) Then you need to determine the serial device. For me, I ls -lart /dev/ and see the last cu and tty devices. In the case of my Digirig, it’s?/dev/tty.usbserial-13120 so the line to enable PTT is :?PTT /dev/tty.usbserial-13120 RTS
I was able to successfully test APRS and Packet (Winlink) with this setup. Direwolf presents AGW and KISS ports and apps on my phone like??and RadioMail both see the dns-sd share of the TNC.? The caveat on Mac is that you will need to adjust the volume for the input/output device in the Sound settings AND the radio’s volume knob to alleviate the errors/warnings about volume.
What I would like to see is better support for the CM108 device in OSX, this means a working cm108 tool to determine the device and capabilities as well as better documentation in Direwolf for enabling this device. It USED to work and in the past I was able to get the AIOC and Digirig Lite to work, but these days these devices are not working on my updated M4 Mac (ARM processor)
Hope this helps and I’m absolutely open to help if I missed something around building Direwolf for CM108/Digirig Lite etc..
73 de K6EF
?Hi Tim,?
Arecord is part of the Alsa toolset and not present on the Mac.?
Try using ADEVICE?"USB Audio Device”?"USB Audio Device”
For the Digirig, (depending on which one you have) it could be PTT CM108 but I’ve not played with Direwolf on the Mac in a while, I’ve been using it on Linux hosts mostly. I’ll check and see, since I have both the Digirig and the Digirig Lite
Mark K6EF
Hello, ? I am trying to find the audio codec for Direwolf with a Digirig on my Mac.? I do not know a command like ?arecord -l to get the sound cards for ADEVICE? "USB Audio Codec:6"? "USB Audio Codec:5".?I believe the PPT is /dev/tty.usbmodem223101 RTS?cards I know this is different from Linux. ? Tim KM4ESU ?
|
Hi Martin!?
Great to see you here.
I just built from your branch and all seems to have built, but I get an error when trying to use a CM108 device..?
Reading config file direwolf.conf Config file line 196: PTT with CM108 is only available when USB Audio GPIO support is enabled. You must rebuild direwolf with CM108 Audio Adapter GPIO PTT support. See Interface Guide for details. See online documentation: ? ? stable release: ? ?https://github.com/wb2osz/direwolf/tree/master/doc ? ? development version: ? ?https://github.com/wb2osz/direwolf/tree/dev/doc ? ? additional topics: ? ?
I looked over the doc but it seems to lack information on building with GPIO on any platforms other than Linux. Am I missing something?
73 de K6EF
toggle quoted message
Show quoted text
On Apr 16, 2025, at 4:52?PM, Martin Cooper via groups.io <mfncooper@...> wrote:
One clarification to Mark's comments: If you build from my fork or apply my PR, you do get the cm108 tool as well. As with Windows and Linux, running the tool will show you which devices are available to use for 'PTT CM108'.
The changes in the PR were "approved" by John, WB2OSZ, in July 2024, but have never been applied to the main Direwolf repo. I don't know why that is, but you can still run from what I have. I do, and run with both a Dinah and a homebrew CM108 solution.
Martin. KD6YAM As an aside, I re-pulled the source and built direwolf..?
Some thoughts :?
1. The MacOSX instructions are lacking. Ports is far out of support and Homebrew is the replacement.? 2. The Additions that Martin added need to be documented better, specifically around?brew install hidapi.? 3. The CM108 tools are not there in OSX, so there is no documented method of seeing the sound card and building Direwolf with PTT support with GPIO.. The end user gets an error when trying to enable PTT CM108.
As for the sound device, upon starting Direwolf on a Mac, you are given the available sound devices. In the case of Digirig (standard), you get?"USB PnP Sound Device” .. So ADEVICE?"USB PnP Sound Device”?"USB PnP Sound Device” works (on my system) Then you need to determine the serial device. For me, I ls -lart /dev/ and see the last cu and tty devices. In the case of my Digirig, it’s?/dev/tty.usbserial-13120 so the line to enable PTT is :?PTT /dev/tty.usbserial-13120 RTS
I was able to successfully test APRS and Packet (Winlink) with this setup. Direwolf presents AGW and KISS ports and apps on my phone like??and RadioMail both see the dns-sd share of the TNC.? The caveat on Mac is that you will need to adjust the volume for the input/output device in the Sound settings AND the radio’s volume knob to alleviate the errors/warnings about volume.
What I would like to see is better support for the CM108 device in OSX, this means a working cm108 tool to determine the device and capabilities as well as better documentation in Direwolf for enabling this device. It USED to work and in the past I was able to get the AIOC and Digirig Lite to work, but these days these devices are not working on my updated M4 Mac (ARM processor)
Hope this helps and I’m absolutely open to help if I missed something around building Direwolf for CM108/Digirig Lite etc..
73 de K6EF
?Hi Tim,?
Arecord is part of the Alsa toolset and not present on the Mac.?
Try using ADEVICE?"USB Audio Device”?"USB Audio Device”
For the Digirig, (depending on which one you have) it could be PTT CM108 but I’ve not played with Direwolf on the Mac in a while, I’ve been using it on Linux hosts mostly. I’ll check and see, since I have both the Digirig and the Digirig Lite
Mark K6EF
Hello, ? I am trying to find the audio codec for Direwolf with a Digirig on my Mac.? I do not know a command like ?arecord -l to get the sound cards for ADEVICE? "USB Audio Codec:6"? "USB Audio Codec:5".?I believe the PPT is /dev/tty.usbmodem223101 RTS?cards I know this is different from Linux. ? Tim KM4ESU ?
|
Hi Tim,
You'll see updated build instructions here, in case you haven't already seen them:
The final 'make install-conf' is only needed on your first Direwolf build / install. If you already have a direwolf.conf, you're all set, and don't need that. (It's there in the instructions because the instructions largely, and deliberately, parallel those for Linux.)
Martin. KD6YAM
On Thu, Apr 17, 2025 at 8:54?AM Tim Huffaker via <thuffaker= [email protected]> wrote: I learned my Silicon Labs USB driver was out of date.? I updated it and now it says tty.usbserial.? I believe that fixed more than one problem. ?
?
Now to do brew make, brew make install but do I need to do brew make install-conf?
?
Tim?
KM4ESU
|
I learned my Silicon Labs USB driver was out of date. ?I updated it and now it says tty.usbserial. ?I believe that fixed more than one problem. ?
?
Now to do brew make, brew make install but do I need to do brew make install-conf?
?
Tim?
KM4ESU
|
First off, let me say I am not certain this will solve "your issue", but it will help determine if the PTT issue is due to the COM port and sound card on a given DIGIRIG match.
That was the purpose in asking if PTT worked properly with only 1 DIGIRIG installed.
?
I don't have a DIGIRIG, but do have several devices with a CP210x serial device.? Some have {iSerial} or {serial}, but most do not.
I am no longer confident in this approach.
?
Lets like at a "path" option:
? ?Now that we know which BUS:Port? is which, can you show the contents of
? ? ? ?$ ls -Al /dev/serial/by-path/? ? ? ? ? ?(some OSes use ls -Al /dev/serial/by-id/)
See if you can match the information to the physical port on the Pi (top-left, top-right, bottom-left, bottom-right).
?
If so, we can work from there.
-------
Robert Giuliano
KB8RCO
|
Martin,
?
I will build from your tree with homebrew, and I am running homebrew v 4.4.31 on an M1 Mac Mini. My digirig is showing as tty.usbmodem, not a tty.usbserial. ?I am not sure what version I have, but I did not expect that.
?
Thank you both for helping to get a Mac M1 running the Arm processor to start working with direwolf. ?
?
I hope to get this working today.
?
Tim?
KM4ESU
|
On Wed, Apr 16, 2025 at 07:20 PM, Rob Giuliano w
Here's what LSUSB says:
?
: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 009: ID 0d8c:0012 C-Media Electronics, Inc. USB Audio Device
Bus 001 Device 008: ID 10c4:ea60 Silicon Labs CP210x UART Bridge
Bus 001 Device 006: ID 0424:2412 Microchip Technology, Inc. (formerly SMSC) Hub
Bus 001 Device 004: ID 0951:1666 Kingston Technology DataTraveler 100 G3/G4/SE9 G2/50 Kyson
Bus 001 Device 007: ID 10c4:ea60 Silicon Labs CP210x UART Bridge
Bus 001 Device 005: ID 0d8c:0012 C-Media Electronics, Inc. USB Audio Device
Bus 001 Device 003: ID 0424:2412 Microchip Technology, Inc. (formerly SMSC) Hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
?
The 2nd and 5th lines reveal the Silicon Labs bridges (Digirigs).??
?
aplay-l results:
?
card 0: Headphones [bcm2835 Headphones], device 0: bcm2835 Headphones [bcm2835 Headphones]
? Subdevices: 8/8
? Subdevice #0: subdevice #0
? Subdevice #1: subdevice #1
? Subdevice #2: subdevice #2
? Subdevice #3: subdevice #3
? Subdevice #4: subdevice #4
? Subdevice #5: subdevice #5
? Subdevice #6: subdevice #6
? Subdevice #7: subdevice #7
card 1: vc4hdmi0 [vc4-hdmi-0], device 0: MAI PCM i2s-hifi-0 [MAI PCM i2s-hifi-0]
? Subdevices: 1/1
? Subdevice #0: subdevice #0
card 2: vc4hdmi1 [vc4-hdmi-1], device 0: MAI PCM i2s-hifi-0 [MAI PCM i2s-hifi-0]
? Subdevices: 1/1
? Subdevice #0: subdevice #0
card 3: Device [USB Audio Device], device 0: USB Audio [USB Audio]
? Subdevices: 0/1
? Subdevice #0: subdevice #0
card 4: Device_1 [USB Audio Device], device 0: USB Audio [USB Audio]
? Subdevices: 0/1
? Subdevice #0: subdevice #0
|
Thanks for that, Jeff.? I feel exonerated ... well, somewhat.?
|
My read of the DIGIRIG Mobile device website () is that PTT is either CAT or RTS on COM
? "*? permanently available independently from CAT port an open-collector PTT switch
?? controlled by RTS signal of the COM port to interface HTs and mobile radios."
?
From that statement, I would say the proper configuration would be
CHANNEL0
? ?PTT /dev/ttyUSB0 RTS
CHANNEL1
? ?PTT /dev/ttyUSB1 RTS
The manual says nothing about DTR, so I would drop that.??
? If the PTT is constant when connected change RTS to -RTS (but I am pretty sure it needs to be just RTS).
?
Do each have working PTT when connected alone?
if so, I would say the Pi does not guarantee HWplug:4,0 to USB0 and HWplug:5,0 to USB1 matching (example).
?
Since they are the same device {idVender} and {idProduct} values would be enough to separate the COM connection for UDEV rules.
?? You will need to find something unique to each, like maybe {iSerial}
Plug each one separately and run
? start with $ lsusb and look at CP2102 in the name (or close to it):
??? $ lsusb -v -d {idVendor}:{idProduct} > DevPlug4.txt
swap
??? $ lsusb -v -d {idVendor}:{idProduct} > DevPlug5.txt
compare the files to find the key differences like maybe {iSerial} if it is set.? Unfortunately, many do not.
?
You could do the same for the CODEC, but I recommend aplay -l to get names to use in place of HWplug
?
Using udev rules and names should help ensure the audio and com devices are the same.
-------
Robert Giuliano
KB8RCO
|
Hi Steven,
?
PTT CM108 won't work with the Digirig Mobile model, but will with the Digirig Lite and DR-891 models, according to this page: ?
|
Steven
Jeff KP3FT