[arm-allstar] Echolink Connect announcements

[Mike Besemer]

Doug,

You've described my installation here; I'm tying a remote node to the
repeater via RF.  

I certainly agree that node ID's need not have TXCTCSS Encode; there is no
need to transmit those IDs over the repeater.  However, I think that connect
announcements should be TXCTCSS encoded.; there is absolutely no point in
transmitting a connect announcement if nobody can hear it.  As the repeater
owner/control op, I'd like to know when a connect occurs and who connected.
Aside from that, it's hard to initiate a QSO with a listener if you don't
know they are there.

I use ARCOM RC-210 repeater controllers exclusively.  I have the option to
send any announcement, CWID, etc. with or without TXCTCSS.  Seems like that
ought be doable with AllStar as well.   

Just my 2-cents.

Mike
WM4B

-----Original Message-----
From: ARM-allstar [mailto:arm-allstar-bounces at hamvoip.org] On Behalf Of
"Doug Crompton via ARM-allstar"
Sent: Monday, September 10, 2018 5:47 PM
To: ARM Allstar
Cc: Doug Crompton
Subject: Re: [arm-allstar] Echolink Connect announcements

Mike,

 Yes, TXCTCSS follows input COS and not PTT. This means that messages and
ID's are not heard by a receiver using that PL frequency. This is useful
when you don't have Internet access at a repeater site and you connect to
Allstar via remote RF allstar inputs. The remote site see the only the
input RF of the repeater, PL follows the input. In this case you could have
two PL's one following the repeater PTT (output PL) and one using TXCTCSS
following the input. Repeater users would use the output PL


*73 Doug*

*WA3DSP*

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

On Mon, Sep 10, 2018 at 3:42 PM Mike Besemer <mwbesemer at cox.net> wrote:

> Bueller?  Bueller?  Bueller?
>
>
> Mike
> WM4B
>
> -----Original Message-----
> From: ARM-allstar [mailto:arm-allstar-bounces at hamvoip.org] On Behalf Of
> "Mike Besemer via ARM-allstar"
> Sent: Thursday, September 6, 2018 3:56 PM
> To: 'ARM Allstar'
> Cc: Mike Besemer; 'Doug Crompton'
> Subject: Re: [arm-allstar] Echolink Connect announcements
>
> Doug,
>
> I replied, but I don't think it made it on the list.
>
> Yes... SimpleUSB with an RA-42.  TXCTCSS control works via GPIO8 find with
> this setup; TXCTCSS discrete follows COS, but it does not allow TXCTCSS on
> announcements.
>
> Thoughts?
>
> Mike
> WM4B
>
> -----Original Message-----
> From: ARM-allstar [mailto:arm-allstar-bounces at hamvoip.org] On Behalf Of
> "Doug Crompton via ARM-allstar"
> Sent: Tuesday, September 4, 2018 4:03 PM
> To: ARM Allstar
> Cc: Doug Crompton
> Subject: Re: [arm-allstar] Echolink Connect announcements
>
> >
> > Mike,
> >
> >   Are you using simpleusb?  Any transmission should have PL as all
> > simpleusb does is key the PTT. The TX supplies PL on every transmission.
> >
> >
> > *73 Doug*
> >
> > *WA3DSP*
> >
> > *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
> >
> > On Tue, Sep 4, 2018 at 3:40 PM Mike Besemer <mwbesemer at cox.net> wrote:
> >
> >> Doug,
> >>
> >> Didn't notice this yesterday because I was monitoring my RF node on my
> >> HT, but when the connect messages ARE being sent, they are sent without
> PL
> >> being encode.  That definitely limits the usefulness of the connect
> message
> >> as well.
> >>
> >> 73,
> >>
> >> Mike
> >> WM4B
> >>
> >>
> >>
> _______________________________________________
>
> 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