Experimental Physics and
Industrial Control System

Torsten bögershaus <[email protected]> · Wed, 11 Nov 2015 16:28:40 +0100

Hej Matt,
you say, that the problem could be easy re-produced.
Is there any chance to send a recipt here ?

A database ?
And a shell script which sets all the values...
(At least DLY is used, what more ?)
A shell script, or similar, to reproduce ?

BR
/Torsten

Am 11.11.2015 um 16:18 schrieb Pearson, Matthew R. <[email protected]>:

> 
> Hi,
> 
> There seems to be a problem with issuing a motor record STOP while we are waiting for a DLY settling time to expire. I can lock up the motor record if I issue a STOP after MOVN has gone to zero and before DMOV goes to 1. This only seems to be a problem if there are no further updates from the driver (so we have already stopped moving). It’s easy to reproduce using a simulation driver.
> 
> The problem can be cleared by either doing a SPMG cycle (stop, then go), or by setting any field that would cause a driver callback, which causes record processing, like changing CNEN. At the moment, the DLY seems to be repeated after the problem is cleared. So if I have a 5s DLY, I issue a STOP 4s into it, then I clear it by changing CNEN, then DMOV goes to 1 after a further 5s.
> 
> I suspect the desired behavior would be to cancel the delayed callbackRequest that implements the DLY, and not wait for it to expire, at least in this case, since we have already stopped moving then the DLY is probably too long anyway. And probably in other cases I suspect we want a put_callback to complete as soon as we issue a STOP, which is what happens when a STOP is done during a normal move. I can have a go at fixing this if that sounds like reasonable behaviour.
> 
> This is motor record version 6-8-1.
> 
> Cheers,
> Matt
> 
> 
> Data Acquisition and Control Engineer
> Spallation Neutron Source
> Oak Ridge National Lab
> 
> 
> 
> 
> 
> 

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System