- Concerning LabVIEW and DLLs:
For some of our LabVIEW products, we have an interim dll called a Dispatcher
DLL, which itself calls out to the underlying DLL.
Please note that the dispatcher DLL and its associated INI file (which must be
bundled together in the same folder) allow you to be flexible in where the rest
of the DLLs are expected to be found.
• Your application needs to first access the dispatcher DLL.
• The INI file lists the name of the major underlying DLL, and where the DLL
sits.
• You can set the DLL path to be WINSYSDIR or SysWOW64 if that is good for
you.
- Additional explanation:
Each VI has an associated Call Library Function, which has an associated [Library
Name or DLL] and [Function Name].
For some of our LabVIEW products, the DLL name containing the API function
called out by the VI is listed directly in the VI. For some of our LabVIEW
products, we have an interim dll called a Dispatcher DLL, which itself calls out to
the underlying DLL.
When we use a Dispatcher DLL, the first VI call, Init_Module, opens an INI file,
ExcSWToolsForLV.ini, in which there are two lines that tell the dispatcher dll the
name of the underlying DLL, which actually is the API for all functions, and its
path (where it can be found).
This call to function Init_Module, loads the underlying DLL and creates pointers
to each API function therein. Then, for each VI called, the underlying API
function now has an associated pointer, and the actual function can be called.
We place the dispatcher DLL and the INI file in the folder where the LLB files sit.
So, when you open one of our application VIs, it can find & open the necessary
DLLs.
For example, for 429RTx, our default setting in the INI file is:
DLL name=Exc429RTx.dll
DLL path=PCI_and_UNET_DLLS
This indicates that the underlying dll is named Exc429RTx.dll, and is found in
subfolder PCI_and_UNET_DLLS. This folder contains additional DLLs that are
required by Exc429RTx.dll.
1. Can I run a VI written with LabVIEW 32-bit on LabVIEW 64-bit and Vice Versa?
The following information is taken from the FAQ at URL:
http://www.ni.com/product-documentation/54519/en/ .
Yes, a VI that is written with LabVIEW 32-bit development system can be opened in
LabVIEW 64-bit and vice versa because the code is not compiled until the VI is run.
2. Should I Use LabVIEW 32-Bit or 64-Bit?
The following information is taken from the FAQ at URL:
https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000kIctSAE&l=en-IL
Issue Details:
I am looking to download LabVIEW for the first time, or to develop a new application
in LabVIEW. Should I use the 32-bit or the 64-bit version?
Solution:
For our users on 32-bit or 64-bit operating systems, we recommend using LabVIEW
32-bit. This version has wider compatibility with Modules and Toolkits, as well as
greater support for 3rd-party Add-Ons.
LabVIEW 64-bit does not provide any speed improvements over LabVIEW 32-bit, but
does allow the program access to more system memory at once. While most of our
users find that the 32-bit version provides plenty of resources for their projects, some
specialized application areas may require this extra memory. If your program is likely
to handle very large arrays or to process images that are particularly high definition,
you may find that LabVIEW 64-bit is the better option for you.
In general, we recommend that developers start by working in LabVIEW 32-bit, and
only move to LabVIEW 64-bit if they find that they need the additional memory that it
provides.
Our CVIs are written & compiled under 32bit Windows. However, they can be run OK on 64bit Windows, providing that
they have access to the necessary 32bit DLLs.
Once you have verified that the card is installed under 64bit Windows, is visible in the Device Manager, has been
assigned a device number in ExcConfig, and is visible to Showhex, then you can proceed to installing the software.
Some of our LabWindows CVI tools products have been repackaged and are available for installation & use under 32bit
and 64bit Windows. Some have not yet been repackaged for use under 64bit Windows, and will install only on a 32bit
machine. In order to get these working under 64bit Windows, please follow these instructions:
1. On a 32bit Windows machine, install from the CD or download from our website the installation for "[product]
LabWindows CVIs".
The package will install to folder
"C:\Program Files\Excalibur\[product]-CVI" . The CVIs require a 32bit dll, compiled using the Microsoft compiler.
2. On this same 32bit Windows machine, install the 32bit Software Tools for this product. Go to either the Windows
system folder (C:\Windows\System32) or the software installation folder (C:\Program Files\Excalibur\[product]
Software Tools\excMSVisual) and copy DLLs named [product]ms.dll and exc4000ms.dll to the folder where the CVIs are
installed (the application folder).
3. There is one additional file needed in the application folder, where you will run your EXE. It is the 32bit version of
kernel file frontdesk.dll. This file is part of the Hardware Installation Disk for PCI, hw-pci-w2k.zip, on the webpage at
URL http://www.mil-1553.com/kernel-drivers-installation-software .
4. After you have copied the 32bit DLLs [product]ms.dll, exc4000ms.dll, and frontdesk.dll to the folder where the CVI
application EXE sits - copy this whole folder to your 64bit machine.
You should now be able to run the CVI application EXE under 64bit Windows.