[arm-allstar] Duplex function not working correctly?

[Mike Sullivan]

Scott, I've double and triple checked everything as you had listed in the
notes you sent, everything is set up as is, and the repeater beep is still
coming through. I'm working on it right now (22:30) if you want to try to
connect. KG4DVE-R 975506 on Echolink, 49608 on Allstar.

Mike KN4IMU

On Thu, Apr 4, 2019 at 10:07 PM "Scott Zimmerman via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:

> Mike,
>
> Have a look at my notes. (attached)
>
> Unfortunately they say:
> duplex = 0
> linktolink = yes
>
> One clue from simpleusb.conf:
> carrierfrom = usbinvert
> ctcssfrom = usbinvert
>
> The COS input comes from the controller's PTT output, thus the active LOW.
> The CTCSS input is tied to the controller's CTCSS
> encode output pin. (Also active low) The reason this was done is so the
> transmission could end (CTCSS decode off) *then* the
> controller send the CT for that port, then unkey the PTT line.
>
> By connecting the two logic signals as above and using selective encode on
> that port, you can kill the controller's CT
> heading for the internet side.
>
> The other clue is:
> duplex = 1 in simpleusb.conf. I don't remember nor do I have any notes
> that say why this should be set to 1 in this config
> file, but set to 0 in rpt.conf.
>
>  > Port 3 is not set up in repeater mode so it should be operating as a
> simplex connection.
> It's been awhile, and I have slept since the last time I played with this,
> but I *think* you want that port to be full duplex
> from the controller's side. If it's half-duplex, you can't send tones to
> the node while it is transmitting.
>
> Keep in mind, AllStar can be used full duplex.
>
> Upon further thought, that's why duplex=1 in one config file and 0 in the
> other. Duplex=1 in the SimpleUSB channel driver
> configuration since the node is *capable* of full duplex operation. It is
> set for duplex=0 in rpt.conf since in this case we
> don't want any repeat audio functionality. Nodetonode=0 which shuts of
> CT's and other telemetry. (I *may* be backwards on
> that last part.)
>
> There you go!!
>
> Scott
>
> Scott Zimmerman
> Amateur Radio Call N3XCC
> 474 Barnett Road
> Boswell, PA 15531
>
> On 4/4/2019 12:59 PM, "Mike Sullivan via ARM-allstar" wrote:
> > I'm working on our club's node.. configuration is an RC-210 controller,
> > repeater on port 1, RIM-Lite for the RC-210 on Port 3 (2 is reserved for
> a
> > link radio) I think I finally fixed the poor audio issue, but I'm still
> > having issues with courtesy beeps.
> >
> > I have the rpt.conf file duplex variable set to 0, which should be half
> > duplex, no telemetry/tones. No matter of the configuration of linktolink
> > (yes, no, or commented out) the repeater's courtesy beep is somehow being
> > looped back into the transmission as a pre-PTT beep, when it should only
> be
> > a post-PTT courtesy beep.
> >
> > If I switch to duplex=1, the controller's courtesy beep goes away.. but
> at
> > the cost of the Allstar beep, telemetry, etc (that I can comment out, I
> > know that). Now here's the weird part.. when I comment out the courtesy
> > beep in rpt.conf, the problem returns. I've checked everything on the
> > controller side, Port 3 is not set up in repeater mode so it should be
> > operating as a simplex connection.
> >
> > I'm baffled as to what's going on. Am I missing something that would
> > otherwise cause the issue
> > _______________________________________________
> >
> > 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