[arm-allstar] Node keeps rekeying up

Wed Jul 25 12:18:12 EST 2018

Mike,

 Yes there is a way to have output PL follow input and it is detailed in a
howto -

https://hamvoip.org/hamradio/arm-allstar/documents/howtos/txctcss_bit_enable_howto.pdf

When using simpleusb you would need a separate tone encoder board key by
the txctcss bit connected to your transmitter.

*73 Doug*

*WA3DSP*

*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*

On Wed, Jul 25, 2018 at 12:28 PM, Mike Besemer - WM4B <mwbesemer at cox.net>
wrote:

> Doug,
>
> Copy all and fully understand.  All my repeaters transmit PL that follows
> the input.  Courtesy tones, announcements, idle ID's, etc are not
> transmitted with tone.
>
> With regard to the node, are you saying there is no means to control IP
> encode via HamVoIP?  To me, it would be very desirable to have the
> capability to set PL encode to follow the node input, thereby eliminating
> node IDs on the repeater system.
>
> The main reason I set PL to follow the input is to eliminate CTs and IDs
> from my Echolink node, but a side benefit of this method is that users can
> set their radio to decode my tone and never have to listen to the
> extraneous stuff.  If my node is always going to encode PL when it
> transmits, then they are always going to hear the node IDs.  Personally,
> I'd rather not have the node IDs go out over the system, especially when
> it's linked to our wide-area intertie.
>
> If controlling PL isn't an option via AVI at this time, perhaps it can be
> added in a future revision.  In the meantime, I can probably control encode
> directly from the COS line.
>
> Just my 2-cents worth.
>
> 73,
>
> Mike
> WM4B
>
> On Wed, Jul 25, 2018 at 11:51 AM, "Doug Crompton via arm-allstar" wrote:
>
> Connecting a simplex node to a repeater requires some planning and always
>> the permission of the repeater owner. I will call this the "poor mans" way
>> to get Allstar on the repeater. The best way is having Internet at the
>> repeater and interfacing Allstar there either using Allstar as the
>> repeater
>> controller or bringing it in on a port of an existing controller.
>>
>> In the event this is not possible there are things you can do to make it
>> work reasonably well. I personally have a repeater that does not have
>> access to the Internet and I use a remote simplex node to provide full
>> time
>> Allstar on that repeater. The key is to have the repeater PL follow the
>> input to the repeater not the output. Then your remote simplex node sees
>> keyups like they were coming directly from the input station to the
>> repeater and not the repeater itself thus eliminating the repeater tail
>> and
>> ID from being transmitted out over Allstar. This would require a change at
>> the repeater. The downside is that the repeater users would not hear the
>> repeater tail or ID either if they were using tone squelch. You could add
>> a
>> second PL so that one followed the repeater input and one followed the
>> repeater output so both repeater users and Allstar would be happy BUT if
>> this is a full time Allstar connection there would be no reason to do
>> that.
>> The remote simplex node stays in duplex=1 with no other changes. Its
>> courtesy tone becomes the repeater courtesy tone and tail that the users
>> would hear. When the repeater unkeys it would either not have a PL or have
>> a PL that the remote simplex Allstar node would not respond to thus no
>> keyup loop.
>>
>> When doing this you can set the repeater to have a short CW ID and let the
>> remote simplex node do a normal ID. Repeater users would just have to get
>> use to hearing it and observe the rules of Allstar - no quick keyups. The
>> key here is not being upset that Allstar is being added to the repeater
>> and
>> accepting some changes. Many of the repeaters we have are not being used
>> or
>> utilized beyond a few keyups a day. Adding Allstar could be a big benefit
>> but requires some education and understanding that things will change a
>> bit.
>>
>>
>> *73 Doug*
>>
>> *WA3DSP*
>>
>> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>>
>> On Wed, Jul 25, 2018 at 6:50 AM, "Mike Besemer - WM4B via arm-allstar" <
>> arm-allstar at hamvoip.org> wrote:
>>
>> Doug,
>>>
>>> I'm interested in hearing the fix for this, as it exactly describes the
>>> situation with the node I'm building.
>>>
>>> The repeater it will be connected to is mine.  It does not transmit CTCSS
>>> on IDs or announcements, so that will prevent half of the ping-pong
>>> cycle.
>>> Is there a way to have the node transmit IDs without CTCSS?
>>>
>>> Mike
>>> WM4B
>>>
>>>
>>> On Wed, Jul 25, 2018 at 12:31 AM, "Doug Crompton via arm-allstar" wrote:
>>>
>>> John,
>>>
>>>>
>>>>  You cannot connect a simplex node to a repeater without some
>>>> adjustments.
>>>> The problem is your node has a courtesy tone which keys up on RF after
>>>> the
>>>> repeater drops. The repeater hears this and again keys up and a loop
>>>> forms.
>>>> To eliminate this you need to set  nounkeyct=1  in rpt.conf  - the
>>>> default
>>>> is =0 or perform the tone. You could also set duplex=0 instead but that
>>>> eliminates many other telemetry things you may want to maintain. When
>>>> you
>>>> make changes to the config files you must restart asterisk or reboot the
>>>> system for them to take effect.
>>>>
>>>> Connecting a simplex node to a repeater is not a good idea unless you
>>>> either own the repeater or have permission to do so. You ID's will show
>>>> up
>>>> on the repeater and the repeater ID's will go out over the nde and to
>>>> wherever it is connected. There are ways around this if you have control
>>>> over the repeater. If that is the case and you want more info let me
>>>> know.
>>>>
>>>>
>>>> *73 Doug*
>>>>
>>>> *WA3DSP*
>>>>
>>>> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>>>>
>>>>
>>>> On Wed, Jul 25, 2018 at 12:08 AM, "w7jca via arm-allstar" <
>>>> arm-allstar at hamvoip.org> wrote:
>>>>
>>>> Good evening,
>>>>
>>>>>
>>>>>
>>>>>
>>>>> I have a RP3 and DMK URI hooked up to a Motorola CDM 1550. It is set to
>>>>> duplex=1 and is a RF node to a repeater. Everything is working fine
>>>>> except
>>>>> when someone unkeys the node keys up for a second. It continues to do
>>>>> this
>>>>> each time someone unkeys. I have courtesy tones turned off and still no
>>>>> change. It does this on Allstar as well as echolink.
>>>>>
>>>>> Any help would be appreciated.
>>>>>
>>>>>
>>>>>
>>>>> Thanks
>>>>>
>>>>>
>>>>>
>>>>> John W7 JCA
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>>
>>>>> 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
>>>>>
>>>>> _______________________________________________
>>>>>
>>>>
>>>> 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
>>>>
>>>> _______________________________________________
>>>
>>> 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
>>>
>>> _______________________________________________
>>
>> 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
>>
>