MAVSDK-Python apython stuck and server waiting

[AdrianVitoria]

Wanted to connect to a Mission Planner Simulation to do the basics of arm, take-off and land.
I have little experience with Python so I followed a guide: Link
Using the "apython" thing, I tried to connect many times, to no avail.
And now it's stuck and have to close the terminal every time I try it.

How I'm opening the server: mavsdk_server_win32 -p 50051
Result:
["Time"|Info ] MAVSDK version: v1.4.12
["Time"|Info ] Waiting to discover system on udp://:14540...

Waits forever.

What I do in apython:

from mavsdk import System
drone = System(mavsdk_server_address="localhost, port=50051")
await drone.connect(system_address="udp://:14540")

Stays stuck right there.

I use Windows 10 and Python 3.11

What am I doing wrong?
Please help.

[JonasVautherin]

Waiting to discover system on udp://:14540...

MAVSDK is waiting for MAVLink messages coming from your (simulated) drone to its UDP port 14540. Is your drone sending MAVLink messages? To which port, and on which protocol?

[AdrianVitoria]

Don't know much about Mission Planner but I'm asuming it's this thing that says TCP and 115200.

I'll try to fiddle with the options and see if I can change those to UDP and 14540.

[JonasVautherin]

Doesn't the Ardupilot SITL listen on TCP 5790 by default, or something like this (maybe 5760)?

You could try something like this to connect MAVSDK to it:

mavsdk_server_win32 -p 50051 tcp://127.0.0.1:5790

[AdrianVitoria]

5790 gave a socket error (?)
5760 is waiting.
Changed the connect to: await drone.connect(system_address="tcp://127.0.0.1:5760").
Stuck again.

UPDATE: Using dronekit I managed to connect to the simulation using the 5762 port. Changed the connect to:
await drone.connect(system_address="tcp://127.0.0.1:5762").
Stuck once more.

I think I'll just go with dronekit and see if it can do what I want. Would be nice to know why it couldn't connect to mavsdk, though.

Want me to continue trying stuff or should I close this?