You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am running gazebo classic simulator in a docker container (image: jonasvautherin/px4-gazebo-headless). QGC running on the same host as docker should automatically connect to default port 14550.
Current Behavior
QGC does not connect. Console shows (with qgc.comms.linkmanager and qgc.comms.linkmanager.verbose on):
I tried turning autoconnect all on, all off except udp, all off but with a manual link for port 14550 (as below). All scenarios produce the same results.
Steps to Reproduce:
Please provide an unambiguous set of steps to reproduce the current behavior
Yes, I tried using the last stable build v4.4.3. Results are the same, except that with Linkmanagerverbose on, console seems to show that QGC is listening to a bluetooth port only:
I am running docker-mac-net-connect to make sure that the host can reach the container. Indeed I can ping the container from the host and when I set up a comm link to point to the container port assigned in px4, px4 reports a valid ground station heart beat (but QGC remains unconnected).
Expected Behavior
I am running gazebo classic simulator in a docker container (image: jonasvautherin/px4-gazebo-headless). QGC running on the same host as docker should automatically connect to default port 14550.
Current Behavior
QGC does not connect. Console shows (with qgc.comms.linkmanager and qgc.comms.linkmanager.verbose on):
I tried turning autoconnect all on, all off except udp, all off but with a manual link for port 14550 (as below). All scenarios produce the same results.
Steps to Reproduce:
Please provide an unambiguous set of steps to reproduce the current behavior
System Information
When posting bug reports, include the following information
The text was updated successfully, but these errors were encountered: