GPIB wont initialize in LabView without MAX

[vienna]

Im using a stepper motor controller through LabView. Commands through MAX and the Interactive Control window are fine. Even when I use LabView the Initialisation and Write functions work, however, only when MAX has been loaded and the 'Devices and Interfaces' expand-option selected. if you close MAX then it will still work, until you close LabView and then it goes back to square one.
Im using the GPIB Initialisation function in the first frame of a sequence, being passed only the (PAD+SAD) combination. The second frame is just some data formatting and the GPIB write. AS i said it works fine but only when MAX has been loaded prior to running the VI. I saw a similar post by Javier Pena, but i couldnt find a solution.

[Michael_N.]

Hello Vienna,

I have not seen this problem before. Are you using an instrument driver or did you write this code yourself? One thing I would recommend doing is seeing if you have the same behavior when you are running an example program that ships with LabVIEW (these are located at C:/Program Files/National Instruments/NI-488.2\Languages\LabVIEW). If you don't see the same behavior then something unique to your code is occurring, but if you see the same behavior then something else is wrong with your system.

You may also want to consider reinstalling your GPIB driver (and upgrading to the latest version as well). It may be a bad installation that is causing this problem. The driver is a free download from our website, and you can find it at the link below.
Just be sure to uninstall your old driver first in Add or Remove Programs.

http://digital.ni.com/softlib.nsf/webcategories/85256410006C055586256BB9002C14EF?opendocument

Best of luck,

Mike N.
Applications Engineer
National Instruments

[vienna]

Sorted it. Downloaded the latest version of NI-488.2 and that removed all functionality, but after working with NI support in Belgium, its fixed. The address you set to the GPIBInit.vi, was I assumed the same to that of GPIBWrite.vi, however, they needed to be set differently (CAD:PAD) and (CAD+PAD) respectively. I understand the logic of the first, but CAD+PAD ???
anyway, its working..