GPIB Error 6- I/O operation aborted(timeout)

[hitech]

I am working on measuring s parameters of a device using Anritsu Vector Network Analyzer and I am having some problems with it. I have written a program which measures on-wafer s parameters and it is programmed in such a way that if there is some gpib error it displays a message on the computer and the application is aborted.
In my case, sometimes I get a error message on the Network Analyzer which says "Phase lock failed" or "Rf power unlevelled". In my program I get error code 6 "I/O operation aborted(Time-out)". I think there is some problem with the device at certain frequencies,at which the device starts oscillating. I would like to skip that device and move on to next device whenever I get such an error. I was wond
ering how do I do that? How do I read this error in my program so that I can take appropriate steps.

[Mache]

Hi hitech,

You have not mentioned the following..

1. What Programming Language you are using?
2. What type of GPIB card you are using? NI or other Vendor?

In Absence of this info - I will give a couple of suggestions.
You shoud check the GPIB status during measurment. In Labview there are built in Error Clusters for VISA or Status Functions for GPIB. If you are Using VB, C the Write String is "ibsta". this will give you status information. If the Status is true which means error occured then you check the Code. In your Case 6 or "EABO" which is timeout error.
Now Instead of Aborting in this case you make the Program loop Back to Begining considering the Current Device as a Fail Device. If you encounter any other error than 6 you can abort the program.


However you must program for eventuality that there is something wrong other than device. The way to do it is count the no of Consecutive occurence of Timeout error. If you get say 5 occurences in a row, most probably something else is wrong other than device. and so if this happens Give message and abort.

On a side Note. "Phase Lock Failed" or "RF Power Unlevelled" does not sound too good. I think your issue is that the device is not getting enough settling time before measurement is extracted. It could also be a contact Problem. You can see by adding a delay before measurement is taken to see if that helps.

Good Luck!!

Mache