From 28c093a5ffa28dd84e9017562ec990da28603838 Mon Sep 17 00:00:00 2001 From: Jack Harper Date: Fri, 15 May 2026 16:19:44 +0100 Subject: [PATCH] Document method to check recent motor field changes --- .../motors/Motors-Trouble-Shooting.md | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/doc/specific_iocs/motors/Motors-Trouble-Shooting.md b/doc/specific_iocs/motors/Motors-Trouble-Shooting.md index 4a2123447..b494d68ca 100644 --- a/doc/specific_iocs/motors/Motors-Trouble-Shooting.md +++ b/doc/specific_iocs/motors/Motors-Trouble-Shooting.md @@ -19,6 +19,25 @@ IN:INST:MOT:JAWS:VGAP:MIN:SP On many instruments, this has been set to `-2147483648` to effectively disable the minimum-gap checking. This can also be set temporarily. +### Settings are suspected to have changed recently + +Not all motor record fields are archived, however their values are saved in autosave files. + +An easy way of seeing whether a field has changed recently, is to use `grep` and look in the file contents. As the files are suffixed with the time they were created this effectively gives a time record of when things happened: + +For example in this case we want to see the `UEIP` field of `MTR0102`. First open a git bash session (which works over ssh): +``` +"\Program Files\Git\bin\bash.exe" +``` + +then: + +``` +grep -rnw '/c/Instrument/var/autosave/GALIL_01' -e 'MTR0103.UEIP' +``` + + + ### Position needs to be restored Note: [a script exists for this](/tools/archive_tools/Restore-Motor-Positions-from-Archive)