You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have been hoping to have fly scanning of our undulator and monochromator since opening to general users. However, it is just getting going now. Dean Hidas and @mrakitin have been working hard to get this going in bluesky.
Currently, you need to enable this coordinated motion on a CSS page, under the Operator page for the 5-ID insertion device, there is a button for scan mode. From there you can see all the options. Enabling fly-scan is done by setting 1 to SR:C5-ID:G1{IVU21:1}MACROControl-SP.
If this mode is enabled, then the undulator cannot be moved in bluesky (energy.move(new_energy)) doesn't work. Can we put in some checking to see if there is write access to the undulator PVs, or maybe disable the fly-scan mode and then perform the move?
The text was updated successfully, but these errors were encountered:
We have been hoping to have fly scanning of our undulator and monochromator since opening to general users. However, it is just getting going now. Dean Hidas and @mrakitin have been working hard to get this going in bluesky.
Currently, you need to enable this coordinated motion on a CSS page, under the Operator page for the 5-ID insertion device, there is a button for scan mode. From there you can see all the options. Enabling fly-scan is done by setting 1 to SR:C5-ID:G1{IVU21:1}MACROControl-SP.
If this mode is enabled, then the undulator cannot be moved in bluesky (energy.move(new_energy)) doesn't work. Can we put in some checking to see if there is write access to the undulator PVs, or maybe disable the fly-scan mode and then perform the move?
The text was updated successfully, but these errors were encountered: