# Slow/stale telemetry using python MAVSDK server

**URL:** <https://discuss.px4.io/t/slow-stale-telemetry-using-python-mavsdk-server/45668>\
**Category:** MAVSDK\
**Created:** [May 21, 2025, 9:55am UTC](https://discuss.px4.io/t/slow-stale-telemetry-using-python-mavsdk-server/45668 "2025-05-21T09:55:24Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![thomastolbol](https://discuss.px4.io/user_avatar/discuss.px4.io/thomastolbol/32/19466_2.png) [@thomastolbol](https://discuss.px4.io/u/thomastolbol)\
**Post date:** [May 21, 2025, 9:55am UTC](https://discuss.px4.io/t/slow-stale-telemetry-using-python-mavsdk-server/45668/1 "2025-05-21T09:55:25Z")

</div>

I’m running PX4 SitL in Gazebo and trying to connect to it via python using MAVSDK server.

Code:

```auto
import mavsdk
drone = mavsdk.System(port=50041)
await drone.connect(system_address=f"udp://14541")
async for position in drone.telemetry.position():
   print(position)

```

At first the position data is good, but it quickly gets out of sync. For instance, the telemetry data will show that the drone is in the air even long after it has landed. Even after shutting down the simulation old telemetry data will keep coming in, even 30 minutes later! Is there some sort of buffer in MAVSDK server that stores the incoming telemetry?

---

<div class="post-metadata">

**Author:** ![thomastolbol](https://discuss.px4.io/user_avatar/discuss.px4.io/thomastolbol/32/19466_2.png) [@thomastolbol](https://discuss.px4.io/u/thomastolbol)\
**Post date:** [May 21, 2025, 2:34pm UTC](https://discuss.px4.io/t/slow-stale-telemetry-using-python-mavsdk-server/45668/2 "2025-05-21T14:34:59Z")

</div>

I solved the problem. It turns out that somewhere else in my code was blocking my async loop, preventing the telemetry data from being consumed at the rate it is being received.