[App_rpt-users] Help on using CTCSS with usbradio.conf

Neil H. Gray neil at ohiogray.org
Wed Nov 1 02:42:17 UTC 2017


I apologize for the long delay.  Family life got in the way for a bit, 
and then I thought to check and double-check that I had implemented your 
suggestions faithfully. This was the usual "Because I waited so long I 
have to do better" type of paralysis.


Thank you Keith for the pinouts between the URIx and the BCR-40U. I have 
to wonder if suboptimal audio level settings might cause my issues.  I 
don't suppose that you have those audio levels documented.  I would 
expect that the levels would be nearly identical between any URIx+BCR 
combination.


Thank you for the suggestion Steve.  I implemented your usbradio.conf 
then made single adjustments until I could get something to happen.

For the moment, I can confirm that I do get a working CTCSS encoding.  
At least it is enough to open the squelch on a test radio.

For receive tests, my test criteria is watching to see the red tx light 
on the URIx or listening to the signal via the allstar node.

I have txmixa set to composite as I am connected to the left audio 
channel of the URIx.

carrierfrom = dsp    does not appear to work for me.  I have to leave 
this set on usbinvert for anything to work.

If the 'rxctcssoverride' parameter is set to '0' or commented, I can 
never open the squelch.   So I have to leave this as '1'.

ctcssfrom = dsp does not appear to do anything.  Even in this setting, 
any signal without CTCSS gets repeated.

I left the other settings identical.





On 10/23/2017 09:55 AM, Keith Goobie wrote:
> Neil
>
> We have a Bridgecom 220 repeater hooked to an RLC-DSP404.  Guidance regarding connectivity can be gained from -
>
> https://cdn.shopify.com/s/files/1/0833/9095/files/BCR_Repeater_to_URI.pdf?7576387813378094434
>
> https://cdn.shopify.com/s/files/1/0833/9095/files/BCR_to_RLC_Pinout_Diagram_b06dbd28-8f77-439b-9a74-3adc552f93a3.pdf?9343440214198702669
>
> Between these two documents, you should be able to connect things together.
>
> Keith
>
>> On Oct 22, 2017, at 9:47 PM, Steve Zingman <szingman at msgstor.com> wrote:
>>
>> See if this helps:
>>
>> txctcssdefault = 123.0    ; default tx ctcss freq, any frequency permitted
>>
>> rxctcssfreqs = 123.0    ; rx ctcss freqs in floating point. must be in table
>>
>> txctcssfreqs = 123.0    ; tx ctcss freqs, any frequency permitted
>> ; rxctcssoverride = 0    ; Set to 1 or yes to start out in carrier squelch mode
>>
>> carrierfrom = dsp    ; no,usb,usbinvert,dsp,vox
>>              ; no - no carrier detection at all
>>              ; usb - from the COR line on the modified USB sound fob
>>              ; usbinvert - from the inverted COR line on the modified USB sound fob
>>              ; dsp - from RX noise using dsp techniques
>>              ; vox - voice activated from RX audio
>>
>> ctcssfrom = dsp        ; no,usb,dsp
>>              ; no - CTCSS decoding, system will be carrier squelch
>>              ; usb - CTCSS decoding using input from USB FOB
>>              ; (currently not supported)
>>              ; dsp - CTCSS decoding using RX audio in DSP.
>>              ; rxdemod option must be set to flat for this to work.
>>
>> rxdemod = flat            ; input type from radio: no,speaker,flat
>>              ; no - RX audio input not used
>>              ; flat - Use RX audio from discriminator (before de-emphasis)
>>              ; speaker - use de-emphasized audio
>>
>> txprelim = yes        ; Audio processing on left output channel: no,yes
>>              ; no - Audio is not pre-emphasized and limited.
>>              ; Suitable for use on a microphone input
>>              ; yes - Audio is pre-emphasized and limited.
>>              ; Suitable for direct connection to an FM modulator
>>
>> txlimonly = no        ; Audio limiting with no pre-emphasis on output channel: no,yes
>>              ; no - Audio is not limited.
>>              ; yes - Audio is  limited.
>>              ; Suitable for transmitters with no limiting but with pre-emphasis.
>>
>> txtoctype = phase    ; Transmit tone control type: no,phase,notone
>>              ; no - CTCSS tone encoding with no hang time
>>              ; phase - encode CTCSS and reverse phase
>>              ; AKA ("reverse burst") before unkeying TX
>>              ; notone - encode CTCSS and stop sending tone before unkeying TX
>>              ; AKA ("chicken burst")
>>
>> txmixa = no        ; Left channel output: no,voice,tone,composite,auxvoice
>>              ; no - Do not output anything
>>              ; voice - output voice only
>>              ; tone - CTCSS tone only
>>              ; composite - voice and tone
>>              ; auxvoice - auxiliary voice output at headphone level for monitoring
>>
>> txmixb = composite    ; Right channel output: no,voice,tone,composite, auxvoice
>>              ; See txmixa above.
>>
>>
>>
>> On 10/22/2017 09:41 PM, Neil H. Gray wrote:
>>> To Whom It May Concern,
>>>
>>> I am trying to get a DMK URIx working with a BridgeCOM repeater using the usbradio.conf to provide CTCSS decode/encode and am having no success.
>>>
>>> I can confirm that a received FM signals get repeated, and the allstar configuration also appears to be working.  However any configuration related to CTCSS does not work at all.
>>>
>>> I can confirm that the CTCSS tone is present with the input audio being fed to the URIx, but none of the relevant settings in usbradio.conf(e.g. rxctcssfreqs, ctcssfrom = dsp) seem to have any effect.
>>>
>>> Adjusting the carrierfrom parameter in usbradio.conf has the expected results.  The COR signal comes to the URIx from the repeater and functions correctly with carrierfrom set to usbinvert.  At least with this I can confirm that apt_rpt is using usbradio.conf rather than simpleusb.conf.
>>>
>>> While I have tested the hardware, I have not tried looking at the software beyond glancing through the source code to get a rough idea of the layout of apt_rpt.
>>>
>>> Could anyone offer a working configuration example on CTCSS, or perhaps give debugging hints?
>>>
>>> I can handle a debugger but am not sure of a good way to debug a program that operates on signals in real time.
>>>
>>>
>>> Thanks in advance,
>>>
>>> Neil
>>>
>>> _______________________________________________
>>> App_rpt-users mailing list
>>> App_rpt-users at lists.allstarlink.org
>>> 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 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 at lists.allstarlink.org
>> 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 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 at lists.allstarlink.org
> 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 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.





More information about the App_rpt-users mailing list