ISISComputingGroup / ISISComputingGroup/IBEX

IMAT: motion upgrade

Open
#9,027 2 comments 0 reactions 2 assignees Claimed by @Tom-Willemsen View on GitHub
added during sprint Core motion control Pair Program
Dominant language
No language data
Stars
6
Forks
2
Avg merge
16h 40m
Merged PRs (30d)
2

Description

Realised I hadn't put this in a ticket.

IMAT's motion is being migrated from Galils to Beckhoff in entirety. Previously IMAT used a Beckhoff for just the large Z/Rot stage.

Things to do:
- [x] sort out networking to the beckhoff
- [x] re-set up ADS route
- [x] change amsnetID
- [x] remove galils from main configuration
- [x] copy over axes.cmd
- [x] copy over jaws.cmd
- [x] copy over motionsetpoints.cmd
- [x] copy over sampleChanger.cmd
- [x] fix this - dbd isn't loaded currently
- [x] add toggle for axis velocity forwarding (we previously removed this due to a race condition within the beckhoff, but we should re-add it for future commissioning as it'll be fixed going forwards, but not retrospectively)
- [x] add safety variables
- [x] add the above to banner.xml
- [x] add "motion isolator status"
- [x] add homing variable PVs and archive readbacks
- [ ] document safety system and any other items which need making clear for support calls etc.
- [x] document `FORWARD_VELO` change: https://isiscomputinggroup.github.io/ibex_developers_manual/specific_iocs/motors/beckhoff/Beckhoff-commissioning.html#beckhoff-manual-commission-step
- [ ] remove any references to IMAT having galils in wiki pages and anywhere else relevant
- [x] set `.DLY` to non-zero
- [x] set `.EGU` as appropriate - can use stDescription.sUnits
- [x] `make` this and copy over to NDXIMAT when SC is done filling this part of `stDescription` out
- [x] set soft limits up

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.