Experimental Physics and
Industrial Control System

Mark Rivers via Tech-talk <tech-talk at aps.anl.gov> · Thu, 27 May 2021 19:49:57 +0000

Hi Torsten,

asynInt32 device support for bo records always attempts an initial readback from the device to support "bumpless reboots".  If your driver returns asynSuccess on that read operation then it will set the value and set udf=0.  However, that initial read does not cause the record to process, so it will not reset STAT and SEVR.

You have also set the info tag asynREADBACK=1.  That will cause the record to process if your driver does a callback to device support.  You did not say if your driver is doing that.  Is your driver based on asynPortDriver?

If you boot the IOC, wait a few seconds, and then type the following at the iocsh what do you see?

dbpr $(PREFIX)$(MOTOR_NAME)-OpenClutch 2

Mark

-----Original Message-----
From: Tech-talk <tech-talk-bounces at aps.anl.gov> On Behalf Of Torsten Bögershausen via Tech-talk
Sent: Thursday, May 27, 2021 5:50 AM
To: tech-talk at aps.anl.gov
Subject: asyn bo record staying in INVALID DRIVER UDF

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      <undefined>              INVALID DRIVER UDF (0) 
Closed

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

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

IOC:m6-OpenClutch.SEVR <undefined>              INVALID DRIVER UDF (3) 
INVALID

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

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

IOC:m6-OpenClutch      2021-05-27 12:44:11.032  INVALID DRIVER UDF (0) 
Closed

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

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

(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

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System