Support the 12ID monochromator with bluesky

[prjemian]

Need to set and read energy. There may be details how to operate it. It's not a Kohzu monochromator.

[prjemian]

Started asking in BCDA for experience with this monochromator.

[prjemian]

EPICS database: /net/s12dserv/xorApps/epics/synApps_6_1/ioc/12ida1/db/SB_DCM.db

IOC: https://git.aps.anl.gov/12ID/12ida1

[prjemian]

Review the existing SPEC controls.

[prjemian]

... they used to have the 2nd crystal on a slide . . . so it roughly had to be positioned in the correct spot, but wasn't moved with the 1st crystal routinely . . . not sure if that design is/was still basically the same.

In the EPICS database...

Choices like this need to be considered by the users of the controls:

record(bo, "$(P)Z2_Mode") {  field(ZNAM, "Freeze Z2")  field(ONAM, "Move Z2")}

Bluesky can choose whether to avoid exposing this PV.

[jilavsky]

PVs
12ida2:E2P_driveValue.A is target energy keV
12ida2:E2P_driveValue.B is target wavelength
12ida:EnCalc and 12ida2:LambdaCalc
screen is BESSRC_Mono.ui in /net/s12dserv/xorApps/ui-autoconvert/12id/iocs/12ida2

[prjemian]

Thinking energy and wavelength should both be positioner Components so they act like motors, as part of a monochromator Device. Will need additional Components for things like Z2_Mode PV. Also, if there is any caution of adjust this before that, we'll need Components for each such PV and a procedure for such adjustment.

[jilavsky]

Tested 10-26 and looks like we need tolerance value. Trying 0.0002

[jilavsky]

Success, added tolerance and get mono E scans, however, the BS crashed again, see issue #7. Looks like #7 is showstopper at this time. Am I the only one or why is this the case?

[jilavsky]

Monochromator works as needed now, energy can be scanned, energy and wavelength can be recorded to metadata. This issue is fixed.