Hi Mike,
Are you specifying an address string in your GPIB Initialization function? It should be of the form "bus:pad+sad", where bus is the bus #, example 0 (zero) for GPIB0; pad is the primary address of your GPIB controller; and sad is the secondary address of your GPIB controller (0, if no sad). I was looking at the Online Help for the GPIB Initialization function, and it states that if you do not specify an address, then read and write functions will not re-address your devices. This could result in the EADR error (GPIB error 3) that you've been seeing.
I think this is different from the previous behavior of this function, where it would assume "0:0+0" (or GPIB0:PAD0+SAD0" for the default controller values. If you are not specifying this information, then
I suggest that you add it to your program to see if this helps.
Otherwise, I would be interested to know what your GPIB settings (bus #, pad, sad, etc.) are for your GPIB controller and for your hardware. The Developer Exchange allows you to attach files, too. If you have an example of the VI that you're using to initialize your GPIB (no necessarily the VI itself, but a snippet of the GPIB code), then you could attached it to your response.
Mr. KB
P.S. A good place to look for GPIB Settings information is the main GPIB Support page at http://www.ni.com/support/gpibsupp.htm. Follow the link to "The Measurement & Automation Explorer and GPIB".
