Simplex node with RPi and discriminator audio
I'm wondering if this is a realistic configuration for a simplex node: RPi3 with DMK URI connected to the 9600 audio in and out signals of an Alinco DR-135T. I want to be able to use CTCSS so that random signals don't get bridged to connected nodes. My concern is that with the above configuration, the CTCSS decode in the radio is bypassed. Consequently, CTCSS decode needs to be done via usbradio since simpleusb does not have this capability. However, I keep hearing that usbradio is not handled well with an RPi and yields less than ideal audio quality. So all of the above implies that I either use a higher performance node PC or continue to use the RPi, switch to the 2400 audio in and out signals (so that the Alinco can handle the CTCSS) and use simpleusb. Opinions? Thanks, Keith KF7DRV
Keith, When I have a chance, I will give the USBradio with rx discriminator audio a test on the Pi 3 and tell you what my results are. I think it just might work fine now that we have a Pi 3's. 73 Marshall - ke6pcv From: App_rpt-users [mailto:app_rpt-users-bounces@lists.allstarlink.org] On Behalf Of Keith Williamson Sent: Sunday, May 05, 2019 11:37 AM To: Users of Asterisk app_rpt Subject: [App_rpt-users] Simplex node with RPi and discriminator audio I'm wondering if this is a realistic configuration for a simplex node: RPi3 with DMK URI connected to the 9600 audio in and out signals of an Alinco DR-135T. I want to be able to use CTCSS so that random signals don't get bridged to connected nodes. My concern is that with the above configuration, the CTCSS decode in the radio is bypassed. Consequently, CTCSS decode needs to be done via usbradio since simpleusb does not have this capability. However, I keep hearing that usbradio is not handled well with an RPi and yields less than ideal audio quality. So all of the above implies that I either use a higher performance node PC or continue to use the RPi, switch to the 2400 audio in and out signals (so that the Alinco can handle the CTCSS) and use simpleusb. Opinions? Thanks, Keith KF7DRV
Keith, I've run usbradio on many Raspberry Pi 3's without issue. The 3B+ works fine with 2 nodes on usbradio, but I don't really recommend it. I also don't recommend a CM119B based radio adapter for usbradio deployments for several reasons. Kevin On 5/5/2019 2:36 PM, Keith Williamson wrote:
I'm wondering if this is a realistic configuration for a simplex node:
RPi3 with DMK URI connected to the 9600 audio in and out signals of an Alinco DR-135T. I want to be able to use CTCSS so that random signals don't get bridged to connected nodes.
My concern is that with the above configuration, the CTCSS decode in the radio is bypassed. Consequently, CTCSS decode needs to be done via usbradio since simpleusb does not have this capability. However, I keep hearing that usbradio is not handled well with an RPi and yields less than ideal audio quality.
So all of the above implies that I either use a higher performance node PC or continue to use the RPi, switch to the 2400 audio in and out signals (so that the Alinco can handle the CTCSS) and use simpleusb.
Opinions?
Thanks,
Keith KF7DRV
I'm using an old Motorola R100 repeater. It's got the DCS option that can not be turned off. I'm running it on a Pi3B, and usbradio and full duplex with no issues, and fixing to add a 2m node to it, on simplex, with the antenna on top of the db-413 who's base is at 50'. It is the setup I had at my previous residence sans the rpi3b. Gonna be interesting. 73 = Best Regards, W5OMR / 29655 On Sun, May 5, 2019, 20:41 Kevin Custer <kuggie@kuggie.com> wrote:
Keith,
I've run usbradio on many Raspberry Pi 3's without issue. The 3B+ works fine with 2 nodes on usbradio, but I don't really recommend it. I also don't recommend a CM119B based radio adapter for usbradio deployments for several reasons.
Kevin
On 5/5/2019 2:36 PM, Keith Williamson wrote:
I'm wondering if this is a realistic configuration for a simplex node:
RPi3 with DMK URI connected to the 9600 audio in and out signals of an Alinco DR-135T. I want to be able to use CTCSS so that random signals don't get bridged to connected nodes.
My concern is that with the above configuration, the CTCSS decode in the radio is bypassed. Consequently, CTCSS decode needs to be done via usbradio since simpleusb does not have this capability. However, I keep hearing that usbradio is not handled well with an RPi and yields less than ideal audio quality.
So all of the above implies that I either use a higher performance node PC or continue to use the RPi, switch to the 2400 audio in and out signals (so that the Alinco can handle the CTCSS) and use simpleusb.
Opinions?
Thanks,
Keith KF7DRV
_______________________________________________ App_rpt-users mailing list App_rpt-users@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.
Keith, I just had a chance to test out your configuration. I happen to have all the hardware on hand. RPi 3 Model B with DMK URIxB connected to an Alinco DR-135 radio set for 9600 baud packet. (Discriminator Audio) I was able to set the audio levels and CTCSS levels without any issues. I used a service monitor to do so. Receive and transmit audio sounded fine. CTCSS decode/encode on the radio also seems to work using the USBradio channel driver. DSP squelch works well. I ran several tests using 100.0 Hz for CTCSS decode on the receiver. There may be one slight issue, but if you are running simplex node at home, it may not really be an issue, just something for you to be aware of. Here are my findings: 88.5Hz = NO decode falsing 91.5Hz = decode falsing 94.8Hz = decode falsing 97.4Hz = decode falsing 103.5Hz = decode falsing 107.2Hz = decode falsing 1109Hz = = NO decode falsing I hope this helps out. 73 Marshall - ke6pcv From: App_rpt-users [mailto:app_rpt-users-bounces@lists.allstarlink.org] On Behalf Of Keith Williamson Sent: Sunday, May 05, 2019 11:37 AM To: Users of Asterisk app_rpt Subject: [App_rpt-users] Simplex node with RPi and discriminator audio I'm wondering if this is a realistic configuration for a simplex node: RPi3 with DMK URI connected to the 9600 audio in and out signals of an Alinco DR-135T. I want to be able to use CTCSS so that random signals don't get bridged to connected nodes. My concern is that with the above configuration, the CTCSS decode in the radio is bypassed. Consequently, CTCSS decode needs to be done via usbradio since simpleusb does not have this capability. However, I keep hearing that usbradio is not handled well with an RPi and yields less than ideal audio quality. So all of the above implies that I either use a higher performance node PC or continue to use the RPi, switch to the 2400 audio in and out signals (so that the Alinco can handle the CTCSS) and use simpleusb. Opinions? Thanks, Keith KF7DRV
Hi Marshall, Thanks! Would you mind sharing both your usbradio.conf and usbradio_tune_usb*.conf? Those would provide a great baseline for me. I'll still need to tweak deviation but your settings should get me close. 73, Keith KF7DRV On Wed, May 8, 2019 at 5:51 PM Marshall Oldham <ke6pcv@cal-net.org> wrote:
Keith,
I just had a chance to test out your configuration. I happen to have all the hardware on hand.
RPi 3 Model B with DMK URIxB connected to an Alinco DR-135 radio set for 9600 baud packet. (Discriminator Audio)
I was able to set the audio levels and CTCSS levels without any issues. I used a service monitor to do so.
Receive and transmit audio sounded fine.
CTCSS decode/encode on the radio also seems to work using the USBradio channel driver.
DSP squelch works well.
I ran several tests using 100.0 Hz for CTCSS decode on the receiver.
There may be one slight issue, but if you are running simplex node at home, it may not really be an issue, just something for you to be aware of.
Here are my findings:
88.5Hz = NO decode falsing
91.5Hz = decode falsing
94.8Hz = decode falsing
97.4Hz = decode falsing
103.5Hz = decode falsing
107.2Hz = decode falsing
1109Hz = = NO decode falsing
I hope this helps out.
73
Marshall - ke6pcv
*From:* App_rpt-users [mailto:app_rpt-users-bounces@lists.allstarlink.org] *On Behalf Of *Keith Williamson *Sent:* Sunday, May 05, 2019 11:37 AM *To:* Users of Asterisk app_rpt *Subject:* [App_rpt-users] Simplex node with RPi and discriminator audio
I'm wondering if this is a realistic configuration for a simplex node:
RPi3 with DMK URI connected to the 9600 audio in and out signals of an Alinco DR-135T. I want to be able to use CTCSS so that random signals don't get bridged to connected nodes.
My concern is that with the above configuration, the CTCSS decode in the radio is bypassed. Consequently, CTCSS decode needs to be done via usbradio since simpleusb does not have this capability. However, I keep hearing that usbradio is not handled well with an RPi and yields less than ideal audio quality.
So all of the above implies that I either use a higher performance node PC or continue to use the RPi, switch to the 2400 audio in and out signals (so that the Alinco can handle the CTCSS) and use simpleusb.
Opinions?
Thanks,
Keith
KF7DRV _______________________________________________ App_rpt-users mailing list App_rpt-users@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.
Keith, Sure not a problem. One item to consider so that these settings will work for everyone. Currently the DMK URIxB receive gain on Pin 21 is low, this is due to a resister value that is being changed in the next revision. If you do not have a URIxB and you have a URI or URIx you should be fine and can use pin 21 for the receiver input from the radio. If you have a URIxB then you should use Pin 9 on the URIxB along with the 1K resister and a non polarized 10uf Cap in series to protect the CM119B chip as there is no protection on pin 9 of the DMK URIxB. usbradio_tune_usb_45024.conf [usb_45024] ; name=usb_45024 ; devicenum=1 devstr=1-1.2:1.0 rxmixerset=500 txmixaset=640 txmixbset=500 rxvoiceadj=0.177778 rxctcssadj=0.177186 txctcssadj=100 rxsquelchadj=500 fever=1 usbradio.conf [general] [usb_45024] eeprom = 0 ; EEPROM installed: 0,1 ; 0 = no (default) ; 1 = yes hdwtype = 0 ; Leave this set to 0 for USB sound fobs modified using ; the instructions from usbfob.pdf. Use a setting of ; 1 is for Dingotel/Sph interfaces. rxboost = 1 ; 0 - 20db attenuator inserted ; 1 - 20db attenuator removed ; Set to 1 for additonal gain if using a low-level receiver output rxctcssrelax = 1 ; reduce talkoff from radios w/o CTCSS TX HPF ; Do not change this, leave this as a 1 rxsqhyst = 3000 ; Setting Squelch Hysteresis ; 3000 is the default amount. ; An amount of 500 seems good. ; Then set the squelch to the highest number revealed when doing a "radio ; tune rxsquelch" - running the command multiple (like 20) times in a row. ; <http://allstarnode.com/wiki/lib/exe/fetch.php?media=asterisk-notes-wj8g.pdf> txctcssdefault = 100.0 ; default TX CTCSS frequency, any frequency permitted rxctcssfreqs = 100.0,91.5 ; RX CTCSS frequencies list in floating point. must be in table txctcssfreqs = 100.0,91.5 ; TX CTCSS frequencies list. any frequency permitted. will follow RX CTCSS frequency rxctcssoverride = 0 ; Set to 1 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 USB sound fob (Active high) ; usbinvert - from the inverted COR line on the USB sound fob (Active low) ; dsp - from RX noise using DSP techniques ; vox - voice activated from RX audio ctcssfrom = dsp ; no,usb,usbinvert,dsp ; no - no CTCSS decoding, system will be carrier squelch ; usb - from the CTCSS line on the USB sound fob (Active high) ; usbinvert - from the inverted CTCSS line on the USB sound fob (Active low) ; 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 rxsquelchdelay = 30 ; delayline in ms carrier squelch tail eliminator rxondelay = 0 ; Number of 20mSec intervals following the release of PTT. ; Uncomment and/or adjust for simplex nodes to eliminate "Ping Ponging" ; or "Relay Racing". A positive value here will instruct the usbradio ; driver to ignore the COR line for a specified number of 20mSec ; intervals following the release of PTT. Use this ONLY on simplex ; nodes, and leave commented out for repeaters or other full duplex nodes. txboost = 0 ; Add transmitter audio gain boost: 0,1 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 = yes ; 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 = notone ; 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 = composite ; 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 = no ; Right 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 invertptt = 0 ; Invert PTT: 0,1 ; 0 - ground to transmit ; 1 - open to transmit duplex = 0 ; Duplex 0,1 ; 0 - half duplex ; 1 - full duplex duplex3 = 0 ; duplex 3 gain setting (0 to disable) ??? #includeifexists custom/usbradio.conf I hope this helps you out. 73 Marshall - ke6pcv From: App_rpt-users [mailto:app_rpt-users-bounces@lists.allstarlink.org] On Behalf Of Keith Williamson Sent: Thursday, May 09, 2019 7:30 AM To: Users of Asterisk app_rpt Subject: Re: [App_rpt-users] Simplex node with RPi and discriminator audio Hi Marshall, Thanks! Would you mind sharing both your usbradio.conf and usbradio_tune_usb*.conf? Those would provide a great baseline for me. I'll still need to tweak deviation but your settings should get me close. 73, Keith KF7DRV On Wed, May 8, 2019 at 5:51 PM Marshall Oldham <ke6pcv@cal-net.org> wrote: Keith, I just had a chance to test out your configuration. I happen to have all the hardware on hand. RPi 3 Model B with DMK URIxB connected to an Alinco DR-135 radio set for 9600 baud packet. (Discriminator Audio) I was able to set the audio levels and CTCSS levels without any issues. I used a service monitor to do so. Receive and transmit audio sounded fine. CTCSS decode/encode on the radio also seems to work using the USBradio channel driver. DSP squelch works well. I ran several tests using 100.0 Hz for CTCSS decode on the receiver. There may be one slight issue, but if you are running simplex node at home, it may not really be an issue, just something for you to be aware of. Here are my findings: 88.5Hz = NO decode falsing 91.5Hz = decode falsing 94.8Hz = decode falsing 97.4Hz = decode falsing 103.5Hz = decode falsing 107.2Hz = decode falsing 1109Hz = = NO decode falsing I hope this helps out. 73 Marshall - ke6pcv From: App_rpt-users [mailto:app_rpt-users-bounces@lists.allstarlink.org] On Behalf Of Keith Williamson Sent: Sunday, May 05, 2019 11:37 AM To: Users of Asterisk app_rpt Subject: [App_rpt-users] Simplex node with RPi and discriminator audio I'm wondering if this is a realistic configuration for a simplex node: RPi3 with DMK URI connected to the 9600 audio in and out signals of an Alinco DR-135T. I want to be able to use CTCSS so that random signals don't get bridged to connected nodes. My concern is that with the above configuration, the CTCSS decode in the radio is bypassed. Consequently, CTCSS decode needs to be done via usbradio since simpleusb does not have this capability. However, I keep hearing that usbradio is not handled well with an RPi and yields less than ideal audio quality. So all of the above implies that I either use a higher performance node PC or continue to use the RPi, switch to the 2400 audio in and out signals (so that the Alinco can handle the CTCSS) and use simpleusb. Opinions? Thanks, Keith KF7DRV _______________________________________________ App_rpt-users mailing list App_rpt-users@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.
participants (4)
-
ARS W5OMR -
Keith Williamson -
Kevin Custer -
Marshall Oldham