LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

GPIB Initialization problems


@belfast wrote:

I have the same problem here... i found out it was because .. MAX actually did initialize the GPIB interface when u scan instruemtns.. Meanwhile, if u run ya program in LABVIEW. Eg: communicating with non-HP instrument, GPIB initialization is required!!! 


No it is not required. I have not used the low level GPIB functions in years (use VISA) and certainly not the GPIB initialize. What makes you think its necessary?

0 Kudos
Message 11 of 14
(787 Views)


No it is not required. I have not used the low level GPIB functions in years (use VISA) and certainly not the GPIB initialize. What makes you think its necessary?


thanks for response....haha.. currently working on LabVIEW automation for my final year project. i have 1 of my instrument(Wentworth wafer prober) have problem for every first time(everytime i switch it on) i send command from LabVIEW into it where i think it was the same case u have here..When i use MAX and return into it... it will become normal again.. could u asist me please... currently i assumed it was the GPIB interface issue ...

0 Kudos
Message 12 of 14
(781 Views)

By the way .. i did use VISA for both the instruments i am using... however, it works on the HP instrument but not on the non-HP one

0 Kudos
Message 13 of 14
(779 Views)

Are you wiring a 2 to the mode input of the GPIB write? (the manual for the Fluke 45 can be found here) GPIB write with Mode =2 appends the <LF> character and asserts EOI on <LF>- just like the manual asks.  VISA defaults to this behavior for GPIB resources (in later versions of LabVIEW) as I recall there are some ideosynchrocies in the 6i VISA. (and modern VISA drivers would not support such an old LabVIEW revision).  

 


@belfast wrote:

By the way .. i did use VISA for both the instruments i am using... however, it works on the HP instrument but not on the non-HP one


Is the big clue here- HP kinda did a better job writing 488 interfaces (it used to be called Hewlett-Packard Interface Bus after all) Fluke burned a few revisions that implemented 488 standards with only fair overall performance.


"Should be" isn't "Is" -Jay
0 Kudos
Message 14 of 14
(772 Views)