Upgrade old Labview 32-bit to current version 64 bit

[OnlyOne]

Helo,

currently, LABVIEW 2015 Runtime (32-bit) is installed on my PC.

The VIs are called within TestStand 2014 (32-bit).

Now, the PC is to be replaced with a new one running Windows 11 and the latest version of TestStand, this time in 64-bit.

The LabVIEW Runtime will also be updated to the latest version.

1. Do the existing 32-bit VIs need to be recompiled (i.e., mass-compile)?

2. Can I assume that this should generally work, or are there known issues when switching from 32-bit to 64-bit?

Thanks for help and tipps
BRF

TM

[GerdW]

Hi One,

---

@OnlyOne wrote:

Helo,

currently, LABVIEW 2015 Runtime (32-bit) is installed on my PC.

The VIs are called within TestStand 2014 (32-bit).

Now, the PC is to be replaced with a new one running Windows 11 and the latest version of TestStand, this time in 64-bit.

---

So there are two issues: upgrading LabVIEW and TestStand at the same time…

• Do you call "plain" VIs or do you call VIs within ppls from TestStand?
  (Usually it is recommend to use PPLs with TestStand.)
  You will need to recompile PPLs…
• Do you call any 3rd party code? Changing EXE bitness may introduce problems with DLLs etc and so may need recompilation…

[OnlyOne]

All used VIs (only ~30 files) are part of a *.lvproj. The directory of the created files of this project are set as search path in TestStand.
In teststand i call only the *.vi in this directory.

All other teststeps are c#-steps that will be recompiled to 64 bit.

[thols]

Some more answers:

Migrating LabVIEW Code Modules from 32-bit TestStand to 64-bit TestStand

Using NI Products on 32-bit and 64-bit Windows 

LabVIEW 32-Bit and 64-Bit Compatibility