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.

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

in BLACS, Zaber stage does not obviously handle when device is not homed #39

Open
philipstarkey opened this issue Jan 28, 2020 · 0 comments
Labels
enhancement New feature or request minor

Comments

@philipstarkey
Copy link
Member

Original report (archived issue) by Chris Billington (Bitbucket: cbillington, GitHub: chrisjbillington).


Copying and pasting from a comment on PR #85:

The check-if-homed functionality is tricky.

As it stands, if not homed, one gets an error saying that the position is not as expected (remote value check reports the max position if not homed), and one can say ‘keep remote value’ then tell the device to go to position 0 in the GUI to actually home it.

I’ve been playing with ways of getting it to explicitly say ‘hey the device isn’t homed', but have been fighting BLACS' state machine to do so, it’s not really fitting in neatly. I’ll file a separate issue for it and merge this for now.

@philipstarkey philipstarkey added minor enhancement New feature or request labels Apr 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request minor
Projects
None yet
Development

No branches or pull requests

1 participant