Skip to content
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

shutter not moving when expected #269

Closed
prjemian opened this issue Dec 5, 2019 · 2 comments
Closed

shutter not moving when expected #269

prjemian opened this issue Dec 5, 2019 · 2 comments
Assignees
@prjemian
Labels
bug
Milestone
1.1.16

Comments

@prjemian
Copy link
Contributor

prjemian commented Dec 5, 2019 •
edited
Loading

As observed at XPCS 8-ID-I by @sureshnaps, a shutter is not moving with the bps.mv(shutter, "close") command from bluesky. Previously, the shutter was closed with the same command, then opened from the GUI screens (unknown to bluesky). When bluesky was told to close the shutter, nothing happened.
@prjemian prjemian added the bug label Dec 5, 2019
@prjemian prjemian added this to the 1.1.16 milestone Dec 5, 2019
@prjemian prjemian self-assigned this Dec 5, 2019
@prjemian
Copy link
Contributor Author

prjemian commented Dec 5, 2019

We're observing problems at times with signal.value where the value seems stale. Replacing with signal.get() produces the expected result. Probably the case here. Look in the Shutter base class.

@prjemian
Copy link
Contributor Author

prjemian commented Dec 5, 2019

Responsibility for this is in the state() method defined by each subclass.

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

@prjemian prjemian

Labels
bug
Projects
None yet
Milestone
1.1.16
Development

No branches or pull requests
1 participant
@prjemian