LV 2023 64 bit problems

[Mark1349]

My company has inherited a test fixture from the UK.  As the only person with LV experience (although dated), I have been tasked with getting it up and running.  The company purchased a license to allow me to get this running.

NI MAX shows LV 2023 Q1 64bit is installed, along with runtime engines 2017, 2020-2026.

The fixture is running a LabVIEW application, so I am not positive what version of runtime it is using. The programmer left the company in 2020. 

After numerous problems with dependency issues that I have solved, and removing the 240VAC power only bar code printer, I am having some issues with the call library function.  This uses a TTI PL303-P power supply and the drivers were 32 bit. I am not aware of why this test fixture operated but now does not.

Here are a few screen shots of the errors:

thank you for your time.

[altenbach]

You need to use 32bit LabVIEW or find 64bit drivers.

[crossrulz]

Personally, I would get rid of the DLL and replace the DLL calls with VISA commands. The TTi power supply I have used used SCPI-like enough  commands that I could just make a few minor tweaks to my normal driver to get it to work.

[altenbach · Accepted solution]

---

@crossrulz wrote:

Personally, I would get rid of the DLL and replace the DLL calls with VISA commands.

---

Definitely a better solution in the long run.

The reason it works on the "fixture" is because that must run off a 32bit runtime. IF you want to use the 32bit dll, you need LabVIEW 32bit.

I am not a hardware guy, but if crossrulz says that substituting Visa would easily work, I would believe him. 😄 

[rolfk]

See this thread: https://forums.ni.com/t5/LabVIEW/AIM-TTi-PL-P-driver-64-bit/td-p/4345539

It seems that AIM-TTi has created a 64-bit version of the DLL and send it to the OP in that thread on request but they have not managed to update the driver on the website in the last 2 years.

The archive https://www.aimtti.com/resources/new-pl-p-series-power-supplies-ivi-driver-v160 is the actual LabWindows CVI source code so it's possible to create the DLL yourself with a LabWindows/CVI installation but that may be slightly intimidating if you have no CVI experience.

Still think that creating a (minimal) LabVIEW PnP driver would be better in the longer run.

Attached is a build of the sources with LabWindows/CVI 2020.

You probably will either need to rename the PLP_64.DLL to PLP_32.DLL and put it wherever IVI expects the according DLL driver for 64-bit execution, or you may instead change the VI PLP Initialize With Options.vi in PLP.LLB to expect PLP_64.DLL instead of PLP_32.DLL. But I did not test it.

[Mark1349]

The comments from everyone got me thinking that possibly the application was made with 32-bit, but not sure of the LabVIEW version.  I used strings64.exe to look at the application and found it used LV2017.  I then installed LV2017 32-bit and the application has only DAQmx errors because DAQmx version 23 is installed.  

Now waiting on IT to give me a password so I can install DAQmx 17.  

I hope that onedrive does not prevent operation.

My time here is limited, as my contract expires on Friday afternoon.  I will likely not return. 

I will update everyone on the progress.  Thanks.

[Mark1349]

Installing DAQmx 17 made no difference.  I then uninstalled the 2024 daqmx and re-installed Daqmx 17, and it works.  There are some issues with the RFID scanner and some other things, but at least the software works and is communicating with the hardware.

Thank you everyone.

[crossrulz]

FYI, it looks like DAQmx 20.7 was the last version to support LabVIEW 2017. But keeping with the same version is a good strategy.