08-15-2007 03:26 PM
08-16-2007 04:16 PM
08-16-2007 04:46 PM - edited 08-16-2007 04:46 PM
Hey,
I forgot to mention where the text based programs are found. If you're interested in labVIEW It wouldn't be a bad thing to try and download the evaluation version at www.ni.com/downloads.
But here's the examples for the other drivers.
Message Edited by Nick D on 08-16-2007 04:46 PM
08-16-2007 07:21 PM
08-17-2007 04:48 PM
Thanks for all the info. I had actually already done the Lab View example and that was a good start but didn't real tell what was happening in the background like some good code would. I'm working through many of the documents that were attached now and came to a few questions.
When using MAX, should the "Scan for Instruments" return a device specific to my GPIB device? It says no instruments found, though I have a GPIB-USB-B cable attached to an Agilent 33250A Function Generator. Are these tools all specific to NI GPIB devices, or should I be able to use all my Agilent devices (since that's all I currently have)?
Also, how do I find the secondary address of my devices? I can't any mention of it in my manuals. None even refer to a primary address, but just call it the address.
Also, the documents said that VISA is an abstraction to GPIB, and some other protocols, do you recommend starting with VISA or some other API. I'd like to avoid doing much in Lab View since I'm not very familiar with it, and it seems to hide some of the details or at least the example does.
Thanks again for your time,
Mike
08-18-2007 04:26 PM
If you're interested on what's going on behind the scenes, I would recommend using NI-SPY. If you go to Start->Programs->National Instruments->NI-SPY. This is a utility that monitors all the driver calls being made. So if you wanted, you could run any example that uses NI's drivers, and this will show all the low levels calls being made, and if you were to emulate what the driver calls were being made, then it should work the same.
Regards,
Nick D.