Experimental Physics and
Industrial Control System

Asyn-Experts,

I am chasing an interesting problem.
For a motor, we have a clutch that can be opened under very
special conditions, say service mode.


We define it like this:
record(bo, "$(PREFIX)$(MOTOR_NAME)-OpenClutch")
{
    field(DTYP, "asynInt32")
    field(DESC, "$(DESC=Clutch)")
    field(OUT,  "@asyn($(MOTOR_PORT),$(AXIS_NO))OpenClutch")
    field(ZNAM, "Closed")
    field(ONAM, "Open")
    info(asyn:READBACK,"1")
}

When the IOC starts, it talks to the motion controller, and
reads back the value of the clutch.
This does work, but the PV stays in an "INVALID DRIVER UDF"
alarm.

I can see that the value is read back, and pr->udf is reset
from 1 to 0.
However, there is no post here.
Re-starting the pvmonitor shows that udf goes to 0.
.STAT stay at UDF,
.SEVR stay at INVALID


(base) [xx@yy test]$ pvmonitor IOC:m6-OpenClutch IOC:m6-OpenClutch.UDF

IOC:m6-OpenClutch.STAT IOC:m6-OpenClutch.SEVR

IOC:m6-OpenClutch.UDF  <undefined>              1 INVALID DRIVER UDF

IOC:m6-OpenClutch.STAT <undefined>              INVALID DRIVER UDF (17) UDF

^C(base) [xx@yy test]$ pvmonitor IOC:m6-OpenClutch IOC:m6-OpenClutch.UDF

IOC:m6-OpenClutch.STAT IOC:m6-OpenClutch.SEVR

IOC:m6-OpenClutch.UDF  2021-05-27 12:44:11.032  0 INVALID DRIVER UDF

IOC:m6-OpenClutch.STAT 2021-05-27 12:44:11.032  INVALID DRIVER UDF (17) UDF

(Sorry for this slightly garbled log file)

The alarm seem to go away, if the record is processed one more time.
(by disconnecting the IOC from the controller and re-establishing the
connection).

Is this a know phenomena ?
Anything that can be done ?

Thanks
/Torsten

Replies:

Re: asyn bo record staying in INVALID DRIVER UDF Ralph Lange via Tech-talk

RE: asyn bo record staying in INVALID DRIVER UDF Mark Rivers via Tech-talk

Navigate by Date:

Prev: Re: IOC unusable if no ethernet interface at startup Torsten Bögershausen via Tech-talk

Next: Re: asyn bo record staying in INVALID DRIVER UDF Ralph Lange 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  2019  2020  <2021>  2022  2023  2024 

Navigate by Thread:

Prev: Important Notice Regarding EPICS Collaboration Meeting Spring 2021 Glen Wright via Tech-talk

Next: Re: asyn bo record staying in INVALID DRIVER UDF Ralph Lange 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  2019  2020  <2021>  2022  2023  2024