# A better status API

**URL:** <https://forum.hello-robot.com/t/a-better-status-api/320>\
**Category:** Discuss\
**Created:** [November 9, 2021, 8:21am UTC](https://forum.hello-robot.com/t/a-better-status-api/320 "2021-11-09T08:21:09Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![aedsinger](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.hello-robot.com/aedsinger/32/6_2.png) [@aedsinger](https://forum.hello-robot.com/u/aedsinger)\
**Post date:** [November 9, 2021, 7:04pm UTC](https://forum.hello-robot.com/t/a-better-status-api/320/2 "2021-11-09T19:04:23Z")

</div>

Thank you for starting the conversation on this.

It would be helpful to understand what type of behavior you’re looking to generate by using queued rather than preempting incremental moves. Perhaps you can share some pseudo code?

The currently available incremental move interface is designed with servoing applications in mind. In this case, an external ‘observer’ commands a series of small motions until a target is achieved. Preemption is desirable as it allows for dynamic response to changes in the servo target.

Your goals may be achievable with the current control interface. If not, we can extend the interface for you.

Also, the progress of the joint trajectory is available as `motor.status['is_mg_moving']`. On the [other thread](https://forum.hello-robot.com/t/stretch-body-python-sdk-and-python-multithreading/221/10) I just posted details on working with it.

Finally, we are about to [release a significant upgrade](https://github.com/hello-robot/stretch_body/pull/118) to the Stretch Body Python SDK that introduces splined waypoint trajectories. This interface may be of interest depending on your use case.

---

_[View the full topic](https://forum.hello-robot.com/t/a-better-status-api/320)._