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
Which will remove trying to get the limits from the PV and make the motor appear to immediately move to the setpoint. I propose that we put something like this in as default behaviour in FakeEpicsMotor. Obviously generally simulating motion could be a pandoras box but this will at least allow plans with a basic mv in them to work
The text was updated successfully, but these errors were encountered:
Currently if we do a
bps.mv
on aFakeEpicsMotor
the plan will fail:We can fix this doing something like:
Which will remove trying to get the limits from the PV and make the motor appear to immediately move to the setpoint. I propose that we put something like this in as default behaviour in
FakeEpicsMotor
. Obviously generally simulating motion could be a pandoras box but this will at least allow plans with a basicmv
in them to workThe text was updated successfully, but these errors were encountered: