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

[dcl9000]

It would be great to see more LabWindows/CVI related articles in "Instrumentation Newsletter" that NI sends out to us quarterly.  More than 90% of the articles in "Instrumentation Newsletter" so far are about LabVIEW.  Not quite pleasing to CVI users .....

[Adri_K.]

Hi,

I appreciate the feedback for the Instrumentation Newsletter. We are currently working on articles to include in future Instrumentation Newsletter that will feature LabWindows/CVI and Measurement Studio. Additionally, there is an quarterly electronic distribution of the LabWindows/CVI Developer Newsletter that is centered around LabWindows/CVI developers and ANSI C related technologies. In this Newsletter you will find LabWindows/CVI tips and tricks, how-to articles, product release information, updates and event announcements. If you are not already signed up, you can do so here. You can also make suggestions for future featured articles to be included in the LabWindows/CVI Developer Newsletter.

Thanks,

Adri Kruger

LabWindows/CVI Product Manager

[Y. D.]

as a windows programmer, personally I like CVI more than labview from past two decades windows programmming.

Targeting on Measuring Instrument and windows OS, I have been using Labview for 10 years.  but I chose CVI for my own copy.

Yes,  it would be great and pleasing if CVI could occupy more pages In NI's published support. and hope NI can extend the support to next decade.

anyway appreciate NI for their wonderful tools and support. 

[Ray.R]

I just read this thread and now I am curious..

What made you become concerned with the support for CVI in the future?

I have to agree with others that find this forum as an excellent source of support.  This forum beats any other C language support forum out there..  Especially for vxWorks (hope Tornado reads this 😛  😉  )

I don't even think of the possibility that NI or this forum would ever dissappear.  It's here for a long time.  Probably much longer after I retire.. 😄

[GayleCRoth]

Hi,

I'm on a project team whose task is to figure out which of 3 development packages would be best for building a Display Subsystem to integrate with our new data system which we're in the process of developing.  The 3 possibilities are:  LabWindows/CVI, LabVIEW, and C++ w/ Qwt classes.  Our team lead asked me to find out how long LabWindows/CVI would be supported, as a factor to weigh into our decision.  That's why I posted this question and started this thread.  The LabWIndows/CVI Product Manager, Adri Kruger, assured me that LabWindows will be supported and new versions created, for at least the next 10-15 years.  I'm now reassured that LabWindows has a future.  Thank you all for your responses.

Sincerely,

Gayle Roth, Computer Scientist

NASA Glenn Research Center

[Adri_K.]

National Instruments is dedicated to future support for LabWindows/CVI. Standard support for NI software platforms are provided through NI Software Maintenance Programs and give customers access to the latest updates, maintenance releases and technical support. The LabWindows/CVI Life Cycle Policy provides additional information on current, mainstream and extended support for the LabWindows/CVI development platform. This information is meant to help you better understand our investment in LabWindows/CVI and plan your software migrations. 

NI has a 15 year roadmap for releasing new versions of the LabWindows/CVI development platform with new features for developer productivity, improved performance, integration with new hardware and support for the latest PC technologies.

LabWindows/CVI is dedicated to adding value forto ANSI C test and measurement developers and NI will continue to include development plans for new features based on user feedback and new technologies.

If you have additional concerns regarding future support for LabWindows/CVI or any NI software platform I encourage you to contact your NI Sales Representative.

National Instruments is dedicated to future support for LabWindows/CVI. Standard support for NI software platforms are provided through NI Software Maintenance Programs and give customers access to the latest updates, maintenance releases and technical support. The LabWindows/CVI Life Cycle Policy provides additional information on current, mainstream and extended support for the LabWindows/CVI development platform. This information is meant to help you better understand our investment in LabWindows/CVI and plan your software migrations.

NI has a 15 year roadmap for releasing new versions of the LabWindows/CVI development platform with new features for developer productivity, improved performance, integration with new hardware and support for the latest PC technologies.

LabWindows/CVI is dedicated to adding value for ANSI C test and measurement developers and NI will continue to include development plans for new features based on user feedback and new technologies.If you have additional concerns regarding future support for LabWindows/CVI or any NI software platform I encourage you to contact your NI Sales Representative.

Thanks,

Adri Kruger

LabWindows/CVI Product Manager

[dcl9000]

It's great to know that NI has the dedication to LabWindows/CVI for the coming future.

We know NI makes more money from LabVIEW, but there are still a great number of CVI users out there like us.

Browsing through NI's web site, you definitely see much more links about LabVIEW then LabWindows/CVI.

Even at the first page of NI's web site (www.ni.com), LabWindows/CVI is not listed as one of NI's product platforms,

and the "User Groups" link in the "Support and Community" tab directs you only to the "LabVIEW User Groups."

Nor is LabWindows/CVI seen in the Industrial Measurement and Control page (www.ni.com/industrial). 

That makes us nervous about CVI's future.

[Y. D.]

yes, the above comments is what we see from NI webs and what we can feel.

look at the fate of microsoft C (existed more than a decade ago): with the "advanced technology" developed by the company, we become a program user of C++, C#.....  instead of programmer.  more and more fundamental, critical and "innovative" technology controlled by the company, what we do is pay the fee, and use it  instead of programming with it.  

anyway, it is good for application user, but not good for us programmer.