--7224926.1085495914102.JavaMail.quiq.tekken
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
As pointed out, it is very possible that your dir.mnu file was
accidently over written in your labview\instr.lib directory. This
can happen when unzipping an instrument driver
Ah, You're right. The two dir.mnu files used to be interchangeable
and synchronize to whatever directory they were in. Doesn't seem that
way anymore. Darn.
You didn't mention why you wanted to store the instrument state data
to a data file. Depending on your need, an NI-Spy log might suffice.
NI-Spy allows you to log all your instrument communication to a file.
There are several options that you might want to enable (Log to File,
Large Buffers,
Have you tried sending the string with the decimal data and appending
a CR? Typically if an instrument expects a space between two numbers,
the numbers are sent as ASCII numbers (i.e., in string format). Is
the instrument you are communicating with similar to those NI has
instrument drivers for
Just to let you know, the VISA Refnum delay was signficantly improved in
LabVIEW 7.1 (http://www.ni.com/labview/).
Noel Adorno
National Instruments
I'm guessing you installed the IVI driver for the Agilent signal
generator. Based on the error, it is likely that you do not have VISA
(or some other dependent software component) installed on your system.
When VISA is not present on a system, the IVI engine fails to load.
This causes functions
Do you have a href=http://www.ni.com/visa/NI-VISA/a installed?
IVI drivers require VISA to be installed. If installed, the VISA
header files will be installed in your defined VISA directory (by
default is C:\VXIPNP\WINNT\include (if on an NT-based windows
machine).
There are various techniques used when creating a driver that supports
multiple models or models with different installed options, where
there are slight functional differences between the models and
options. br
If there are VIs that only pertain to a specific model or option, then
modify the VI
Under the hood VISA is using the POSIX serial interface for Mac OS X
(same as for Linux and Solaris). This interface does not support
changing the buffer size. Hence, the buffer size is fixed to the
internal OS buffer size. The only thing that changing the buffer size
will do (for the out
Definitely you will want configure an alias to your USBTMC instrument
and copy your visaconf.ini to your target machine.
Unlike other traditional GPIB instruments, it is unlikely that your
USB device has the same address when connected to another computer.
Therefore, use VISA aliases that allow
When formatting strings to be sent to the instrument, wire a False
Constant to the Use System Decimal Point terminal of the Number To
Exponential String and Number To Fractional String functions.
As you probably know, instruments send and receive ASCII numbers using
decimal points as separators,
Based on the data you included in your question, I would guess your
(A) analyzer is set to return data in ASCII format while your (B)
analyzer is set to return data in binary format. Typically data
encoding format is settable on many instrument. Therefore, you can set
(B) to return data in the
12 matches
Mail list logo
