Experimental Physics and
Industrial Control System

Érico Nogueira Rolim via Tech-talk <tech-talk at aps.anl.gov> · Thu, 21 Sep 2023 20:13:31 +0000

Ø  I needed to avoid the NDPluginDriverQueueSize and NDPluginDriverNumThreads functions, because XIP has this message:
Ø  Specify BlockCallbacks to true, which is how it should stay.

BlockCallbacks is independent of NDPluginDriverQueueSize and NDPluginDriverNumThreads.  There is no need to “avoid” them.  You can change plugins from blocking to non-blocking at runtime in the OPI, and the current setting is normally restored with autosave, so the value in the startup script typically does not matter.

Mark

I already have full IOC compiled for ADCore 2.2.0.
I'm trying to update to the latest version of ADCore=3.12.1.
·         If you 
·         are building with R3.12.1 then why are you trying to avoid calling the 
·         base class for NDPluginDriverQueueSize and NDPluginDriverNumThreads?

Because when trying to run IOC to the latest version, I get these errors in the IOC prompt:
NDPluginDriver::deleteCallbackThreads timeout waiting for plugin thread 0 exit message
NDPluginDriver::writeInt32 ERROR, status=3, function=57, value=1, connectedToArrayPort_=1
NDPluginXIP:writeInt32: error, status=3 function=57
IPE:RIXSCam1:XIP1:NumThreads devAsynInt32::processCallbackOutput process error.

After avoiding calling the functions, the errors did not occur. But the problem of resetting the PVs arose
IPE:RIXSCam1:XIP1:ArraySize2_RBV = 0
IPE:RIXSCam1:XIP1:ArraySize1_RBV = 0

In the IOC cmd file using ADCore=2.2.0, the plugins look like this:

# Create a netCDF file saving plugin.
NDFileNetCDFConfigure("FileNetCDF1", $(QSIZE), 0, "$(PORT)", 0)
dbLoadRecords("NDFileNetCDF.template","P=$(PREFIX),R=netCDF1:,PORT=FileNetCDF1,ADDR=0,TIMEOUT=1,NDARRAY_PORT=$(PORT)")
# Load XIP plugin.  Specify BlockCallbacks to true, which is how it should stay.
NDPluginXIPConfigure("XIP1", $(QSIZE), 1, "$(PORT)", 0, -1, -1)
dbLoadRecords("NDPluginXIP.template", "P=$(PREFIX),R=XIP1:,  PORT=XIP1,ADDR=0,TIMEOUT=1,NDARRAY_PORT=$(PORT)")

In the IOC cmd file using ADCore=3.12.1, the plugins look like this:
# Create a netCDF file saving plugin
NDFileNetCDFConfigure("FileNetCDF1", $(QSIZE), 0, "$(PORT)", 0)
dbLoadRecords("NDFileNetCDF.template","P=$(PREFIX),R=netCDF1:,PORT=FileNetCDF1,ADDR=0,TIMEOUT=1,NDARRAY_PORT=$(PORT)")
# Load XIP plugin.  Specify BlockCallbacks to true, which is how it should stay.
NDPluginXIPConfigure("XIP1", $(QSIZE), 1, "$(PORT)", 0, -1, -1)
dbLoadRecords("$(ADPLUGINXIP)/db/NDPluginXIP.template", "P=$(PREFIX),R=XIP1:,PORT=XIP1,ADDR=0,TIMEOUT=1,NDARRAY_PORT=$(PORT)")
dbLoadRecords("$(ADPLUGINXIP)/db/XIPPVDefinitions.template", "P=$(PREFIX),R=XIP1:,PORT=XIP1,ADDR=0,TIMEOUT=1,NDARRAY_PORT=$(PORT)")

I needed to avoid the NDPluginDriverQueueSize and NDPluginDriverNumThreads functions, because XIP has this message:
Specify BlockCallbacks to true, which is how it should stay.

I didn't try to reset the argument like other plugins.
Hi everyone, I'm compiling a RIXSCam detector.
I compiled EPICS BASE = 7.0.7
SYNAPPS = 6.2 with AreaDetector -> ADCore, ADSupport.

I was successful in compiling the entire system, detector and epics modules.
But after compiling and changing the version of ADCore, the XIP plugin has been showing strange behavior.

I think it's something related to the version of ADCore=2.2.0, it doesn't handle NDPluginDriverQueueSize and NDPluginDriverNumThreads.

In the new version of ADCore = 3.12.1, it handles these functions.

I got around this problem with the code:
asynStatus NDPluginXIP::writeInt32(asynUser *pasynUser, epicsInt32 value)
{
int function = pasynUser->reason;

asynStatus status = setIntegerParam(function, value);

for (auto histogramParam : _histogramParams)
{
if (histogramParam->HasParameterIndex(function))
{
_histogramParamsChanged = true;
break;
}
}

/* If this parameter belongs to a base class, call its method */
if (function < FIRST_NDPluginXIP_PARAM && function != NDPluginDriverQueueSize && function != NDPluginDriverNumThreads)
status = NDPluginDriver::writeInt32(pasynUser, value);

/* Do callbacks so higher layers see any changes */
callParamCallbacks();
ReportWriteStatus(pasynUser, status, "writeInt32");
return status;
}

But after that, IOC zeroed out the Array Size. And by definition, this is the PluginXIP call.

# Load XIP plugin. Specify BlockCallbacks to true, which is how it should stay.
NDPluginXIPConfigure("XIP1", $(QSIZE), 1, "$(PORT)", 0, -1, -1)
dbLoadRecords("$(ADPLUGINXIP)/db/NDPluginXIP.template", "P=$(PREFIX),R=XIP1:,PORT=XIP1,ADDR=0,TIMEOUT=1,NDARRAY_PORT=$(PORT)")
dbLoadRecords("$(ADPLUGINXIP)/db/XIPPVDefinitions.template", "P=$(PREFIX),R=XIP1:,PORT=XIP1,ADDR=0,TIMEOUT=1,NDARRAY_PORT=$(PORT)")
set_requestfile_path("$(ADPLUGINXIP)", "Db")

I needed to make the change in deleteCallbackThreads and createCallbackThreads, because when we raised the IOC, the shell showed: errors involving these two functions:

2023/07/11 12:00:50.994 NDPluginDriver::deleteCallbackThreads timeout waiting for plugin thread 0 exit message
2023/07/11 12:00:51.001 NDPluginDriver::writeInt32 ERROR, status=3, function=57, value=1, connectedToArrayPort_=1
2023/07/11 12:00:51.011 NDPluginXIP:writeInt32: error, status=3 function=57
2023/07/11 12:00:51.019 IPE:RIXSCam1:XIP1:NumThreads devAsynInt32::processCallbackOutput process error

I think it might be something related to the PVs
·         IPE:RIXSCam1:XIP1:QueueFree
·         IPE:RIXSCam1:XIP1:QueueSize

Because in the image with ADCore 2.2.0, the PVs IPE:RIXSCam1:XIP1:QueueSize and IPE:RIXSCam1:XIP1:QueueFree have the values 1 and 1 respectively.
While with ADCore 3.12.1 they have the values 1 and 0 respectively.

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System