11-30-2008 04:06 AM
11-30-2008 09:04 AM
The answer is Yes, you go through the examples in the driver and go through the manual.
Unless you have a good understanding of the instrument itself, the driver probably won't help all that much. Study the manaul and be able to setup a measurement manually. You should then be able to determine what functions in the driver to use, what they do, and what parameters need to be set.
p.s. It's GPIB and not GBIP.
11-30-2008 09:11 AM
11-30-2008 09:23 AM
The commands are being sent by the functions in the driver. Open the functions up and look at their block diagrams. They are just normal VIs. Read the information here about what a driver is and how to use it. You may or may not have to write any code yourself to send commands. Drivers are usually pretty thorough but occasionally, you will find that a few commands are missing and then you write a function and add it to the driver.
If you are curious about finding a specific command in one of the drivers, you can use the Find and Replace tool in the edit menu to search for text.
11-30-2008 09:58 AM
11-30-2008 10:05 AM
11-30-2008 11:31 AM
First, please read the information on what a driver is and how to use it.
Generally, you don't change the code of a driver. You select the correct functions and pass values to the inputsof the function. That is what the example shows.
Assuming that you've installed all of the drivers for the GPIB board (including NI-VISA), you would have done a scan for instruments in MAX (Measurement & Automation Explorer). On the front panel of each of the functions is a VISA Resource Name Control. You can directly enter the VISA resource name (i.e. GPIB0::18::INSTR) but it is much easier to click the arrow on the right side of the control. When you do that, you will get a list of all resources on your pc. This will inlcude com ports, the printer port, and any instrument found in MAX. Just select your instrument.
12-01-2008 07:05 AM
12-01-2008 07:06 AM
12-01-2008 01:39 PM
You first attachment shows that the instrument is not being initialized. You cannot go any further without proper initialization. Your program should look for an error after intialization, and end the program if there is an error. You would benefit by using state machine architecture instead of the sequence structure. Search NI site for state machine.
The error message states that the ID Query failed. If you send the command *IDN using GPIB, what do you get back? Whatever it is, your program must match the return string from your instrument. You can also turn off ID Query by wiring a False constant on the ID Query input. It really isn't necessary. Try this to see if you still get an error message on initialization.