-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ASL3 ID is unreliable #384
Comments
You indicate that it starts but does not complete. Is there any frequency to this problem? Do you see any error or interesting messages in the cli? |
I have not noticed a pattern necessarily. Sometimes it fails on the first
ID, other times the first ID after an idle period works fine. I have not
seen any interesting messages with debug level 3
…On Fri, Jul 12, 2024, 12:01 PM Danny Lloyd ***@***.***> wrote:
You indicate that it starts but does not complete. Is there any frequency
to this problem?
Do you see any error or interesting messages in the cli?
—
Reply to this email directly, view it on GitHub
<#384>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIGP5NTWL3UUMLJS7KTENS3ZMADXHAVCNFSM6AAAAABKZGXTYGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRVHE3TINRZGI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Update: I have multiple Dell Wyse 3040 units running ASL3, and have not noticed the unreliable ID on these units. May only apply to the Rpi 4? |
Move to app_rpt |
Are you using chan_simpleusb or chan_usbradio? |
chan_usbradio. Not using app_rpt for PL.
Since creating this ticket, I have spun up several ASL3 boxes using Dell
Wyse 3040 units, have not yet noticed this issue on that hardware. May be
an issue with multiple RF nodes on a Raspberry Pi 4 as in past versions of
ASL?
…On Sat, Aug 10, 2024 at 12:54 PM Danny Lloyd ***@***.***> wrote:
Are you using chan_simpleusb or chan_usbradio?
Are you using PL on transmit?
—
Reply to this email directly, view it on GitHub
<#384 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIGP5NTN2BT5RSQWQUTCDV3ZQZHUPAVCNFSM6AAAAABMJ4Q3U2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOBSGIZDMNBUGE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
There are some notes on the internet that using two sound card devices on the RPI 4 is a problem. I am using a 3040 with two nodes without a problem. The notes seem to indicate a kernel problem. In another place I found someone saying that later rpi 4s did not have this issue. |
The does not appear to be a repeatable or wide-spread problem. Please re-open if there is a diagnosable problem here. Cleanup GitHub. |
Describe the bug
ID will often begin but not fully send ID audio. PTT is asserted but the ID is not always fully sent out. This occurs both with standard CWID as well as a custom ID audio file I have used for many years.
Manually sending the audio works reliably:
rpt playback 2212 filename
Just updated to latest ASL3 today and issue persists.
Have you run a software update and rebooted?
What is the platform - e.g. Raspberry Pi 4, Raspberry Pi 5, Virtual Machine, Desktop, etc.
Additional context
Pi4b does have two RF CM108 nodes on it, but I have not noticed any correlation of this ID issue to having multiple RF nodes. This ID reliability issue happens on both RF nodes, even if one has been idle for hours.
The text was updated successfully, but these errors were encountered: