Experimental Physics and
Industrial Control System

Eric Norum <[email protected]> · Fri, 27 Aug 2010 11:15:25 -0700

It sounds like what is happening is this:
1) Record ai_1 begins to process.
2) Command for ai_1 is sent.
3) Instrument does not reply quickly enough and devGpib times out.
4) Record ai_1 finishes processing.
5) Record ai_2 begins to process.
6) Command for ai_2 is sent.
7) Instrument gets confused because it sees a second command before it has replied to the first.

Try increasing the TIMEOUT value to a larger value.   Perhaps 10 seconds or so? 

On Aug 27, 2010, at 11:01 AM, Andrew Wagner wrote:

> Hey Mark, 
> 
> My device support includes devGpib.h and was created using a template produced with makeSupport.pl -t devGpib . I then edited the template to include the commands appropriate to my device in the command array. In the startup script, I connect to the device with drvAsynIPPortConfigure, i.e. drvAsynIPPortConfigure("L0","172.25.100.69:1234",0,0,0) . I have 3 passive ai records and 3 calc records that process the ai records every 10 seconds. Each ai record calls device support to talk to the MUX. Periodically the IOC prints the message: read status "172.25.100.69:1234" timeout: Resource temporarily unavailable, and the MUX gets a -410 error. Perhaps if I increase the TIMEOUT or TIMEWINDOW ?
> 
> Cheers, 
> 
> Andrew
> 

-- 
Eric Norum
[email protected]

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System