New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

SmarPod scanning issues #1

Closed

klauer opened this issue Feb 18, 2016 · 1 comment

Contributor

klauer commented Feb 18, 2016

Scanning multiple SmarPod axes (e.g., in a mesh scan) fails due to bluesky's set and wait_on_group style of motion commands.

Best would be to fix it on the IOC level such that multiple motion requests all return motion complete properly.

Simple immediate fix could be:

Move axes individually in the scan plans

Post ophyd refactor

A PseudoPositioner should take care of this - set all setpoints and then move()

Hanfei indicated this could be worked around in the short term, so leaving it open as-is.

The text was updated successfully, but these errors were encountered:

klauer mentioned this issue

Motion with multiple axes can cause put completion to not return properly klauer/smarpod#1

Open

jklynch commented Jul 16, 2019

closing as stale, HXN staff report they do not see this issue anymore.

jklynch closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment