EPICS Home

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: Problems with motor record
From: Jörn Dreyer <[email protected]>
To: [email protected]
Date: Tue, 17 Oct 2017 12:29:23 +0200
Hi Torsten

I enabled the full debugging output from my motor driver, and this is what I 
get:

Starting iocInit
############################################################################
## EPICS R3.15.5
## EPICS Base built Feb  6 2017
############################################################################
2017/10/17 12:25:24.277 port1 0 registerInterruptUser
2017/10/17 12:25:24.277 asynMotorController:readGenericPointer: MotorStatus = 
status0, position=1.000000, encoder position=1.000000, velocity=0.000000
2017/10/17 12:25:24.277 devMotorAsyn::build_trans: P:m1 motor_cmnd=9, pact=0, 
value=0.000010
2017/10/17 12:25:24.277 devAsynMotor::build_trans: calling queueRequest, 
pmsg=0xcae280, sizeof(*pmsg)=24pmsg->command=10, pmsg->interface=1, pmsg-
>dvalue=0.000010
2017/10/17 12:25:24.277 port1 addr 0 queueRequest priority 0 not lockHolder
2017/10/17 12:25:24.277 devMotorAsyn::init_controller, P:m1 setting of 
position not required, position=1.000000, mres=0.000010, dval=0.000000, 
rdbd=0.0000102017/10/17 12:25:24.277 P:m1 devMotorAsyn::update_values, 
needUpdate=1
2017/10/17 12:25:24.278 devMotorAsyn::build_trans: P:m1 motor_cmnd=19, pact=0, 
value=0.000000
2017/10/17 12:25:24.278 devAsynMotor::build_trans: calling queueRequest, 
pmsg=0xcbc770, sizeof(*pmsg)=24pmsg->command=14, pmsg->interface=1, pmsg-
>dvalue=0.000000
2017/10/17 12:25:24.278 port1 addr 0 queueRequest priority 0 not lockHolder
2017/10/17 12:25:24.278 devMotorAsyn::build_trans: P:m1 motor_cmnd=20, pact=0, 
value=0.000000
2017/10/17 12:25:24.278 devAsynMotor::build_trans: calling queueRequest, 
pmsg=0xcbc6a0, sizeof(*pmsg)=24pmsg->command=15, pmsg->interface=1, pmsg-
>dvalue=0.000000
2017/10/17 12:25:24.278 port1 addr 0 queueRequest priority 0 not lockHolder
2017/10/17 12:25:24.278 port1 0 autoConnect
2017/10/17 12:25:24.278 asynPortDriver:connect:, pasynUser=0xca79a8
2017/10/17 12:25:24.278 asynManager::portThread port=port1 callback
2017/10/17 12:25:24.278 devMotorAsyn::asynCallback: P:m1 pmsg=0xcae280, 
sizeof(*pmsg)=24, pmsg->command=10,pmsg->interface=1, pmsg->ivalue=0, pmsg-
>dvalue=0.000010, pasynUser->reason=13
2017/10/17 12:25:24.278 asynPortDriver:getDoubleParam: port=port1 error 
getting parameter 6 MOTOR_VEL_BASE, in list 0, value undefined
2017/10/17 12:25:24.278 asynPortDriver:getDoubleParam: port=port1 error 
getting parameter 7 MOTOR_ACCEL, in list 0, value undefined
2017/10/17 12:25:24.278 asynMotorController:writeFloat64: Set driver port1, 
axis 0 encoder ratio=0.000010
2017/10/17 12:25:24.278 asynMotorController:writeFloat64:: axis=0, 
function=13, value=0.000010
2017/10/17 12:25:24.278 asynManager::portThread port=port1 callback
2017/10/17 12:25:24.278 devMotorAsyn::asynCallback: P:m1 pmsg=0xcbc770, 
sizeof(*pmsg)=24, pmsg->command=14,pmsg->interface=1, pmsg->ivalue=0, pmsg-
>dvalue=0.000000, pasynUser->reason=17
2017/10/17 12:25:24.278 asynPortDriver:getDoubleParam: port=port1 error 
getting parameter 6 MOTOR_VEL_BASE, in list 0, value undefined
2017/10/17 12:25:24.278 asynPortDriver:getDoubleParam: port=port1 error 
getting parameter 7 MOTOR_ACCEL, in list 0, value undefined
2017/10/17 12:25:24.278 asynMotorController:writeFloat64: Set driver port1, 
axis 0 high limit=0.000000
2017/10/17 12:25:24.278 asynMotorController:writeFloat64:: axis=0, 
function=17, value=0.000000
2017/10/17 12:25:24.278 asynManager::portThread port=port1 callback
2017/10/17 12:25:24.278 devMotorAsyn::asynCallback: P:m1 pmsg=0xcbc6a0, 
sizeof(*pmsg)=24, pmsg->command=15,pmsg->interface=1, pmsg->ivalue=0, pmsg-
>dvalue=0.000000, pasynUser->reason=19
2017/10/17 12:25:24.278 asynPortDriver:setDoubleParam: port=port1 error 
setting parameter 19 in list 0, wrong type
2017/10/17 12:25:24.278 asynPortDriver:getDoubleParam: port=port1 error 
getting parameter 6 MOTOR_VEL_BASE, in list 0, value undefined
2017/10/17 12:25:24.278 asynPortDriver:getDoubleParam: port=port1 error 
getting parameter 7 MOTOR_ACCEL, in list 0, value undefined
2017/10/17 12:25:24.278 asynMotorController:writeFloat64 error, status=8 
axis=0, function=19, value=0.000000
2017/10/17 12:25:24.278 devMotorAsyn::asynCallback: P:m1 pasyn{Float64,Int32}-
>write returned 
iocRun: All initialization complete

I have checked, that the code is completely compiled an linked with thze 
correct versions of asyn (4.32) and motor (R6-9).

Regards,

Jörn


Am Dienstag, 17. Oktober 2017, 11:21:00 CEST schrieb Torsten Bögershausen:
> The last problem reports smelled as if the code executed was not
> corresponding to the source code. (things not compiled/linked
> appropriately)
> 
> This one looks the same.
> Can you put your source code somewhere ?
> 
> On 17/10/17 11:07, Jörn Dreyer wrote:
> > Hi,
> > 
> > still fighting with the motor record...
> > 
> > I get a strange error message at startup of my IOC:
> > 
> > asynPortDriver:setDoubleParam: port=port1 error setting parameter 19 in
> > list 0, wrong type
> > asynMotorController:writeFloat64 error, status=8 axis=0, function=19,
> > value=0.000000
> > devMotorAsyn::asynCallback: m1 pasyn{Float64,Int32}->write returned <empty
> > error message>
> > 
> > In my parameter list the number 19 is motorClosedLoop, which indeed is an
> > int32 parameter. I'm using basic_asyn_motor.db to setup the motor record.
> > 
> > What goes wrong here?
> > 
> > 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:
Problems with motor record Jörn Dreyer
Re: Problems with motor record Torsten Bögershausen

Navigate by Date:
Prev: Re: Problems with motor record Torsten Bögershausen
Next: RE: Problems with motor record Mark Rivers
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: Problems with motor record Torsten Bögershausen
Next: RE: Problems with motor record Mark Rivers
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