09-27-2015 09:51 AM
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.
Solved! Go to Solution.
09-27-2015 09:57 AM
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
09-27-2015 10:07 AM
Here is a picture:
09-27-2015 11:36 AM
09-27-2015 11:48 AM
09-27-2015 12:07 PM
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
09-27-2015 04:22 PM - edited 09-27-2015 04:25 PM
Here is a snippet:
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.
09-27-2015 04:52 PM
09-27-2015 05:06 PM
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
09-27-2015 07:22 PM
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.