Calling Matlab 7.1 from LabView 6.1

Hello,
I am using LabView 6.1 and I have recently installed Matlab 7.1 on the same machine.
When I try to call Matlab by a Matlab script node, I only get the error
message that the script could not be executed and that a failure
occured calling the script server. (This does not depend on what script
I implement.)
Earlier, I had Matlab 6.5 which worked well with the script nodes.
What can I do to get the script nodes running?

Hello ffffff 
I can pretty much assure you that LabVIEW 6.1 has not been tested with MATLAB 7.1, and "officially" I might go so far as to say it's not supported.
That said, you might try downloading the MATLAB Script.zip file attached to this KnowledgeBase entry:
http://digital.ni.com/public.nsf/allkb/4475BC3CEB062C9586256D750058F14B
Follow the directions in the KB to update the matscript.dll file in your LabVIEW 6.1 distribution, and this might resolve the issue.  This addressed numerous issues with the MATLAB script node so that version 7.0 of MATLAB would work well with LabVIEW.  I'm not sure if this version of the matscript.dll has been tested with LabVIEW 6.1 or not, but in theory it should work.  Also, if the problems you are encountering are new to MATLAB 7.1 in specific, there may not yet be a solution for this; I don't know how new MATLAB 7.1 is.
Good luck!
Message Edited by Jeff B on 02-16-2006 07:44 AM

Similar Messages

  • Calling matlab 6.0 from labview

    I need know how to start Matlab 6.0 from Labview, and I will need to pass strings of script commands (for example, a=10;b=5;c=b/a;disp(c)) to Matlab to be executed. And Labview will need to get the result (value of c) back. Thanks for all the help!

    You can use the matlab script funtion under Functions»Mathematics»Formula»MATLAB Script
    Also you can find the matlab script examples in the examples»communication»Importing MATLAB Script.
    I hope this helps... Have fun
    Ogulcan

  • Error 1050, when calling MATLAB 7.1 from LV8.0 - Function Definitions not allowed.

    I am trying to call a MATLAB M-file from LabVIEW 8.0. I keep getting Error Code 1050:
    "Error 1050 occurred at LabVIEW:  Error occurred while executing script. Error message from server: ??? Error: Function definitions are not permitted at the prompt or in scripts.
    . in rickfito.vi->impedo.vi
    Possible reason(s):
    LabVIEW:  Error occurred while executing script"
    I tried running the sample MATLAB script example on the knowledge base, and everything works fine.
    I am guessing that this error is happening because I have functions defined in the MATLAB script. But i thought this is better programming techinque. Also, the MATLAB window opens up when I start the VI.
    Is there a way around this? I really do not want to remove the function definitions on the script.
    Thx,
    Pelo...

    First, see if the Matlab Script Node is trying to open any files. If
    so, then make sure that the current Matlab directory is set to the
    directory where that file is located. The Matlab script node in LabVIEW
    does call the Matlab script server and executes the function in the
    Matlab script node through Matlab. Therefore, even though LabVIEW may
    be in the correct directory where the file is located, make sure Matlab
    is as well.
    The error may also occur if there is a disruption
    in the script server between MATLAB and LabVIEW and the connection was
    never re-established (possibly by closing MATLAB prematurely). Close
    both LabVIEW and MATLAB then relaunch them both and run the VI.
    MATLAB®
    is a registered trademark of The MathWorks, Inc. Other product and
    company names listed are trademarks and trade names of their respective
    companies.
    -Bob
    -Bob

  • Calling Matlab MEX Files in LabView ?

    What is the procedure to call a MATLAB MEX File in Labview?

    Nope Battler.
    I didnt find any help regarding Matlab MEX DLLs on that link by Chris.
    I presume if they are keeping mum, there is no solution possibly.
    Btw, I migrated my testing from LV to MSVC.
    Its a lot more easier to call  Matlab MEX DLLs from MSVC.
    http://www.mathworks.com/support/tech-notes/1600/1605.html

  • I am using the NI application note "Calling IVI-COM drivers from LabVIEW" I created an Automation Open and an Invoke Node, after wiring

    the 2, the AN asked to right click the Invoke Node(this is step9) and choose initialize. However there is no intialize option on the pop up menu. Anything am I doing wrong? I am using Labview6 and I did add the "enableCustomInterface=True" in the INI-fileThank you for your help.
    T Tall

    the 2, the AN asked to right click the Invoke Node(this is step9) and choose initialize. However there is no intialize option on the pop up menu. Anything am I doing wrong? I am using Labview6 and I did add the "enableCustomInterface=True" in the INI-fileT Tall,
    What's the number of the application note "Calling IVI-COM drivers from LabVIEW"? I'm unable to find what you're looking at.
    Thanks,
    --Bankim

  • How can i call a DLL file from labview?

    Iam using a sensoray 2601 module.It is given as DLL file(S2600.DLL).How can i call this function from LabVIEW?
    Please Mark the solution as accepted if your problem is solved and donate kudoes

    As far as I can tell problems might occur with the call library function node if the the DLL from visual basic is actually an ActiveX dll if that is the case it seems calling the dll by using the Invoke node is the way to go.
    Have a look at this 
    /sletten

  • When calling Excel 97 Macro from Labview 5.1, get error: cant find macro!

    I have a macro written that I am trying to call from Labview. To assist in this task I downloaded an Excel Macro VI off the NI Websight. The VI came with an excel workbook that included a sample macro. I can run the example with no problems. I then modified the VI to fit what I am trying to do. I can get it to work with the Sample excel macro but not the one I created (I get an error saying it can't find the Macro). I have played with the timing and that has not worked. I have also noticed that when I use the sample Macro, it will work fine for a while then after a random number of executions, it will stop working and I will get the same error as with my Macro. In order to get it working ag
    ain, I have to remove the sample worksheet (macro) and replace it with the original copy. I have been pulling my hair out for a couple of days now with this one so any help would be greatly appreciated!

    I am not sure what the problem could be. The VI you speak of can be found at the following link:
    http://zone.ni.com/devzone/explprog.nsf/6c163603265406328625682a006ed37d/190d1f351297ef9a862567740073e2bc?OpenDocument
    I ran the program for excel 2000 on my LabVIEW 6.1 about 50 times and did not get the error you reported. Your macro should not be corrupted with use. Have you considered reinstalling excel? I liked the idea about turning off multithreading. Do you see the same behavior if you run in high light execution mode?
    Jeremy Braden
    National Instruments

  • Matlab script launched from labview

    Hi everyone,
    I need to run a matlab script controlling a network analizer from labview. I use labview to start the movement of the motors in some experiment. Then, once the movement starts, matlab should run a script to perform adquisition and treatment of the data. Could anyone give me some trick of how to launch the matlab script?
    Best

    Here is a link that looks to describe what you are asking
    http://zone.ni.com/reference/en-XX/help/371361J-01/lvhowto/creating_a_matlab_script/
    Hope that helps.

  • Closing a Matlab model window from Labview

    Hi,
    I use Labview with the Simulation Interface Toolkit to control a simulation system from Labview. I need to change the Simulink model dynamically from Labview when the users choose a given option (I directly replace code snippets in the .mdl file). In order to do this, I need to close the model window in Matlab from Labview and reload it when the modification is done.
    Any idea?
    Thanks,
    Alex

    Greetings!
       Thanks for the request. Re-launching the model is required after
    every change. The connection manager retains the information and uses it in re-launch.
    Please refer to Page 16 of the simulation interface toolkit. You can submit a
    product suggestion in our product suggestion page. Also I am sure you would
    know the following -
    You could build the model into a DLL for stand-alone simulation. You need
    MATLAB, Simulink, and Real-Time Workshop to build a model DLL and configure the
    user interface using the SIT Connection Manager Dialog box. Once you create the
    model DLL and user interface, you need only LabVIEW to run the simulation.
    Thanks and hope this helps. Good luck
    Avi

  • Calling 64-bit dll from labview 8.2 on Windows7

    Hello,
    I have tried the LABview driver from the OMNIDRIVER (OceanOptics) package. But when calling functions from the “OmniDriver32.dll” , LABView is crashing and  says that the memory is corrupted.
    I am using LABVIEW 8.2 (32-bit) running on Windows 7 (64-bit).  I have tried some LABView code examples given for LABview 7.1 and 8.0. These example are using the OmniDriver32.dll (not the OmniDriver64.dll).
    But maybe these example are assuming that you are on a 32-bit operating system, which is not my case.
    So I have tried calling the OmniDriver64.dll. but LABView seems not to recognised the dll and can’t read the included functions.
    Is there a way to call some 64-bit dll from LABview 8.2 ?
    Or do I need to buy a new license for LABVIEW 64-bit ?
    Thanks,
    Pierre

    There is no virtualization support for DLL bitness issues outside of the Windows standard directories. The Windows and System directories that an application "sees" depends on its bitness. All other directories are not mapped depending on the calling process' bitness.
    So if you have installed 32 Bit LabVIEW and are not calling one of the system DLLs, you have to point the path of the DLL to the real 32 bit DLL. Pointing it to a 64 bit DLL should not even be able to get the VI compilable, since Windows will refuse to load the DLL into the 32 bit process as being an unknown file format, and that should make the VI broken.
    If you need to call a system DLL you simply enter the DLL name without path and Windows will find the according DLL for LabVIEW.
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • Calling executable file generated from labview in C++

    Hi,
    I am new to LabVIEW. I have to call an executable file  from C++ in a system where LabVIEW is not installed and Run Time Engine is installed. Can anyone please guide me with it. Thanks in advance.

    If it's just an executable (.exe) and you have the Runtime Engine installed, why not just launch the executable from your C++ application? I think it's something like CreateProcess() (You'll have to look up the details as I'm a LabVIEW not a C++ programmer!).
    Certified LabVIEW Architect, Certified TestStand Developer
    NI Days (and A&DF): 2010, 2011, 2013, 2014
    NI Week: 2012, 2014
    Knowledgeable in all things Giant Tetris and WebSockets

  • Calling third party software from LabVIEW

    Hi All,
    In one of the requirement, I need to open the Debugger(AXD debugger) then needs to send some commands from it.
    Is it possible to invoke debugger from LabVIEW and work on specific text boxes in the debugger.
    Details : APIs or DLLs related to debugger are not exposed to outside world.
    I am using teststand3.1 software as manangement tool.
    AXD debugger runs on Windows.
    Is any body come across similar type of issue ?,,Please suggest me the way to wokr on it.
    Regards,
    KHN

    If you cross post to multiple forums, please provide a link to your other posts.

  • How to call a Linux exe from LabVIEW for Windows

    Hello,
    I need to call a non-LabVIEW Linux executable using LabVIEW for Windows. Any suggestions, aside from buying LabVIEW for Linux?
    Thank you,
    Chris White

    Okay, I'll throw out a few ideas and I'll let you pick which one you may think is easiest.
    1. Use the internet toolkit ($$$) or build a simple telnet client yourself in LabVIEW (use the TCP VIs in labview). This would allow you to connect to the telnet port of your linux box, login, password, and execute a command. (You'll probably want to use nohup, do a man on nohup to find out more).
    2. Install SSH daemon on your linux box, and an ssh client on your windows machine. You can't get SSH for windows from cygwin. This would be more secure, and you wouldn't need to use the TCP VIs, you could simply use the "system exec" vi to call SSH.
    3. On your linux box, install your app in inetd. Then, whenever someone connected to a certai
    n port # on the linux box, it would execute your command. A little dangerous because someone might try to connect 50 million times (or a port scan) and kill your box. You also wouldn't be able to send a dynamic command line argument.
    4. Write a small TCP application on your linux box to wait for connections (listen for command line options) and execute your command.
    You'll probably find one of these options ideal depending on your administration and programming background.

  • When I call an external program from Labview, how can I embed the interface into the front panel?

    I'm running Labiew 6i for Linux. I'm using a system exec.vi to call an external program to do image manipulation (since there is no IMAQ for linux). How can I embed the user interface of the external program into the front panel of Labview?

    As far as I know, the only way to embed other GUIs in LabView is an ActiveX in a container.
    As long as you are using Linux, try to place (moving them on the desktop ) the two windows linked (like those 3 of WinAmp).

  • Input parameter setting when calling a DLL(Built from LabVIEW and a kind of VISA communication driver) in Teststand.

    In labVIEW7.1 I wrote a COM port communications driver by using "VISA Write/Read". I put a string as the input of "VISA Write" and made it the input of the whole vi. Then I converted the vi into a DLL, which is called in Teststand3.1 by specifying DLL adapter. In "Edit C/C++ DLL Call" dialog, I pass a message of "60 6A 94 80 86 81" as the input parameter. My problem is I tried three kinds of methods to pass the message, see attached 1.jpg,2.jpg and 3.jpg. and found the first one sometimes doesn't work, the second work fine and the last doesn't work all time. I don't know why the first one and last one don't work well.
    Thanks!
    Jacky
    Attachments:
    31.jpg ‏38 KB
    11.jpg ‏36 KB
    21.jpg ‏49 KB

    Hi Srinivas,
    Just another note, I noticed that the Math Interface Toolkit version (MIT) 1.0 is not compatible with LabVIEW 7.1. You’ll need version 1.0.1. of the MIT toolkit in order for it to work with LabVIEW 7.1.
    The LabVIEW 7.0 lvanlys.dll is also attached. I had to rename it with a .txt extension, so you’ll want to delete the extension.
    Kileen
    Attachments:
    lvanlys.dll.txt ‏516 KB

Maybe you are looking for