Asl3 ver allstar3-arm64-3.0.15.img no tx or tx audio

App_rpt-users
1

Good evening.

Got 2 problems not tx, not tx audio and running raspberry pi5 through a Rimlite to a 3 port Arcom rc210 uhf repeater. I ve been fighting wth this for the last 2 day.

Await your reply , Thanks

2

these are my ports open in terminal:

Screen Shot 2024-12-07 at 6.54.40 PM
Screen Shot 2024-12-07 at 6.54.40 PM1572×1188 50.9 KB

and router 4569 and 80

3

No audio is generally not a networking issue.
Sound fob/ sound fob setup (URI)
or maybe as simple as tx and rx audio lines are backwards.
But include proper duplex mode, and link to link setting if you are feeding a hardwired controller.

But I’m not writing a book on possibilities. You will need to provide more info.

4

1
11290×1253 228 KB

I use one node at a time. 569840 & 569841

5

Im using a Rimlite to connect to my UHF Arcom RC210 3 port repeater

6

@ve6mld - Your question doesn’t make any sense. If you’re hearing your node announcing time, “beeps”, and “give the announcements” then it sounds like TX works just fine? So are you saying you have an RX problem? And why do you keep re-imaging your system over and over since you keep referencing the image version file .img?

7

I use AllScan and Supermon 7.4.
so due dtmf on the node # on all scan to make connection, ,
I used Parrot 5553 to do audio test
So parrot is enabled, I try to transmit with either two his it doesn’t show red that I’m transmitting parrot doesn’t hear me so tx problem maybe in software…
so I followed the Zimmerman rimlite instructions for SimpleUSB and for RPT.

[
RIM_RC210_connection_notes.pdf (352.0 KB)

Screenshot 2024-12-09 at 4.52.09 PM
Screenshot 2024-12-09 at 4.52.09 PM861×1033 90.6 KB

](https://)

8

Those directions are not for ASL3. I would not expect them to work.

9

Screenshot 2024-12-09 at 4.52.09 PM
Screenshot 2024-12-09 at 4.52.09 PM861×1033 90.6 KB

Screenshot 2024-12-09 at 4.52.20 PM
Screenshot 2024-12-09 at 4.52.20 PM842×1021 47.8 KB

10

what service has to be enabled in terminal Unser service incase it was disabled
to receive my handheld tx and audio

11

I did a fresh install using the same asl version you are having issues with: allstar3-arm64-3.0.15.img.xz

AND I am not having any issues.

Have there been any hardware changes since the last time your node(s) worked fine?

12

No hardware changes since I started on the Allstar

13

Got the error this morning:

Screen Shot 2024-12-10 at 7.23.59 AM
Screen Shot 2024-12-10 at 7.23.59 AM1402×600 25.6 KB

14

…for whatever it’s worth:

  1. I switched from usbradio to simpleusb on my LOCAL NODE and noticed I could no longer key up such node from my radio.
  2. Realtime telemetry was showing that the COS was keyed and unkeyed as I pressed and depressed the radio’s PTT. But the LOCAL NODE did not open its squelch.
  3. LOCAL NODE was able to be keyed up by REMOTE NODE (another of my private nodes).

THE FIX (in simpleusb.conf):
Changed ctcssfrom=usbinvert to ctcssfrom=no

This solved my ‘no tx or tx audio’!

Hopefully this helps.

*** I have no idea why this variable has any impact on the simpleusb channel driver if simpleusb does not have the capability to decode ctcss ***

15

Because carrierfrom and ctcssfrom are seperate logic inputs that must BOTH be triggered in order for the channel to start RXing.

With simpleUSB, it doesn’t have the ability to decode CTCSS in software, but the ability to connect an input logic signal that goes high or low when the correct CTCSS is present is still there.

Usually, nobody uses both of these. They just connect the CTCSS detect output from the radio to the CARRIER input of the interface, and then set ctcssfrom = no to disable/ignore it, because that’s easier than finding/connecting both signals.

1 Like