08-03-2023 03:17 PM
I've seen Matlab do some pretty cool stuff and I was wondering just what kind of limitations are there with LabVIEW trying to run various Matlab scripts? If Matlab requires packages to be downloaded - will that mean those Matlab scripts are not going to work in LabVIEW? How does all this play out if you make an executable? Does anything need to be included when building the application? Anyone got more advanced experience with this? I feel like what I'm quickly finding online is a = 2+2 and you get a double called a for an output.
08-03-2023 03:59 PM
How Can I Call a .m Script in LabVIEW?
Calling the MATLAB® Software from LabVIEW
You must have a licensed copy of the MATLAB® software version 6.5 or later installed to use MATLAB script nodes because the script nodes invoke the MATLAB software script server to execute scripts written in the MATLAB language syntax.
If you use the legacy Mathscript Node, you cannot run the function from the toolboxes. How Can I Run a MathWorks, Inc. MATLAB® Script That Uses MATLAB® Toolboxes in LabVIEW?
You can also compile the Matlab function into a .NET assembly using Matlab Coder. Integrating Compiled MATLAB Functions with LabVIEW with a .NET Assembly Approach
08-03-2023 04:06 PM
Since you already accomplished cool stuff with MATLAB, why do you need to add another layer to wrap them in LabVIEW?
08-03-2023 04:12 PM
@santo_13 wrote:
Since you already accomplished cool stuff with MATLAB, why do you need to add another layer to wrap them in LabVIEW?
LabVIEW is the full automation tester. It's doing a bunch of stuff. But there's some stuff other people have already done in Matlab that we'd love to run in our LabVIEW automated system so as not to have to rewrite and thus fully utilize our team. Also I think it significantly simplifies pushing to all our test racks.
08-03-2023 08:12 PM
@LuminaryKnight wrote:
@santo_13 wrote:
Since you already accomplished cool stuff with MATLAB, why do you need to add another layer to wrap them in LabVIEW?
LabVIEW is the full automation tester. It's doing a bunch of stuff. But there's some stuff other people have already done in Matlab that we'd love to run in our LabVIEW automated system so as not to have to rewrite and thus fully utilize our team. Also I think it significantly simplifies pushing to all our test racks.
That sounds legit, there could be performance hit with the data transfer and handshaking between MATLAB and LabVIEW. It would be best to try Proof of Concept with a few MATLAB stuff and LabVIEW to see how much overhead is observed compared to plain MATLAB or plan LabVIEW implementation.