Bug in latest versions for Android? #2500
Comments
|
mavsdk-server-2.1.5 seems quite old? Any chance you can try latest? Do you have an example for me to test this with? |
|
2.1.5 is the latest version on Apache maven..
the entire source code is what I posted - just added a button to start the
server that calls start server (posted). I’ll try to post the entire kt
file but it doesn’t have any new info.
…On Tue, 28 Jan 2025 at 3:20 AM, Julian Oes ***@***.***> wrote:
mavsdk-server-2.1.5 seems quite old? Any chance you can try latest?
Do you have an example for me to test this with?
—
Reply to this email directly, view it on GitHub
<#2500 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BIN4CD3G3CUZZGXTH6H2BFD2M2S2PAVCNFSM6AAAAABV5ZWYS2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMJWHE3TANBVGA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Does it detect a mavlink system? Does your drone report receiving messages from MAVSDK over TCP? |
|
Yes. I tried both arm and disarm commands and they worked fine. I wasn’t
able to get any debugging output on ACKs , but I was able to see the SITL
received and acted on the commands. Funnily enough, the SITL also disarmed
automatically and notified my client it did so, even if I didn’t send the
disarm command . I haven’t tried the commands yet with the 1.x versions -
can try that if it will help.
…On Tue, 28 Jan 2025 at 9:40 AM, Jonas Vautherin ***@***.***> wrote:
Does it detect a mavlink system? Does your drone report receiving messages
from MAVSDK over TCP?
—
Reply to this email directly, view it on GitHub
<#2500 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BIN4CD5WBCA526754X42H2D2M37M5AVCNFSM6AAAAABV5ZWYS2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMJXHAYDCMRTGI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
And now its stopped working ; tried both version 1.2 and version 2.0. The entire source code is below : import android.annotation.SuppressLint class MainActivity : ComponentActivity() { } ` Here are the log messages I'm seeing: |
This sounds like mavlink messages sent by MAVSDK are received by the autopilot, but mavlink messages sent by the autopilot are not received by MAVSDK. Because you use a TCP connection, I don't think it would be a problem there (usually that happens with UDP) 🤔. Are you sure that you don't have multiple clients competing on the connection? Not sure how Ardupilot implements TCP support. Did you make your tests when only MAVSDK and Ardupilot are running, and not pymavlink or QGC in parallel? |
|
I'm sure about multiple clients. I do have mavproxy running (as part of
sim_vehicle), but that is only listening on localhost on UDP. I confirmed
in the SITL run that only one connection is active.
…On Tue, Jan 28, 2025 at 10:59 AM Jonas Vautherin ***@***.***> wrote:
Yes. I tried both arm and disarm commands and they worked fine.
This sounds like mavlink messages sent by MAVSDK are received by the
autopilot, but mavlink messages sent by the autopilot are not received by
MAVSDK. Because you use a TCP connection, I don't think it would be a
problem there (usually that happens with UDP) 🤔.
Are you sure that you don't have multiple clients competing on the
connection? Not sure how Ardupilot implements TCP support. Did you make
your tests when only MAVSDK and Ardupilot are running, and not pymavlink or
QGC in parallel?
—
Reply to this email directly, view it on GitHub
<#2500 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BIN4CD2WFZAXZQANLNPSHGL2M4ISRAVCNFSM6AAAAABV5ZWYS2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMJXHEZDINZZGM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
I’m encountering the same issue! I’m currently migrating a Python DroneKit app from Windows to Android, and it seems there’s a problem with the TCP protocol. Specifically, it appears that the Android app isn’t sending the required message to properly configure the connection. When I test the DroneKit version using TCP (e.g., port 5760), it works fine. Similarly, the MAVSDK version operates as expected. However, when I attempt to use the Android app without first running the Windows version, the app fails to listen for the connection unless the link is already established. It seems that we need to ensure the connection is properly established before attempting to listen with the Android app. This doesn’t seem to be an SITL issue, since I can successfully listen to telemetry on Mission Planner, QGC, and their respective Android versions. I’m 100% sure the problem is related to the TCP protocol. |
|
If hepls. Catlogs differences
|
|
tcp error can be seen on the 2.1.5 |
Using mavsdk-2.1.0 and mavsdk-server-2.1.5 and Ardupilot SITL as the backend on an IP port I cannot get telemetry data on Android. Keeps telling me its retrying when I subscribe for position data. The only code I'm using beside server.run() and new System() is this in my main activity.kt :
fun runServer() {
MavsdkEventQueue.executor().execute({
val address = "tcp://192.168.29.118:5763"
val port = server.run(address)
Log.d(TAG, "port is $port")
if(port == 0) {
Log.e(TAG,"Unable to start server")
return@execute
}
drone = System("127.0.0.1",port)
isRunning = true
buttonText= "Destroy"
Log.i(TAG,"Server started")
setupSubscriptions()
})
}
I've validated that QGC and mavproxy are able to both communicate with the SITL. When I change the mavsdk and server versions to 2.0 , then this works perfectly.
The text was updated successfully, but these errors were encountered: