Best Software for 2025 is now live!
By NI
Save to My Lists
Unclaimed
Unclaimed

Top Rated LabWindows/CVI Alternatives

LabWindows/CVI Reviews & Product Details - Page 2

LabWindows/CVI Overview

What is LabWindows/CVI?

LabWindows/CVI is an ANSI C integrated development environment (IDE) and engineering toolbox with built-in libraries for measurement, analysis, and engineering UI design.

LabWindows/CVI Details
Show LessShow More
Product Description

LabWindows/CVI is an ANSI C integrated development environment (IDE) and engineering toolbox with built-in libraries for measurement, analysis, and engineering UI design.


Seller Details
Seller
NI
Year Founded
1976
HQ Location
Austin, TX
Twitter
@NIglobal
26,869 Twitter followers
LinkedIn® Page
www.linkedin.com
8,107 employees on LinkedIn®
Ownership
NASDAQ: NATI
Total Revenue (USD mm)
$1,286

Recent LabWindows/CVI Reviews

TS
Tao S.Enterprise (> 1000 emp.)
5.0 out of 5
"For everyday development and testing"
Powerful and integration with many many hardware components
Verified User
A
Verified UserSmall-Business (50 or fewer emp.)
2.0 out of 5
"Nice IDE platform"
reat libraries, active development community, full C language compliance
Verified User
U
Verified UserEnterprise (> 1000 emp.)
3.5 out of 5
"Great program!"
The LabWindows program was extremely easy to use - would recommend to others
Security Badge
This seller hasn't added their security information yet. Let them know that you'd like them to add it.
0 people requested security information

LabWindows/CVI Media

Answer a few questions to help the LabWindows/CVI community
Have you used LabWindows/CVI before?
Yes

Video Reviews

12 LabWindows/CVI Reviews

3.7 out of 5
The next elements are filters and will change the displayed results once they are selected.
Search reviews
Popular Mentions
The next elements are radio elements and sort the displayed results by the item selected and will update the results displayed.
Hide FiltersMore Filters
The next elements are filters and will change the displayed results once they are selected.
The next elements are filters and will change the displayed results once they are selected.
12 LabWindows/CVI Reviews
3.7 out of 5
12 LabWindows/CVI Reviews
3.7 out of 5
G2 reviews are authentic and verified.
Kevin M.
KM
Reliability Engineer
Information Technology and Services
Enterprise(> 1000 emp.)
More Options
Validated Reviewer
Review source: G2 invite
Incentivized Review
What do you like best about LabWindows/CVI?

LabView is great for one or two instruments running one or two tests. The programs are easy to start, stable, good looking and support just about every kind of hardware.

I prefer text-based programming environments like like VB, C#, pythion, etc. because I think they handle larger programs better. The main limitation to LabView for larger programs is the schematic based environment. A design with too many wire connections can turn into a hellish self-destructing haystack when a central block moves or changes. For the same reason, programs of all sizes are spacially inefficient - an entire screen of well made LabView can often be reduced to ten text lines of VB.

All of that to say this:

If you find yourself stuck in a lab where NI software is a mandate, look for CVI. Last I checked CVI was still included with the highest license level of Labview. NI keeps it hushed, I think because it looks like circa 1999 Microsoft MFC. LabWindows/CVI lets you circumvent arbitrary and capricious requirements to use clunky software when Microsoft publishes a perfectly usable, completely free version of C#.

LabWindows/CVI is fairly clunky itself, but I believe it's the lesser of two evils. Review collected by and hosted on G2.com.

What do you dislike about LabWindows/CVI?

NI keeps it hushed, I think because it looks like circa 1999 Microsoft MFC. LabWindows/CVI lets you circumvent arbitrary and capricious requirements to use clunky software when Microsoft publishes a perfectly usable, completely free version of C#. Review collected by and hosted on G2.com.

Recommendations to others considering LabWindows/CVI:

Use C# or Python instead. Review collected by and hosted on G2.com.

What problems is LabWindows/CVI solving and how is that benefiting you?

I write hardware test programs for semiconductor characterization and production. I automate water/gas/electric utility hardware testing. Review collected by and hosted on G2.com.

Hung-Chi L.
HL
Mfg Test Development Engineer
Computer Networking
Enterprise(> 1000 emp.)
More Options
Validated Reviewer
Review source: G2 invite
Incentivized Review
What do you like best about LabWindows/CVI?

LabWindows/CVI has a good UI integration which allows you to design your GUI and have the codes generated very easily. Most people used it to create instrument drivers. However, it can be used to beyond this scope. Since it's an ANSI C IDE, you can use it like a regular IDE tool for simple C projects. Review collected by and hosted on G2.com.

What do you dislike about LabWindows/CVI?

It's just an ANSI C IDE and compiler, period. There is no C++ features available. Hence, the nice exception handling and object-oriented programming (OOP) features are missing. The traditional error-code scheme really lacks the ability for the program to pass important error information in details, and hence, hampers the debug efforts when things fail. C++'s exception handling really helps simplifying the error handling and retains the failure details. The OOP feature can simplify the coding structure and complexity, making the codes more intuitive and readable. I wished that LabWindows/CVI can be upgraded to a C++ IDE/compiler. If for some reason some people just wanted the pure C features, the C++ compiler can always be restricted into the C-only mode. Review collected by and hosted on G2.com.

Recommendations to others considering LabWindows/CVI:

Simple but good UI integration. ANSI C only, period. Review collected by and hosted on G2.com.

What problems is LabWindows/CVI solving and how is that benefiting you?

I had developed a Manufacturing test framework using TestStand with LabView as the working layer. However, LabView manages its own objects in its own memory space. This makes the object passing between TestStand and LabView very inefficient. The result was a slow and memory hungry monster. Later, I had to rewrite the Laview part into multi-threaded C codes using LabWindows/CVI. The binary produced LabWindows/CVI is run in the same process space of TestStand making it more efficient to share and manage objects. The C version resulted in 33% decrease in memory usage and 33% faster than the LabView version. Review collected by and hosted on G2.com.