Closed enymuss closed 1 year ago
Thanks for the issue, hopeully @JonasVautherin can look into this soon.
Does it work for other examples, like taking off?
BACKEND_IP_ADDRESS
is the IP where mavsdk_server
is running. On Android that would be 127.0.0.1
, unless you run mavsdk_server
on your computer (which I sometimes do for debugging).
docker run --rm -it jonasvautherin/px4-gazebo-headless:v1.10.1 PHONE_IP
should do it, if the computer running that can reach the phone over the network (obviously).
In the Android example, do you see the map and the pin at the location of the drone?
Any news about that?
Could you write a guide on how to connect it to the SITL jmavsim? I wrote in BACKEND_IP_ADDRESS ip of network and added jmavsim port (4560). App is opened, but "takeoff" button does not work.
@Mark718real seems like your issue is not "failed to upload the mission". Would you mind opening a new issue for your question? :blush:
When trying to run the android-client example, the app opens, the mapView loads and pressing on the screen adds waypoints. After adding the waypints, pressing the fab does nothing visable on screen. Logcat prints
io.mavsdk.androidclient E/MapsViewModel: [grpc-default-executor-4] - Failed to upload the mission
Pressing Land, Return, Kill or Takeoff all kill the app and it closes.In the uploadMission, translateFromRpc() returns result.result as ERROR and result.resultStr as also Error.
It looks like it is sending something to a ?simulator?, but can't, so I've tried changing the ip addresses, looking for it to connect.
Things Tried
network interface eth0, IP: 172.17.0.2
. This makes the warning disappear, but nothing happens on screen.docker run --rm -it jonasvautherin/px4-gazebo-headless:v1.10.1 PHONE_IP
, but the docker logs never show something connected to it and the error appears.Running this on Android version 9.
What can I try to get the android-client example working?