[arm-allstar] No Rx On Echolink.
Kenneth Grimard
n1dot1 at gmail.com
Sun Jul 30 16:30:37 EST 2017
your welcome
i had to do the same when creating a link to my dr-1x via
an ftm-400dr radio to the repeater.
I also had to shorten the tail on my repeater to almost no tail also.
my link radio also handles both allstar node ras-pi and a wires-x node
via a hamstir-x
interface. this allows me to use the same link radio for both at the
same time.
http://www.onechipdesign.com/hamstir_x/hamstir_x_en.html
ken n1dot
On 7/30/2017 5:22 PM, Stephen Grob wrote:
> Ken,
> nounkeyct=1 did the trick! :-)
>
> And thanks for the link to the rpt.conf reference. That will help me a lot in the future.
>
> Once again, a really fast reply that fixed my issue immediately.
>
> You guys are awesome.
>
> 73,
> Steve
> KD9AER
>
>> On Jul 30, 2017, at 2:40 PM, Kenneth Grimard via arm-allstar <arm-allstar at hamvoip.org> wrote:
>>
>> try using
>>
>> nounkeyct=1 in your rpt.conf node stanza
>>
>> the will stop the node from transmitting after carrier drop from the repeater
>> but still allow a courtesy status tones from the network.
>>
>> if that does not work use duplex=0 in your rpt.conf node stanza. that will stop all courtesy tones and tails from the allstar node.
>>
>> |;duplex = 2 ; (Optional) set duplex operating mode ;; 0 = half duplex (telemetry and courtesy tones do not transmit) ;; 1 = semi-half duplex (telemetry and courtesy tones transmit, but not ;; repeated audio ;; 2 = normal full-duplex mode (Default) ;; 3 = full-duplex mode, without repeated audio from main input source ;; 4 - Normal except no main repeat audio during autopatch only|
>>
>>
>>
>> ken n1dot
>>
>>
>>
>> On 7/30/2017 3:26 PM, "Steve via arm-allstar" wrote:
>>> Node still running great but with one small annoyance.
>>>
>>> eg. Node transceiver receives transmission from repeater. At the end of every receive, node transmitter keys up momentarily then un-keys. Happens every time and very consistent. I tried changing RXONDELAY and RXAUDIODELAY in simpleusb menu but neither had any effect.
>>>
>>> Any suggestions?
>>>
>>> 73
>>> Steve
>>> KD9AER
>>>
>>>> On Jun 27, 2017, at 7:20 AM, Steve <sgrob at mtco.com> wrote:
>>>>
>>>> Doug,
>>>> You hit the nail on the head! I rewired the cable according to your info and it works!
>>>>
>>>> Set Tx and Rx levels and it sounds great!
>>>>
>>>> Now, have to reconfigure for the node sitting on the repeater location network, turn off time hack, courtesy tones and a few other simple things at it will be ready for the club to enjoy. To Do’s for everything I need to do are documented on the website.
>>>>
>>>> Thanks to all for your contributions. Your website is very well documented and supported and very much appreciated!
>>>>
>>>> Steve
>>>> KD9AER
>>>>
>>>>> On Jun 26, 2017, at 12:39 PM, Doug Crompton <wa3dsp at gmail.com <mailto:wa3dsp at gmail.com>> wrote:
>>>>>
>>>>> OK, That radio has the same DB9 wiring as the Alinco's. It looks like it should be COSFROM=usbinvert. The COS line goes low on carrier or PL. This is an open collector output so you will not see any voltage change unless it is connected to the DMK-URI which has a pullup for COS. Here is how it should be wired -
>>>>>
>>>>> DMK-URI DB25 Male Alinco DB9 male
>>>>> COS 8 1
>>>>> RX Audio 21 4
>>>>> GND 19,20 5
>>>>> PTT 1 7
>>>>> TX Audio 22 9
>>>>>
>>>>>
>>>>> Doug
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Mon, Jun 26, 2017 at 12:58 PM, Steve <sgrob at mtco.com <mailto:sgrob at mtco.com>> wrote:
>>>>> The node radio is a Yaesu FT2600M. Using DMK URIx. I did not wire the cable but it was supposedly used with this radio in a previous Echolink node.
>>>>>
>>>>> Any suggestions on where to find pinouts for this application?
>>>>>
>>>>> I will check voltages.
>>>>>
>>>>> 73
>>>>> Steve
>>>>> KD9AER
>>>>>
>>>>>
>>>>>> On Jun 26, 2017, at 11:50 AM, Doug Crompton via arm-allstar <arm-allstar at hamvoip.org <mailto:arm-allstar at hamvoip.org>> wrote:
>>>>>>
>>>>>> Steve,
>>>>>>
>>>>>> It sounds like you have a COS problem from the node radio. Without COS you
>>>>>> will get no audio as you are experiencing. You should see a change in
>>>>>> COSFROM when the ht is keyed and unkeyed into the node radio.
>>>>>>
>>>>>> What radio are you using for the node radio? What FOB are you using? Did
>>>>>> you wire the connections or someone else?
>>>>>>
>>>>>>
>>>>>> *73 Doug*
>>>>>>
>>>>>> *WA3DSP*
>>>>>>
>>>>>> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio> <http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>>*
>>>>>>
>>>>>>
>>>>>> On Mon, Jun 26, 2017 at 11:38 AM, Steve <sgrob at mtco.com <mailto:sgrob at mtco.com>> wrote:
>>>>>>
>>>>>>> Yes, I agree - get the radio link working as that is where the problem
>>>>>>> lies.
>>>>>>> Goal is to make an Echolink node that sits in our club repeater room and
>>>>>>> transmits at low power for members to use while traveling.
>>>>>>>
>>>>>>> I see where the confusion is I think. I didn’t do a good job describing my
>>>>>>> problem. Allow me to try again.
>>>>>>>
>>>>>>> I have the node radio and my ht both tuned to the same simplex frequency.
>>>>>>> I have no problem connecting to the node with my cell phone echolink app.
>>>>>>> When I key the cell phone app and speak, I can hear my voice clearly on
>>>>>>> the ht speaker.
>>>>>>> So far, so good.
>>>>>>> When I key the ht and speak, I hear nothing on the cell phone app. This is
>>>>>>> the problem.
>>>>>>>
>>>>>>> I choose item 2 on simpleusb-tune-menu and see the following:
>>>>>>> Please enter your selection now: 2
>>>>>>> RX VOICE DISPLAY:
>>>>>>>
>>>>>>> v -- 3KHz v -- 5KHz
>>>>>>> When I key the ht and speak, nothing changes on the RX level display and I
>>>>>>> still don’t hear anything on the cell phone app.
>>>>>>> I change the RX level to 999 and key the ht again but still don’t see
>>>>>>> anything change on the RX level display and of course nothing heard on the
>>>>>>> cell phone app.
>>>>>>>
>>>>>>> The above was all done with the volume turned all the way down on the node
>>>>>>> radio. If I turn the volume up on the node radio, I can hear everything
>>>>>>> (through the node radio speaker) when I key the ht and speak. But do not
>>>>>>> hear anything through the cell phone app.
>>>>>>>
>>>>>>> When I key the ht, COS status does not change - it remains in CLEAR status
>>>>>>> whether the ht is keyed or not. So, I assume this means I need to change
>>>>>>> COSFROM from usbinvert to USB. But if I change COSFROM to USB then I get
>>>>>>> the hash on the cell phone and COS status is keyed whether the ht is keyed
>>>>>>> or not.
>>>>>>>
>>>>>>> 73
>>>>>>> Steve
>>>>>>> KD9AER
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Jun 26, 2017, at 9:42 AM, Doug Crompton via arm-allstar <
>>>>>>> arm-allstar at hamvoip.org <mailto:arm-allstar at hamvoip.org>> wrote:
>>>>>>>
>>>>>>> OK, as I said lets get the radio link working first. Then deal with
>>>>>>> echolink.
>>>>>>>
>>>>>>> When we refer to "radio keyed" we mean the radio talking TO your node
>>>>>>> radio. So if you key a handheld or whatever on the frequency and PL of
>>>>>>> your node radio the COSFROM should show keyed. With the handheld unkeyed it
>>>>>>> should show clear. If it is not doing this or doing the opposite then
>>>>>>> switch from usb to usbinvert or vica versa.
>>>>>>>
>>>>>>> When this is set correctly you should hear courtesy tone on unkey. The next
>>>>>>> thing you need to do, again in simpleusb-tune-menu, is set your levels.
>>>>>>> Item 2 on the menu is RX level. This is the level for your NODE radios rx.
>>>>>>> In other words what it hears FROM your handheld transmitting TO the node
>>>>>>> radio.The level shows on the screen as a bar graph and should kick up to
>>>>>>> 5-6khz on peaks. If not hit 'return' change the level and recheck. Be sure
>>>>>>> to save with the 'w' command before exiting if you change something.
>>>>>>>
>>>>>>> If this is not set correctly DTMF will either not work or will be erratic.
>>>>>>>
>>>>>>> You can check DTMF in the Asterisk client from the main menu. As you key
>>>>>>> and push the keys the ones selected should show on the screen. Key in 0-9*#
>>>>>>> and make sure they all decode.
>>>>>>>
>>>>>>> I am not sure what your ultimate goal is here? Do you just want to run
>>>>>>> Echolink or are you using Allstar? Echolink requires port forwarding. There
>>>>>>> is an Echolink howto on the hamvoip.org <http://hamvoip.org/> web page.
>>>>>>>
>>>>>>>
>>>>>>> *73 Doug*
>>>>>>>
>>>>>>> *WA3DSP*
>>>>>>>
>>>>>>> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio> <http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>>*
>>>>>>>
>>>>>>>
>>>>>>> What node radio are you using? What FOB?
>>>>>>>
>>>>>>> On Mon, Jun 26, 2017 at 9:44 AM, "Steve via arm-allstar" <
>>>>>>> arm-allstar at hamvoip.org <mailto:arm-allstar at hamvoip.org>> wrote:
>>>>>>>
>>>>>>> Since I was subscribed to daily digest and did not get Doug's reply to my
>>>>>>> post directly, I could not reply. I have since unsubscribed to daily digest
>>>>>>> as requested so should receive future replies to my posts directly. I have
>>>>>>> attached Doug’s reply at the bottom for reference.
>>>>>>>
>>>>>>> Doug,
>>>>>>> Here is my COS View with COSFROM set to usbinvert and the node radio not
>>>>>>> keyed:
>>>>>>> REALTIME RX TELEMETRY DISPLAY:
>>>>>>> COS | COS | COS | CTCSS | CTCSS | PTT
>>>>>>> (composite) | (input) | (test) | (input) | (override) |
>>>>>>> CLEAR | CLEAR | CLEAR | IGNORE | CLEAR | CLEAR
>>>>>>>
>>>>>>> Here is my COS View with COSFROM set to usbinvert with node radio keyed:
>>>>>>> REALTIME RX TELEMETRY DISPLAY:
>>>>>>> COS | COS | COS | CTCSS | CTCSS | PTT
>>>>>>> (composite) | (input) | (test) | (input) | (override) |
>>>>>>> CLEAR | CLEAR | CLEAR | IGNORE | CLEAR | KEYED
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Here is my COS View with COSFROM set to usb and the node radio not keyed:
>>>>>>> REALTIME RX TELEMETRY DISPLAY:
>>>>>>> COS | COS | COS | CTCSS | CTCSS | PTT
>>>>>>> (composite) | (input) | (test) | (input) | (override) |
>>>>>>> KEYED | KEYED | CLEAR | IGNORE | CLEAR | CLEAR
>>>>>>>
>>>>>>> At this point I hear continuous hash on the Echolink cell phone app and
>>>>>>> the transmit key is not available so can’t show you what the COS view with
>>>>>>> COSFROM set to usb. Hearing the same hash on the node radio too if I turn
>>>>>>> the volume up a bit.
>>>>>>>
>>>>>>> With the COSFROM set to usbinvert I do hear the courtesy tone when
>>>>>>> un-keying.
>>>>>>> Had to set Transmit level A and B to 999 to get it to sound right.
>>>>>>> It does play the time on the hour.
>>>>>>> Don’t know how to do DTMF yet.
>>>>>>> I get the same results if the cell phone is on my home network or using
>>>>>>> the cellular network.
>>>>>>>
>>>>>>> Here are current parameter values:
>>>>>>> Active simpleusb stanza: [usb]
>>>>>>> USB device String: 1-1.2:1.0
>>>>>>>
>>>>>>> Card is: 0
>>>>>>> Name is: usb
>>>>>>> Rx Level: 500
>>>>>>> Rx no-delay: 0
>>>>>>> Rx audio-delay: 1
>>>>>>> Tx A Level: 999
>>>>>>> Tx B Level: 999
>>>>>>> preemphasis: yes
>>>>>>> deemphasis: no
>>>>>>> plfilter: yes
>>>>>>> rxboost: yes
>>>>>>>
>>>>>>> PTT: Active LOW
>>>>>>> PTT status: Un-Keyed
>>>>>>>
>>>>>>> CTCSS (input): Ignored
>>>>>>> COS (input): CM108/CM119 Active LOW
>>>>>>> COS (test): Un-Keyed
>>>>>>> COS (composite): Un-Keyed
>>>>>>>
>>>>>>> 73
>>>>>>> Steve
>>>>>>> KD9AER
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Message: 2
>>>>>>> Date: Fri, 23 Jun 2017 17:42:40 -0400
>>>>>>> From: Doug Crompton <wa3dsp at gmail.com <mailto:wa3dsp at gmail.com> <mailto:wa3dsp at gmail.com <mailto:wa3dsp at gmail.com>
>>>>>>> <wa3dsp at gmail.com <mailto:wa3dsp at gmail.com>>>>
>>>>>>> To: ARM Allstar <arm-allstar at hamvoip.org <mailto:arm-allstar at hamvoip.org> <mailto:arm-allstar at hamvoip.org <mailto:arm-allstar at hamvoip.org>
>>>>>>> <arm-allstar at hamvoip.org <mailto:arm-allstar at hamvoip.org>>>>
>>>>>>> Subject: Re: [arm-allstar] No RX on Echolink.
>>>>>>> Message-ID:
>>>>>>> <CAMp6vsvT5Ob1hKsTTA=Gw62a8tKuRvZoE=OJMsmFUgvs6BNGu
>>>>>>> Q at mail.gmail.com <mailto:Q at mail.gmail.com> <mailto:CAMp6vsvT5Ob1hKsTTA <mailto:CAMp6vsvT5Ob1hKsTTA>=Gw62a8tKuRvZoE=
>>>>>>> OJMsmFUgvs6BNGuQ at mail.gmail.com <mailto:OJMsmFUgvs6BNGuQ at mail.gmail.com>>>
>>>>>>> Content-Type: text/plain; charset="UTF-8"
>>>>>>>
>>>>>>> Steve,
>>>>>>>
>>>>>>> First of all you need to have your radio setup correctly independent of
>>>>>>> Echolink. If you go into the simple-usb-tune-menu there is a 'v' option
>>>>>>> which allows you view the COS and PTT signals. When you key the radio
>>>>>>> talking to your node radio you should see a key indication in cos input.
>>>>>>> When you unkey it should show clear. If this is reversed you need to change
>>>>>>> either from usb to usbinvert or vica versa. Once you have this setup
>>>>>>> correctly you should hear a courtesy tone when you unkey and you should be
>>>>>>> able to use DTMF. Try *81 to see if it plays the time. You will also
>>>>>>> probably have to set the levels - items 2 and 3. All this is detailed in
>>>>>>> the setup instructions.
>>>>>>>
>>>>>>> Once that is setup you need to make sure echolink is setup correctly. There
>>>>>>> is also a howto on this on the web page - hamvoip.org <http://hamvoip.org/> <http://hamvoip.org/ <http://hamvoip.org/>
>>>>>>>> .
>>>>>>> You need to have
>>>>>>> port forwarding and you can only have one Echolink existence per public IP.
>>>>>>> If you do use a smart phone running echo link it must be using the cell
>>>>>>> network for Internet and not your local wifi where the Pi is running.
>>>>>>>
>>>>>>>
>>>>>>> *73 Doug*
>>>>>>>
>>>>>>> *WA3DSP*
>>>>>>>
>>>>>>> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio> <http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>> <
>>>>>>> http://www.crompton.com/hamradio <http://www.crompton.com/hamradio> <http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>>>*
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>>
>>>>>>> arm-allstar mailing list
>>>>>>> arm-allstar at hamvoip.org <mailto:arm-allstar at hamvoip.org>
>>>>>>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar <http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar>
>>>>>>>
>>>>>>> Visit the BBB and RPi2/3 web page - http://hamvoip.org <http://hamvoip.org/>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>>
>>>>>>> arm-allstar mailing list
>>>>>>> arm-allstar at hamvoip.org <mailto:arm-allstar at hamvoip.org>
>>>>>>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar <http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar>
>>>>>>>
>>>>>>> Visit the BBB and RPi2/3 web page - http://hamvoip.org <http://hamvoip.org/>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>> _______________________________________________
>>>>>>
>>>>>> arm-allstar mailing list
>>>>>> arm-allstar at hamvoip.org <mailto:arm-allstar at hamvoip.org>
>>>>>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar <http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar>
>>>>>>
>>>>>> Visit the BBB and RPi2/3 web page - http://hamvoip.org <http://hamvoip.org/>
>>>>>
>>> _______________________________________________
>>>
>>> arm-allstar mailing list
>>> arm-allstar at hamvoip.org
>>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>>>
>>> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>>
>>
>> ---
>> This email has been checked for viruses by Avast antivirus software.
>> https://www.avast.com/antivirus
>> _______________________________________________
>>
>> arm-allstar mailing list
>> arm-allstar at hamvoip.org
>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>>
>> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>
More information about the arm-allstar
mailing list