Open DominicOram opened 2 weeks ago
I suspect this may be because DetectorMotion
is an ophyd
device and BartRobot
is a n ophyd_async
device. Is this a known issue @coretl or @callumforrester?
Could only be on old versions of ophyd/ophyd_async:
ophyd 1.9.0
ophyd-async 0.3.4
I saw a similar issue a few months ago when using both ophyd
and ophyd-async
devices. I had to run a bluesky plan on an ophyd
device before trying to set
anything on an ophyd-async
device, otherwise it would timeout
Does this branch fix the issue: https://github.com/DiamondLightSource/aioca/tree/contexts?
Great, that fixed it, thank you! Are we able to get it into a release soon? Or will we have to live with reading a dummy ophyd
device for a bit?
I just have to work out how to write a test for the change... then I can make a release. Maybe a couple of weeks?
Ok, we will keep the dummy PV for now then. This issue will be for adding the read in on main and spin off a new issue to remove when aioca is released
During beamline testing it was found that the following script timed out reading from
current_pin
:However, if the
current_det_z
lines were uncommented it would no longer timeout and was happy to continue. The timeout error was:Acceptance Criteria
ophyd
device first