EPICS Controls Argonne National Laboratory

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  <20132014  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  <20132014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: motorRecord simulation & STUP field
From: Ron Sluiter <[email protected]>
To: "Konrad, Martin" <[email protected]>
Cc: "[email protected]" <[email protected]>
Date: Thu, 8 Aug 2013 13:28:22 -0500
Hello Martin,

I don't know the details, but I suspect that the asyn motor phase 3
device/driver model (which I believe "motorSimCreate" is) lacks support
for the Status Update (STUP) motor record field.

The asyn motor phase 2 simulator (see motorSimSupport.dbd) has
support for STUP; see motorAxisforceCallback() in MotorSimSrc/drvMotorSim.c

Ron

On 8/8/2013 12:47 PM, Konrad, Martin wrote:
Hi,
I came across the following issue while using motor record with
DTYP="asynMotor". If I request a status update by

$ caput test.STUP 1

the field seems to stay in state BUSY forever:

$ camonitor motorSim:test0.STUP
test.STUP            2013-08-08 13:31:58.426150 OFF
test.STUP            2013-08-08 13:31:58.426150 ON
test.STUP            2013-08-08 13:32:47.299463 BUSY

I guess that's not the intended behavior. Here is my database file
(pretty much the example):

record(motor,"test")
{
    field(DESC,"Motor Simulation test")
    field(DTYP, "asynMotor")
    field(VELO,"1")
    field(VBAS,"0")
    field(VMAX,"1")
    field(HVEL,"1")
    field(ACCL,"1")
    field(BDST,"0.01")
    field(BVEL,"0.1")
    field(BACC,"0.1")
    field(OUT,"@asyn(sim1,1)")
    field(MRES,"0.001")
    field(PREC,"5")
    field(EGU,"mm")
    field(DHLM,"30")
    field(DLLM,"-30")
}

In st.cmd I have:
motorSimCreate( 0, 0, -22000, 42000, 10000, 1, 2 )
drvAsynMotorConfigure("sim1", "motorSim", 0, 2)

Is the STUP field supposed to work with this device support?

Regards,

Martin


Replies:
RE: motorRecord simulation & STUP field Mark Rivers
Re: motorRecord simulation & STUP field Pearson, Matthew R.
References:
motorRecord simulation & STUP field Konrad, Martin

Navigate by Date:
Prev: motorRecord simulation & STUP field Konrad, Martin
Next: RE: motorRecord simulation & STUP field Mark Rivers
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: motorRecord simulation & STUP field Konrad, Martin
Next: RE: motorRecord simulation & STUP field Mark Rivers
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 20 Apr 2015 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·