From b04d6d4d7ffbaf6d230f801e33c79eb08040f440 Mon Sep 17 00:00:00 2001 From: Jack Harper Date: Thu, 13 Nov 2025 09:39:37 +0000 Subject: [PATCH] Document velocity setting for Beckhoff commissioning --- doc/specific_iocs/motors/beckhoff/Beckhoff-commissioning.md | 1 + 1 file changed, 1 insertion(+) diff --git a/doc/specific_iocs/motors/beckhoff/Beckhoff-commissioning.md b/doc/specific_iocs/motors/beckhoff/Beckhoff-commissioning.md index cd98e4411..17c3ab428 100644 --- a/doc/specific_iocs/motors/beckhoff/Beckhoff-commissioning.md +++ b/doc/specific_iocs/motors/beckhoff/Beckhoff-commissioning.md @@ -37,6 +37,7 @@ Although commissioning a Beckhoff is far simpler than a Galil from an IBEX persp - Axis description (`.DESC`) - [ticket to automatically populate](https://github.com/ISISComputingGroup/IBEX/issues/6860) - Note, if `stDescription` is actually filled out on a Beckhoff you can use the `FORWARD_DESC` macro set to `1` which will forward the PLC description to the corresponding motor record's `.DESC` field. - Soft limits - [ticket to automatically populate](https://github.com/ISISComputingGroup/IBEX/issues/8763) +- Velocities (`.VELO`, `.JVEL`, `.VMAX` and others) These can be set via a `caput` and will be autosaved thereafter.