I stand corrected. You should be just fine though there is a duplex setting in usbradio.conf too.
http://ohnosec.org/drupal/node/84
···
On Jul 5, 2013 11:58 AM, “Joshua Hintze” joshh@imsar.com wrote:
Ok all I’m back to work today and playing with this setup again.
I was able to isolate a much better signal for COR than what I had before.
This now truely goes from 0V->5V only when receiving and not when
transmitting. However I’m still having issues.
As soon as asterisk receives a signal it immediately tries to transmit a
signal out. This then effectively pulls the PTT low and my receiver stops
receiving. It is almost like it is in duplex mode but I have in
usbradio.conf
duplex=0 ; Full Duplex
rxondelay=0 ; Uncomment and/or adjust for simplex nodes to
eliminate “Ping Ponging”
; or "Relay Racing". ; A positive value here will instruct the usbradiodriver to ignore the
; COR line for a specified number of 20mSecintervals following the
; release of PTT. Use this only on simplex nodes,and leave commented
; out for repeaters or other full duplex nodes.eeprom=1
Just for clarity I’ll post my entire usbradio.conf below:
[general]
[usb]
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-levelreceiver output
rxctcssrelax=1 ; reduce talkoff from radios w/o CTCSS Tx HPF
; Do not change this, leave this as a 1;txctcssdefault=100.0 ; default tx ctcss freq, any frequency permitted
;rxctcssfreqs=100.0 ; rx ctcss freqs in floating point. must be in table
;txctcssfreqs=100.0 ; tx ctcss freqs, any frequency permitted
rxctcssoverride=1 ; Set to 1 or yes to start out in carrier squelch
mode
carrierfrom=usb ; no,usb,usbinvert,dsp,vox
; no - no carrier detection at all ; usb - from the COR line on the modified USB soundfob
; usbinvert - from the inverted COR line on themodified USB sound fob
; dsp - from RX noise using dsp techniques ; vox - voice activated from RX audioctcssfrom=no ; no,usb,dsp
; no - CTCSS decoding, system will be carriersquelch
; 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 towork.
rxdemod=speaker ; input type from radio: no,speaker,flat
; no - RX audio input not used ; flat - Use RX audio from discriminator (beforede-emphasis)
; speaker - use de-emphasized audiotxprelim=no ; 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 modulatortxlimonly=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 butwith pre-emphasis.
txtoctype=no ; 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 beforeunkeying TX
; AKA ("chicken burst")txmixa=voice ; 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 headphonelevel for monitoring
txmixb=no ; Right channel output: no,voice,tone,composite,
auxvoice
; See txmixa above.invertptt=0 ; Invert PTT 0 = ground to transmit, 1 = open to
transmit
; This is the collector lead of the 2n4401 on themodified
; usb sound fob. ; please refer to the howto for the procedure to dothis.
duplex=0 ; Full Duplex
rxondelay=0 ; Uncomment and/or adjust for simplex nodes to
eliminate “Ping Ponging”
; or "Relay Racing". ; A positive value here will instruct the usbradiodriver to ignore the
; COR line for a specified number of 20mSecintervals following the
; release of PTT. Use this only on simplex nodes,and leave commented
; out for repeaters or other full duplex nodes.eeprom=1
Any thoughts on why asterisk would be trying to send a signal as soon as it
receives one? After the first time (upon asterisk restart) it receives a
signal it sends a beep followed by a morse code sequence.
Thanks,
Josh
-----Original Message-----
From: Corey Dean [mailto:n3fe@repeater.net]
Sent: Thursday, July 04, 2013 8:48 AM
To: Joshua Hintze; app_rpt-users@ohnosec.org
Subject: RE: [App_rpt-users] Issue with Hangup after first keying
Are you running full duplex on a simplex radio?
Corey N3FE
From: app_rpt-users-bounces@ohnosec.org [app_rpt-users-bounces@ohnosec.org]
On Behalf Of Joshua Hintze [joshh@imsar.com]
Sent: Wednesday, July 03, 2013 3:58 PM
Subject: [App_rpt-users] Issue with Hangup after first keying
Hello,
It is my first posting on here. I have ALMOST gotten the ACID installation
working. I’m using the URI interfaced to ACID and to my radio. The asterisk
can properly key the radio and its working just fine with that. I can also
connect to the node with iaxRpt directly with no problem and transmit OUT of
my radio.
However I am having some issues when my radio receives communication in that
as soon as I get my first radio RX, asterisk will then play a tone out of
the URI into the radio over and over again at about a one second interval.
In the asterisk terminal it just keeps repeating:
-- Hungup 'Zap/pseudo-1726358622' -- Hungup 'Zap/pseudo-1774817359' -- Hungup 'Zap/pseudo-691532115' -- Hungup 'Zap/pseudo-81389311' -- Hungup 'Zap/pseudo-465154784'– Hungup ‘Zap/pseudo-627058532’
-- Hungup 'Zap/pseudo-1656870264' -- Hungup 'Zap/pseudo-1671691803' -- Hungup 'Zap/pseudo-50274194'forever keeping my radio always keyed.
I have the COR from the radio going into the URI. I do not plan on using
CTCSS and have tried tying it to ground as well as tying it to the COR as
well. My usbradio.conf has the following:
carrierfrom=usb
ctcssfrom=no
I have tried also ctcssfrom=usb as well.
Any help would be appreciated.
Thanks,
Josh
–
This message was scanned and is believed to be clean.
Click here to report this message as
spam.<http://simba.repeater.net:8080/cgi-bin/learn-msg.cgi?id=6EF48221A.A93B
App_rpt-users mailing list