Experimental Physics and
Industrial Control System

1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 <2022> 2023 2024	Index	1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 <2022> 2023 2024
<== Date ==>		<== Thread ==>

Subject:	Re: motor record field assignment problem
From:	Mark Rivers via Tech-talk <tech-talk at aps.anl.gov>
To:	Kevin Peterson <kmpeters at anl.gov>, 高振华 <gaozh at ihep.ac.cn>
Cc:	"tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>
Date:	Mon, 31 Jan 2022 15:38:14 +0000

Hi Zhenhua,

Sorry for the delay in getting back to you. I can add to some things Kevin said.

You asked about the DTYP field. For model-3 drivers this is always "asynMotor". For older model-1 drivers it is driver-specific. One way to determine the correct value is to look at the example substitutions files. For example, motor/modules/motorOms/iocs/omsIOC/iocBoot/iocOms/MAXv.substitutions contains this:

{P, N, M, DTYP, C, S, DESC, EGU, DIR, VELO, VBAS, ACCL, BDST, BVEL, BACC, MRES, PREC, DHLM, DLLM, INIT}
{oms:, 1, "m$(N)", "OMS MAXv", 0, 0, "MAXv M$(N)", mm, Pos, 1, .1, .2, 0, 1, .2, 2.5e-4, 5, 100, -100, ""}

So you can see that DTYP is "OMS MAXv".

If there is no example substitutions file, then you can look at the .dbd file for that driver. In this case devOms.dbd contains this line:

devOms.dbd:device(motor,VME_IO,devMAXv,"OMS MAXv")

> The content of the motordevicedriver. HTML file is not completely displayed, and only this sentence is displayed:

You are correct, that documentation file is incomplete. It ends with this line:

NOTE: This documentation file is incomplete. It needs to be completed.

I started writing that documentation in 2012 and never finished it.

Mark

From: Kevin Peterson <kmpeters at anl.gov>
Sent: Monday, January 31, 2022 9:09 AM
To: 高振华 <gaozh at ihep.ac.cn>; Mark Rivers <rivers at cars.uchicago.edu>
Cc: tech-talk at aps.anl.gov <tech-talk at aps.anl.gov>
Subject: Re: motor record field assignment problem

1. The motor record provides databases that simplify specifying the OUT
field. Older model-1 motor drivers use motor.db:

https://github.com/epics-modules/motor/blob/master/motorApp/Db/motor.db#L16

C is the index of the controller and S is the index of the motor. Both
start at zero.

Newer model-3 motor drivers use asyn_motor.db:

https://github.com/epics-modules/motor/blob/master/motorApp/Db/asyn_motor.db#L16

PORT is the name of the asyn port created by when the motor driver was
started. ADDR is the index of the axis, starting at zero.

2. Is the content on this web page visible?

   https://epics-modules.github.io/motor/motorDeviceDriver.html

If not, the file also resides in the motor module's docs directory
(documentation for older versions).

3. The name of the motor's VAL field is written to one of the sscan
record's positioner fields (P1PV, P2PV, P3PV, P4PV).

Kevin

On 1/27/22 21:49, 高振华 via Tech-talk wrote:
> *Hello Mark,*
>
> *I am learning stepper motor control and have encountered some problems. *
>
> *1. I don't know how to fill in the values of DTYP and OUT fields in
> motor records. *
>
> *For a certain type of stepper motor controller how to know its
> corresponding DTYP value and OUT or INP field assignment format? I
> can't find the assignment format description in the motor example and
> documentation, do I have to look it up in the source code? *
>
> *2. the content of the motordevicedriver. HTML file is not completely
> displayed, and only this sentence is displayed: *
>
> *“****asynMotorAxis base class*
>
> *The asynMotorAxis base class defines the following methods:”*
>
> *Where can I download a full version?*
>
> *3. **By which field is the SSCAN record connected to the motor record? *
>
> **
>
>   * *
>
>     For example, the motor record of the OMS VME58 is shown below
>
>     *
>
> **
>
> Thank you!
>
> Best regards,
>
> Gao Zhenhua
>
>
> --
>
> BSRF(Beijing Synchrotron Radiation Facility)
> Email:gaozh at ihep.ac.cn <mailto:gaozh at ihep.ac.cn>
>
>
>
>

Replies:: Re: Re: motor record field assignment problem 高振华 via Tech-talk

References:: motor record field assignment problem 高振华 via Tech-talk; Re: motor record field assignment problem Kevin Peterson via Tech-talk

Navigate by Date:: Prev: Re: motor record field assignment problem Kevin Peterson via Tech-talk; Next: Re: Phoebus-olog integration Larregui, Julian via Tech-talk; Index: 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 <2022> 2023 2024
Navigate by Thread:: Prev: Re: Re: motor record field assignment problem 高振华 via Tech-talk; Next: Re: Re: motor record field assignment problem 高振华 via Tech-talk; Index: 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 <2022> 2023 2024

ANJ, 14 Sep 2022

· Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System