[arm-allstar] half duplex node linking to a repeater

[David McGough]

Hi Doug,

The problem I have RF linking VHF/UHF half duplex AllStar nodes to various
non-AllStar repeaters is that "I have to take what I get" --meaning that
the distant repeater owner isn't going to change their system's operation
to accommodate me.  And, in most cases, the repeater owners aren't the
person who programmed their controllers and they literally don't know how
to configure transmitted PL to follow RX COS---rather than full time
transmitted PL tone (the whole time the TX is up)---or other control
parameters. In this region, I know of only one repeater programmed with TX
PL following RX COS---and, I expect that was a configuration mistake
(LOL!)!

There is probably still confusion about how I'm running my remote nodes
(Doug--not with you, but others)...Perhaps I should try to draw a diagram?  
While more complex, the "private repeater" setup scenario I described
works 100% of the time with any half duplex node, without any changes at
the non-AllStar repeater. That same setup scenario works great for HF 
remote base radios, etc., etc.


73, David KB4FXC



On Sat, 18 Jul 2015, Doug Crompton wrote:

> I have been following this thread and I will put my two cents in. I am 
assuming I understanding correctly what you are doing or what you want to 
do. I do this here with my repeater. Often you do not have Internet 
capability at a repeater site and you want to connect it to Allstar. The 
alternative is to use a half duplex (simplex) node that talks to the 
repeater just like a user. The key is how you setup the repeater. 
> 
> First of all you do not want the repeater output to control the distant 
COS. If that was the case you would have hangtime (tail) and ID's coming 
through the Allstar system. You want the repeater output PL to follow 
it's input PL. Thus no input signal to the repeater no output PL. Your 
local simplex node RX COS follows the input to the distant repeater. The 
downside is that repeater users who use RX PL decode will not hear the 
repeater ID or tail either. It is still legal though. 
> 
> Another way to do this is to have two PL's on the output. One follows 
the input and is the one you decode for Allstar. The other is the decoded 
by the repeater users and they would hear all ID's and tails.
> 
> I do the former using one PL since 99% of the repeater users are 
talking to Allstar nodes. I send a courtesy tone and voice ID from the 
half duplex transceiver to the repeater. This is the easiest way to do it 
and the repeater sounds to repeater users like it is controlling the tone 
and ID. It requires a simple mod to the repeater making output PL follow 
the input signal rather than the repeater PTT.
> 
> No special configuration needs to be done at the simplex node. It is 
duplex=1 and the tail time and ID become the repeaters tail and ID.
> 
> 73 Doug
> WA3DSP
> http://www.crompton.com/hamradio
> 
> 
> > To: arm-allstar at hamvoip.org
> > From: ke6sth at ke6sth.ampr.org
> > Date: Fri, 17 Jul 2015 20:15:35 -0700
> > Subject: [arm-allstar] half duplex node linking to a repeater
> > 
> > 
> > Hi I have a node that is used for linking my local repeater to another 
> > repeater using a half duplex node.
> > 
> > Some repeaters I link do have a long hang time and I find that I can't 
> > keyup the link until the remote repeater is unkey. Is there a way to 
> > make it so I can key up the half duplex node at any time I want and not 
> > wait for the carrier to drop from the remote end?
> > 
> > Thanks,
> > --Sione
> > 
> > _______________________________________________
> > 
> > arm-allstar mailing list
> > arm-allstar at hamvoip.org
> > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> > 
> > Visit the BBB and RPi2 web page - http://hamvoip.org
> > 
>