Windows XP supports Labwindows/CVI Test Executive 2.01?

Is Windows XP supports Labwindows/CVI Test Executive 2.01? If no, any patch SW available to make work it on Win XP?

We have run cvi Test executive on Win 2000 and XP we used CVI 7 to build the exe.
not sure if an existing exe compiled for an earlier version of windows will work.
Note with the later versions of OS come multiprocessor support we have had some issues with programs written for single processor operating systems crashing after a few hours when running on a multiprocessor system. This was fixed by setting the processor affinity to restrict the application to a single processor ( under task manager go to process right click and select set affinity then only tick one of the processors.)
Colin

Similar Messages

Coverting an application from test executive to test stand.

I have used LabWindows CVI and the "test executive" toolkit to develop production test applications. The production operators who use the programs like the look and feel of the interface.
I want to convert to Test Stand so that I can support solutions written in languages other than CVI. How do I modify the test stand user inteface so that I get an identical operator interface?

Hi Tom,
You can also convert your CVI test executive sequence files into Teststand sequence files. Under the Tools menu in the TS Sequence Editor you will find a wizard that performs the task for you. It will take the CVI callback functions and generated the equivilant TS Callback sequence calls. You may still have to make some manual changes, but you wont have to completely regenerate your original test sequences from scratch.
Regards
Ray Farmer
Regards
Ray Farmer

How to call test Sequences developed by using CVI Test Execuitve toolkit in Test Stand?

There is a feature in TestSatnd which can convert CVI sequence to test Stand Sequences. But test stand is not recognising these sequences saying " not a valid CVI test sequence". Is there any version Issues, while converting these sequences to TestStand?

Hi Scott
In continuation of previous question..
As per the suggestion, when I am trying opening one sequence(.SQU) file,developed in CVI Test Executive V 1.0.1., in CVI Test Execcuitve V 2.0.1, Executive is throwing error.
The Pop Error is " Section [Sequence] missing from sequence file c:\xxx.squ"..
and when I am trying opening these sequence file in sequence editor, the tool it self is crashing.
Please suggest!!
Is there any specific tokens which we need to add in .SQU files of V 1.0.1, so that V 2.0.1 can understand them? Just to check the possibility of manual updation of .SQU files.
Regards
Amit

LabWindows/CVI Process Communications

I have a LabWindows/CVI application (executable) that must launch a second executable via the "LaunchExecutableEx" library function. When the second executable terminates, it must return an integer value to the first executable. Other than the horrid solution of using a disk file, how can this be done?
Maybe by using a shared DLL?
Thanks.

Please refer to the post on the LabWindows/CVI forum here
Al B.
Staff Software Engineer - TestStand
CTA/CLD

Does LabWindows/CVI support C++?

Hi there,
I have been using labview for long time and we are looking for another way to improve the performance and labwindows/CVI seems to be a good choice. But here I got few questions
1) Does it support C++ also?
2) Could I compile the LabWindows/CVI applicaiton as a standalone program using in other computer without labview installed?

Hi dragondriver,
are you using CVI or LabVIEW??!? 'Cause here we are on the CVI board
Anyway, whichever is the system you are developing on the Run-time Engine must match the requirements for the executable. As per CVI, the runtime must be of the same level or higher that this. That is why you cannot run a CVI2012 executable with a CVI7 IDE or runtime installed, while it is safe to so the opposite. I do not know the state of the art with LV: in the past the release of the development system and that of the runtime needed to match exactly (infact you could have several LV runtime installed on the same system).
You cannot expect of course that a CVI executable can run on a system with the LV runtime installed (and vice versa)!
With reference to your last question, Traditional DAQ and DAQmx are completely different products, so installing one of them does not affect the other. Additionalle, you cannot mix commands from both environments in the same application: either you develop using old Traditional DAQ functions or you move entirely to the new DAQmx. You can have both of them installed on the target system.
Proud to use LW/CVI from 3.1 on.
My contributions to the Developer Zone Community
If I have helped you, why not giving me a kudos?

Test NI cDAQ-9188 using LabWindows/CVI

I am looking for help to create test for cDAQ-9188 with DIO and AIO modules.
Would you please advise with information as follow:
1. Adding device driver to a project.
2. Sample of UI.
3. Sample of test script for DO (AO) control.
4. Sample of test script for DI (AI) acquisition.
Thank you.
Sincerely,
Sam.
[email protected]

There is a tutorial on using DAQmx with LabWindows/CVI here: http://zone.ni.com/devzone/cda/tut/p/id/2931. That is probably a good place to start.
Another good article to check out is the NI Ethernet Data Acquisition Overview here: http://zone.ni.com/devzone/cda/tut/p/id/7374.
As far as examples go, there are several text-based examples (as long as you have DAQmx installed) located at: Start Menu >> All Programs >> National Instruments >> NI-DAQ >> Text-based Code Support >> ANSI C Examples.
National Instruments

Using Labwindows CVI Version 10.0.1 USB communication with FTDI FT2232D to unit under test.

Communication with unit under test works fine in hypterminal after I downloaded virtual driver from FTDI site.
Never done any USB communication before in LabWindows CVI. What functions can I use in labwindows CVI?

Since the device presents itself as a COM port (pretty standard with the FTDI chips) you should be able to use the RS-232 library in CVI. OpenComConfig() will open a connection to the device, ComWrt() will write data to it, and the various ComRd() functions can be used to read the responses back.

Running a LabWindows/CVI application created and built in Windows XP Serv.Pack 2 on a Windows 2000 computer

I have created an application using LabWindows/CVI on my computer. I would like to install this application on a Windows 2000 machine but I receive a message saying something like "This program requires Windows XP service pack 2".
What can I do to make this work.
I am using LabWindows/CVI version 2010.
Any Ideas?

OK, Thanks, I will try that.
Regards
// Mikael

How's NI's support for LabWindows/CVI? How's it likely to be in the future?

Hello Fellow LabWindows/CVI Users,
Have you found that National Instruments provides good support for LabWindows/CVI? If so, do you expect good support to continue in the future?
Thanks,
Gayle Roth

Duplicated post
Proud to use LW/CVI from 3.1 on.
My contributions to the Developer Zone Community
If I have helped you, why not giving me a kudos?

Labwindows CVI install - Windows SDK error

Hello,
I have a problem when I try to install Labwindows CVI 9 on Windows 7.
I had no problems so far, but now the installation doesn't work and the following message appears:
Do you help me please, it's very important and urgent.
Thank you.
Best Regards.
Karine.

Hello,
I don't really understand the issue... you said that you have no problem when you install LabWindows CVI 2009 on Windows 7 - that's good!
And now you have an issue with an installation... with another software (I guess) ?
This error appears when you are installing an incompatible version or your toolkit/drivers/software with your actual OS.
As you are using Win 7, I suggest you to check the compatibility of what you want to install on your computer : http://www.ni.com/white-paper/10383/en
Regards,
Celine
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
Journées Techniques LabVIEW
Du 15 octobre au 7 novembre : Strasbourg - Lyon - Lille - Toulouse - Mar...

Conversion of an Instrument Driver from LabWindows/CVI to LabVIEW

Hello All,
Conversion of an Instrument Driver from LabWindows/CVI to LabVIEW
http://zone.ni.com/devzone/conceptd.nsf/webmain/9A93316BEBEDB17786256FA300675A0A
But I can not find any hyperlinkt to download
"LabVIEW Interface Generator for LabWindows/CVI Instrument Drivers"
Is there any evaluation version for downloading?
Thanks,
nonomiya

So strange,
I go through three pages but does not find any entry for download,
hmm...,
1. After press the hyperlink,
See Also:
LabVIEW Interface Generator for LabWindows/CVI Instrument Drivers
2. and for a resuest info. form.
3. press download..
====
LabVIEW Interface Generator for LabWindows/CVI Instrument Drivers
System Requirements
NI LabVIEW 7.1 or later
Windows 2000/NT/XP
Use the LabVIEW Interface Generator for LabWindows/CVI Instrument Drivers to create LabVIEW VIs for VXIplug&play and IVI-C instrument drivers from function panel (.fp) files.
Instrument Driver Network
Before using the conversion utility to create a new instrument driver wrapper, please visit ni.com/idnet to see if a LabVIEW Plug and Play instrument driver is available for your device. The Instrument Driver Network (IDNET) provides support for more than 3,000 different instrument models from over 170 different instrument vendors.
Recommendations
This utility was created for developers of C-based instrument drivers who wish to provide a LabVIEW interface, but do not develop a LabVIEW Plug and Play driver. By developing the C and LabVIEW interfaces together, it keeps the components synchronized, and eliminates the need for customers to create their own LabVIEW interfaces. Vendors should distribute the LabVIEW wrapper files with the associated VXIplug&play or IVI instrument driver, so that end users do not have to visit multiple web sites to download the complete driver.
If you are not an instrument vendor, we recommend that you use this utility only if you have instrument driver expertise. Access to the instrument driver source code is preferred, in case you need to edit the C instrument driver in LabWindows/CVI.
After generation, the wrapper VIs should be tested with the instrument.
Instructions
Once you install the software, simply access the utility from the Tools>>Instrumentation>>Import CVI Instrument Driver...menu in LabVIEW. This software replaces the built-in tool and provides feature enhancements.
For additional information on this utility, view the resources below.
Readme for the LabVIEW Interface Generator for LabWindows/CVI Instrument Drivers
Submit your Driver
Visit the Instrument Driver Network
nonomiya

.exe Build from LabWindow/CVI 7.1 run exception under RTE 8.0.1

Below is the source file of test1.exe, which was built using LabWindow/CVI 7.1 environment, OS is Windows XP SP3
Due to some reason(install TestStand, or LabView, or ...), the Runtime Engine cvirte.dll, cvirt.dll (exists in c:\windows\system32\ )is 8.0.1
Executing this file, the GenericMessagePopup() will generate window's exception. But if executing GenericMessagePopup() before LoadLibrary(), it will be ok.
By the way, "cp3245mt.dll" is Borland's DLL. If load other DLL, everything is OK.
Is there any suggestion to solve the conflict between NI and Borland? Thanks!
// test1.c sourcefile
#include <windows.h>
#include <userint.h>
#include <stdio.h>
main()
// If execute the below line first. it will be ok.
//    GenericMessagePopup("Info", "Test","Yes","No",0,0,0,0,
//   VAL_GENERIC_POPUP_BTN1,VAL_GENERIC_POPUP_NO_CTRL,VAL_GENERIC_POPUP_BTN2);
   LoadLibrary("cp3245mt.dll");
   GenericMessagePopup("Info", "Test","Yes","No",0,0,0,0, VAL_GENERIC_POPUP_BTN1,VAL_GENERIC_POPUP_NO_CTRL,VAL_GENERIC_POPUP_BTN2);

Did you ever figure this out. I've set classpaths, the APPCPATH variable several
times with many variations and its not working for me, though the jsp thing is working.

Introducing LabWindows/CVI 2009

National Instruments released LabWindows/CVI 2009 on Friday, December 4th.
LabWindows/CVI 2009 includes enhanced productivity tools and introduces a new toolkit for run-time analysis and optimization. LabWindows/CVI 2009 also includes support for new technologies such as the Microsoft Windows 7 operating system, 64-bit application development and deployment, and provides a new interface for communicating with NI PXI FPGA-based hardware including FlexRIO and R Series data acquisition modules.
Visit the What's New page to see a full list of the new features in LabWindows/CVI 2009 that will help users create more reliable applications in a shorter amount of time and take advantage of new PC technologies. You can also view the What's New webcast series to get a closer look at the new features in LabWindows/CVI 2009. Some of the new features include:
The new Execution Profiler Toolkit, an application performance measurement and analysis tool
Improved debugging capabilities capabilities with extended information in the variables and watch windows
Easier user interface development with the attribute browser
Integrated support for 64-bit application development and deployment
The C- Interface to LabVIEW FPGA, a communication interface for FPGA-based hardware
Support for Windows 7, the latest Microsoft operating system
Additional Technical Resources Just for LabWindows/CVI Developers
Subscribe to the LabWindows/CVI Quarterly quarterly newsletter to receive the latest product news, tips and tricks, and developer resources. You can also join the LabWindows/CVI user community and start collaborating with users.
Adri Kruger
LabWindows/CVI Product Manager
Message Edited by Adri K. on 12-07-2009 03:28 PM
Adri Kruger
National Instruments
LabVIEW Product Marketing

Turbo,
There isn't a document that covers all the features from 6.0 to 2009, though there are documents that talk about individual upgrades.
http://www.ni.com/lwcvi/whats_new.htm
Also this document covers the upgrades since 8.0 http://zone.ni.com/devzone/cda/tut/p/id/7995
There have been quite a few upgrades, you can always download an evaluation version and test it out for yourself http://www.ni.com/lwcvi/try.htm
Richard S -- National Instruments --Applications Engineer -- Data Acquisition with TestStand

Running Python Scripts through Labwindows/CVI

Hello,
I'm trying to execute Python scripts through Labwindows/CVI. I believe I have the correct library for the code to access in my project. I'm getting errors as it can't find "io.h", "stat.h", or "wchar.h" files. There is another post on this, where a modified pyconfig.h file was provided, however that file does not work for me. I'm not sure how to obtain the correct files for what I need here. Is there any dependable method to do this?
I'm on Windows 7, I'm running CVI version 9.1.1 and Python 2.6.6 (32-bit). The library file I'm using was proveded as part of the python install, called "Python26.lib". I zipped and attached the project, but to get it working you have to download Python (http://www.python.org/download/releases/2.6.6/), and point CVI to the "Python.h" header file (in the "include" directory under the "Python26" directory.
Attachments:
Test project.zip ‏4 KB

Where are these .h files located? If you know where these files are located go to Options>>Environment...>>Include Paths... you can add directories that the workspace will look for include files that are not explicitly included in your project.
Ian M.
National Instruments

Visual Studio or LabWindows/CVI?

I have a bit of a dilemma.
I currently own Visual Studio 2010, IMAQ Vision Development Module 2013, and Measurement Studio (not sure of version). I currently do all of my programming in VB.net. Because IMAQ VDM is stuck in .Net framework 3.5 and there will be no further .net development by NI, I need to plan for the future. My applications need run on Win 8, 9, 43, or whatever my company decides to migrate to from Win 7.
My understanding is that the NI modules I currently own will work with LabWindows/CVI. Correct? I also believe I can use them with C++ using the VS IDE. Is this also correct?
Within my applications I do a lot of interfacing with Excel, writing text files, and interfacing to non-NI devices (cameras, DAQs, scanners, etc). I am able to do these things pretty easily using VB.net using vendor-provided SDK's.
Therefore, my question is this...given the investment I have in software already, do I gain anything by migrating to LabWindows/CVI? What do I lose?
I should point out that regardless of the path I choose I will need to bone up on my programming skills in the corresponding language.
Thanks for all your help!

Hello Steverino!
Here are some advantages when using LabWindows/CVI over Visual Studio, which make the product more suitable for various industry-related applications:
You are correct, LabWindows/CVI integrates with the NI platform: NI hardware and software, like TestStand or LabVIEW (e.g. debugging source code from one software to another, seamlessly).
NI hardware and third-party hardware connectivity.
OpenMP support.
CVI integrates with intrument control.
CVI Run-Time benefits from User Protection.
Run-Time checking (e.g. for uninitialized variables).
Scientific User Interface Controls and GUI Editor.
Advanced debugging capabilities:
Remote debugging support from ADE.
Real-Time debugging support from ADE.
Memory leak detection using the LabWindows/CVI Resource Tracking Window.
Just-In-Time debugging.
Deployment: build custom installers and patches that you can ship as stand-alone easy-to-use installers.
LabWindows/CVI libraries: Advanced Analysis, Toolbox, Connectivity (Network Variables, Network Streams, DataSocket), etc.
Support for LabWindows/CVI Toolkits: SQL Toolkit, Vision, PID, RT.
Regards,
- Johannes.

Windows XP supports Labwindows/CVI Test Executive 2.01?

Similar Messages

Maybe you are looking for