[arm-allstar] CTCSS Output
Kevin Custer
kevin at kc-wireless.com
Mon Sep 9 08:11:31 EDT 2019
The PiTone 2 documentation refers to using the Masters Communications
RA-35 or RA-40. While either of those work perfectly fine as suggested,
the RA-42 was specifically designed to bring out the TXCTCSS logic
through a buffer transistor. Jumpers were reconfigured to allow this
logic to be routed to a pin on the DB9 (without soldering), and a
TXCTCSS indicator LED was added to visually show the status of the
TXCTCSS logic. Either GPIO 4 or 8 can be used as the source, and is
selectable by a jumper. GPIO 8 is default, and no additional soldering
is required to use this output. More information is available from the
Masters Communications website.
Kevin W3KKC
On 9/8/2019 9:45 PM, "Steve Smith via ARM-allstar" wrote:
> We wrote a program called PiTone which runs on the same Pi that is
> running Allstar. It generates a CTCSS tone that we use with our DR-1X
> repeater and MABEL controller. Information is available at
> www.customcomms.net. There is information about PiTone in the FILES
> section.
>
> Steve - N8AR
>
> ------ Original Message ------
> From: "kg5rdf via ARM-allstar" <arm-allstar at hamvoip.org>
> To: arm-allstar at hamvoip.org
> Cc: "kg5rdf" <kg5rdf at gmail.com>
> Sent: 9/8/2019 6:29:50 PM
> Subject: Re: [arm-allstar] CTCSS Output
>
>> Ok thanks! I have a DR2-X running under a Allstar controller with
>> external wiring. Its working analog and translates any inbound c4fm
>> to analog. it just will not apply ctcss rules when audio comes from
>> the allstar node or my dmr bridge. PL works though, everyone just
>> going to have to live without tone squelch....lmao.
>> null
More information about the ARM-allstar
mailing list