[arm-allstar] COS line lost and frequent spurious Key Downs.

[Jon Rorke]

What pin are you connected to on the FR5000 for COS?

Are you using pin 17 or 21?
And what are the settings of those pins in the FR 5000?

By default pin 17 is set for "Busy". This is the COR active line and goes
active when the squelch is tripped. This signal ignores PL decode on the
repeater.

If you use pin 21 by default it is set to "Analog Audible". This line goes
active when the signal goes above the squelch and the correct CTCss tone
decoded. This is the desirable line to use for the simple USB squelch and
should be connected to cor in line on the usb interface.

Also these signals from the repeater should be set to active low. Which
means the lines pull to ground when they go active. Ensure the input logic
on simple usb is set for active low or USB invert.

If you are connected to pin 17 then noise on the repeater input could be
tripping the squelch.

Hope this helps,

Jon VA3RQ

On Wed, Dec 28, 2022 at 2:33 AM Glenn Lyons via ARM-allstar <
arm-allstar at hamvoip.org> wrote:

> Version: RPi2-3-4  Version 1.7-03 Allstar - September 12, 2022 - K4FXC
> Driver:  simpleusb
> Duplex: 2
> RIM: RB-RIM-Lite Version 2.1
> Repeater: IC5000
>
> For some reason I am yet to determine our ASL has lost the COS input. It
> may be a broken wire or a programming error on the IC5000 AUX port. I will
> diagnose when I am next on site.
>
> What I am surprised to find is that ASL still functions well for QSO's.
> However, this setup has one not so good side effect. When not in a QSO the
> repeater goes key down for a second or less frequently. At the worst times
> this can occur up to 47 times an hour.
>
> Question 1. Is the simpleusb driver using the RX (audio from the repeater)
> in the absence of COS to key PTT? There is nothing else it can be using.
>
> Question 2. Please confirm that the simpleusb driver ignores CTCSS. I have
> CTCSS connected and tried to implement that protocol without success.
>
> Question 3. I used  "12 Run Simpleusb-tune-menu application, option
> V) View COS, CTCSS and PTT Telemetry using real-time display" to determine
> the signals. What is the time interval between refreshes as I may be
> missing states between refreshes.
>
> Question 4. Are there any scripts or code segments available for this very
> useful utility?  I would like to mod it so it scrolls with a timestamp
> instead of refreshing in situ so I can follow the changes over time.
>
> I have implemented logging by setting the “archivedir” parameter in the
> rpt.conf, which was helpful. However, it was the V) View COS, CTCSS and PTT
> Telemetry using real-time display that alerted me to the cause of my
> problem.
>
> I have confirmed there is no traffic keying the repeater as the uplink is
> silent, so I am left with local "noise" on the Audio into the RB RIM. I
> will know more after visiting the site.
>
>
> Thanks,
> Glenn
>
> Callsign: VK4PK
> Email: Glenn at LyonsComputer.com.au
> _______________________________________________
>
> 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/4 web page - http://hamvoip.org
>