I'm calling a TestStand sequence from 32-bit LabVIEW (2019). The computer has TestStand 64-bit (2019) installed.
When I run the TestStand API from LabVIEW, everything goes well up to a point:
On the first run through, I was asked to locate the "modelsupport2.dll". I did a search, found it and got the following:
----------------------------------------
Details:
Could not load DLL or external library 'C:\Program Files\National Instruments\TestStand 2019\Components\Models\TestStandModels\modelsupport2\modelsupport2.dll'.
The DLL is a 64-bit DLL and thus cannot be loaded by 32-bit TestStand.
----------------------------------------
Error Code:
-17004; Could not load DLL or library.
----------------------------------------
Location:
Step 'Read Model Option Defaults' of sequence 'Initialize Execution Entry Point' in 'ModelSupport.seq'
----------------------------------------
I tried finding a 32-bit version, but the 64-bit one is the only one that I can find on the machine.
Any suggestions?
Here are thoughts that I have:
Is it because the sequence that I'm trying to call was built in TS 64-bit?
Is that DLL call based on the entry point that I'm trying to use? i.e. I'm calling "Single Pass" in the SequentialProcessModel.seq - should I try another entry point?
Is there a way to force LabVIEW to run TS in 64-bit version, like a switch in the ini file?
Our system uses VeriStand 32-bit, LabVIEW 32-Bit and TestStand 64-bit. These were decided on prior to me coming to the team. I would have recommended staying with 32-bit across the board. Is there a workaround for this, or do we need to change to TS 32-bit? This would cause headaches as we have a LOT of sequences written in the 64-bit version.
Any thoughts or suggestions are greatly appreciated.
