Yeah, sorry. I did write up a description for this problem, but between pressing the 'post' button and it going on the forum, the text must have disappeared.
I am running a simple signal recording VI using a PCI card. It reads in ECG and Blood pressure waveforms, displays them, and does inline signal processing to measure the time between beats identified on ECG and Blood Pressure traces, and displays statistical information about this. The software was originally written for Labview 7.1 with NI-DAQ 7.2.2(traditional) Analogue Input routines, and I am attempting to deploy the software in other research labs. All of the signal processing is done in several Matlab Scripts
I have tested the original software using Labview 7.1/NI-DAQ 7.2.2 and Matlab 6.5, and I have also updated the IO routines to use DAQmx routines in Labview 8.6 with NI-DAQmx 9.1.7 and Matlab R2010b and tested that.
What I have been finding is that I can get the updated version to run in Labview 8.6 environment, but when I build an executable application and run it in the same environment, I get error 1048 'failed to get variable from script' every time a subVI with a Matlab script runs. I am confused as to why this would occur, because if the code executes, shouldn't the executable perform in exactly the same manner? This error was also happening if I installed only Labview 7.1/Ni-DAQ 7.2.2 and ran the original executables that were developed in Labview 7.1.
Since the time I originally attempted to post this thread, I have made some progress. To work around this problem, I took the code that was in the subVIs (they were just matlab scripts, with no Labview code other than controls/indicators) and placed it directly in the main VI code. This seemed to solve the issue, and I was able to run the executable with no Matlab errors. This works ok, but makes the code less readable, which is only a minor concern. However I am just wondering what could have caused this error.
