Experimental Physics and
Industrial Control System

"Allison, Stephanie" <[email protected]> · Wed, 30 Apr 2008 10:52:05 -0700

Hello,

I'm currently upgrading all my GPIB device support from old-style GPIB to new-style GPIB/ASYN support and find myself struggling with a similar problem reported by Benjamin Franksen in January:

http://www.aps.anl.gov/epics/tech-talk/2008/msg00066.php

In my case, the first time the LAN/GPIB gateway box is power-cycled after an IOC reboot, everything automatically reconnects but the second (and all times afterward), only the port automatically reconnects and not the device.  I can manually reconnect the device by setting the CNCT field of the ASYN record but this shouldn't be required since the device has the autoConnect attribute set.  Perhaps this has been fixed or reported already (sorry if it has!), but in asyn version 4-9, there is a bug in the routine autoConnectDevice in asyn/asynDriver/asynManager.c where pport pointer is accidentally used instead of pdevice.  When fixed, I have no problems reconnecting after power cycles:

    if(!pdevice->dpc.connected
    &&  pdevice->dpc.autoConnect
    && !pdevice->dpc.autoConnectActive) {
        epicsTimeStamp now;

        epicsTimeGetCurrent(&now);
        if(epicsTimeDiffInSeconds(
            &now,&pdevice->dpc.lastConnectDisconnect) < 2.0) return FALSE;
        epicsTimeGetCurrent(&pdevice->dpc.lastConnectDisconnect);
        pdevice->dpc.autoConnectActive = TRUE;
        epicsMutexUnlock(pport->asynManagerLock);
        connectAttempt(&pdevice->dpc);
        epicsMutexMustLock(pport->asynManagerLock);
/*****  pport is the wrong *****/
/****   pport->dpc.autoConnectActive = FALSE;   *****/
	  pdevice->dpc.autoConnectActive = FALSE;
    }

Stephanie Allison

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System