Re: Can't use the Measurement Automation Explorer in the dl eval version
Unfortunately, there is no MAX eval version. However, I just tested this issue and the full error message is Measurement Automation Explorer or the Instrument I/O Assistant is not installed correctly. Please install these from the LabVIEW Driver CD. Installing DAQmx, as described before, should solve this error with the DAQ Assistant. If you get this error when launching the Instrument I/O Assistant, please send us an email request, and I will zip you a version of the driver CD. a href=http://sine.ni.com/apps/we/niae_asc.main;Request Support/a Zvezdana S.
Re: Basics 2 CBT - Requires Acquire Signal.vi - not on disk
Hello, In addition to installing LabVIEW eval, you also have to install the Basics2.llb. The instructions from the ReadMe file: Copy the Basics2.llb file from Course Disc 1 to the labview\user.lib directory. This is usually stored in [drive letter]\Program Files\National Instruments\LabVIEW\user.lib. To make the Basics2.lib show up under the user.lib on your functions palette, please review the following KnowledgeBase: a href=http://digital.ni.com/public.nsf/websearch/1D0D514BC3852BFD8625685F007BC976?OpenDocument;How Do I Add Custom SubVI to the Functions Palette?/a Also, make sure that you have DAQmx installed. The LabVIEW Evaluation Version gives the option of installing simulation DAQ VI's. If the complete install option is chosen, the simulation VIs are installed. To avoid this, choose a custom install and don't allow the Evaluation Version to install NI-DAQ. After the LabVIEW Evaluation Version is installed, install NI-DAQ and include support for LabVIEW 7.0. The DAQ VIs will now read data from your DAQ device. There is a link to the NI-DAQ download page below. a href=http://www.ni.com/support/daq/versions.htm;NI-DAQ Driver Support for Windows/a Zvezdana S. National Instruments
Re: Can't use the Measurement Automation Explorer in the dl eval version
Hello, You should be able to use MAX with LabVIEW eval. To make sure MAX is installed, go to ..\Program Files\National Instruments\MAX If you have NIMax.exe, MAX is installed. Even if you don't have LabVIEW installed, you should still be able to open MAX from this location. Do you get this error when launching MAX from its installation directory, or when opening some of the LabVIEW wizards that call MAX? The LabVIEW Evaluation Version gives the option of installing simulation DAQ VI's. If the complete install option is chosen, the simulation VIs are installed. To avoid this, choose a custom install and don't allow the Evaluation Version to install NI-DAQ. After the LabVIEW Evaluation Version is installed, install NI-DAQ and include support for LabVIEW 7.0. The DAQ VIs will now read data from your DAQ device. There is a link to the NI-DAQ download page below. a href=http://www.ni.com/support/daq/versions.htm;NI-DAQ Driver Support for Windows/a a href=http://digital.ni.com/public.nsf/websearch/402D2EB45062FBC486256DD600634695?OpenDocument;Using the DAQ Assistant or Creating a DAQmx Task in LabVIEW 7.0 Evaluation Version/a a href=http://digital.ni.com/public.nsf/websearch/8968DE19FB0EAC8886256D55004FCC06?OpenDocument;Frequently Asked Questions about the LabVIEW 7.0 Evaluation Version/a Zvezdana S. National Instruments
Re: Can I transfer a license or find out the current status of the product registration.
Hello, It would be best for you to contact your internal sales rep at (888) 280-7645 to get this information. Please have the serial numbers handy. Also, you can check if a product is alredy registered on ni.com MyNI My Registered Products Zvezdana S. National Instruments
Re: Differences beetwen versions
George, I would not be able to tell you about different versions of MATLAB, but to find out what changed between certain versions of LabVIEW, it would be best to look at LabVIEW release notes for the specific version. The latest one can be found here: a href=http://digital.ni.com/manuals.nsf/websearch/0FB36A66EDEA837A86256E40007051FF?OpenDocumentnode=132090_US;LabVIEW Release Notes/a LabVIEW 7.1 supports MATLAB versions 6.5 and earlier. LabVIEW 6.x and earlier does not interface properly with MATLAB 6.1 or MATLAB 6.5. Zvezdana S. National Instruments
Re: DAQ vis not in vi.llb
If you did a custom installation and selected only LabVIEW, or canceled when it asked you to insert the DriverCD, no drivers were installed. You can install individual drivers from the DriverCD that shipped with the LabVIEW 7.1 CD, or can download the latest NI-DAQ from our web site: a href=http://digital.ni.com/softlib.nsf/954feaeea92d90918625674b00658b83/50f76c287f531aa786256e7500634be3?OpenDocument;NI-DAQ Version 7.2 for Windows 2000/NT/XP/a Zvezdana S. National Instruments
Re: Application builder-Office report generation toolkit
Eki, When you use the Report Generation Toolkit to build a stand-alone application with the Application Builder, you must add _Word Dynamic VIs.vi from _wordsub.llb and _Excel Dynamic VIs.vi from _exclsub.llb as dynamic VIs. These two VIs contain subVIs that are called dynamically by the high-level Report Generation VIs. I believe that if you grab these VIs from the (desired office version part of the) installation CD instead of from the development machine, then everything should work. Zvezdana S.
Re: Looking for Application Builder 6.1
Christian, Since the launch of LabVIEW 7.1, we are not selling the App Builder 6.1 any more. We don't keep the old version CDs in stock. It is best to contact your regional sales rep to see what options there are. If you absolutely have to use this older version, you could maybe purchase the App Builder 7.1 and the sales rep could also send you the older copy. You can contact the sales department at Tel: (888) 280-7645 A HREF =https://sine.ni.com/apps/we/nicc.call_me?p_country=United+Statesp_lang_id=USp_form_id=6;E-mail/a sales Fax: 512-683-8411 Zvezdana S. National Instruments
Re: Dispose Report closes all Excel spreadsheets
Henry, This is the expected behavior. The Dispose Report VI calls Excel_Quit.vi. This subVI calls _Application.Quit Excel method. You can modify this subVI to not call this method, or to call it if you press a boolean button. Excel_Quit.vi is located in LabVIEW\vi.lib\addons\_office\exclsub.llb Zvezdana S. National Instruments
Re: Wanted: Any version of LV Full + app builder....
You may also want to contact your regional NI sales rep or alliance members to see if they have older versions or know where would be a good place to get them. Zvezdana S.
Re: New to active X, why does this not work
Which version of media player do you have? LabVIEW (6.1, 7.0, and 7.1) doesn't work with media player 9.0. a href=http://digital.ni.com/public.nsf/websearch/5EBD67575DD88DD186256E8B0050453E?OpenDocument;Windows Media Player 9 ActiveX Container Does Not Display Video in LabVIEW Front Panel/a Zvezdana S.
Re: Disable Monitoring of Remote Panels
Kura, I am not sure I understand your request. If you don't want several students to view the same remote panel simultaneously, you should use one remote panel license. That way, only one computer at a time can access remotely the VI. If you do want to allow multiple students to view and control the VI remotely, then please explain what you would like to see happen to prevent students looking over someone's shoulder? Zvezdana S.
Re: Error #3, memory.cpp, line 865(V6.0) 876(V6.0.2)
Hello, It seems that while copying your file, memory is filling up too quickly for LabVIEW to clean it up and it's crashing LabVIEW. View the memory usage in the Task Manager to confirm this. a href=http://digital.ni.com/public.nsf/websearch/01B186B5CEB1D07786256747000F4319?OpenDocument;LabVIEW Internal Errors (Failure in XXX.c / XXX.cpp at line YYY)/a If the Copy function is not the cause of the error, about 95% of the time, the next step is to look for DLL nodes or CIN nodes. The likely culprit is that a string or array is being handed to the C code, which either overwrites memory, or leaves the array/string data structure to an inconsistent state leading LV to overwrite memory. Anyway, this is a very common cause. If you eliminate that possibility, the remainder are usually some sort of corruption saved in the VI, but normally those will not even load. To simplify it before submitting it to support, please try executing individual subVIs and see if the problem is limited to a particular VI or a smaller set of VIs. Zvezdana S.
Re: Ignition Switch to use in a Labview panel?
Chris, I don't have experience in designing such systems, but here is one document that I think will help you in your design. a href=http://zone.ni.com/devzone/conceptd.nsf/webmain/D367783F087E57E386256CC90055172B;Building Flexible, Cost-Effective ECU Test Systems/a I was able to find few other articles when I searched on Google for ignition switch and labview. Zvezdana S.
Re: Image.cpp error, line 11067
Hello, Which version of LabVIEW was the VI last opened and saved in? Here are some general suggestions for you to try to recover this VI: a href=http://digital.ni.com/public.nsf/websearch/01B186B5CEB1D07786256747000F4319?OpenDocument;LabVIEW Internal Errors (Failure in XXX.c / XXX.cpp at line YYY)/a If after these you still cannot open the VI, please send a support request email to ni.com/ask with the VI. Zvezdana S. National Instruments
Re: format into string
You can submit this suggestion directly to RD engineers at NI. Just go to ni.com Contact NI Product Feedback Zvezdana S.
Re: I keep getting an error stating that my disk is full in...
Hello, Yes, you can delete the file. A new file in Syslog directory is started each time that LabVIEW and the Tag Engine is started. You can either manually delete old files or write a simple VI to automatically delete files that are older than a certain number of days. As an alternative, you can save these files into another folder, just to free up syslog directory space, and still have these history files for later use. Zvezdana S. National Instruments
Re: Application Builder error 2036400
Michael, I wasn't able to find any references to error code 2046300, but here are some things you can try: - first recompile your VIs into LabVIEW 7.1 ( by opening and save them) before building them with App Builder 7.1 - save all of your VIs in a library and then select your top level VI from library when building the executable. Add any dynamic VIs and support files e.g. DLLs etc. Here is what I found another NI engineer posted on google about this to another customer for whom the above solution worked: The documentation doesn't explain this because it is not really necessary. What is necessary is that all of the linkages in your hierarchy of VIs are correct *before* building the application. I suspect that if you were to open your VIs in the LabVIEW development environment and then close them, LabVIEW would start prompting you to save changes in your VIs. This indicates that the linkage information stored in the VIs does not reflect the actual state of the VIs on your computer (i.e. LabVIEW had to search to find a subVI rather than linking to the VI identified by the relative path stored in the calling VI). If you save these changes and then build the application, I bet it would work correctly. Saving things to a new library via the Save With Options dialog is way of forcing the linkages to be correct, which is why it solved the problem for you. - reinstall the application builder 7.1 - make sure you have run-time engine 7.1 installed before you run the executable Zvezdana S. National Instruments
Re: windows media player 9 labview 7
Dave, This should be fixed in the next release of LabVIEW. Zvezdana S.
Re: windows media player 9 labview 7
Dave, This is a known issue with the compatibility between Windows Media Player 9 and LabVIEW 6.1, 7.0, and 7.1. When you play a movie file with WMP9, the video portion of it does not show up in the Media Player display. Microsoft has changed the version of the Windows Media Software Development Kit used with Windows Media Player 9. LabVIEW was designed to work with the SDK version used to build Windows Media Player 8.0. The issue can be resolved by downgrading your version on Windows Media Player to 8.0. Zvezdana S. National Instruments
Re: Take windows screen shot and output to file
I didn't find that page that has the VI. But here is a document that allows you to save a front panel window as a picture: a href=http://pong.ni.com/public.nsf/websearch/942DAA35C7B35616862565FE005F713F?OpenDocument;How Can I Programmatically Save a Front Panel Image as an Image File?/a I hope this is what you were looking for. Zvezdana S. National Instruments
Re: Examples VIs from Report generation Tool kit is not executable.
Suresh, Where are the toolkit examples breaking? Is it that they cannot recognize some activex objects and property nodes, or is it that they cannot find some subVIs? Which properties/SubVIs are those? When you go to reinstall the toolkit, make sure you specify you want to install the VIs for Office XP. Maybe the first time it installed the VIs for Office2000, thinking that is the version you have since you run it on Win2000. Also, do you have the earlier version of the toolkit installed, version 1.0? You should uninstall it before installing version 1.0.1. If you are still having problems, try to force the recompile of the toolkit VIs. Recompile is different from the mass compile in that it rebuilds the VI binary. Open the VI that is broken (Sample Text Report) and select CTRL+Run Arrow. It will recompile all VIs in memory. Save and close the VI. Open the VI again and if it still broken look in the sub-subVI called Font Style.vi. In the upper left-hand corner of this VI there is a property node. Change the property node to a different property and back. This should fix the broken arrow. Here is a document that talks about similar problem: a href=http://digital.ni.com/public.nsf/websearch/5A42F1725790DFBC86256B900075F884?OpenDocument How Do I Fix the Report Generation Examples for LabVIEW 6.1 so They Don't Generate an Error?/a Zvezdana S. National Instruments
Re: Running VI from another VI
Julien and Shreesha, What I meant by 'Program 2 has to be open is that Program1 will run Program2 dynamically, but will not open its front panel. Program1 doesn't launch the front panel of Program2, it just runs Program2 in the background. To actually see the Program2 open, and be able to stop it by clicking on the Boolean on its front panel, you have to use the FP.Open property node, or have Program2 front panel opened before clicking on Lauch Progam 2 boolean in Program1. Zvezdana S.
Re: Filter Express vi building appllication problem.
Neuvos, Thanks for this feedback. Yes, we are already aware that the problem is with the frequency limits, but only when the VI is used as an express VI. Converting it to a regular VI, even with those limits, resolves the problem. Zvezdana S.
Re: Filter Express vi building appllication problem.
Neuvos, This problem with the Filter express VIs built into exeuctables has already been reported to LabVIEW engineers, and they are working on a solution. For now, a workaround is to convert the particular filter express VI into a regular VI. To do this, right-click on the express VI and select Open Front Panel. Select Convert in the dialog window. Then just save the opened VI into your project directory. Zvezdana S. National Instruments
Re: Error in LabView.exe after each start
Hello, The file you attached is a LabVIEW.ini file, where the configuration settings are stored. Please find the error log file, and this should give you a better idea what might have caused the error. There are two types of log files. There are those created by LabVIEW and those created by Windows. The log file created after internal LabVIEW errors is called LabVIEW_Failure_Log.txt and it is stored in your temporary LabVIEW directory. By default, this directory is located at C:\Documents and Settings\(User Name)\Local Settings\Temp (Windows 2000). NOTE: By default, the Local Settings folder is a hidden folder. In order to view hidden files and folders in Windows Explorer, select Tools =BB Folder Options =BB View. In the Advanced Settings field, select Show hidden files and folders. If you have modified the location of you temporary directory, the log file will be located there. To view or change LabVIEW's temporary directory path, go to Tools =BB Options =BB Paths =BB Temporary Directory. For more information on the error information contained in the LabVIEW_Failure_Log.txt file, visit the LabVIEW Internal Error Support Page linked below. If you receive an error message saying that LabVIEW has generated errors and will be closed by Windows, there will be a different log file created. This is a log file created by Windows, and by default it is a Dr. Watson's error log file. These log files are saved as .log file under ...\WINNT folder for NT based systems, and as .wlg under ..\Windows\Drwatson folder for Windows 9.x systems. If you open just LabVIEW, without trying to open a VI, will you still receive the crash? If so, can you create a new simple VI similar to the VIs that crash LabVIEW and run it? Do you call any hardware driver or other dlls with the VIs that cause LabVIEW to crash? Zvezdana S. National Instruments
Re: How to set PCR temperature profile in LabVIEW?
Wingston, Please give us some more information on what PCR (Polymerase Chain Reaction?) Temperature and the tree set points are. There is no LabVIEW shipping VI that would specifically set this value. If you already have a formula that would calculate the PCR temperature based on the three temperature inputs, then just use the Formula Node in LabVIEW. Zvezdana S. National Instruments
Re: How to compile wavread on MatLab Script?
Janet, Remove the quotes around blah. Just put in your MATLAB Script Node f=wavread(blah) With the quotes, MATLAB was trying to read the string 'blah', and not the blah input, which is 'annano.wav' Zvezdana S. National Instruments
Re: Item names in a strictly typed ring control do not update.
Sudhir, That quote does state that the strict type controls and indicators on the front panel will update in value and appearance. However, the change will not affect the constants on the block diagram. I am still investigating the second issue about rings with the sequential values. Zvezdana S. National Instruments
Re: Item names in a strictly typed ring control do not update.
Sudhir, This is an expected behavior with strictly typedef ring constants. Instead of menu rings, you will want to use enums. A Strict typedef keeps its cosmetic information on the front panel but not on the Block Diagram. The type of the ring does not depend upon its strings - like it does with enums. See a similar post on this topic bellow: a href=http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101RPAGEID=135HOID=506500080016B2UCATEGORY_0=_49_%24_6_UCATEGORY_S=0;Strict Type Def with Menu Ring does not automatically update linked constants/abr Zvezdana S. National Instruments
Re: question on DAQmx
Jim, You can wire an array or strings indicator to the output of Channels property node. Zvezdana S.
