acquisition constant wm = w1 not functioning as intended

[DLafayetteII]

When scanning w1, and setting the constant wm = w1:

1. wm moves to current w1 setpoint. This is before w1 has moved to its first acquisition setpoint.
2. w1 moves to first color setpoint. wm remains stationary
3. w1 scans through all colors. wm remains stationary

It seems that the constant is only enforced before motor scanning starts?

[DLafayetteII]

I will note that checking both the w1 and wm box for a given energy scan range (and not using a constant wm = w1) does move the motors as intended.

[ksunden]

Are you sure you are using the right grating/ranges? it works fine when I try it...

Constants are indeed precomputed, but that should not matter, it takes into account the hardware setpoints to get the full multidimensional array.

[DLafayetteII]

1. I am using the proper grating
2. Is the 'proper' grating newly software limited? Historically either grating can be set to any color, but the efficiency/resolution/functionality will suffer.

I can reproducibly observe the monochromator position in the GUI not moving from initial, and the grating inside the monochromator remaining stationary from scan start.

I will go reproduce this again now to verify.

[DLafayetteII]

Reproduced, output data also supports the monochromator being at a single color.

[ksunden]

Monos have always been limited, at least in practice... (I think we may have let you set them outside of the range at one point, but they go to random (at least seeming) positions if you go above 1580 nm for a 1200 g/mm grating (lower g/mm allows you to go to longer wavelengths, proportionally)

In wn, you can go from some minimum value to inf (as 0 nm is inf wn)

[DLafayetteII]

I just know I can visit colors that will literally put the grating perpendicular to the entrance, blocking all light. Regardless, I am using the a good grating for my intended scanning range.