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  2013  2014  2015  2016  2017  2018  <20192020  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  <20192020 
<== Date ==> <== Thread ==>

Subject: Re: Undefined Timestamp on Motor Record
From: "Peterson, Kevin M. via Tech-talk" <tech-talk@aps.anl.gov>
To: Dominic Oram - UKRI STFC <dominic.oram@stfc.ac.uk>, "tech-talk@aps.anl.gov" <tech-talk@aps.anl.gov>
Date: Thu, 15 Aug 2019 19:26:43 +0000
Dominic,

If the motorStatusCommsError_ is set to 1 on the first poll, long before 
iocInit, and a one is written to MOTOR.PROC after iocInit, does the 
camonitor output show an up-to-date timestamp and the comm invalid status?

Kevin

On 8/15/19 12:16 PM, Dominic Oram - UKRI STFC via Tech-talk wrote:
> Hello,
> 
> I’m in the process of writing a model 3 motor driver using version 6-11 
> of the motor record.
> 
> I have found some unexpected behaviour on initialisation if the driver 
> has no device connected.
> 
> It appears the motor stays in the following state unless a parameter is 
> updated at some point after initialisation (I’m not sure when):
> 
> caget –a MOTOR
> MOTOR        <undefined> 0
> 
> If I have no device connected I set motorStatusCommsError_ to 1 on the 
> first call to poll(). However, because all subsequent calls to poll() do 
> not change any parameters I stay in the above state. I would instead 
> expect to see something like:
> 
> caget –a MOTOR
> MOTOR        2019-08-15 15:57:41.931650 0 COMM INVALID
> 
> as in the undefined timestamp situation it’s not obvious to users that 
> there is a comm error.
> 
> Setting motorStatusCommsError_ to 1 at some time after initialisation 
> does give me the expected state.
> 
> Is this actually expected behaviour? Do other people see something similar?
> 
> Thanks,
> 
> Dominic Oram
> 
> Senior Software Engineer
> 
> Experimental Controls
> 
> ISIS Neutron and Muon Source
> 

References:
Undefined Timestamp on Motor Record Dominic Oram - UKRI STFC via Tech-talk

Navigate by Date:
Prev: FW: mbboDirect record setup Mark Rivers via Tech-talk
Next: Re: Undefined Timestamp on Motor Record William Layne 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  <20192020 
Navigate by Thread:
Prev: Undefined Timestamp on Motor Record Dominic Oram - UKRI STFC via Tech-talk
Next: Re: Undefined Timestamp on Motor Record William Layne 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  <20192020 
ANJ, 15 Aug 2019 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·