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: "Pearson, Matthew R." <[email protected]>
To: "Konrad, Martin" <[email protected]>
Cc: "[email protected]" <[email protected]>
Date: Fri, 9 Aug 2013 10:31:13 -0400
Hi Martin,

In the past I've tested both simulation drivers to make sure they have the same behavior (although, with a limited set of tests). I would use the new phase-3 driver when ever possible. However, if you are using phase-2 drivers it would make sense to use the phase-2 simulation if you are concerned about changes in behavior.

The phase-3 drivers inherit from the asymMotorController base class, which in-turn inherits from asynPortDriver. So a quick look at the source code can tell you what kind of driver it is. Also, the phase-3 drivers tend to have IOC shell functions that look something like this:

createMyController(..)
createMyAxis(1)
createMyAxis(2)
etc.

with a separate function to instantiate the controller object, then either a function to create a single axis or a set of axes for that controller object.


I'm also using R6-8 here.

If you send me a tar file of your IOC, I'll build it here and see if I can reproduce it.

Maybe a detailed Asyn trace would also help.

Cheers,
Matt


On Aug 9, 2013, at 10:05 AM, "Konrad, Martin" <[email protected]> wrote:

> Hi,
>> Martin is actually using the 'phase 2' simulation driver. The phase 3
>> sim driver also has support for on-demand status updates.
> Which simulation driver is recommended? Do they all have the same
> behavior? Or is it wise to use the 'phase 2' simulation driver when
> simulating a device that only has a 'phase 2' driver?
> 
> How can I find out to which phase a driver belongs?
> 
>> Looking at the code, I think it should work. I just tested it with
>> both types of driver, and it works for me…
> 
>> Could you send me a dbpr of the motor record?
> I repeated the test with your DB file and st.cmd. Unfortunately the 
> record is still stuck in BUSY state. See the attached file for details.
> 
> Martin
> <output_IOC_shell.txt>



References:
motorRecord simulation & STUP field Konrad, Martin
Re: motorRecord simulation & STUP field Ron Sluiter
Re: motorRecord simulation & STUP field Konrad, Martin

Navigate by Date:
Prev: RE: [asyn] link already open! Mark Rivers
Next: Re: motor record: continuously update limit switches Konrad, Martin
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: Re: motorRecord simulation & STUP field Konrad, Martin
Next: Re: motorRecord simulation & STUP field Konrad, Martin
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 ·