update generic_ioc, support_module

Author: gilesknap

docs/tutorials/generic_ioc.md

@@ -713,5 +713,8 @@ You can follow along with the CI build by clicking the actions tab in your repos
 
 https://github.com/orgs/YOUR_GITHUB_ACCOUNT/packages?repo_name=ioc-lakeshore340
 
-EXERCISE: Now that you have a published container for ioc-lakeshore340. See if you can add an IOC instance that uses this into your `bl01t` beamline. You should then be able to run up your IOC instance with `ec deploy-local`. You could also run a local version of the simulator and see if you can get the IOC to talk to it.
+## EXERCISE
+
+Now you have a published Generic IOC container image for ioc-lakeshore340. See if you can add an IOC instance that uses this into your `bl01t` beamline. You should then be able to run up your IOC instance with `ec deploy-local`. You could also run a local version of the simulator and see if you can get the IOC to talk to it.
+
 

docs/tutorials/support_module.md

@@ -1,32 +1,23 @@
 # Working with Support Modules
 
 :::{Warning}
-This tutorial is out of date and will be updated soon.
+This tutorial is an early draft and is not yet complete.
 :::
 
-TODO: this is currently a stub with some pointers.
-
-TODO: suggest that we will make a new Stream Device that will be a
-simple echo server. Use this to step through the process of creating a
-new support module.
-
 This is a type 3. change from the list at {any}`ioc-change-types`.
 
-If you are starting a new support module then the preceding tutorials
-have covered all of the skills you will need.
-
-To work on a new support module you will need a Generic IOC project to
-work inside. You could choose to create two new projects:
-
-```{eval-rst}
-
-:ioc-MyNewDeviceSupport:
+In the tutorial on {doc}`/tutorials/generic_ioc`, we created a new Generic IOC container image that wrapped the existing support module `lakeshore340`.
 
-    a Generic IOC container definition based on ioc-template
+If you wanted to create a completely new support module then you would use a very similar workflow to the above.
 
-Once you have created the project(s), working on the support module will
-look very similar to the procedures set out here `debug_generic_ioc`
-```
+In brief, the steps are:
 
-Once you have created the project(s), working on the support module will
-look very similar to the procedures set out here {any}`debug_generic_ioc`
+- Create a new Generic IOC project using the <https://github.com/epics-containers/ioc-template>
+- Create a new folder in /workspaces/YOUR_SUPPORT_MODULE_NAME
+- Link the new folder to the epics support folders:
+  - ln -s /workspaces/YOUR_SUPPORT_MODULE_NAME /epics/support/YOUR_SUPPORT_MODULE_NAME
+  - TODO the ibek command `ibek dev support YOUR_SUPPORT_MODULE_NAME` will do this in future
+- Now work on your support module and get it compiling
+- Then add `ibek-support` for the new module as per {doc}`/tutorials/generic_ioc`
+- create an example instance in the Generic IOC project to test your work
+- When ready, push your new support and new ioc-support projects.