Skip to content
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

PTT Remains engaged and Audio/Serial Devices crash on Linux and Mac #54

Closed
b4ux1t3 opened this issue Jan 20, 2024 · 5 comments
Closed

Comments

@b4ux1t3
Copy link

b4ux1t3 commented Jan 20, 2024

Whenever I transmit using a UV-5R and an Explorer QRZ-1, the AIOC seems to crash, making the audio and serial devices disappear and sticking the PTT on permanently.

Unplugging and plugging it back in works just fine, but I can't transmit at all.

This happens in both classic serial PTT and CM108 PTT modes.

Direwolf throws this at me:

ioctl HIDIOCGRAWINFO failed for /dev/hidraw0. errno = 0.
Audio input device 0 error code -19: No such device
...
Audio input device 0 error code -19: No such device
Terminating after audio input failure.

I haven't tested on windows yet, but I have tested with a Mac, a Pi, and a linux laptop.

I opened a ticket last year about this, but never got back around to trying any of the fixes recommended.

@b4ux1t3 b4ux1t3 changed the title PTT Remains engaged and Audio Device crashes on Linux and Mac PTT Remains engaged and Audio/Serial Devices crash on Linux and Mac Jan 20, 2024
@skuep
Copy link
Owner

skuep commented Jan 20, 2024

Can you have a look at this issue?
#11

There have been some problems in the past regarding with EMI issues. Maybe you can find a workaround there

@b4ux1t3
Copy link
Author

b4ux1t3 commented Jan 20, 2024

Ah, I gave it a glance and thought it didn't have anything to do with me, but reading closer there are some things I haven't tried yet.

I don't have the same issues on Windows (completely different issues, haha), but it's similar enough that it's worth trying. Thanks!

I'll give some of it a try and update.

@skuep
Copy link
Owner

skuep commented Jan 20, 2024

Ah sorry, you are right. I should close that one.
I meant to say this issue:
#22

@skuep
Copy link
Owner

skuep commented Mar 24, 2024

I assume your problem is solved or you found another solution and I am going to close this issue. Feel free to reopen if you need more help.

@skuep skuep closed this as completed Mar 24, 2024
@b4ux1t3
Copy link
Author

b4ux1t3 commented Mar 28, 2024

I just haven't had any free time to look at it. Ha! I'll get to it eventually, and reopen if necessary, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants