Experimental Physics and
Industrial Control System

"Mark Rivers" <[email protected]> · Thu, 2 Dec 2010 14:40:14 -0600

> It seems that the ioc upon  "exit" does not unlock the links nor close
the sockets, 
> whereas ctrl-c at least does one of them.

An EPICS exit handler should be written to do the cleanup when the IOC
exits normally.

Mark

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of William Lu
Sent: Thursday, December 02, 2010 2:35 PM
To: Eric Norum
Cc: [email protected]
Subject: Re: Asyn VXI-11 Driver and VXI-11 Locking

I set the crLinkP.lockDevice to 1 as Eric suggested, and it does the 
trick!  My ioc locked the devices exclusively.

Additional findings:

1, the ICS 8065 Ethernet-GPIB controller has a configurable timeout for 
the communications with the TCP/IP clients.  If the ioc does not 
communicate with any GPIB devices for the timeout amount of time, the 
8065 will release all locks created by the ioc.

2, if the ioc is terminated by the iocshell "exit" command, the 8065 
does not release the locks created by the ioc until the communication 
timeout expires.

3, if the ioc is terminated by ctrl-c in the iocshell, the 8065 releases

the locks created by the ioc immediately.  It seems that the ioc upon 
"exit" does not unlock the links nor close the sockets, whereas ctrl-c 
at least does one of them.

Thank you Eric and Mark for your help.

Best regards,
William

Eric Norum wrote:
> Here's the code at the beginning of the vxiCreateDeviceLink routine.
As you can see, the lockDevice parameter is always set to 0.
>
> static BOOL vxiCreateDeviceLink(vxiPort * pvxiPort,
>     char *devName,Device_Link *pDevice_Link)
> {
>     enum clnt_stat   clntStat;
>     Create_LinkParms crLinkP;
>     Create_LinkResp  crLinkR;
>     BOOL             rtnVal = FALSE;
>     asynUser         *pasynUser = pvxiPort->pasynUser;
>
>     crLinkP.clientId = (long) pvxiPort->rpcClient;
>     crLinkP.lockDevice = 0;  /* do not try to lock the device */
>     crLinkP.lock_timeout = 0;/* if device is locked, forget it */
>     crLinkP.device = devName;
> .
> .
> .
>
>
> You could try setting lockDevice to 1 and see if this gets you the
effect that you want.
> I don't have my VXI-11 documents handy right now to see what happens
if a client disappears suddenly (from a power-fail or such) without
explicitly releasing the lock.
>
>
> On Dec 2, 2010, at 9:10 AM, William Lu wrote:
>
>   
>> Hello,
>>
>> I am using asyn records with the vxi-11 driver in a soft ioc to
control the HP3458A GPIB devices through an ICS 8065 Ethernet-GPIB
Controller.  I want to lock the devices using the vxi-11 locking so that
the ioc has an exclusive access to the devices.  Does asyn vxi-11 driver
or asyn record already provide the vxi-11 locking function for users to
lock and unlock GPIB devices and if they do, how do I use them?
>>
>> Best regards,
>> William Lu
>>
>> -- 
>> Weiwei Lu
>> 757-269-7476
>> [email protected]
>>
>>     
>
>   

-- 
Weiwei Lu
757-269-7476
[email protected]

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System