On 2/20/24, 9:09 AM, "Tech-talk" <tech-talk-bounces at aps.anl.gov> wrote:
I would like to use the connection/communication management features of Asyn with a TCP/IP based driver using the asynPortDriver class.
I have a limitation to the underline device driver that expose the device has a non-thread-safe object , meaning it should only be access from the thread that made the
API call to initiate the device handle.
what I want to do, is to create the device handle instance within the asyn port thread, instead of the main thread. thus, all record init and runtime operation should
be performed from inside the asyn porthread. is that possible?
my understand of asyn port drivers is still cloudy somehow. this works, but the handle is hosted by the main thread.
drvXXTest::drvXXTest( const char *portName, const char *interface, const char *icsCtrtype, epicsInt16 autoConnect )
: asynPortDriver( portName,
asynCommonMask | asynInt32Mask | asynUInt32DigitalMask | asynFloat64Mask | asynDrvUserMask | asynOctetMask,
asynCommonMask | asynInt32Mask | asynUInt32DigitalMask | asynFloat64Mask | asynOctetMask,
ASYN_CANBLOCK, // asynFlags.
autoConnect, // Autoconnect
0 ), // Default stack size
static const char *functionName = "drvXXTest";
pasynManager->exceptionDisconnect( pasynUserSelf );
// How to to call devConnect(deviceSession_, interface_) from port thread?
// as this call run from the main one.
asynStatus status = this->connect( pasynUserSelf );
asynPrint( pasynUserSelf, ASYN_TRACE_ERROR,
"drvXXTest, error calling connect - %s\n",
pasynUserSelf->errorMessage );
asynStatus drvXXTest::connect(asynUser *pasynUser) {
// devConnect instantiate the device handle and open a connection to it.
if( !devConnect(deviceSession_, interface_) ) {
epicsSnprintf( pasynUser->errorMessage,pasynUser->errorMessageSize,
"%s: Can't open %s: %s", deviceSession_, interface_, strerror( errno ) );
pasynManager->exceptionConnect( pasynUser );