[arm-allstar] config for split rx/tx

Tue Jan 2 00:06:47 EST 2018

Dan,

 The simplex/duplex is the RF side definition. Allstar is always full
duplex digitally. If you set duplex=0 or 1 then when the RX becomes true
(COS true) the TX does not transmit, no PTT. This is called half duplex. If
duplex=2 or greater it is full duplex and when RX is true (COS true) the
transmit PTT follows. So if both the RX and TX were in the same location it
would repeat directly. Keying the PTT would
be 
meaningless in a split site system. It does change other parameters though
as Dave mentioned so you could experiment with both and see what you like.

So doing one vs. the other does not save any bandwidth.

*73 Doug*

*WA3DSP*

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

On Mon, Jan 1, 2018 at 11:39 PM, Dan Keizer <ve4drk at gmail.com> wrote:

> thanks Dave and Doug for your input - appreciated.
>
> They are defined statically on our local 44 net and are private.  At some
> point we would most likely link them into allstar in general for public
> access - but we're still working on a few things.
>
> I did initially configure them as duplex - but thinking about it,
> wondering if it would be best to configure them as simplex as that's really
> what they are  on a node basis.  Where they are located will have plenty of
> bandwidth on our private ham net, but if I do move it to simplex that
> should reduce the data required.
>
> While i did get them powered up etc (at least from all indications I can
> see)  - i have to chat with our fellow guys to debug some connection
> items.  I do have it defined as simpleusb but am having issues verifying
> the RF setup and link with the USB fob.  Can't quite get it to talk 100%.
> There is some RF noise coming out.  It does recognize the usb as
> functional, but there may be a connection issue with the radio - will see.
>
> Once I get this stuff connected, I'll want to install a node-less hub on a
> local hosted data server that has an unlimited 20Gbps bandwidth - combine
> that with our ham-friendly provider, makes working on ham projects easier.
>
> 73, Dan ve4drk
>
>
> On Mon, Jan 1, 2018 at 9:46 PM, "Doug Crompton via arm-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
>> Dan,
>>
>>  I just put a split site 6 meter repeater on the air about a month ago
>> using Allstar as the connection medium. The only difference is that BOTH
>> ends are setup as simplex and one end is defined as the RX and only gets
>> the COS and RX audio to the FOB and the other end defined as TX gets the
>> TX
>> audio and PTT from the FOB.
>>
>> I did it differently than Dave though setting duplex=0 on the RX end  and
>> on the TX end duplex=1. To the users this sounds like a typical simplex
>> Allstar node which they are use to. You have a choice either way works.
>>
>> In my case I made both the TX and RX private nodes connected to each other
>> with static addressing in rpt.conf and then one end or the other connected
>> to my hub node. That way you can disconnect and still have a functioning
>> repeater minus connections to the outside Allstar world.
>>
>>
>> *73 Doug*
>>
>> *WA3DSP*
>>
>> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>>
>>
>> On Mon, Jan 1, 2018 at 9:34 PM, "David McGough via arm-allstar" <
>> arm-allstar at hamvoip.org> wrote:
>>
>> >
>> > Hi Dan,
>> >
>> > The method you're suggesting will work fine. While I'm sure there are
>> > probably at least a half dozen different ways to configure this setup,
>> the
>> > way I've done it is to setup both RPi3 configs as if they've connected
>> to
>> > a standard full-duplex repeater (duplex=2 in the rpt.conf node stanza).
>> > This gives me all the typically expected repeater telemetry, hang times,
>> > etc.
>> >
>> > On the TX end, only connect TX audio (headphone output audio from fob)
>> and
>> > PTT to the radio. Make sure COS/CTCSS are set so they never activate.
>> >
>> > On the RX end, attach RX audio (to the fob mic input) and COS/CTCSS, but
>> > no PTT or TX audio.
>> >
>> > Then, link the 2 nodes together via *3 (or *73) and voila! ...a simple
>> > split site repeater that acts just like a "normal" single site repeater!
>> >
>> > ...It really is this simple!
>> >
>> > Happy New Year!
>> >
>> > 73, David KB4FXC
>> >
>> >
>> > On Mon, 1 Jan 2018, "Dan Keizer via arm-allstar" wrote:
>> >
>> > > Hi there - been using the hamvoip distro for a while now - works
>> great.
>> > > We even used it to experiment with linking in different repeater
>> systems
>> > -
>> > > tests went well for us.
>> > >
>> > > Since we don't have much in the way of 220MHz repeater systems here in
>> > > EN19-land, we decided to try out a little linking project.
>> > >
>> > > We run a highspeed 2.3GHz, 3.6GHz and 5.8GHz ham network here in the
>> city
>> > > and area and have access to some decent building/tower sites -
>> reference:
>> > > http://va4wan.ampr.org/  Now, with space and electricity always
>> being an
>> > > issue, we wanted to run it in a low-profile mode, for both space and
>> > power.
>> > >
>> > > I picked up a number of the USB audio dongles a while back and we
>> have a
>> > > surplus stash of some small maxon synthesized 5watt radios - and with
>> the
>> > > recent sales on, i was able to pick up a couple of 220Mhz cushcraft
>> > > antennas for a decent price - so ,with my extra pi 3's i have, we put
>> > > together a little project.
>> > >
>> > > one site will have a raspberry pi, usb dongle, maxon radio and a
>> 220mhz
>> > > receiving antenna.  It will also tie into our highspeed va4wan
>> network.
>> > > the other site will have a raspberry pi, usb dongle, maxon radio and
>> > 220mhz
>> > > transmitting antenna.  it also will be line-of-sight to our highspeed
>> > > network.
>> > > they are separated apart both vertically and horizontally to not
>> cause a
>> > > problem.
>> > >
>> > > I've defined the nodes to be private for now and they are networked.
>> > > i'll be making my final mods to the configs today and powering up the
>> > units
>> > > and test this out --- anyone done something similar to give some
>> insights
>> > > as to what else to watch for?  i don't expect any issues, but always
>> > > interested in hearing others opinions and how things went.
>> > >
>> > > 73, Dan ve4drk
>> > > _______________________________________________
>> > >
>> > > 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
>>
>
>