HFS9003

[Alias007]

I have downloaded the HFS9003 driver from the NI website. But I am not able to talk to the talk to the instrument. Does anybody have a example?

Thank.

[Mathan]

Please tell more detailed information in ur post.

1) How ur communicating with ur instrument?

2) are you using Call Library Node?

3) any errors or exceptions occurs?

Mathan

[Alias007]

Hi Mathan,

1) How ur communicating with ur instrument?

I using a GPIB connector to communicate with the HFS.

2) are you using Call Library Node?

3) any errors or exceptions occurs?

Error NI488: Error connecting to driver or device

[Dennis_Knutson]

Are you using an NI GPIB board? If you are, did you verify the installation and test it in MAX?

[Alias007]

It does show up in MAX.  It is connected.

[Dennis_Knutson]

By connected, I'm assuming that when you did the scan for instruments, your HFS9003 was detected. If that's the case, then verify that the driver is using the same address as was found in MAX. It would also help for you to provide exactly what function is generating the error.

[Alias007]

I am using the same address.

The error occurs in the initialize block.

Message Edited by Alias007 on 05-08-2008 09:49 AM

[Dennis_Knutson]

That wasn't exactly what I was asking. I was more curious about the lower level function being called. In an initialize VI, there is typically an id query and a reset. I can't download the driver to look at the code so I wanted to know if the error occured on a GPIB Write or Read. If it was a Write, what was the command being written? If you would, you could attach the initialize vi to a post. I can downlaod attachments but our IT department blocks downloads from other places.

During the scan for instruments in MAX, after the instrument is detected, it does an *IDN? query and reports the result of a read. You haven't explicitly said so, but if this works in MAX, there should be no reason for it to not work in a driver. If you can isolate the command that is gnerating the error, send the same command in MAX.

[Alias007]

I believe the error is happening in the write buffer. It shows up as *IND?

I took a snap of the block where the error occurs.

[Dennis_Knutson]

An image without seeing the actual data sent does not help. Lets go back to the beginning and can you confirm some of my assumptions that I've been making? Does the scan for instruments in MAX actually return the results of *IDN? or not? If it does and the driver fails with the same query, then I don't know what the problem could be because as I already said, I can't download the driver unless you post it to one of your messages.

edit:

Actually, the image may tell me something. I notice that there is a GPIB Status function. I'm not sure that is valid unless you are addressing the controller. I have only used VISA for a long time and not the lower level GPIB functions. Not sure what will happen if you use this function with it addressed for an instrument. Take it out and see it it makes a difference.

Message Edited by Dennis Knutson on 05-08-2008 09:46 AM