Re: motorRecord simulation & STUP field

[Kevin Peterson <kmpeters@anl.gov>]

Which release of the motor module are you using?

Kevin

On 8/8/13 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
> 
> 
>