Remove SM300 documentation, add note about motorextensions settings

Author: rerpha

doc/iocs/troubleshooting/IOC-flow-control-settings.md

@@ -71,7 +71,6 @@
 | SECI2IBEX           | LVDCOM | LVDCOM | IOC |  |
 | SKFCHOPPER          | IP | IP | IOC |  |
 | SKFMB350            | Off | Off | VI (manual?) | [3180](https://github.com/ISISComputingGroup/IBEX/issues/3180) |
-| SM300               | Off | Off | VI | [3139](https://github.com/ISISComputingGroup/IBEX/issues/3139) |
 | SMC100              | On | Off | Manual | [3139](https://github.com/ISISComputingGroup/IBEX/issues/3139) |
 | SP2XX               | Off | Off | Manual and VI |  |
 | SPINFLIPPER306015   | Off | Off | Manual | [3180](https://github.com/ISISComputingGroup/IBEX/issues/3180) |

doc/specific_iocs/Motors.md

@@ -50,7 +50,6 @@ motors/Linmot
 motors/McLennan-motors
 motors/Newport
 motors/PI-Rotation-Stage-setup
-motors/SM300
 motors/SMC100
 motors/SXD-Attocube
 ```

doc/specific_iocs/motor_extensions/Axis.md

@@ -2,7 +2,7 @@
 
 Axis records add a layer of indirection between the user and the low level motor. This means if the underlying motor needs to change it only need to change in one place, all blocks, motion set points etc use this axis and so don't need to change.
 
-The record is setup in the configuration directory in the motor directory in a file called axes.cmd (e.g. for galil it would by `galil/axes.cmd` for SM300 it would be `SM300_01/axes.cmd` (NB Galil are not based on the IOC number so you need an extra macro to make sure you only add the axis to the correct galil).
+The record is setup in the configuration directory in the motor directory in a file called axes.cmd (e.g. for galil it would by `galil/axes.cmd` (NB Galil are not based on the IOC number so you need an extra macro to make sure you only add the axis to the correct galil).
 
 An example of adding an axis to a galil is:
 

doc/specific_iocs/motor_extensions/Motion-Set-points.md

@@ -3,10 +3,9 @@
 Motion set points allow you to label set positions for any number of axis, though currently db files are only created for single, double or 10 axes. Other numbers of axis can also be easily created by following the example of these. The code for this is in support in the directory [motionSetPoints](https://github.com/ISISComputingGroup/EPICS-motionSetPoints). The configuration for a motion set point is in a number of parts:
 
 1. First, you must set up axes on the motors that you want to configure with the set points
-1. St file called `motionsetpoints.cmd` which sets up the db file which is stored in the configuration under the motor name:
+1. St file called `motionsetpoints.cmd` which sets up the db file which is stored in [the `motorExtensions` settings](https://github.com/ISISComputingGroup/EPICS-motorExtensions/tree/master/settings) under the motor name:
     - galil is `Settings\config\<host name>\configurations\galil`
     - Mclennan is `Settings\config\<host name>\configurations\mcleanan`
-    - SM300 is `Settings\config\<host name>\configurations\<sm300 ioc name e.g. SM300_01>`
 1. The positions which are referenced from the st file. are stored in  `Settings\config\<host name>\configurations\motionSetPoints`
 
 The  `motionsetpoints.cmd` contains the following lines:

doc/specific_iocs/motors/SM300.md

@@ -51,7 +51,11 @@ Configuration files for the DAE.
 
 ### Configuration of devices and extensions
 
-These are directories which configure devices which would be too complicated for macro configuration. For example the Galil configuration with the need to setup the controller, homing routines etc. Historically this was named after a category of device, e.g. galil. This allow configuration of devices as a whole. They can also be named after an IOC which allow configuration of a single IOC, e.g SM300_01. 
+```{note}
+Motion-related configuration has now been moved to [motorExtensions](https://github.com/ISISComputingGroup/EPICS-motorExtensions/tree/master/settings) as per [this ticket](https://github.com/ISISComputingGroup/IBEX/issues/8427)
+```
+
+These are directories which configure devices which would be too complicated for macro configuration. For example the Galil configuration with the need to setup the controller, homing routines etc. Historically this was named after a category of device, e.g. galil. This allow configuration of devices as a whole. They can also be named after an IOC which allow configuration of a single IOC, e.g TC_01. 
 
 The extensions are items which extend an IOC for example a motion setpoints which allow a motor to stop at labelled positions. These are configured from the IOC configuration directory and may need optional extra configuration directories.
 
@@ -61,14 +65,13 @@ Directories:
 
 - `galil`: configures the galil [Galil](/specific_iocs/motors/Galil) and extensions
 - `mclen`: configures McLennan motors [McLennan](/specific_iocs/motors/McLennan-motors) and extensions
-- `sm300_01`: configures the [SM300_01](/specific_iocs/motors/SM300) motor extensions 
 - `motionSetPoints`: setpoint look up files
 - `refl` (for reflectometers only): contains a file `config.py`, which tells instruments using the [Reflectometry IOC](/specific_iocs/Reflectometry-IOC) what their beamline looks like (follow the link for details)
 
 Common extensions:
- - [Motion Set points](/specific_iocs/motor_extensions/Motion-Set-points) (works for galil, McLennan and SM300)
- - [axes](/specific_iocs/motor_extensions/Axis) (works for galil, McLennan and SM300)
- - [sample changer](/specific_iocs/motor_extensions/Sample-Changer-Support-Module) (works for galil, McLennan and SM300)
+ - [Motion Set points](/specific_iocs/motor_extensions/Motion-Set-points) (works for galil, McLennan and TC)
+ - [axes](/specific_iocs/motor_extensions/Axis) (works for galil, McLennan and TC)
+ - [sample changer](/specific_iocs/motor_extensions/Sample-Changer-Support-Module) (works for galil McLennan and TC)
  - [Barn doors and Momentum slits](/specific_iocs/motor_extensions/jaws/Barndoors-and-Momentum-Slits-on-MUON-Front-End)
 
 ### Version Control