LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Program works fine in LabVIEW 32-bit, but not in 64-bit

Solved!
Go to solution

I have a very complicated program that is working fine with LabView 2014 32-bit on a Windows 7 64-bit PC. I installed LabView 2014 64-bit to be able to use more RAM, and now the same program is causing problems at one of the sub-VIs. Specifically, the sub-VI has an 'invoke VI' and it is causing problems since LV is not able to find the VI to be invoked. How come it can find it in 32-bit but not in 64-bit?

 

N.B. all copies are legitimate and licensed.

0 Kudos
Message 1 of 10
(4,208 Views)

Can you post at least a snippet showing the method you are using to "invoke" the VI?  There are multiple ways to do this, some of which may play better in 64-bit than 32-bit LabVIEW.

 

Is there a possibility that (since the code runs in 32-bit LabVIEW) you could make the code run more efficiently?  Are you doing a lot of Array things where you might be repeatedly building/copying arrays (which can do lots of memory allocation/deallocation)?

 

Bob Schor

0 Kudos
Message 2 of 10
(4,203 Views)

Here is a picture:

LV2014.png

0 Kudos
Message 3 of 10
(4,186 Views)
Solution
Accepted by topic author student_1
That's NOT a snippet! Please read the help on how to create this special type of image.

What happens when you open the VI normally? It seems you are using DAQmx. Is the 64-but version of that installed.
Message 4 of 10
(4,165 Views)
The error message is very clear. The VI you are trying to call is broken. When you see this error the first thing to always try is to open the VI and see what is wrong.

Mike...

Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion

"... after all, He's not a tame lion..."

For help with grief and grieving.
Message 5 of 10
(4,160 Views)

And while you are placing probes on error lines, catch all the earlier error lines as well to try to isolate the function that first generates the error.  If it's a DAQmx function, you probably have your answer ...

 

BS

0 Kudos
Message 6 of 10
(4,142 Views)

Here is a snippet:

 

a.png

 

The error is coming from 'Run VI', I have made sure that is the case. Also, the DAQ driver does nto seem to have specific versions for 32 or 64 bit of LabVIEW, and since it is working fine with the 32-bist version, I do not know what is wrong. 

 

I am able to open the VI in question without any problems.

0 Kudos
Message 7 of 10
(4,106 Views)
The driver has 32 and 64 bit versions for Windows. Attach the VI you are trying to call.
0 Kudos
Message 8 of 10
(4,095 Views)

My apologies.  The error message you posted (if I read it carefully) says the error is coming from PCBinaryTwoChannelF1.  Please attach that VI so we can take a look at it.  Can you try running it in isolation on your 64-bit system (you may need to wire in suitable constants)?  Can it run?

 

Bob Schor

Message 9 of 10
(4,082 Views)

It turn out that the VI had DAQ Assistant express VI, which was, for the 64-bit version of LV, missing. So I reinstalled the DAQmx driver using the latest version available and the problem was solved.

0 Kudos
Message 10 of 10
(4,057 Views)