Installing a 2021 toolkit on top of a 2023 LV install.

[Tom_Powers]

We are trying to upgrade from 2019 to 2023Q3

Here is an example of the problem I would lay odds that there will be more.  The most current version of Advanced Signal Processing Toolkit is 2021.  When I went to install it the installer dumped everything including the menu items the following places.

C:\Program Files\National Instruments\LabVIEW 2021\vi.lib\addons\_Advanced Signal Processing

C:\Program Files\National Instruments\LabVIEW 2021\menus\Categories\Signal Processing\Advanced Signal Processing

I can go track down the broken links in my programs which is moderately painful but something that I only have to do once per main program.  Does this mean that I have to write a script to copy all of the menu items from LV2021 to LV2023 directory.

Alternately does this mean that I have only update to V2021.

[dkfire]

If you do a search in NI Package Manager for the toolkit, you should be able to install a 2023Q3 version. 

NI has moved a lot of toolkits to NI Package Manager, and has not updated the download page with the same versions. 

[Andrey_Dmitriev]

---

@dkfire wrote:

If you do a search in NI Package Manager for the toolkit, you should be able to install a 2023Q3 version. 

NI has moved a lot of toolkits to NI Package Manager, and has not updated the download page with the same versions. 

---

You're perfectly right, good to know!

[Tom_Powers]

Thanks.  This is an "example" install as I need to come up with a process to do the same install for about 10 or 15 machines after the holidays.  The next step will be to completely uninstall LV and try again.

I will post it as solved once I got through and do it myself with the enterprise license installer.

[Tom_Powers]

Still I needed the Control Design and Simulation Module which Package Manager says is only available up to 2022Q3.  It dumped all of the vis and stuff into part of which was one of the vis that was making my old software crash that was found at:

C:\Program Files\National Instruments\LabVIEW 2022\vi.lib\addons\System Identification

I still can not find any links on the menus other than manually finding that directory. Otherwise it will require that I track stuff down.  I wonder if there is a way to go searching in the past N years of "LabVIEW 202N" directory paths." have that setups that people have to do on a machine by machine basis.

[dkfire]

Now that tool kit seems to have died. 

If you need to use that tool kit, you need to use a version of LabVIEW that matches the tool kit version. 

And no, a tool kit needs to have the same version as LabVIEW or can be up to 3 years in front. 

So a tool kit of 2021 can support LabVIEW 2018, but not the other way around. 

[Tom_Powers]

"

"Now that tool kit seems to have died.

If you need to use that tool kit, you need to use a version of LabVIEW that matches the tool kit version.

And no, a tool kit needs to have the same version as LabVIEW or can be up to 3 years in front. So a tool kit of 2021 can support LabVIEW 2018, but not the other way around."

I hope that you are wrong on both counts.  I will follow up with an official support ticket.  I use advanced signal processing in a number of programs for sound and vibration and for curve fitting on multiple resonances close together.

I did not check that it worked but the 2022 version did load without errors in 2023.  I will have it crunch some numbers when I get in front of that computer.

On the you have to do 2022 rather than 2023 that would be painful as we already have a half a dozen computers, where we don't run that program, upgraded to 2023, have about 20 more to go, 10 of which need these tools.  I hate the concept of having to maintain multiple versions because we push software from computer to computer all of the time.

[Tom_Powers]

A little more research.  There is an article.

https://knowledge.ni.com/KnowledgeArticleDetails?id=kA0VU0000004x7x0AA&l=en-US

A certain fraction of the subVIs are things like express VIs or programs with C-interface nodes.  Those can not be converted from 2022 to 2023. 

However, I think that I am in luck and all of the stuff that is in the system identification pallet all seems to be all written in native code which means that I can just rename them and add them to the project in my current version and they will make it through the upgrade.  There are many pallets where everything drills back down to native code.  Not all of them are.