migrating from lab view 2009 to lab view 2022

[Ahmed_emish_560]

Hello ,

I am migrating from lab view 2009 to lab view 2022  I am facing a lot of problem after download the lab view version 2022 and try to compile my project and it dosesnt work . is there any good practice while migrating to a newer versions how can i FIX THAT

I have 2009 lab view on other machine and the project works just fine , also it i would like to mention that this project is really huge like its around 1 gb so is ther easy safe way to migrate ?

thanks

[johntrich1971]

What do you mean by "try to compile the project"? Is this an FPGA project? Can you share more details about the problems that you are having? 

[JÞB]

---

@Ahmed_emish_560 wrote:

Hello ,

I am migrating from lab view 2009 to lab view 2022  I am facing a lot of problem after download the lab view version 2022 and try to compile my project and it dosesnt work . is there any good practice while migrating to a newer versions how can i FIX THAT

I have 2009 lab view on other machine and the project works just fine , also it i would like to mention that this project is really huge like its around 1 gb so is ther easy safe way to migrate ?

thanks

---

STOP! 

First you need to make sure your working code is absolutely backed up and placed in a source code repository WITH A TAG and never touch it again.

Second Export the MAX configuration of the working development system.   ESPECIALLY NOTE ALL SOFTWARE VERSIONS 

Your largest hurdle is going to be NI Device Drivers.  THERE IS NO VERSION OF ANY OF THEM that will support both LabVIEW versions.

So, you need to understand from the start that you need to be approaching this as an Obsolescence Mitigation project.  

What Hardware is involved?  Will the new Drivers work with them or has support been dropped?  Are any devices reaching the end of availability FPFA technology does not have a decade + useful lifespan.  Most Cars don't last that long (we won't discuss the pos I drive)

What OS versions are changing?

This is non trivial and you may want to engage a consultant with vast experience to guide the process.  Trust me the fee they charge is cheaper than the cost of the mistakes that WILL SURELY BE MADE by a developer that cannot even spell LabVIEW. 

So my answer is "I do not believe that you have the training, knowledge and experience needed to meet your goals."

[Ahmed_emish_560]

Hello , 
First of all my code is code is absolutely backed up  I make sure of that because we cant afford to lose this project . 

secondly the OS is windows and  changes from windows 7 to windows 11 on the new machine  also I would like to use lab view on Linux so what are consideration for this ,  Also the errors that appears after installing the new version is not that much most of it due to property node issues or that's what I think  . 
here is a sample of screenshot : 

[JÞB]

Without code we can only speculate.

What is an SWS3100? What command line utilities are expected? This leads me to guess an external command is either not present (software package not installed) or the driver is not present)  I doubt decade old 3rd party software included support for an OS that hadn't begun development yet.

So, what are the documented dependencies for the project? If it doesn't exist you better believe that you must generate and audit that document first. Then check your IQ, Installation Qualification, document. 

This is example of exactly why you can't just force through some upgrade willy nilly without research and planning.  You need to fully audit the existing system and plan the integration to the new environment. 

[JÞB]

The considerations for moving cross platform to Linux are exactly the same. 

Audit the hardware and software dependencies,  create an integration and installation plan that accounts for all dependencies on the new target and mitigates any obsolete system components. 

[altenbach]

If you keep calling it "lab view" (instead of LabVIEW), we can speculate that you are not very familiar with any of this!

1. There is no LabVIEW 2022 (it is in beta). What do you really have?
2. Windows 11 is not officially supported for any current LabVIEW version.
3. You have not mentioned if you are using LabVIEW 32bit or 64bit for the new version and how did you decide on bitness.
4. You have not really told us about the drivers and toolkits you are using. Did you really download and install everything needed first?
5. Is this running mostly on windows or does it involve RT and FPGA
6. Define what you mean by "compile the project". As soon as you open any VI, it will compile instantly unless there are errors. Are you talking about building a standalone exe instead? Are you talking about the mass-compile tool?
7. A 1GB project seems unreasonably massive. How do you measure the size? What is using all that space??? (Gigantic default data in controls and indicators? Gigantic background images and decorations?)