LabWindows/CVI
Is LabWindows 2020 the final version that NI will release?
For information :
- Since version f3 was released
- We agreed to be put in contact, but we never made contact
- e-mail received in October 2022
Hi Patrick,
Finally, our R&D replied to our question.
Below is the current statement of the product which we have not yet messaged publicly, but are working with key customers like this to discuss the best path forward for maintaining existing systems and considerations for new projects.
LabWindows/CVI is a mature, feature-complete product where we are not currently planning any major releases. We will continue to support existing test systems built with LabWindows/CVI 2020 version through the Mainstream Support timeframe (9/2025) and beyond that, we are open to long-term service contracts on this version. (see https://www.ni.com/en-us/support/software-product-life-cycle-policies.html)
We have tested LabWindows/CVI 2020 f2 on Windows 11 and we expect no functional execution issues, we only observed minor UI degradation. I can provide more details if needed.
If you need a call to understand better I obtained permission to offer you the opportunity to talk with "...", the owner of this product in NI.
Would you like to have this call?
Kind regards, Cordiali Saluti, Cordialement, Freundlichen Grüßen, Se despide cordialmente, Vriendelijke groeten, 親切的問候
"..."
Technical Support Representative
... | ni.com
DISCLAIMER: ...
@pistino wrote:
Question: If Emerson/National Instruments is no longer interested in releasing updates or new versions of LabWindows/CVI, why not make this product free and open source?
Unfortunately, making a software like LabWindows/CVI open source is not just a throw over the fence and see if it sticks. There are a lot of legacy code parts in a sofware that started development more than 30 years ago (timeframe 1990-1992 and used parts of LabVIEW source code for a head start).
There is almost certainly licensed code in there that NI does not own and can't just publish at will. So there exists a significant task in cleaning up the code base of such legacy parts, comments unsuitable for public consumption, and third party licensed components, and legal consultation about possible license conflicts. Who is going to do that? And who is going to pay for it?
