LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Program doesn't detect library

Solved!
Go to solution
Highlighted

So I have a program that I'm trying the first time I used it when I accidentally clicked ignore when he was searching for the library any way to get the program that searchs for the Sub VIs and Library location to pop up again?

Here is a screenshot

0 Kudos
Message 1 of 14
(595 Views)
Highlighted

Hi Max,

 

close all without saving.

Exit LabVIEW.

 

Start LabVIEW again.

Load your project and the mainVI…

Best regards,
GerdW

using LV2011SP1 + LV2017 (+LV2019 sometimes) on Win10+cRIO
Message 2 of 14
(593 Views)
Highlighted

Sadly it didn't work I don't get it

this program worked perfectly fine on two others computers one was using labciew 2016 the other 2018 (and this one 2018 as well)

0 Kudos
Message 3 of 14
(591 Views)
Highlighted

Hi Max,

 

checkout an older version of the VI(s) from your SCC system.

 

You don't use any SCC (source code control) so far? Lesson learned: use SCC!

Best regards,
GerdW

using LV2011SP1 + LV2017 (+LV2019 sometimes) on Win10+cRIO
Message 4 of 14
(588 Views)
Highlighted

I dont really need to this is a VI provided from a company to use on of their Instruments. It didnt get any modification

0 Kudos
Message 5 of 14
(585 Views)
Highlighted
Solution
Accepted by topic author 77maxmustermann

Hi Max,

 

when there is no modification to the VI(s) then LabVIEW will try to load that DLL (after the next restart) again!

Best regards,
GerdW

using LV2011SP1 + LV2017 (+LV2019 sometimes) on Win10+cRIO
Message 6 of 14
(582 Views)
Highlighted

Yeah tried  that the problem seems to be something else. It appears my theory was wrong the reason is that the program actually already found the dll. The problem seems to be the dll: The other computers work labview are 32 bits version, this one is 64 bits. could that be the problem?

0 Kudos
Message 7 of 14
(573 Views)
Highlighted

Hi Max,

 

The other computers work labview are 32 bits version, this one is 64 bits. could that be the problem?

I guess you talk about LabVIEW-32bit vs. LabVIEW-64bit versions: then the answer is YES!

You need to use the same bitness for LabVIEW and your DLL…

Best regards,
GerdW

using LV2011SP1 + LV2017 (+LV2019 sometimes) on Win10+cRIO
Message 8 of 14
(570 Views)
Highlighted

Nice we're getting closer and closer like in a saturday morning detective cartoon !

Any idea how to fix it though? how is it possible the change the DLLs "bitness"?

0 Kudos
Message 9 of 14
(567 Views)
Highlighted

Hi Max,

 

there are two options:

1. Get the source code of that DLL (and the same compiler) and compile the DLL for the needed bitness. (I'm no expert in compiling C code.)

2. Install LabVIEW-32bit and use the current DLL.

 

Which option is easier for you?

Best regards,
GerdW

using LV2011SP1 + LV2017 (+LV2019 sometimes) on Win10+cRIO
Message 10 of 14
(561 Views)