Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Mavsdk_server not starting
See original GitHub issueI have installed mavsdk for python in a virtual environment using pip3 install mavsdk. When I run the telemetry.py example the program hangs at Waiting for mavsdk_server to be ready.... I am using MacOS Catalina as my OS. I have tested the same code on an ubuntu vm and it works as expected. Any suggestions or help debugging is greatly appreciated.
Issue Analytics
- State:
- Created 3 years ago
- Comments:9
Top Results From Across the Web
Cannot connect to mavsdk-server · Issue #130 - GitHub
Hi! I'm struggling to get the internally started or externally started mavsdk server connected. I can therefore not reach any further in ...
Read more >Troubleshooting · MAVSDK Guide
The callbacks are stored in a queue. If the user does not return quickly enough from the callback, it can happen that the...
Read more >Python QuickStart - Mavsdk
A running SITL instance (jMAVSim, gazebo, …). A quick way to run a headless gazebo SITL instance using docker is documented here. Install....
Read more >Building mavsdk_server from Source · MAVSDK Guide
This gRPC server around the MAVSDK C++ library is called mavsdk_server (in the past it was referred to as the backend).
Read more >Example: Autopilot Server - Mavsdk
This example shows how to use MAVSDK Server Plugins! This is a good starting point if you are looking to implement MAVLink services...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
It solves the problem. It appears that apple has a service running on port 50051 causing mavsdk to not be able to use the default port.
Good to know!