Re: Would this motor record documentation be considered "current"

[Torsten Bögershausen via Tech-talk <tech-talk at aps.anl.gov>]

Now,

I would say that this document is not fully current.
- It seems to describe the model 1 driver
- It misses the model 3 driver "framework", which is what
  is used for all modern controllers.
- The Chapter 3.3 Backlash seems wrong.

I don't think that there is a difference between EPICS 3 and 7
regarding the EPICS motor module.


What information are you looking for ?

The "official" documentation is here:
<https://urldefense.us/v3/__https://github.com/epics-modules/motor/tree/master/docs__;!!G_uCfscf7eWS!bcxx9VUxVgj00rhv7GcRujSbI-VVEzfqzYfZbdlNlgPVpX63Dmc661WHUFNZwXo52oV7GMu64E0WgVPhsPQ$ >

And then I gave some introduction here:

<https://urldefense.us/v3/__https://github.com/EPICS-motor-wg/epics-mwg-discussions/blob/master/documents/2024-04-16-MotionTraining-at-PAL/3-MotorRec2024-v4.pptx__;!!G_uCfscf7eWS!bcxx9VUxVgj00rhv7GcRujSbI-VVEzfqzYfZbdlNlgPVpX63Dmc661WHUFNZwXo52oV7GMu64E0Wcco47Ts$ >

HTH
/Torsten


On 2025-04-29 18:16, Graeme Winter via Tech-talk wrote:
> Thanks Andy
>
> Yes, I had found that one also - however that one feels much more an 
> index of definitions than a narrative on how to get started :-)
> I’ll try following them in parallel to see if I can get an idea of where 
> things deviate… though maybe EPICS 3 and 7 deviate little in this area?
> All the best Graeme
>
> > On Apr 29, 2025, at 11:13 AM, Foster, Andrew (-,RAL,TEC) 
> > <Andrew.Foster at diamond.ac.uk> wrote:
> > Hi Graeme,
> > I’m not familiar with that document, I always look here:
> > https://urldefense.us/v3/__https://epics-modules.github.io/motor/motorRecord.html__;!!G_uCfscf7eWS!bcxx9VUxVgj00rhv7GcRujSbI-VVEzfqzYfZbdlNlgPVpX63Dmc661WHUFNZwXo52oV7GMu64E0WYs45UsU$  <https:// 
> > nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fepics- 
> > modules.github.io%2Fmotor%2FmotorRecord.html&data=05%7C02%7Cgw363%40cornell.edu%7Cd98be9eddd8b49bcda6c08dd8738d606%7C5d7e43661b9b45cf8e79b14b27df46e1%7C0%7C0%7C638815400507629612%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=xSHUzBvBgw%2BRhuRN4Bkg21wEDBnYlwKthI6w9ZZCoIg%3D&reserved=0>
> > Cheers, Andy
> > *From:*Tech-talk <tech-talk-bounces at aps.anl.gov <mailto:tech-talk- 
> > bounces at aps.anl.gov>>*On Behalf Of*Graeme Winter via Tech-talk
> > *Sent:*29 April 2025 16:40
> > *To:*tech-talk at aps.anl.gov <mailto:tech-talk at aps.anl.gov>
> > *Subject:*Would this motor record documentation be considered "current"
> > Good morning
> > Before I start committing too much of this to memory or putting it 
> > into effect, would this be considered “current”?
> > <image001.png>
> > epics-motor <https://urldefense.us/v3/__https://nam12.safelinks.protection.outlook.com/?__;!!G_uCfscf7eWS!bcxx9VUxVgj00rhv7GcRujSbI-VVEzfqzYfZbdlNlgPVpX63Dmc661WHUFNZwXo52oV7GMu64E0W5fMXQaM$  
> > url=https%3A%2F%2Fmdavidsaver.github.io%2Fepics-doc%2Fepics- 
> > motor.pdf&data=05%7C02%7Cgw363%40cornell.edu%7Cd98be9eddd8b49bcda6c08dd8738d606%7C5d7e43661b9b45cf8e79b14b27df46e1%7C0%7C0%7C638815400507648712%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=PsYmq0bx87OSQ9L5iTFyrxyX1wyVuatTwnj840nZAlk%3D&reserved=0>
> > PDF Document · 178 KB <https:// 
> > nam12.safelinks.protection.outlook.com/? 
> > url=https%3A%2F%2Fmdavidsaver.github.io%2Fepics-doc%2Fepics- 
> > motor.pdf&data=05%7C02%7Cgw363%40cornell.edu%7Cd98be9eddd8b49bcda6c08dd8738d606%7C5d7e43661b9b45cf8e79b14b27df46e1%7C0%7C0%7C638815400507663645%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=%2F3Zd6m2zw%2Bsl7yqtlMxURVcU0WxsJbOefFheopU0WGY%3D&reserved=0>
> > I note it is from 2010, which may or may not be recent in EPICSland
> > Thanks and all the best Graeme
> > This e-mail and any attachments may contain confidential, copyright 
> > and or privileged material, and are for the use of the intended 
> > addressee only. If you are not the intended addressee or an authorised 
> > recipient of the addressee please notify us of receipt by returning 
> > the e-mail and do not use, copy, retain, distribute or disclose the 
> > information in or attached to the e-mail. Any opinions expressed 
> > within this e-mail are those of the individual and not necessarily of 
> > Diamond Light Source Ltd.
> > Diamond Light Source Ltd. cannot guarantee that this e-mail or any 
> > attachments are free from viruses and we cannot accept liability for 
> > any damage which you may sustain as a result of software viruses which 
> > may be transmitted in or with the message.
> > Diamond Light Source Limited (company no. 4375679). Registered in 
> > England and Wales with its registered office at Diamond House, Harwell 
> > Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United 
> > Kingdom.