Corrupt 488.2 function calls in gpib-32.dll ??

[Steven_T]

Angelo,

I haven't gone through your code, however you should check out your spy capture.  You can clearly see that there are actually two processes using the GPIB.  One of them is using incorrect values as input for ibrd and ibwrt.  This is not the same problem as corrupt function calls.

Thanks,

Steven T.

[Steven_T]

Hello Kurt,

Although this probably isn't a surprise to you, I can't find anything with your spy captures...at least nothing that your application is doing wrong.  I would like to try reproducing this problem here with our C API.  I just need a little more information.

What version of NI-488.2 are you using (you can find this in the NI-488.2 readme linked from the start menu or by finding the NI-488.2 software in MAX).

Thanks,

Steven T.

[Kurt__]

Hi Steven,

I was using NI 488.2 versoin 2.4, but now I am using version 2.81 and the same error(s) occurs: NULLend is used despite specifying NLend, and more importantly, using Read/Write shows returns the wrong answer.

Attached please find the new spy files.

Thanks,

Kurt