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  2013  2014  2015  2016  <20172018  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  2013  2014  2015  2016  <20172018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: Motor module problem
From: Jörn Dreyer <[email protected]>
To: [email protected]
Date: Thu, 28 Sep 2017 11:25:24 +0200
Am Donnerstag, 28. September 2017, 11:05:50 CEST schrieb Torsten Bögershausen:
> First of all, I don't understand that either.
> 
> Which versions (EPICS base, motor) do you use ?
I use EPICS base 3.15.5 and motor R6-9 ans asyn4-32.
> Are you sure that everything is freshly compiled ?
Yes.
> And, could you send us a complete log file ?
Will follow. That's not trivial. I changed the code slightly and now run into 
a segmentation fault.

Regards,

Jörn
> 
> On 28/09/17 10:04, Jörn Dreyer wrote:
> > Hello,
> > 
> > currently I'm working on a piezo motor driver based on the
> > asynMotorController. At startup of the IOC the Axis::move command is
> > called
> > with parameters that I do not understand. If I put a printout statement at
> > the beginning of the function like this:
> > 
> > printf("%s %d %s %f %d %f %f %f\n", "Moving axis", axisNo_+1, "to
> > position", position, relative, minVelocity, maxVelocity, acceleration);
> > 
> > it results in:
> > 
> > Moving axis 1 to position inf 0 0.000000 0.000000 0.000000
> > 
> > The corresponding record looks like this:
> > 
> > record(motor, "A:m1") {
> > 
> >    field(DESC, "Mirror 1")
> >    field(DTYP, "asynMotor")
> >    field(DIR, "1")
> >    field(VELO, "110.")
> >    field(VBAS, ".05")
> >    field(ACCL, ".5")
> >    field(BDST, "0")
> >    field(BVEL, "1.0")
> >    field(BACC, "2")
> >    field(OUT, "@asyn(B,0)")
> >    field(MRES, "0.00001")
> >    field(PREC, "5")
> >    field(EGU, "mm")
> >    field(DHLM, "0.32768")
> >    field(DLLM, "1")
> >    field(INIT, "")
> >    field(RTRY, "5")
> >    field(TWV, "1")
> >    field(SDIS, "A:m1_able.VAL")
> >    field(VMAX, "190.")
> > 
> > }
> > 
> > It gets called three times, first with inf, then with DHLM, and then with
> > 10000. Looks like it wants to do something like homing. How can I prevent
> > this?
> > 
> > Regards,
> > 
> > Jörn


-- 
Dr. Joern Dreyer
HIBEF DAQ + Controls
Institut für Strahlenphysik
Helmholtz-Zentrum Dresden - Rossendorf e.V
Abt. FWKH                Tel: +49 351 260 3263
                                   FAX: +49 351 260 3700
01314 Dresden        eMail: [email protected]

Helmholtz-Zentrum Dresden - Rossendorf e.V
Bautzner Landstraße 400, 01328 Dresden
Vorstand: Prof. Dr. Roland Sauerbrey, Dr. Dr. h. c. Peter Joehnk
VR 1693 beim Amtsgericht Dresden

References:
Motor module problem Jörn Dreyer
Re: Motor module problem Torsten Bögershausen

Navigate by Date:
Prev: Re: Motor module problem Torsten Bögershausen
Next: Question about the epics driver for PXIe-5162 high speed digitizer (National instruments) lzf neu
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <20172018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: Motor module problem Torsten Bögershausen
Next: Question about the epics driver for PXIe-5162 high speed digitizer (National instruments) lzf neu
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <20172018  2019  2020  2021  2022  2023  2024 
ANJ, 21 Dec 2017 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·