You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have been assuming that the drvInfo field for NDArrays is ARRAY_DATA, i.e. that pasynUser->reason=0. Plugins provide PVs to specify the portName, and addr, but not the drvInfo field.
In the case of the NDPluginStats plugin when it does NDArray callbacks of time-series callbacks (using doCallbacksGenericPointer) it would have been more logical to use a new drvInfo field, like ND_STATS_TIME_SERIES. Since there was no easy way to do this, and have it visible in OPI screens, I instead used ADDR=1 for these callbacks, and ADDR=0 for the default NDArray callbacks of the input array with possibly modified NDAttributes.
This change would not be difficult, it just means adding a new record to NDPluginDriver and adding that field to the plugin "more" screen.
The text was updated successfully, but these errors were encountered:
We have been assuming that the drvInfo field for NDArrays is ARRAY_DATA, i.e. that pasynUser->reason=0. Plugins provide PVs to specify the portName, and addr, but not the drvInfo field.
In the case of the NDPluginStats plugin when it does NDArray callbacks of time-series callbacks (using doCallbacksGenericPointer) it would have been more logical to use a new drvInfo field, like ND_STATS_TIME_SERIES. Since there was no easy way to do this, and have it visible in OPI screens, I instead used ADDR=1 for these callbacks, and ADDR=0 for the default NDArray callbacks of the input array with possibly modified NDAttributes.
This change would not be difficult, it just means adding a new record to NDPluginDriver and adding that field to the plugin "more" screen.
The text was updated successfully, but these errors were encountered: