bec/ophyd_devices
0
0
Fork 0
mirror of https://github.com/bec-project/ophyd_devices.git synced 2025-05-31 09:00:40 +02:00
Code Issues Packages Projects Releases Wiki Activity

Update README.md

Browse Source
This commit is contained in:
mohacsi_i 2024-03-12 10:49:41 +01:00
parent 172d735672
commit 1b328d31de
1 changed files with 4 additions and 45 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

49
ophyd_devices/epics/devices/aerotech/README.md
View File

@ -1,13 +1,6 @@
## Integration log for the Ophyd integration for the Aerotech Automation1 EPICS IOC
This is a short collection of reverse engineered wisdom from integrating the first complex device to BEC. The integration involved both the ophyd part and the corresponding scan API. It might not be fully accurate and some issues are probably misdiagnosed.
## Avoid the safespace API!!!
@ -28,9 +21,10 @@ The BEC has it's own event model, that's different from vanilla Bluesky. Particu
What's more is that unless it's explicitly specified in the scan, **ALL** ophyd devices (even listeners) get staged and unstaged for every scan. This either makes device management mandatory or raises the need to explicitly prevent this in custom scans.
### Scan server hangs
### The BEC hangs or deadlocks
Unfortunately a common behavior that manifests in . Common causes include the described issue with num_pos or raising an exception from the Ophyd layer. I'll expand this later.
Unfortunately a common behavior.
### Class
@ -135,38 +129,3 @@ Otherwise