ibnotify callback does not start up intermittantly.

[TI_GPIB]

Hardware = NI-GPIB-PCI

When writing to a TSK Prober intermittently the "ibnotify callback" command does not execute.

I have attached an NISPY of the problem.  You will find the occurance at line #44604 the ibwrt executes and then ibnotify is  supposed to listen for a responce from the instrument indicating that the action has been accomplished.  However, it doesn't execute.  The next ibonl at line #44605 is when the program was reset.

This is controlled in a software loop and you will see several hundred occurences where the software executes as desired.

I have duplicated the issue with NI_GPIB Driver package 2.5.1 and 2.5.4 on RHEL4 U3 and RHEL4 U6

[MXI Master]

Would it be possible for you to attach the .spy file? It contatins some additional debugging information that would be useful in this case. I do not see anything readily apparent from the document you send. I would be interested to look into it further.


Message Edited by MXI Master on 05-29-2008 02:33 PM

[TI_GPIB]

Marshall,

Attached is the Text Output of the SPY file.

The end user did not retain the original data file.

I hope this has what you are looking for.

[MXI Master]

Actually that file was more unwieldy than the word document, but I think I think I have an idea for us. Have you tried lengthing any of the delays in your program. There is a chance we are teetering on the edge of what instrument is capable of we are sending commands to frequently. Since it works almost all of the time, I don't see it being a problem with the driver. Usually intermittent problems like this occur on the instrument side.  Is it possible for us to ignore this error and continue with the program, or is it a application where missing a sample is ultra critical?


Message Edited by MXI Master on 06-03-2008 09:33 AM