Re: Instrument Lib icon is missing in function palette
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.
Re: Instrument Lib icon is missing in function palette
--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 \instr.lib directory. This can happen when unzipping an instrument driver without the create directories option enabled in your unzip utility or if the zip file was created without storing folder information. One quick fix, without re-installing LabVIEW or repairing LabVIEW, is to copy the user.lib's dir.mnu file to the instr.lib directory. The menu palettes behave the same, they just have a different icon. Alternatively you can copy the attached dir.mnu file to your \instr.lib directory. --7224926.1085495914102.JavaMail.quiq.tekken Content-Type: application/octet-stream; name=dir.mnu Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename=dir.mnu Content-Description: dir.mnu file for instr.lib UlNSQw0KAANMTU5VTEJWVwAABXwAAAGRIAAABVwAAACAAOAAQABAIEUAWbJBAFUkRcBU pEUg9ZR1QAP//wAEAACABf+AgAUApoAFYLaABZCggAUJtoAFCaaABQaAgAX/ toAEAACAA///AAHADgAAA///AAQAAIAF/8iABf/cgAW2yIAFqsCABarAgAQA AAD///8AAP8A AAD/AAD//wAAAP8A/wAAAP8A//8AAP//AP//AAD/AAD/ AAD//wD/AP8A/wAA/wAA/wAAAP8AAAD/AP///wD/AP8A/wAA/wD/AAD/ /wAAAP8A/wAA/wAA/wD/AP//AAD/AP8AAAD///8A/wD/AP8A AIGBgYGBgYGBgYGBgYGBgYGBgQD///+B gQAA/ysrKysrKysrKysrKysrKysrK/+BAAD/K/8r KysrKysr/4EAAP8r/0hISEhISEhI/yv/Kyv//yv/gQAA/yv/SP// SEhISEj/K///K///K/+BAAD/K///SEj/SEhISP8r/ysrKysr/4EA AP8r/0hISEj/SEj//yv//yv//yv/gQAA/yv/SEhISP9ISP//K/8rK///K/+B AAD/K/9ISEhISP//SP8rKysrKysr/4EAAP8r/yv//yv/ /yv/gQAA/ysrKysrKysrKysrKysrKysrK/8A VlZWVlZWVlZWVv///wCB gYGBgYGBgYGBgYGBgYGBgYEAgYEA AP8rKysrKysrKysrKysrKysrKyv/gQAA/yv//ysr/ysrK/+B AAD/K//6+vr6+vr6+vr/Kysr/4EAAP8r//r6+vr6+vr6+v8r K/8rKyv/gQAA/yv/+vr6+vr6+vr6/ysrKysrK/+BAAD/K//6+vr6 +vr6+vr/KysrKysr/4EAABgA BAAC//8AAAEAAP//AAACAABSAlBUSDAgAwo8aW5zdHJsaWI+CGhw MzQ0MDFhB2Rpci5tbnVQVEgwHgMKPGluc3RybGliPgZhbjIwNTAHZGlyLm1udQAA HAMGYW4yMDUwB2Rpci5tbnUIaHAzNDQwMWEfAhNIUDM0NDAxQSBNdWx0aU1ldGVy BmFuMjA1MAAXUFRIMA8BCjxpbnN0cmxpYj4AUlNSQw0KAANMTU5VTEJWVwAABXwA AAGRIAAABVzkJcUAOXAACQAAACA0AAABDAVJQ09OAExpY2w4 AGBQTE0yAHRMUFRIAIhDUFNUAQAAAJxQQVRIAMT/ 6FT3f/8TAIS0J/d//wAAACYEiLwg93// OQSkJCf3f/0AAABfBPxUJ/d//wAAAEwFHOxU93// cgVAiCD3fxJJbnN0cnVtZW50IERyaXZlcnMSSW5zdHJ1bWVudCBEcml2ZXJz Ekluc3RydW1lbnQgRHJpdmVycxJJbnN0cnVtZW50IERyaXZlcnMSSW5zdHJ1bWVudCBEcml2ZXJz Ekluc3RydW1lbnQgRHJpdmVycxJJbnN0cnVtZW50IERyaXZlcnM= --7224926.1085495914102.JavaMail.quiq.tekken--
Re: Best way for recording instrument commands
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, etc). The actual commands you send to the instrument will also be logged.
Re: send serial command in decimal format
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 (www.ni.com/idnet)? Instruments by the same manufacturer often have similar requirements. You might be able to look at those instrument drivers to understand how to communicate with your instrument.
RE: VISA Refnum delays
There is not a comprehensive list of all the fixes that were implemented in LabVIEW 7.1. However, the LabVIEW Upgrade Notes contains a list of new features and changes. Noel Adorno National Instruments
Re: VISA Refnum delays
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
Re: Where to download asci_c.h, visa.h and vpptype.h?
Do you have http://www.ni.com/visa/>NI-VISA 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).
Re: "Hi,I'm having problems controlling the Agilent E4422B...
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 that use the IVI engine error -1074135040 (xBFFA). You can download NI-VISA from NI's support and downloads page.
Re: How to manage different instrument models with one driver?
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. If there are VIs that only pertain to a specific model or option, then modify the VI prefix to associate that VI with the particular model/option. For example, a function general family driver might use "ag33xxx" as the general prefix, but VIs that only operate on the ag33250 might use the prefix "ag33250". It sounds as if you need to remember this model/option to modify functionality within a common VI. For example, the commands might differ between two different models. To handle this situation, you store model information in the User Data VISA property. At initialization time, you can detect which model you are connected with and either store the model number directly or some ID to represent the model. Both these techniques are used in the http://zone.ni.com/idnet97.nsf/9b2b33e1993d877786256436006ec498/0027109f3d6e32dd86256d6d0068a5bd?OpenDocument> Agilent 33xxx function generator driver . You will see how User Data is set in the Initialize VI and the retrieved in the Configure Burst Modulation VI.
Re: VISA ERROR(hex 0xBFFF0011)
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 you to configure your USB device outside of your application. To learn more about VISA and USB, you the following app note is helpful: http://zone.ni.com/devzone/conceptd.nsf/webmain/6792BAB18242082786256DD7006B6416?opendocument> Using NI-VISA 3.0 to Control Your USB Device
Re: Warning 1073676424 from VISA Set I/O Buffer Size.vi on a serial port
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 buffer) is to have VISA not flush the data after every write. This is a limitation in the serial API for Mac OS X. Therefore, VISA reports a warning.
Re: is it possible for the test equip. to tell me the measured data is ready?
If you are programming using VISA, the following link takes you to some examples of waiting until the instrument has data available. The example link also includes other examples of synchronizing your application with your instrument. http://sine.ni.com/apps/we/niepd_web_display.DISPLAY_EPD4?p_guid=C99424CC48EC1273E034080020E74861&p_node=dz59204_us&p_submitted=N&p_rank=&p_answer=&p_source=External>Using Instrument Status Registers with Service Requests and Polling
Re: , instead of . depending on PC
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, regardless of how you configure your the number format for on your operating system. For LabVIEW to use the decimal point separator of the operating system and communicate properly with instruments, all string operations that operate on floating point numbers must include the modifiers to use a period (.) as the decimal separator. To force the decimal point, include the "%.;" in the format string input of Format Into String or Array to Spreadsheet String functions. To use the decimal specifier format string, attach %.; to the beginning of the standard format string input for floating point inputs (floats, exponential inputs). If you use the Number To Exponential String or Number To Fractional String functions, wire a False Constant from the Boolean palette to the Use System Decimal Point terminal. You do not need this decimal specifier for decimal numbers (those that use %d or %x format specifier). You can see this format specifier in most instrument drivers on ni.com/idnet.
Re: GPIB Read.vi does not output right data?
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 same format as (A). Alternatively, the binary format is probably an IEEE 488.2 definite length block format. You might choose to return data in binary format for improved performance. Below is a link to some examples for parsing definite length block format: http://sine.ni.com/apps/we/niepd_web_display.DISPLAY_EPD4?p_guid=C993A8A8911F19DDE034080020E74861&p_node=DZ52341&p_submitted=N&p_rank=&p_answer=&p_source=External";>Waveform Encoding and Scaling for Instrument Control Applications
