DiamondLightSource / DiamondLightSource/mx-bluesky
Investigate potential motion issues with VMXm
Open
- Dominant language
- Python
- Stars
- 4
- Forks
- 5
- Avg merge
- 1d 30m
- Merged PRs (30d)
- 2
Description
The old bluesky gridscans on VMXm had an issue where the omega setpoint needed to be sent twice in order to get the expected motion - see https://github.com/DiamondLightSource/dodal/pull/211/files#r1404213835
For the new gridscans, we haven't got logic to resend Omega. During testing, we should check whether or not this is still an issue, and investigate properly if it is.
## Acceptance Criteria
- Check if omega needs to be resent when doing new VMXm gridscans
- If yes, find out why and deal with it
Contributor guide
Assessment
This issue has not been assessed yet.