Hi!
There are many good places to ask. I've sent this reply to the list just
to share some LabVIEW resources:
* NI tech support, fill out the form at www.ni.com/ask .
* Search the NI knowledge base at
http://digital.natinst.com/public.nsf/$$Search/ .
* SRS tech support, see www.srsys.com .
* Info-LabVIEW, mailing list with 2200 well-informed subscribers, see
http://labview.pica.army.mil/ for subscription & to search the archives.
* Various newsgroups created by NI. The best ones for this would be
comp.lang.labview and natinst.public.gpib.general .
There are different ways to access them: your ISP may already have them
in which case you can just visit news://comp.lang.labview &
news://natinst.public.gpib.general .
If not, go via the NI news server newsgroups.ni.com and have a look at
all the newsgroups.
Or via Deja: www.deja.com/group/comp.lang.labview or
www.deja.com/group/natinst.public.gpib.general .
* Lastly, use the NI utility to see if the instrument & cables & GPIB
card are all OK. That also tells you if you are sending the right
commands in the right order with suitable time intervals between them.
There should be a command-line utility called something like ibic or
wibic. The later versions of 488.2 software have a Getting Started
Utility.
* When you describe the problem, say more than "seems not to work"! What
happens when you send a command with the utility & with your program? It
should respond to a command like "ID" or "*IDN?" and give its ID string.
Best, Mark
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|