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

OpenIPC S30KQ telemetry_tx exception #1660

Open
lida2003 opened this issue Jan 12, 2025 · 1 comment
Open

OpenIPC S30KQ telemetry_tx exception #1660

lida2003 opened this issue Jan 12, 2025 · 1 comment

Comments

@lida2003
Copy link

It's weird, S30KQ+8812AU(2W), it seems that telemetry_tx process crashed.
80% chance telemetry_tx process crashed, I have tested about 10 rounds. so it will fail most of time.

Have anyone met this before?

https://www.youtube.com/watch?v=0OCi0GjeCTA

PS: svpcom/wfb-ng#396

@aepkolol
Copy link

I have the exact same issue. Mavlink telemetry sends fine, until the GCS makes a connection, then within 30 seconds I get disconnected from the flight controller. wfb-cli shows no mavlink packets are being received from the drone, but video and tunnel are fine. As a one way telem link, it works fine, its only when its bidirectional.

With a onboard computer connected directly to another 8812eu wifi chip running pure wfb-ng on both sides, it seems fine. It's only when openIPC is the middleman (In this case, running a runcam wifilink on the drone)

That being said, SOMETIMES it works and doesn't crash within 30 seconds. I've had it on for a little while working fine, but more than 9 times out of 10, its a crash.

I'll try and get some logs off the wifilink the next time I'm connected to it via ethernet.

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