@JoseRivero wrote:
Hi Rolfk,
Thanks for the quick reply. Would it be correct to assume that if I keep the current LabVIEW libraries created when the library wizard was used, and I install the Matlab Development in the PC where this code is ultimately going to run, this problem will go away, or would it persist regardless?
Not likely. Unless you execute the analysis function inside the Matlab environment and just call it remotely for instance through the Matlab script node. If you build the Matlab library into a DLL/shared library each of them will try to initialize the Matlab runtime and that does not work as you have seen.