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

Scanner crosshair is not following the countrate #7

Closed
bbuusshh opened this issue Aug 2, 2022 · 3 comments
Closed

Scanner crosshair is not following the countrate #7

bbuusshh opened this issue Aug 2, 2022 · 3 comments

Comments

@bbuusshh
Copy link
Owner

bbuusshh commented Aug 2, 2022

No description provided.

@bbuusshh
Copy link
Owner Author

bbuusshh commented Aug 5, 2022

Changing the self._default_timer_interval = 1 # in ms
From 5ms to 1 ms seems to solve it and the attocube scanner scans much smoothly.
Needs more testing

@bbuusshh
Copy link
Owner Author

bbuusshh commented Aug 5, 2022

I as well constrained the moving velocity. It helped during a scan, Then after stopping and restarting the scan the weird behavior with skewed lines came back

@bbuusshh
Copy link
Owner Author

bbuusshh commented Aug 8, 2022

With default timer interfal 1 ms seems to be working fine.

@bbuusshh bbuusshh closed this as completed Aug 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant