# CM119 USB interface **URL:** \ **Category:** AllStarLink\ **Created:** [December 24, 2018, 12:28am UTC](https://community.allstarlink.org/t/cm119-usb-interface/14678 "2018-12-24T00:28:11Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Brian\_G](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/b/58f4c7/32.png) [@Brian\_G](https://community.allstarlink.org/u/Brian_G)\ **Post date:** [December 24, 2018, 12:28am UTC](https://community.allstarlink.org/t/cm119-usb-interface/14678/1 "2018-12-24T00:28:11Z")
Hi all, Merry Christmas My local club is working on setting up a few ASL nodes, and I’ve been busy modifying some CM119 based USB sound cards to control the radios. I’m using this card/dongle: [https://www.amazon.ca/Syba-SD-CM-UAUD-Adapter-C-Media-Chipset/dp/B001MSS6CS ](https://www.amazon.ca/Syba-SD-CM-UAUD-Adapter-C-Media-Chipset/dp/B001MSS6CS) I’ve done several so far and have a few nodes working great with CTCSS carrier detect. One issue I’m consistently running into, is when setting the “RX Squelch Level” in the radio-tune-menu, it detects the current RX signal strength as 999. This results in the inability to use anything other than CTCSS for carrier detect. I can make plain old VOX work too, but it results in considerable (2 sec+) hang time. Using DSP carrier detect won’t work because it’s impossible to set the squelch high enough (max value 999). It always thinks there’s a signal present when there isn’t. This happens regardless of whether there’s a radio connected to the dongle or not. As a matter of fact it happens even when plugging in an unmodified dongle right out of the package. I need it to work with no CTCSS. VOX would be fine if it wasn’t for the hang time, but would rather use the DSP option in usbradio.conf. I assume it’s just the nature of the beast, and if I want it done properly I need an adapter and radio capable of COS. But maybe someone knows if there’s something that can be done or not? Anyone have any insight on how to either eliminate the VOX hang time, or eliminate that “invisible” signal? I might be overlooking something. Thanks for reading! > **···** > > – > Brian - VA3DXV ---
**Author:** ![Mike](https://community.allstarlink.org/user_avatar/community.allstarlink.org/mike/32/1569_2.png) [@Mike](https://community.allstarlink.org/u/Mike)\ **Post date:** [December 24, 2018, 1:30am UTC](https://community.allstarlink.org/t/cm119-usb-interface/14678/2 "2018-12-24T01:30:20Z")
Brian, ``` I could be wrong and you may get a better answer but I believe if ``` I understand right, ``` the rx sq level is for vox and you should/normally be using cos ``` from a pin on your fob, parallel port or using ctcss trigger for the COS …mike/kb8jnm ``` (oh... I may be about to find out for sure again as I try to ``` setup my hr remote again anew) > **···** > > On 12/23/2018 7:28 PM, Brian G wrote: > > > ``` > > Hi all, > > > > ``` > > > > Merry Christmas > > > > ``` > > My local > > > > ``` > > > > club is working on setting up a few ASL nodes, and I’ve been > > busy modifying some CM119 based USB sound cards to control the > > radios. I’m using this card/dongle: [[https://www.amazon.ca/Syba-SD-CM-UAUD-Adapter-C-Media-Chipset/dp/B001MSS6CS](https://www.amazon.ca/Syba-SD-CM-UAUD-Adapter-C-Media-Chipset/dp/B001MSS6CS) > > > > ``` > > ](https://www.amazon.ca/Syba-SD-CM-UAUD-Adapter-C-Media-Chipset/dp/B001MSS6CS) > > > > I've > > > > ``` > > > > done several so far and have a few nodes working great with > > CTCSS carrier detect. One issue I’m consistently running into, > > is when setting the “RX Squelch Level” in the radio-tune-menu, > > it detects the current RX signal strength as 999. This results > > in the inability to use anything other than CTCSS for carrier > > detect. I can make plain old VOX work too, but it results in > > considerable (2 sec+) hang time. > > > > ``` > > Using > > > > ``` > > > > DSP carrier detect won’t work because it’s impossible to set > > the squelch high enough (max value 999). It always thinks > > there’s a signal present when there isn’t. This happens > > regardless of whether there’s a radio connected to the dongle > > or not. As a matter of fact it happens even when plugging in > > an unmodified dongle right out of the package. I need it to > > work with no CTCSS. VOX would be fine if it wasn’t for the > > hang time, but would rather use the DSP option in > > usbradio.conf. > > > > ``` > > I assume > > > > ``` > > > > ## it’s just the nature of the beast, and if I want it done properly I need an adapter and radio capable of COS. But maybe someone knows if there’s something that can be done or not? Anyone have any insight on how to either eliminate the VOX hang time, or eliminate that “invisible” signal? I might be overlooking something. Thanks for reading! > > > > ``` > > Brian - VA3DXV > > > > ``` > > > > > ```auto > > _______________________________________________ > App_rpt-users mailing list > To unsubscribe from this list please visit and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" > You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem. > > ``` > > [App\_rpt-users@lists.allstarlink.org](mailto:App_rpt-users@lists.allstarlink.org)[http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app\_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users)[http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app\_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users) ---
**Author:** ![W3KKC](https://community.allstarlink.org/user_avatar/community.allstarlink.org/w3kkc/32/442_2.png) [@W3KKC](https://community.allstarlink.org/u/W3KKC)\ **Post date:** [December 24, 2018, 2:29am UTC](https://community.allstarlink.org/t/cm119-usb-interface/14678/3 "2018-12-24T02:29:08Z")
Brian, If the application reports 999, my guess is you aren't inputting raw discriminator audio into the interface. If the audio you are inputting into your radio interface has been Low Pass Filtered or is squelch gated, you cannot use DSP for noise squelch detection. The application will tell you if there is sufficient squelch noise to utilize DSP noise squelch detection after you do the "radio tune rxnoise" command. If it fails, the audio type, amount, or quality isn't sufficient for DSP noise detection. When fed with good discriminator audio, the noise squelch detection in app\_rpt is nearly as good as a Motorola M6709 (analog) squelch chip, commonly thought to be the high water mark in noise squelch detection. 999 is the total absence of noise, and is the result one would expect with a full quieting signal, or an inappropriately muted RX audio line. Kevin W3KKC > **···** > > On 12/23/2018 7:28 PM, Brian G wrote: > > > Hi all, Merry Christmas > > > > My local club is working on setting up a few ASL nodes, and I've been busy modifying some CM119 based USB sound cards to control the radios. I'm using this card/dongle: [https://www.amazon.ca/Syba-SD-CM-UAUD-Adapter-C-Media-Chipset/dp/B001MSS6CS](https://www.amazon.ca/Syba-SD-CM-UAUD-Adapter-C-Media-Chipset/dp/B001MSS6CS) > > > > I've done several so far and have a few nodes working great with CTCSS carrier detect. One issue I'm consistently running into, is when setting the "RX Squelch Level" in the radio-tune-menu, it detects the current RX signal strength as 999. This results in the inability to use anything other than CTCSS for carrier detect. I can make plain old VOX work too, but it results in considerable (2 sec+) hang time. > > > > Using DSP carrier detect won't work because it's impossible to set the squelch high enough (max value 999). It always thinks there's a signal present when there isn't. This happens regardless of whether there's a radio connected to the dongle or not. As a matter of fact it happens even when plugging in an unmodified dongle right out of the package. I need it to work with no CTCSS. VOX would be fine if it wasn't for the hang time, but would rather use the DSP option in usbradio.conf. > > > > I assume it's just the nature of the beast, and if I want it done properly I need an adapter and radio capable of COS. But maybe someone knows if there's something that can be done or not? Anyone have any insight on how to either eliminate the VOX hang time, or eliminate that "invisible" signal? I might be overlooking something. Thanks for reading! > > -- > > Brian - VA3DXV ---
**Author:** ![Brian\_G](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/b/58f4c7/32.png) [@Brian\_G](https://community.allstarlink.org/u/Brian_G)\ **Post date:** [December 24, 2018, 2:58am UTC](https://community.allstarlink.org/t/cm119-usb-interface/14678/4 "2018-12-24T02:58:51Z")
Hi Kevin, thanks very much… I understand 999 is supposed to represent a strong fully quiet signal. That’s the issue, there isn’t one…but app\_rpt thinks there’s a signal present and is sending it 100% of the time, unless I use CTCSS decode (or plain vox), which I don’t want to do for this node. I’m using the discriminator output from a Motorola Radius M120, but the same issue occurs on other rigs, and the “signal level” is still at 999 regardless of if there’s a radio connected to the dongle or not ☹ If there’s no input, signal level should be at (or close to) zero, shouldn’t it? > **···** > > On Sun, Dec 23, 2018 at 9:29 PM Kevin Custer [kuggie@kuggie.com](mailto:kuggie@kuggie.com) wrote: > > > Brian, > > > > ``` > > If the application reports 999, my guess is you aren't inputting > > > > ``` > > > > raw discriminator audio into the interface. If the audio you are > > inputting into your radio interface has been Low Pass Filtered or > > is squelch gated, you cannot use DSP for noise squelch detection. > > The application will tell you if there is sufficient squelch > > noise to utilize DSP noise squelch detection after you do the > > “radio tune rxnoise” command. If it fails, the audio type, amount, > > or quality isn’t sufficient for DSP noise detection. > > > > ``` > > When fed with good discriminator audio, the noise squelch > > > > ``` > > > > detection in app\_rpt is nearly as good as a Motorola M6709 > > (analog) squelch chip, commonly thought to be the high water mark > > in noise squelch detection. 999 is the total absence of noise, > > and is the result one would expect with a full quieting signal, or > > an inappropriately muted RX audio line. > > > > ``` > > Kevin W3KKC > > > > On 12/23/2018 7:28 PM, Brian G wrote: > > > > ``` > > > > ``` > > > Hi all, > > > > > > ``` > > > > > > Merry Christmas > > > > > > ``` > > > My local > > > > > > ``` > > > > > > club is working on setting up a few ASL nodes, and I’ve been > > > busy modifying some CM119 based USB sound cards to control the > > > radios. I’m using this card/dongle: [[https://www.amazon.ca/Syba-SD-CM-UAUD-Adapter-C-Media-Chipset/dp/B001MSS6CS](https://www.amazon.ca/Syba-SD-CM-UAUD-Adapter-C-Media-Chipset/dp/B001MSS6CS) > > > > > > ``` > > > ](https://www.amazon.ca/Syba-SD-CM-UAUD-Adapter-C-Media-Chipset/dp/B001MSS6CS) > > > > > > I've > > > > > > ``` > > > > > > done several so far and have a few nodes working great with > > > CTCSS carrier detect. One issue I’m consistently running into, > > > is when setting the “RX Squelch Level” in the radio-tune-menu, > > > it detects the current RX signal strength as 999. This results > > > in the inability to use anything other than CTCSS for carrier > > > detect. I can make plain old VOX work too, but it results in > > > considerable (2 sec+) hang time. > > > > > > ``` > > > Using > > > > > > ``` > > > > > > DSP carrier detect won’t work because it’s impossible to set > > > the squelch high enough (max value 999). It always thinks > > > there’s a signal present when there isn’t. This happens > > > regardless of whether there’s a radio connected to the dongle > > > or not. As a matter of fact it happens even when plugging in > > > an unmodified dongle right out of the package. I need it to > > > work with no CTCSS. VOX would be fine if it wasn’t for the > > > hang time, but would rather use the DSP option in > > > usbradio.conf. > > > > > > ``` > > > I assume > > > > > > ``` > > > > > > ## it’s just the nature of the beast, and if I want it done properly I need an adapter and radio capable of COS. But maybe someone knows if there’s something that can be done or not? Anyone have any insight on how to either eliminate the VOX hang time, or eliminate that “invisible” signal? I might be overlooking something. Thanks for reading! > > > > > > ``` > > > Brian - VA3DXV > > > > > > ``` > > > ---
**Author:** ![W3KKC](https://community.allstarlink.org/user_avatar/community.allstarlink.org/w3kkc/32/442_2.png) [@W3KKC](https://community.allstarlink.org/u/W3KKC)\ **Post date:** [December 24, 2018, 4:24am UTC](https://community.allstarlink.org/t/cm119-usb-interface/14678/5 "2018-12-24T04:24:04Z")
Brian, Signal Strength is determined by the noise level of the inputted audio from the receiver. Normally, with audio from a good discriminator source, calibrated by the radio tune rxnoise command, you'll have a signal strength of around 500 to 600 with NO signal. This is shown by inputting the command "radio tune rxsquelch". This number goes up as the noise level is reduced (from an increasing signal level making the FM receiver quiet). A level of 999 with the adapter unplugged from the receiver is the expected result. The adapter/application doesn't know if the receiver has reached full quieting or if the audio has simply disappeared from the adapter. The result is the same no matter which happened. In the case, no signal input results in an audio signal that's full of broadband noise. It's a loud white noise. When the receiver quiets, the amount of white noise is reduced, to a point of "full quieting" where the receiver is not outputting much or any noise. This is why a strong signal into the receiver shows as 999 and no signal results in something between 0 and 500 or so. Again, this all points to muted audio from the receiver, and that by definition is NOT discriminator audio. Real discriminator audio is not muted, or filtered in any way. Please have a look at the discriminator audio from your receiver and make sure noise is there when the receiver is not hearing a valid signal. Kevin > **···** > > On 12/23/2018 9:58 PM, Brian G wrote: > > > Hi Kevin, thanks very much... I understand 999 is supposed to represent a strong fully quiet signal. That's the issue, there isn't one...but app\_rpt thinks there's a signal present and is sending it 100% of the time, unless I use CTCSS decode (or plain vox), which I don't want to do for this node. > > > > I'm using the discriminator output from a Motorola Radius M120, but the same issue occurs on other rigs, and the "signal level" is still at 999 regardless of if there's a radio connected to the dongle or not ☹ If there's no input, signal level should be at (or close to) zero, shouldn't it? > > > > On Sun, Dec 23, 2018 at 9:29 PM Kevin Custer \ \\> wrote: > > > >     Brian, > > > >     If the application reports 999, my guess is you aren't inputting > >     raw discriminator audio into the interface. If the audio you are > >     inputting into your radio interface has been Low Pass Filtered or > >     is squelch gated, you cannot use DSP for noise squelch detection. > >      The application will tell you if there is sufficient squelch > >     noise to utilize DSP noise squelch detection after you do the > >     "radio tune rxnoise" command. If it fails, the audio type, amount, > >     or quality isn't sufficient for DSP noise detection. > > > >     When fed with good discriminator audio, the noise squelch > >     detection in app\_rpt is nearly as good as a Motorola M6709 > >     (analog) squelch chip, commonly thought to be the high water mark > >     in noise squelch detection. 999 is the total absence of noise, and > >     is the result one would expect with a full quieting signal, or an > >     inappropriately muted RX audio line. > > > >     Kevin W3KKC > > > >     On 12/23/2018 7:28 PM, Brian G wrote: > > > > >     Hi all, Merry Christmas > > > > > >     My local club is working on setting up a few ASL nodes, and I've > > >     been busy modifying some CM119 based USB sound cards to control > > >     the radios. I'm using this card/dongle: > > >     [https://www.amazon.ca/Syba-SD-CM-UAUD-Adapter-C-Media-Chipset/dp/B001MSS6CS](https://www.amazon.ca/Syba-SD-CM-UAUD-Adapter-C-Media-Chipset/dp/B001MSS6CS) > > > > > >     I've done several so far and have a few nodes working great with > > >     CTCSS carrier detect. One issue I'm consistently running into, is > > >     when setting the "RX Squelch Level" in the radio-tune-menu, it > > >     detects the current RX signal strength as 999. This results in > > >     the inability to use anything other than CTCSS for carrier > > >     detect. I can make plain old VOX work too, but it results in > > >     considerable (2 sec+) hang time. > > > > > >     Using DSP carrier detect won't work because it's impossible to > > >     set the squelch high enough (max value 999). It always thinks > > >     there's a signal present when there isn't. This happens > > >     regardless of whether there's a radio connected to the dongle or > > >     not. As a matter of fact it happens even when plugging in an > > >     unmodified dongle right out of the package. I need it to work > > >     with no CTCSS. VOX would be fine if it wasn't for the hang time, > > >     but would rather use the DSP option in usbradio.conf. > > > > > >     I assume it's just the nature of the beast, and if I want it done > > >     properly I need an adapter and radio capable of COS. But maybe > > >     someone knows if there's something that can be done or not? > > >     Anyone have any insight on how to either eliminate the VOX hang > > >     time, or eliminate that "invisible" signal? I might be > > >     overlooking something. Thanks for reading! > > >     -- > > >     Brian - VA3DXV ---
**Author:** ![Brian\_G](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/b/58f4c7/32.png) [@Brian\_G](https://community.allstarlink.org/u/Brian_G)\ **Post date:** [December 24, 2018, 5:21am UTC](https://community.allstarlink.org/t/cm119-usb-interface/14678/6 "2018-12-24T05:21:16Z")
Ok, I’m thick sometimes 🙂 I get what you’re saying now, makes sense. Thank you for the clarification. The Motorola is working as you described, the other rigs not so much. So the gist of it is, there’s no way to use DSP carrier detect without using discriminator audio? It’s CTCSS or VOX only in that case? > **···** > > On Sun, Dec 23, 2018 at 11:24 PM Kevin Custer [kuggie@kuggie.com](mailto:kuggie@kuggie.com) wrote: > > > Brian, > > > > ``` > > Signal Strength is determined by the noise level of the inputted > > > > ``` > > > > audio from the receiver. Normally, with audio from a good > > discriminator source, calibrated by the radio tune rxnoise > > command, you’ll have a signal strength of around 500 to 600 with > > NO signal. This is shown by inputting the command “radio tune > > rxsquelch”. This number goes up as the noise level is reduced > > (from an increasing signal level making the FM receiver quiet). > > > > ``` > > A level of 999 with the adapter unplugged from the receiver is the > > > > ``` > > > > expected result. The adapter/application doesn’t know if the > > receiver has reached full quieting or if the audio has simply > > disappeared from the adapter. The result is the same no matter > > which happened. > > > > ``` > > In the case, no signal input results in an audio signal that's > > > > ``` > > > > full of broadband noise. It’s a loud white noise. When the > > receiver quiets, the amount of white noise is reduced, to a point > > of “full quieting” where the receiver is not outputting much or > > any noise. This is why a strong signal into the receiver shows as > > 999 and no signal results in something between 0 and 500 or so. > > > > ``` > > Again, this all points to muted audio from the receiver, and that > > > > ``` > > > > by definition is NOT discriminator audio. Real discriminator > > audio is not muted, or filtered in any way. Please have a look at > > the discriminator audio from your receiver and make sure noise is > > there when the receiver is not hearing a valid signal. > > > > ``` > > Kevin > > > > On 12/23/2018 9:58 PM, Brian G wrote: > > > > ``` > > > > ``` > > > Hi Kevin, thanks very much... I understand 999 is > > > > > > ``` > > > > > > supposed to represent a strong fully quiet signal. That’s the > > > issue, there isn’t one…but app\_rpt thinks there’s a signal > > > present and is sending it 100% of the time, unless I use CTCSS > > > decode (or plain vox), which I don’t want to do for this node. > > > > ``` > > > I'm using the discriminator output from a Motorola Radius > > > > > > ``` > > > > > > M120, but the same issue occurs on other rigs, and the > > > “signal level” is still at 999 regardless of if there’s a > > > radio connected to the dongle or not ☹ If there’s no input, > > > signal level should be at (or close to) zero, shouldn’t it? > > > > > > > > > > > > ``` > > > On Sun, Dec 23, 2018 at 9:29 PM Kevin Custer > > wrote: > > > > > > ``` > > > > > Brian, > > > > > > > > ``` > > > > If the application reports 999, my guess is you aren't > > > > > > > > ``` > > > > > > > > inputting raw discriminator audio into the interface. > > > > If the audio you are inputting into your radio interface > > > > has been Low Pass Filtered or is squelch gated, you > > > > cannot use DSP for noise squelch detection. The > > > > application will tell you if there is sufficient squelch > > > > noise to utilize DSP noise squelch detection after you > > > > do the “radio tune rxnoise” command. If it fails, the > > > > audio type, amount, or quality isn’t sufficient for DSP > > > > noise detection. > > > > > > > > ``` > > > > When fed with good discriminator audio, the noise > > > > > > > > ``` > > > > > > > > squelch detection in app\_rpt is nearly as good as a > > > > Motorola M6709 (analog) squelch chip, commonly thought > > > > to be the high water mark in noise squelch detection. > > > > 999 is the total absence of noise, and is the result one > > > > would expect with a full quieting signal, or an > > > > inappropriately muted RX audio line. > > > > > > > > ``` > > > > Kevin W3KKC > > > > > > > > On 12/23/2018 7:28 PM, Brian G wrote: > > > > > > > > ``` > > > > > > Hi all, Merry Christmas > > > > > > > > > > ``` > > > > > My local club is working on setting up a few ASL > > > > > > > > > > ``` > > > > > > > > > > nodes, and I’ve been busy modifying some CM119 based > > > > > USB sound cards to control the radios. I’m using > > > > > this card/dongle: [[https://www.amazon.ca/Syba-SD-CM-UAUD-Adapter-C-Media-Chipset/dp/B001MSS6CS](https://www.amazon.ca/Syba-SD-CM-UAUD-Adapter-C-Media-Chipset/dp/B001MSS6CS) > > > > > > > > > > ``` > > > > > ](https://www.amazon.ca/Syba-SD-CM-UAUD-Adapter-C-Media-Chipset/dp/B001MSS6CS) > > > > > > > > > > I've done several so far and have a few nodes > > > > > > > > > > ``` > > > > > > > > > > working great with CTCSS carrier detect. One issue > > > > > I’m consistently running into, is when setting the > > > > > “RX Squelch Level” in the radio-tune-menu, it > > > > > detects the current RX signal strength as 999. This > > > > > results in the inability to use anything other than > > > > > CTCSS for carrier detect. I can make plain old VOX > > > > > work too, but it results in considerable (2 sec+) > > > > > hang time. > > > > > > > > > > ``` > > > > > Using DSP carrier detect won't work because it's > > > > > > > > > > ``` > > > > > > > > > > impossible to set the squelch high enough (max value > > > > > 999). It always thinks there’s a signal present when > > > > > there isn’t. This happens regardless of whether > > > > > there’s a radio connected to the dongle or not. As a > > > > > matter of fact it happens even when plugging in an > > > > > unmodified dongle right out of the package. I need > > > > > it to work with no CTCSS. VOX would be fine if it > > > > > wasn’t for the hang time, but would rather use the > > > > > DSP option in usbradio.conf. > > > > > > > > > > ``` > > > > > I assume it's just the nature of the beast, and > > > > > > > > > > ``` > > > > > > > > > > ## if I want it done properly I need an adapter and radio capable of COS. But maybe someone knows if there’s something that can be done or not? Anyone have any insight on how to either eliminate the VOX hang time, or eliminate that “invisible” signal? I might be overlooking something. Thanks for reading! > > > > > > > > > > ``` > > > > > Brian - VA3DXV > > > > > > > > > > ``` > > > > > > > > > > > * * * > > > > App\_rpt-users mailing list > > > > [App\_rpt-users@lists.allstarlink.org](mailto:App_rpt-users@lists.allstarlink.org) > > > > [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app\_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users) > > > > To unsubscribe from this list please visit [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app\_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users) and scroll down to the bottom of the page. Enter your email address and press the “Unsubscribe or edit options button” > > > > You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem. ---
**Author:** ![W3KKC](https://community.allstarlink.org/user_avatar/community.allstarlink.org/w3kkc/32/442_2.png) [@W3KKC](https://community.allstarlink.org/u/W3KKC)\ **Post date:** [December 24, 2018, 7:56pm UTC](https://community.allstarlink.org/t/cm119-usb-interface/14678/7 "2018-12-24T19:56:54Z")
Correct - BUT, discriminator audio should be available from that M120 radio. You just have to hook it up and possibly program it correctly. Kevin > **···** > > On 12/24/2018 12:21 AM, Brian G wrote: > > > Ok, I'm thick sometimes 🙂 I get what you're saying now, makes sense. Thank you for the clarification. The Motorola is working as you described, the other rigs not so much. > > > > So the gist of it is, there's no way to use DSP carrier detect without using discriminator audio? It's CTCSS or VOX only in that case? ---
**Author:** ![Mark\_DuMoulin](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/m/e9c0ed/32.png) [@Mark\_DuMoulin](https://community.allstarlink.org/u/Mark_DuMoulin)\ **Post date:** [January 1, 2019, 2:19pm UTC](https://community.allstarlink.org/t/cm119-usb-interface/14678/8 "2019-01-01T14:19:17Z")
Kevin,Brian; I have been trying to set up use of radiousb instead of simpleusb. I see here Brian is doing that with the issues he is having. I can't get nearly that far. I am running hamvoip rc19 on some and recently downloaded stretch. In both cases I set the usbradio module to load however I cannot get the driver to work and keep getting asterisk failures. Additionally the menus set up by the programmer show only simpleusb-radio-tune not radio-tune-menu. Is there another image or procedure I need to run to get this started? Tnx, Mark WB2ERS > **···** > > -----Original Message----- > From: App\_rpt-users [mailto:app\_rpt-users-bounces@lists.allstarlink.org] On Behalf Of Kevin Custer > Sent: Monday, December 24, 2018 2:57 PM > To: Users of Asterisk app\_rpt; Brian G > Subject: Re: [App\_rpt-users] CM119 USB interface > > On 12/24/2018 12:21 AM, Brian G wrote: > > > Ok, I'm thick sometimes 🙂 I get what you're saying now, makes sense. > > Thank you for the clarification. The Motorola is working as you > > described, the other rigs not so much. > > > > So the gist of it is, there's no way to use DSP carrier detect without > > using discriminator audio? It's CTCSS or VOX only in that case? > > Correct - > > BUT, discriminator audio should be available from that M120 radio. You just have to hook it up and possibly program it correctly. > > Kevin > \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ > App\_rpt-users mailing list > App\_rpt-users@lists.allstarlink.org > [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app\_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users) > > To unsubscribe from this list please visit [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app\_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users) and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" > You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem. ---
**Author:** ![Mike](https://community.allstarlink.org/user_avatar/community.allstarlink.org/mike/32/1569_2.png) [@Mike](https://community.allstarlink.org/u/Mike)\ **Post date:** [January 1, 2019, 4:09pm UTC](https://community.allstarlink.org/t/cm119-usb-interface/14678/9 "2019-01-01T16:09:52Z")
Mark, Can you show me the line in your rpt.conf where you are loading the channel. ie rxchannel = Radio/usb\_29285 And your usbradio.conf file text ...mike/kb8jnm What > **···** > > On 1/1/2019 9:19 AM, Mark DuMoulin wrote: > > > Kevin,Brian; > > > > I have been trying to set up use of radiousb instead of simpleusb. I see here Brian is doing that with the issues he is having. > > I can't get nearly that far. > > I am running hamvoip rc19 on some and recently downloaded stretch. > > In both cases I set the usbradio module to load however I cannot get the driver to work and keep getting asterisk failures. > > Additionally the menus set up by the programmer show only simpleusb-radio-tune not radio-tune-menu. > > Is there another image or procedure I need to run to get this started? > > > > Tnx, > > Mark > > WB2ERS > > > > -----Original Message----- > > From: App\_rpt-users [mailto:app\_rpt-users-bounces@lists.allstarlink.org] On Behalf Of Kevin Custer > > Sent: Monday, December 24, 2018 2:57 PM > > To: Users of Asterisk app\_rpt; Brian G > > Subject: Re: [App\_rpt-users] CM119 USB interface > > > > On 12/24/2018 12:21 AM, Brian G wrote: > > > > > Ok, I'm thick sometimes 🙂 I get what you're saying now, makes sense. > > > Thank you for the clarification. The Motorola is working as you > > > described, the other rigs not so much. > > > > > > So the gist of it is, there's no way to use DSP carrier detect without > > > using discriminator audio? It's CTCSS or VOX only in that case? > > > > Correct - > > > > BUT, discriminator audio should be available from that M120 radio. You just have to hook it up and possibly program it correctly. > > > > Kevin > > \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ > > App\_rpt-users mailing list > > App\_rpt-users@lists.allstarlink.org > > [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app\_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users) > > > > To unsubscribe from this list please visit [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app\_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users) and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" > > You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem. > > \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ > > App\_rpt-users mailing list > > App\_rpt-users@lists.allstarlink.org > > [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app\_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users) > > > > To unsubscribe from this list please visit [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app\_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users) and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" > > You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem. ---
**Author:** ![W3KKC](https://community.allstarlink.org/user_avatar/community.allstarlink.org/w3kkc/32/442_2.png) [@W3KKC](https://community.allstarlink.org/u/W3KKC)\ **Post date:** [January 1, 2019, 5:23pm UTC](https://community.allstarlink.org/t/cm119-usb-interface/14678/10 "2019-01-01T17:23:09Z")
Howdy Mark, This particular group is for supporting the "official" AllStarLink distribution of Asterisk and app\_rpt called ASL1.01, and legacy distributions like ACID and DIAL. As such, we don't generally get into the discussions and support for HamVoIP. Those folks have their own support system. However, I'll attempt to answer your questions. HamVoIP doesn't recommend the use of usbradio, however it's fully supported in ASL 1.01. My suggestion is you download ASL 1.01 and give it a try. \<[https://wiki.allstarlink.org/wiki/Main\_Page>](https://wiki.allstarlink.org/wiki/Main_Page>); USBradio is one of the features that I really like about AllStarLink. When fed with discriminator audio, the software will determine the noise squelch and CTCSS detection, eliminating the need for hardware modifications and obtaining the right logic signals for COS and CTCSS (sometimes not as easy as one would like). Then, feeding the FM modulator directly with audio that's been filtered, pre-emphasized and limited, makes all transmitters sound the same no matter who made them. The noise squelch detection is as close to a Motorola M6709 as you can get. That's often thought of as the high water mark in noise squelch circuitry. The CTCSS detection is as good as any COM-SPEC product of past or present, also thought of as the best in the industry. Since we're on the subject of usbradio, there's something else that I should mention. Since 2008, a C-Media integrated circuit of some kind has been used as the heart of most radio to computer audio interfacing in AllStar Link. The CM108, CM119 and CM119A are used in most of the adapters to date. Some manufacturers have settled on the new CM119B chipset. In my opinion, the adapters based on this chipset shouldn't be used with usbradio. Why? All of these components are similar, except the CM119B. The "B"component includes a few changes which are significantly different. These differences may not allow the CM119B to operate correctly with AllStar. The two big differences are the lack of crystal stability, and a new "feature' called Pop Filtering on the MIC input. In review of the spec sheet for the CM119B in comparison with its prior counterparts, the pop filter rolls off the low end frequency response. This slope might be enough to cause unreliable detection of CTCSS when using the usbradio channel driver, especially on lower tone frequencies. I'm also concerned that without the crystal time base, the RC stability of the CM119B will result in unreliable CTCSS detection caused by frequency drift. This is especially true in systems where the audio adapter is subjected to wide ambient temperature changes, as found in shelters that are not environmentally controlled. In addition, there are audio scaling differences between the prior chipsets, and the CM119B. The scaling differences are currently being worked out in software. In conclusion, the CM119B may be fine when used with the simpleusb channel driver, but there are lots of people that rely on the DSP of app\_rpt for software noise squelch and CTCSS detection. I recently purchased several hundred CM119A components directly from C-Media. That's what I will continue to supply in my radio adapter offerings, as we know it works in every distribution, no matter if it's simpleusb or usbradio. Kevin W3KKC > **···** > > On 1/1/2019 9:19 AM, Mark DuMoulin wrote: > > > Kevin,Brian; > > > > I have been trying to set up use of radiousb instead of simpleusb. I see here Brian is doing that with the issues he is having. > > I can't get nearly that far. > > I am running hamvoip rc19 on some and recently downloaded stretch. > > In both cases I set the usbradio module to load however I cannot get the driver to work and keep getting asterisk failures. > > Additionally the menus set up by the programmer show only simpleusb-radio-tune not radio-tune-menu. > > Is there another image or procedure I need to run to get this started? > > > > Tnx, > > Mark > > WB2ERS ---
**Author:** ![Mark\_DuMoulin](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/m/e9c0ed/32.png) [@Mark\_DuMoulin](https://community.allstarlink.org/u/Mark_DuMoulin)\ **Post date:** [January 1, 2019, 5:25pm UTC](https://community.allstarlink.org/t/cm119-usb-interface/14678/11 "2019-01-01T17:25:50Z")
Kevin, I downloaded ASL 1.01 and had the same issue as with the RC.19 When I try to use it asterisk fails claiming to not find the chan. I'll put it back in and try again to give you feedback. Tnx! Mark > **···** > > -----Original Message----- > From: Kevin Custer [mailto:kuggie@kuggie.com] > Sent: Tuesday, January 01, 2019 12:23 PM > To: Users of Asterisk app\_rpt; Mark DuMoulin > Subject: Re: [App\_rpt-users] CM119 USB interface > > Howdy Mark, > > This particular group is for supporting the "official" AllStarLink distribution of Asterisk and app\_rpt called ASL1.01, and legacy distributions like ACID and DIAL. As such, we don't generally get into the discussions and support for HamVoIP. Those folks have their own support system. However, I'll attempt to answer your questions. HamVoIP doesn't recommend the use of usbradio, however it's fully supported in ASL 1.01. My suggestion is you download ASL 1.01 and give it a try. > \<[https://wiki.allstarlink.org/wiki/Main\_Page>](https://wiki.allstarlink.org/wiki/Main_Page>); > > USBradio is one of the features that I really like about AllStarLink. When fed with discriminator audio, the software will determine the noise squelch and CTCSS detection, eliminating the need for hardware modifications and obtaining the right logic signals for COS and CTCSS (sometimes not as easy as one would like). Then, feeding the FM modulator directly with audio that's been filtered, pre-emphasized and limited, makes all transmitters sound the same no matter who made them. The noise squelch detection is as close to a Motorola M6709 as you can get. That's often thought of as the high water mark in noise squelch circuitry. The CTCSS detection is as good as any COM-SPEC product of past or present, also thought of as the best in the industry. > > Since we're on the subject of usbradio, there's something else that I should mention. > > Since 2008, a C-Media integrated circuit of some kind has been used as the heart of most radio to computer audio interfacing in AllStar Link. The CM108, CM119 and CM119A are used in most of the adapters to date. Some manufacturers have settled on the new CM119B chipset. In my opinion, the adapters based on this chipset shouldn't be used with usbradio. Why? All of these components are similar, except the CM119B. The "B"component includes a few changes which are significantly different. These differences may not allow the CM119B to operate correctly with AllStar. The two big differences are the lack of crystal stability, and a new "feature' called Pop Filtering on the MIC input. In review of the spec sheet for the CM119B in comparison with its prior counterparts, the pop filter rolls off the low end frequency response. This slope might be enough to cause unreliable detection of CTCSS when using the usbradio channel driver, especially on lower tone frequencies. I'm also concerned that without the crystal time base, the RC stability of the CM119B will result in unreliable CTCSS detection caused by frequency drift. This is especially true in systems where the audio adapter is subjected to wide ambient temperature changes, as found in shelters that are not environmentally controlled. In addition, there are audio scaling differences between the prior chipsets, and the CM119B. The scaling differences are currently being worked out in software. > > In conclusion, the CM119B may be fine when used with the simpleusb channel driver, but there are lots of people that rely on the DSP of app\_rpt for software noise squelch and CTCSS detection. I recently purchased several hundred CM119A components directly from C-Media. That's what I will continue to supply in my radio adapter offerings, as we know it works in every distribution, no matter if it's simpleusb or usbradio. > > Kevin W3KKC > > On 1/1/2019 9:19 AM, Mark DuMoulin wrote: > > > Kevin,Brian; > > > > I have been trying to set up use of radiousb instead of simpleusb. I see here Brian is doing that with the issues he is having. > > I can't get nearly that far. > > I am running hamvoip rc19 on some and recently downloaded stretch. > > In both cases I set the usbradio module to load however I cannot get the driver to work and keep getting asterisk failures. > > Additionally the menus set up by the programmer show only simpleusb-radio-tune not radio-tune-menu. > > Is there another image or procedure I need to run to get this started? > > > > Tnx, > > Mark > > WB2ERS ---
**Author:** ![Mark\_DuMoulin](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/m/e9c0ed/32.png) [@Mark\_DuMoulin](https://community.allstarlink.org/u/Mark_DuMoulin)\ **Post date:** [January 1, 2019, 5:26pm UTC](https://community.allstarlink.org/t/cm119-usb-interface/14678/12 "2019-01-01T17:26:35Z")
Mike, Thanks for the reply. Here is what I have in the HamVoip RC.19 Rpt.conf [1400] ; Change this to your assigned node number ; Channel Driver settings                                 ; Define a channel driver to use and which                                 ; interface within that channel driver                                 ; To define a radioless node use the                                 ; psuedo channel driver - rxchannel=dahdi/pseudo rxchannel=Radio/usb1400                                 ; Example usbradio channel driver ;rxchannel=SimpleUSB/usb                                 ; Example simpleusb channel driver ;rxchannel=dahdi/pseudo                                 ; Example pseudo channel driver List of programs in asterisk [root@1400\_Home\_Test asterisk]# ls amd.conf indications.conf asterisk.conf local chan\_dahdi.conf logger.conf dnsmgr.conf manager.conf dundi.conf modules.conf echolink.xxx rpt.conf extensions.conf rpt.conf.sample extensions.conf\_2018.12.30.2105 rpt.conf\_2018.12.30.2105 extensions.conf\_2018.12.30.2113 rpt.conf\_2018.12.30.2113 extensions.conf\_2018.12.30.2114 rpt.conf\_2018.12.30.2114 extensions.conf\_orig rpt.conf\_orig features.conf simpleusb.conf iax.conf simpleusb.conf\_2018.12.30.2113 iax.conf\_2018.12.30.2105 simpleusb.conf\_2018.12.30.2115 iax.conf\_2018.12.30.2113 simpleusb\_tune\_usb.conf iax.conf\_2018.12.30.2114 sip.conf iax.conf\_orig usbradio.conf.xxx usbradio.conf.xxx ; Usbradio channel driver Configuration File ; [general] [usb1400] hdwtype=0 rxboost=1 txboost=1 rxctcssrelax=1 txctcssdefault=100.0 rxctcssfreqs=100.0 txctcssfreqs=100.0 ;rxctcssoverride=0 carrierfrom=dsp ctcssfrom=dsp rxdemod=flat txprelim=yes txlimonly=no txtoctype=notone txmixa=composite txmixb=0 invertptt=0 duplex=1 rxondelay=0 rxnoisefiltype=0 eeprom=0 #includeifexists custom/usbradio.conf Modules.conf ; ; Asterisk configuration file ; ; Module Loader configuration file ; [modules] autoload=yes ;noload=chan\_voter.so ;noload=chan\_usbradio.so ;noload=chan\_irlp.so ;noload=chan\_echolink.so ;noload=chan\_simpleusb.so noload=app\_hamvoip.so ;noload=res\_crypto.so ;noload=func\_callerid.so noload=chan\_oss.so noload=chan\_alsa.so noload=chan\_phone.so noload=res\_config\_pgsql.so noload=cdr\_pgsql.so noload=app\_radbridge.so noload=app\_festival.so noload=app\_queue.so noload=func\_odbc.so noload=chan\_mgcp.so noload=chan\_skinny.so noload=cdr\_custom.so noload=cdr\_csv.so noload=chan\_agent.so noload=chan\_simple2.so noload=func\_moh.so noload=res\_musiconhold.so noload=res\_speech.so noload=res\_odbc.so noload=res\_smdi.so noload=res\_config\_odbc.so noload=chan\_tlb.so noload=app\_milliwatt.so noload=app\_image.so noload=app\_sendtext.so noload=format\_h264.so noload=app\_hasnewvoicemail.so noload=app\_ices.so noload=app\_lookupblacklist.so noload=app\_voicemail.so noload=chan\_usrp.so noload=app\_lookupidname.so noload=app\_zapateller.so noload=format\_jpeg.so noload=app\_parkandannounce.so noload=app\_meetme.so noload=app\_settransfercapability.so noload=app\_amd.so noload=app\_followme.so noload=app\_transfer.so noload=app\_directed\_pickup.so noload=app\_flash.so noload=app\_page.so noload=app\_gps.so noload=pbx\_dundi.so noload=app\_setcallerid.so noload=app\_dictate.so noload=res\_adsi.so noload=app\_mp3.so noload=app\_privacy.so noload=app\_disa.so noload=app\_alarmreceiver.so noload=app\_externalirv.so noload=chan\_beagle.so noload=chan\_sip.so [global] > **···** > > -----Original Message----- > From: App\_rpt-users [mailto:app\_rpt-users-bounces@lists.allstarlink.org] On Behalf Of Mike > Sent: Tuesday, January 01, 2019 11:10 AM > To: app\_rpt-users@lists.allstarlink.org > Subject: Re: [App\_rpt-users] CM119 USB interface > > Mark, > > Can you show me the line in your rpt.conf where you are loading the channel. > > ie rxchannel = Radio/usb\_29285 > > And your usbradio.conf file text > > ...mike/kb8jnm > > What > > On 1/1/2019 9:19 AM, Mark DuMoulin wrote: > > > Kevin,Brian; > > > > I have been trying to set up use of radiousb instead of simpleusb. I see here Brian is doing that with the issues he is having. > > I can't get nearly that far. > > I am running hamvoip rc19 on some and recently downloaded stretch. > > In both cases I set the usbradio module to load however I cannot get the driver to work and keep getting asterisk failures. > > Additionally the menus set up by the programmer show only simpleusb-radio-tune not radio-tune-menu. > > Is there another image or procedure I need to run to get this started? > > > > Tnx, > > Mark > > WB2ERS > > > > -----Original Message----- > > From: App\_rpt-users > > [mailto:app\_rpt-users-bounces@lists.allstarlink.org] On Behalf Of > > Kevin Custer > > Sent: Monday, December 24, 2018 2:57 PM > > To: Users of Asterisk app\_rpt; Brian G > > Subject: Re: [App\_rpt-users] CM119 USB interface > > > > On 12/24/2018 12:21 AM, Brian G wrote: > > > > > Ok, I'm thick sometimes 🙂 I get what you're saying now, makes sense. > > > Thank you for the clarification. The Motorola is working as you > > > described, the other rigs not so much. > > > > > > So the gist of it is, there's no way to use DSP carrier detect > > > without using discriminator audio? It's CTCSS or VOX only in that case? > > > > Correct - > > > > BUT, discriminator audio should be available from that M120 radio. You just have to hook it up and possibly program it correctly. > > > > Kevin > > \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ > > App\_rpt-users mailing list > > App\_rpt-users@lists.allstarlink.org > > [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app\_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users) > > > > To unsubscribe from this list please visit [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app\_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users) and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" > > You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem. > > \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ > > App\_rpt-users mailing list > > App\_rpt-users@lists.allstarlink.org > > [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app\_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users) > > > > To unsubscribe from this list please visit [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app\_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users) and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" > > You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem. > > \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ > App\_rpt-users mailing list > App\_rpt-users@lists.allstarlink.org > [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app\_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users) > > To unsubscribe from this list please visit [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app\_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users) and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" > You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem. ---
**Author:** ![Mike](https://community.allstarlink.org/user_avatar/community.allstarlink.org/mike/32/1569_2.png) [@Mike](https://community.allstarlink.org/u/Mike)\ **Post date:** [January 1, 2019, 5:30pm UTC](https://community.allstarlink.org/t/cm119-usb-interface/14678/13 "2019-01-01T17:30:36Z")
Mark, A quick question, Can you make this node work using the dahdi driver ? Please test that and let me know. ...mike/kb8jnm > **···** > > On 1/1/2019 12:26 PM, Mark DuMoulin wrote: > > > Mike, > > > > Thanks for the reply. Here is what I have in the HamVoip RC.19 > > > > Rpt.conf > > > > [1400] ; Change this to your assigned node number > > > > ; Channel Driver settings > >                                  ; Define a channel driver to use and which > >                                  ; interface within that channel driver > >                                  ; To define a radioless node use the > >                                  ; psuedo channel driver - rxchannel=dahdi/pseudo > > rxchannel=Radio/usb1400 > >                                  ; Example usbradio channel driver > > ;rxchannel=SimpleUSB/usb > >                                  ; Example simpleusb channel driver > > ;rxchannel=dahdi/pseudo > >                                  ; Example pseudo channel driver > > > > List of programs in asterisk > > > > [root@1400\_Home\_Test asterisk]# ls > > amd.conf indications.conf > > asterisk.conf local > > chan\_dahdi.conf logger.conf > > dnsmgr.conf manager.conf > > dundi.conf modules.conf > > echolink.xxx rpt.conf > > extensions.conf rpt.conf.sample > > extensions.conf\_2018.12.30.2105 rpt.conf\_2018.12.30.2105 > > extensions.conf\_2018.12.30.2113 rpt.conf\_2018.12.30.2113 > > extensions.conf\_2018.12.30.2114 rpt.conf\_2018.12.30.2114 > > extensions.conf\_orig rpt.conf\_orig > > features.conf simpleusb.conf > > iax.conf simpleusb.conf\_2018.12.30.2113 > > iax.conf\_2018.12.30.2105 simpleusb.conf\_2018.12.30.2115 > > iax.conf\_2018.12.30.2113 simpleusb\_tune\_usb.conf > > iax.conf\_2018.12.30.2114 sip.conf > > iax.conf\_orig usbradio.conf.xxx > > > > usbradio.conf.xxx > > > > ; Usbradio channel driver Configuration File > > ; > > > > [general] > > > > [usb1400] > > > > hdwtype=0 > > rxboost=1 > > txboost=1 > > rxctcssrelax=1 > > txctcssdefault=100.0 > > rxctcssfreqs=100.0 > > txctcssfreqs=100.0 > > ;rxctcssoverride=0 > > carrierfrom=dsp > > ctcssfrom=dsp > > rxdemod=flat > > txprelim=yes > > txlimonly=no > > txtoctype=notone > > txmixa=composite > > txmixb=0 > > invertptt=0 > > duplex=1 > > rxondelay=0 > > rxnoisefiltype=0 > > eeprom=0 > > > > #includeifexists custom/usbradio.conf > > > > Modules.conf > > > > ; > > ; Asterisk configuration file > > ; > > ; Module Loader configuration file > > ; > > > > [modules] > > autoload=yes > > ;noload=chan\_voter.so > > ;noload=chan\_usbradio.so > > ;noload=chan\_irlp.so > > ;noload=chan\_echolink.so > > ;noload=chan\_simpleusb.so > > noload=app\_hamvoip.so > > > > ;noload=res\_crypto.so > > ;noload=func\_callerid.so > > noload=chan\_oss.so > > noload=chan\_alsa.so > > noload=chan\_phone.so > > noload=res\_config\_pgsql.so > > noload=cdr\_pgsql.so > > noload=app\_radbridge.so > > noload=app\_festival.so > > noload=app\_queue.so > > noload=func\_odbc.so > > noload=chan\_mgcp.so > > noload=chan\_skinny.so > > noload=cdr\_custom.so > > noload=cdr\_csv.so > > noload=chan\_agent.so > > noload=chan\_simple2.so > > noload=func\_moh.so > > noload=res\_musiconhold.so > > noload=res\_speech.so > > noload=res\_odbc.so > > noload=res\_smdi.so > > noload=res\_config\_odbc.so > > noload=chan\_tlb.so > > noload=app\_milliwatt.so > > noload=app\_image.so > > noload=app\_sendtext.so > > noload=format\_h264.so > > noload=app\_hasnewvoicemail.so > > noload=app\_ices.so > > noload=app\_lookupblacklist.so > > noload=app\_voicemail.so > > noload=chan\_usrp.so > > noload=app\_lookupidname.so > > noload=app\_zapateller.so > > noload=format\_jpeg.so > > noload=app\_parkandannounce.so > > noload=app\_meetme.so > > noload=app\_settransfercapability.so > > noload=app\_amd.so > > noload=app\_followme.so > > noload=app\_transfer.so > > noload=app\_directed\_pickup.so > > noload=app\_flash.so > > noload=app\_page.so > > noload=app\_gps.so > > noload=pbx\_dundi.so > > noload=app\_setcallerid.so > > noload=app\_dictate.so > > noload=res\_adsi.so > > noload=app\_mp3.so > > noload=app\_privacy.so > > noload=app\_disa.so > > noload=app\_alarmreceiver.so > > noload=app\_externalirv.so > > noload=chan\_beagle.so > > noload=chan\_sip.so > > [global] > > > > -----Original Message----- > > From: App\_rpt-users [mailto:app\_rpt-users-bounces@lists.allstarlink.org] On Behalf Of Mike > > Sent: Tuesday, January 01, 2019 11:10 AM > > To: app\_rpt-users@lists.allstarlink.org > > Subject: Re: [App\_rpt-users] CM119 USB interface > > > > Mark, > > > > Can you show me the line in your rpt.conf where you are loading the channel. > > > > ie rxchannel = Radio/usb\_29285 > > > > And your usbradio.conf file text > > > > ...mike/kb8jnm > > > > What > > > > On 1/1/2019 9:19 AM, Mark DuMoulin wrote: > > > > > Kevin,Brian; > > > > > > I have been trying to set up use of radiousb instead of simpleusb. I see here Brian is doing that with the issues he is having. > > > I can't get nearly that far. > > > I am running hamvoip rc19 on some and recently downloaded stretch. > > > In both cases I set the usbradio module to load however I cannot get the driver to work and keep getting asterisk failures. > > > Additionally the menus set up by the programmer show only simpleusb-radio-tune not radio-tune-menu. > > > Is there another image or procedure I need to run to get this started? > > > > > > Tnx, > > > Mark > > > WB2ERS > > > > > > -----Original Message----- > > > From: App\_rpt-users > > > [mailto:app\_rpt-users-bounces@lists.allstarlink.org] On Behalf Of > > > Kevin Custer > > > Sent: Monday, December 24, 2018 2:57 PM > > > To: Users of Asterisk app\_rpt; Brian G > > > Subject: Re: [App\_rpt-users] CM119 USB interface > > > > > > On 12/24/2018 12:21 AM, Brian G wrote: > > > > > > > Ok, I'm thick sometimes 🙂 I get what you're saying now, makes sense. > > > > Thank you for the clarification. The Motorola is working as you > > > > described, the other rigs not so much. > > > > > > > > So the gist of it is, there's no way to use DSP carrier detect > > > > without using discriminator audio? It's CTCSS or VOX only in that case? > > > > > > Correct - > > > > > > BUT, discriminator audio should be available from that M120 radio. You just have to hook it up and possibly program it correctly. > > > > > > Kevin > > > \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ > > > App\_rpt-users mailing list > > > App\_rpt-users@lists.allstarlink.org > > > [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app\_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users) > > > > > > To unsubscribe from this list please visit [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app\_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users) and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" > > > You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem. > > > \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ > > > App\_rpt-users mailing list > > > App\_rpt-users@lists.allstarlink.org > > > [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app\_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users) > > > > > > To unsubscribe from this list please visit [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app\_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users) and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" > > > You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem. > > > > \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ > > App\_rpt-users mailing list > > App\_rpt-users@lists.allstarlink.org > > [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app\_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users) > > > > To unsubscribe from this list please visit [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app\_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users) and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" > > You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem. > > \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ > > App\_rpt-users mailing list > > App\_rpt-users@lists.allstarlink.org > > [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app\_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users) > > > > To unsubscribe from this list please visit [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app\_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users) and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" > > You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem. ---
**Author:** ![Mike](https://community.allstarlink.org/user_avatar/community.allstarlink.org/mike/32/1569_2.png) [@Mike](https://community.allstarlink.org/u/Mike)\ **Post date:** [January 1, 2019, 5:33pm UTC](https://community.allstarlink.org/t/cm119-usb-interface/14678/14 "2019-01-01T17:33:44Z")
Mark, I will have to insist we are not fixing/testing a hamvoip version. Not to be coy, just I don't know the differences and don't want to waste my time or yours. ...mike/kb8jnm > **···** > > On 1/1/2019 12:26 PM, Mark DuMoulin wrote: > > > Mike, > > > > Thanks for the reply. Here is what I have in the HamVoip RC.19 > > > > Rpt.conf > > > > [1400] ; Change this to your assigned node number > > > > ; Channel Driver settings > >                                  ; Define a channel driver to use and which > >                                  ; interface within that channel driver > >                                  ; To define a radioless node use the > >                                  ; psuedo channel driver - rxchannel=dahdi/pseudo > > rxchannel=Radio/usb1400 > >                                  ; Example usbradio channel driver > > ;rxchannel=SimpleUSB/usb > >                                  ; Example simpleusb channel driver > > ;rxchannel=dahdi/pseudo > >                                  ; Example pseudo channel driver > > > > List of programs in asterisk > > > > [root@1400\_Home\_Test asterisk]# ls > > amd.conf indications.conf > > asterisk.conf local > > chan\_dahdi.conf logger.conf > > dnsmgr.conf manager.conf > > dundi.conf modules.conf > > echolink.xxx rpt.conf > > extensions.conf rpt.conf.sample > > extensions.conf\_2018.12.30.2105 rpt.conf\_2018.12.30.2105 > > extensions.conf\_2018.12.30.2113 rpt.conf\_2018.12.30.2113 > > extensions.conf\_2018.12.30.2114 rpt.conf\_2018.12.30.2114 > > extensions.conf\_orig rpt.conf\_orig > > features.conf simpleusb.conf > > iax.conf simpleusb.conf\_2018.12.30.2113 > > iax.conf\_2018.12.30.2105 simpleusb.conf\_2018.12.30.2115 > > iax.conf\_2018.12.30.2113 simpleusb\_tune\_usb.conf > > iax.conf\_2018.12.30.2114 sip.conf > > iax.conf\_orig usbradio.conf.xxx > > > > usbradio.conf.xxx > > > > ; Usbradio channel driver Configuration File > > ; > > > > [general] > > > > [usb1400] > > > > hdwtype=0 > > rxboost=1 > > txboost=1 > > rxctcssrelax=1 > > txctcssdefault=100.0 > > rxctcssfreqs=100.0 > > txctcssfreqs=100.0 > > ;rxctcssoverride=0 > > carrierfrom=dsp > > ctcssfrom=dsp > > rxdemod=flat > > txprelim=yes > > txlimonly=no > > txtoctype=notone > > txmixa=composite > > txmixb=0 > > invertptt=0 > > duplex=1 > > rxondelay=0 > > rxnoisefiltype=0 > > eeprom=0 > > > > #includeifexists custom/usbradio.conf > > > > Modules.conf > > > > ; > > ; Asterisk configuration file > > ; > > ; Module Loader configuration file > > ; > > > > [modules] > > autoload=yes > > ;noload=chan\_voter.so > > ;noload=chan\_usbradio.so > > ;noload=chan\_irlp.so > > ;noload=chan\_echolink.so > > ;noload=chan\_simpleusb.so > > noload=app\_hamvoip.so > > > > ;noload=res\_crypto.so > > ;noload=func\_callerid.so > > noload=chan\_oss.so > > noload=chan\_alsa.so > > noload=chan\_phone.so > > noload=res\_config\_pgsql.so > > noload=cdr\_pgsql.so > > noload=app\_radbridge.so > > noload=app\_festival.so > > noload=app\_queue.so > > noload=func\_odbc.so > > noload=chan\_mgcp.so > > noload=chan\_skinny.so > > noload=cdr\_custom.so > > noload=cdr\_csv.so > > noload=chan\_agent.so > > noload=chan\_simple2.so > > noload=func\_moh.so > > noload=res\_musiconhold.so > > noload=res\_speech.so > > noload=res\_odbc.so > > noload=res\_smdi.so > > noload=res\_config\_odbc.so > > noload=chan\_tlb.so > > noload=app\_milliwatt.so > > noload=app\_image.so > > noload=app\_sendtext.so > > noload=format\_h264.so > > noload=app\_hasnewvoicemail.so > > noload=app\_ices.so > > noload=app\_lookupblacklist.so > > noload=app\_voicemail.so > > noload=chan\_usrp.so > > noload=app\_lookupidname.so > > noload=app\_zapateller.so > > noload=format\_jpeg.so > > noload=app\_parkandannounce.so > > noload=app\_meetme.so > > noload=app\_settransfercapability.so > > noload=app\_amd.so > > noload=app\_followme.so > > noload=app\_transfer.so > > noload=app\_directed\_pickup.so > > noload=app\_flash.so > > noload=app\_page.so > > noload=app\_gps.so > > noload=pbx\_dundi.so > > noload=app\_setcallerid.so > > noload=app\_dictate.so > > noload=res\_adsi.so > > noload=app\_mp3.so > > noload=app\_privacy.so > > noload=app\_disa.so > > noload=app\_alarmreceiver.so > > noload=app\_externalirv.so > > noload=chan\_beagle.so > > noload=chan\_sip.so > > [global] > > > > -----Original Message----- > > From: App\_rpt-users [mailto:app\_rpt-users-bounces@lists.allstarlink.org] On Behalf Of Mike > > Sent: Tuesday, January 01, 2019 11:10 AM > > To: app\_rpt-users@lists.allstarlink.org > > Subject: Re: [App\_rpt-users] CM119 USB interface > > > > Mark, > > > > Can you show me the line in your rpt.conf where you are loading the channel. > > > > ie rxchannel = Radio/usb\_29285 > > > > And your usbradio.conf file text > > > > ...mike/kb8jnm > > > > What > > > > On 1/1/2019 9:19 AM, Mark DuMoulin wrote: > > > > > Kevin,Brian; > > > > > > I have been trying to set up use of radiousb instead of simpleusb. I see here Brian is doing that with the issues he is having. > > > I can't get nearly that far. > > > I am running hamvoip rc19 on some and recently downloaded stretch. > > > In both cases I set the usbradio module to load however I cannot get the driver to work and keep getting asterisk failures. > > > Additionally the menus set up by the programmer show only simpleusb-radio-tune not radio-tune-menu. > > > Is there another image or procedure I need to run to get this started? > > > > > > Tnx, > > > Mark > > > WB2ERS > > > > > > -----Original Message----- > > > From: App\_rpt-users > > > [mailto:app\_rpt-users-bounces@lists.allstarlink.org] On Behalf Of > > > Kevin Custer > > > Sent: Monday, December 24, 2018 2:57 PM > > > To: Users of Asterisk app\_rpt; Brian G > > > Subject: Re: [App\_rpt-users] CM119 USB interface > > > > > > On 12/24/2018 12:21 AM, Brian G wrote: > > > > > > > Ok, I'm thick sometimes 🙂 I get what you're saying now, makes sense. > > > > Thank you for the clarification. The Motorola is working as you > > > > described, the other rigs not so much. > > > > > > > > So the gist of it is, there's no way to use DSP carrier detect > > > > without using discriminator audio? It's CTCSS or VOX only in that case? > > > > > > Correct - > > > > > > BUT, discriminator audio should be available from that M120 radio. You just have to hook it up and possibly program it correctly. > > > > > > Kevin > > > \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ > > > App\_rpt-users mailing list > > > App\_rpt-users@lists.allstarlink.org > > > [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app\_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users) > > > > > > To unsubscribe from this list please visit [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app\_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users) and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" > > > You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem. > > > \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ > > > App\_rpt-users mailing list > > > App\_rpt-users@lists.allstarlink.org > > > [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app\_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users) > > > > > > To unsubscribe from this list please visit [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app\_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users) and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" > > > You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem. > > > > \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ > > App\_rpt-users mailing list > > App\_rpt-users@lists.allstarlink.org > > [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app\_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users) > > > > To unsubscribe from this list please visit [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app\_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users) and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" > > You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem. > > \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ > > App\_rpt-users mailing list > > App\_rpt-users@lists.allstarlink.org > > [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app\_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users) > > > > To unsubscribe from this list please visit [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app\_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users) and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" > > You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem. ---
**Author:** ![W3KKC](https://community.allstarlink.org/user_avatar/community.allstarlink.org/w3kkc/32/442_2.png) [@W3KKC](https://community.allstarlink.org/u/W3KKC)\ **Post date:** [January 1, 2019, 5:33pm UTC](https://community.allstarlink.org/t/cm119-usb-interface/14678/15 "2019-01-01T17:33:49Z")
In looking at your config (quickly) it looks like you aren't loading chan usb in the modules. Kevin > **···** > > On 1/1/2019 12:25 PM, Mark DuMoulin wrote: > > > Kevin, > > > > I downloaded ASL 1.01 and had the same issue as with the RC.19 > > When I try to use it asterisk fails claiming to not find the chan. > > > > I'll put it back in and try again to give you feedback. > > > > Tnx! > > Mark ---
**Author:** ![Mike](https://community.allstarlink.org/user_avatar/community.allstarlink.org/mike/32/1569_2.png) [@Mike](https://community.allstarlink.org/u/Mike)\ **Post date:** [January 1, 2019, 5:38pm UTC](https://community.allstarlink.org/t/cm119-usb-interface/14678/16 "2019-01-01T17:38:41Z")
LOL, I did not scroll down far enough to see that. Good catch. ...mike/kb8jnm > **···** > > On 1/1/2019 12:33 PM, Kevin Custer wrote: > > > In looking at your config (quickly) it looks like you aren't loading chan usb in the modules. > > > > Kevin > > > > On 1/1/2019 12:25 PM, Mark DuMoulin wrote: > > > > > Kevin, > > > > > > I downloaded ASL 1.01 and had the same issue as with the RC.19 > > > When I try to use it asterisk fails claiming to not find the chan. > > > > > > I'll put it back in and try again to give you feedback. > > > > > > Tnx! > > > Mark > > > > \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ > > App\_rpt-users mailing list > > App\_rpt-users@lists.allstarlink.org > > [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app\_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users) > > > > To unsubscribe from this list please visit [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app\_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users) and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" > > You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem. ---
**Author:** ![larry](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/l/47e85d/32.png) [@larry](https://community.allstarlink.org/u/larry)\ **Post date:** [January 1, 2019, 7:09pm UTC](https://community.allstarlink.org/t/cm119-usb-interface/14678/17 "2019-01-01T19:09:45Z")
Kevin & Mike, ``` Did I miss another response somewhere? It appears to me Mark has the noload=chan_usbradio.so commented out ``` so shouldn’t it load automatically upon reboot of the system? ``` As a suggestion I would then stop the loading of chan_simpleusb.so ``` to avoid any conflicts. ``` My other question is how has he configured USB and does it match the ``` same port each time the device is plugged in. ``` Larry - N7FM ``` > **···** > > ```auto > ; Module Loader configuration file > ; > [modules] > autoload=yes > ;noload=chan_voter.so > **;noload=chan_usbradio.so** > ;noload=chan_irlp.so > ;noload=chan_echolink.so > ;noload=chan_simpleusb.so > noload=app_hamvoip.so > ;noload=res_crypto.so > ;noload=func_callerid.so > noload=chan_oss.so > noload=chan_alsa.so > noload=chan_phone.so > > ``` > > On 1/1/19 9:33 AM, Kevin Custer wrote: > > > ``` > > In > > > > ``` > > > > looking at your config (quickly) it looks like you aren’t loading > > chan usb in the modules. > > > > ``` > > Kevin > > > > On 1/1/2019 12:25 PM, Mark DuMoulin wrote: > > > > ``` > > > > > ``` > > > Kevin, > > > > > > I downloaded ASL 1.01 and had the same issue as with the RC.19 > > > > > > When I try to use it asterisk fails claiming to not find the > > > > > > ``` > > > > > > chan. > > > > > > ``` > > > I'll put it back in and try again to give you feedback. > > > > > > Tnx! > > > > > > Mark > > > > > > ``` > > > > ``` > > _______________________________________________ > > > > App_rpt-users mailing list > > > > To unsubscribe from this list please visit > > > > ``` > > > > and scroll down to the bottom of the page. Enter your email > > address and press the “Unsubscribe or edit options button” > > You do not need a password to unsubscribe, you can do it via email > > confirmation. If you have trouble unsubscribing, please send a > > message to the list detailing the problem. > > [App\_rpt-users@lists.allstarlink.org](mailto:App_rpt-users@lists.allstarlink.org) > [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app\_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users) > > [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app\_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users) ---
**Author:** ![Nate\_Hardman](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/n/cdc98d/32.png) [@Nate\_Hardman](https://community.allstarlink.org/u/Nate_Hardman)\ **Post date:** [January 1, 2019, 9:35pm UTC](https://community.allstarlink.org/t/cm119-usb-interface/14678/18 "2019-01-01T21:35:24Z")
ensure the module chan\_usbradio.so is loading in /etc/asterisk/modules.conf ensure that rxchannel = radio/usb\_NODNUMBER in /etc/asterisk/rpt.conf you also need to make sure the file usbradio\_tune\_usb\_NODENUMBER.conf exist in /etc/asterisk and edit the file replacing the default node number 1999 (most likely) with your node number. Then you should be able to run radio-tune-menu > **···** > > Nathan Hardman > > [nhardman1428@gmail.com](mailto:nhardman1428@gmail.com) > > [N8THN@ARRL.NET](mailto:N8THN@ARRL.NET) ---
**Author:** ![Mark\_DuMoulin](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/m/e9c0ed/32.png) [@Mark\_DuMoulin](https://community.allstarlink.org/u/Mark_DuMoulin)\ **Post date:** [January 2, 2019, 5:06pm UTC](https://community.allstarlink.org/t/cm119-usb-interface/14678/19 "2019-01-02T17:06:56Z")
Kevin, Can different ctcss tones be associated with a single USBFOB identified and configured as a separate node? Tnx, Mark > **···** > > -----Original Message----- > From: Kevin Custer [mailto:kuggie@kuggie.com] > Sent: Tuesday, January 01, 2019 12:34 PM > To: Mark DuMoulin; Users of Asterisk app\_rpt > Subject: Re: [App\_rpt-users] CM119 USB interface > > In looking at your config (quickly) it looks like you aren't loading chan usb in the modules. > > Kevin > > On 1/1/2019 12:25 PM, Mark DuMoulin wrote: > > > Kevin, > > > > I downloaded ASL 1.01 and had the same issue as with the RC.19 When I > > try to use it asterisk fails claiming to not find the chan. > > > > I'll put it back in and try again to give you feedback. > > > > Tnx! > > Mark ---
**Author:** ![Mike](https://community.allstarlink.org/user_avatar/community.allstarlink.org/mike/32/1569_2.png) [@Mike](https://community.allstarlink.org/u/Mike)\ **Post date:** [January 2, 2019, 5:18pm UTC](https://community.allstarlink.org/t/cm119-usb-interface/14678/20 "2019-01-02T17:18:56Z")
Mark, You can have different tones on the same fob but no separation for a node. While it 'might' be possible to separate left and right channel audio for 2 nodes if configured, you would need to separate cos/ptt sources not on the same fob, like using Parallel port etc. Can't advise better since you did not state all the methods used. ...mike/kb8jnm > **···** > > On 1/2/2019 12:06 PM, Mark DuMoulin wrote: > > > Kevin, > > > > Can different ctcss tones be associated with a single USBFOB identified and configured as a separate node? > > > > Tnx, > > > > Mark > > > > -----Original Message----- > > From: Kevin Custer [mailto:kuggie@kuggie.com] > > Sent: Tuesday, January 01, 2019 12:34 PM > > To: Mark DuMoulin; Users of Asterisk app\_rpt > > Subject: Re: [App\_rpt-users] CM119 USB interface > > > > In looking at your config (quickly) it looks like you aren't loading chan usb in the modules. > > > > Kevin > > > > On 1/1/2019 12:25 PM, Mark DuMoulin wrote: > > > > > Kevin, > > > > > > I downloaded ASL 1.01 and had the same issue as with the RC.19 When I > > > try to use it asterisk fails claiming to not find the chan. > > > > > > I'll put it back in and try again to give you feedback. > > > > > > Tnx! > > > Mark > > > > \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ > > App\_rpt-users mailing list > > App\_rpt-users@lists.allstarlink.org > > [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app\_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users) > > > > To unsubscribe from this list please visit [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app\_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users) and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" > > You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem. [Next page](https://community.allstarlink.org/t/cm119-usb-interface/14678.md?page=2)