Running Multisim with Labview

Hey,
  I am trying to convert a series of student labs for a dynamic systems course to run on a newer, better setup.  Previously, the lab I am working on took input from a sensor, fed that input through an analog circuit, and fed the output from that circuit into a Labview VI.  My question is, can that be done using a Multisim simulation instead of a physical circuit?  I have found volumes regarding running Labview VIs in Multisim, but nothing regarding a VI taking input from a Multisim circuit.  If this can be done, what configuration would you suggest?

bjw5,
It is likely due to the fact that some of the vi.lib or DAQ driver libraries that you need to link into the VI are missing in the build of your Multisim LabVIEW .llb.   If Multisim cannot locate missing subVIs (from vi.lib or elsewhere) Multisim will not load the LabVIEW VIs that you have built.   Sometimes you need to include these vi.lib subVIs (usually contained in a LabVIEW library - lvlib) in the project build (by default all vi.lib functions are excluded).   When Multisim loads, it loads in the appropriate base level LabVIEW functionality only - this includes most LabVIEW functions, basic math, etc - however any advanced measurments or additional toolkits or drivers need to be included in the .llb build or the support folder directly.
How do you know?  In your LabVIEW project, if you click on the 'Dependencies' +/- twisty you will see any subVIs or .lvlibs which contain subVIs that may be used in your Multisim VI application ...
Here is a sampling of a recent project that I used that included some advanced measurement VIs in LabVIEW.   I believe the only ones included by default in Multisim are the 'Base' lvlibs (which does include most of the LV functionality, but for my application advanced measurements were needed). 
If you DO have any that say 'Pro' in the name or any hardware driver level functions or subVIs, you'll need to do one of two things:
1. Easiest method - Include all vi.libs in the Source Distribution under 'Additional Preferences'
Basically change this ....
to this...
Note that it will take some additional time to build (since when LabVIEW builds your llb it will search all of the lvlibs for VIs that it thinks are in your application and then remove the ones that are not)... but your VI should then run in Multisim...
2.   Advanced method -> explicitly add the subVIs or lvlibs to the top level project and make them 'always included' in the Source Distribution 'Source Files' options.
Here you can explicitely call the lvlibs to be included in your build and then take out functions you don't need (but you may not know what subVIs are used if they are embedded in lvlibs that you're not aware you are using (such as the case with Express VIs) ).   You also have to be careful since I have found out the hard way that menus within the lvlibs cannot be included in .llbs, so you have to exclude any menus folders within the lvlibs (you can include/exclude pieces of lvlibs by the way)...   Sometimes this can reduce the build time, but it can be a little trickier since you need to know which things to include/exclude.   If you are just beginning, use method #1 at first.
Ok thats they way it is with most Multisim VIs that I am familiar with but there may be some things that I am missing because you are using myDAQ...   I've requested that someone familiar with the myDAQ products on the academic team also reply to this thread. 
Hope this helps and good luck!
Regards,
Pat Noonan

Similar Messages

  • Unable to run vi with labview run time engine

    Hi All,
    I have a VI that controls and reads from an NI PXI Spectrum Analyser (5600). The VI works perfectly as expected, I can make a project of it and create a runtime application and installation with no problems, using Labview 8.6.
    When I make a call to it from Test Stand 4.1 it works lovely.
    When I change the VI adaptor in Test Stand 4.1 from development to use the LV Run Time engine 8.6 it fails to work, Test Stand gives the following dialogue (see attached).
    I have uninstalled all older versions of Labview as I've had similair issues before, I've mass compiled everything I think is associated with this VI.
    I don't really understand! And am tearing my hair out.
    The only idea I have is that perhaps there is something in one of the 5 DLLs that is causing a problem or the NI_AALBase.lvlib, NIAALPro.lvlib or NI_PtbyPt.lvlib librarys that are password locked and I presume don't get mass compiled.
    I have attached the problemVI.lvproj.
    Thanks for any advice or help.
    Matt
    Attachments:
    problem VI.lvproj ‏41 KB
    teststand.JPG ‏43 KB

    Matt,
    it sounds like you are having older versions of toolkit/driver VIs in your application. In developement environment, this works since the dev-system is capable to recompile older VIs just during loading and therefor not having issues with older versions.
    Running the VIs using the Runtime Engine, recompilation is not possible. Because every VI knows "its version", the VI will not be executable unless the RTE version matches the VI's. If the VI is older (or newer, doesn't matter), the observed error occurs.
    Please make sure that you have current versions of drivers and toolkits installed in your LV environment instead of simply copy them from older versions of LV (this would be the common source for such issues).
    hope this helps,
    Norbert 
    CEO: What exactly is stopping us from doing this?
    Expert: Geometry
    Marketing Manager: Just ignore it.

  • Open and close multisim contact with LabVIEW

    Can I open and close multisim contact with labview and read the receptor estatus (p.e. lamp)?
    Thanks.
    Attachments:
    Dibujo.JPG ‏13 KB

    Hi Guddan,
    I created a RFC having a query which is taking a long time to execute. So i want to close RFC connection with portals which is via java connector(JCO) before that query and open the connction again after that query.
    I guess i will need to understand your requirement a little more in detail, as i understand you have an RFC which has a query within to fetch some data and is taking a long time to do so. In the meantime you don't want to keep the connection open?
    My question would be, Is the role of this RFC to only execute the query and fetch the data or does it do something else?
    If it does other things and these are independent of the query execution, then you can span a parallel call within the RFC to execute the query and in the meantime the RFC does the other things (or vice versa) hence reducing the overall time taken.
    If the sole purpose of this RFC is to execute the query, then you will not be able(i mean to say there is no simple and direct way of doing this) to close the connection after the Query is started and re-establish the connection after its execution, for a simple reason that - how will you know if the query has completed it's execution, so that you can establish the connection back.
    Alternate solutions, make this a two way asynchronous call, 1) You invoke the RFC asynchronously and close the connection, the RFC in turn will execute the query and transfer the data to JCO via another RFC call.
    If this needs to be a synchronous call, then you will need to optimize the query to its best.
    Regards,
    Chen

  • Calling a VI which uses "system exec.vi" with LabVIEW run-time engine as adapter

    Hi,
    My TestStand sequence calls a VI which includes a call to "system exec.vi". When I try to load it in TestStand and if LabVIEW adapter is set to run-time engine, I get an error message "Unable to load Vi...". If I switch the adapter to "Development system", then it works fine.
    Is there any way to use "system exec.vi" in a VI which is called in TestStand with LabVIEW run-time ?
    Thanks,
    Alex
    Solved!
    Go to Solution.

    Hi Alex,
    In you case, you are getting a -18002 error.
    The reason is explained in the following link:
    -18002 Errors in TestStand
    http://digital.ni.com/public.nsf/allkb/D82FEAF0B4BA293A862575710053E252?OpenDocument
    Please have a look at the 2nd reason. This is your case.
    Hope it helps,
    Regrads
    Julien De Freitas / Applications Engineer / Certified LabVIEW Developer (CLD)
    National Instruments Switzerland

  • Labview 8.5.1's MathScript window failed running imread with an error "A problem occurred in a subVI call."

    Hi,
    I am trying to port a Matlab program into a MathScript script.  Following is the first few lines of the script:
    clear;
    image1=imread('C:\LV_VertAlign\DSC_0104.jpg','jpg');
    image_double1=im2double(image1);
    image_gray11=rgb2gray(image_double1);
    In the first line, imread is supposed to read in a photo taken from a DSLR camera, so I think it's a 32-bit image.  And this is the error I got when trying to run this script in the Labview 8.5.1's Mathscript windows:
    "Error in function imread at line 2.  A problem occurred in a subVI call."
    What is the problem here?  and why does it complain about a subVI call?
    Thanks for any help to point me in the right direction.
    -Anh

    Hello Anh,
    As you may know, LabVIEW MathScript is implemented on top of LabVIEW.  The error message you received indicates that a problem occurred in one of the LabVIEW subVIs that MathScript calls.  As Jim indicated, the problem is in the file type specifier you passed to the function.  MathScript requires the use of 'JPEG' and not 'jpg' or even 'jpeg.'  In this case, we could return a better error message.  I have filed a bug report (115804) for this issue.
    You will find that once you fix this, the im2double and rgb2gray functions are not supported.  In LabVIEW MathScript, you generally can execute scripts written in the MATLAB® language syntax.  However, the MathScript engine executes the scripts, and the MathScript engine does not support some functions that the MATLAB software supports.
    We will look into adding these functions in a future release of LabVIEW MathScript.  If you need this functionality now, these functions are very simple to write yourself.  If you are performing additional image analysis in your script, you may wish to purchase the IMAQ toolkit.  It doesn't add any functions to MathScript at this time, but you could continue your analysis outside of MathScript with LabVIEW VIs.
    MATLAB® is a registered trademark of The MathWorks, Inc.
    Grant M.
    Staff Software Engineer | LabVIEW Math & Signal Processing | National Instruments

  • How to run Speedy 33 with labVIEW 8.5 core software, Please send procedure.

    Dear Sir
                 Wish u Happy New year (2010). I need a technical support for Speedy33. We have purchased NI speedy 33 h/w setup on 5/11/2008 from Tridet Techlabs Pvt. Ltd. Now we have got new(virtual Instrumentation) lab. when we purchased NI speedy 33 we have got only installation guide with the h/w. we want to run speedy33 with core s/w(LabVIEW8.5.1). So we kindly request you send procedure for running & working with speedy 33 using core module. 
    Thanking you
    S. Antony Jesudurai
    Lecturer, ICE Dept,.
    Dr. Mahalingam College of engineering & technology,
    Pollachi.
    TamilNadu
    India.

    Happy New Year to you as well Dr. Mahalingam!
         This forum is a predominently user supported one, although National Instruments monitors it and supports questions when they can, but it isn't an "official" communications pathway to National Instruments. To assure a response I would suggest contacting your nearest National Instruments representative in India, they probably can get you the info you need.
    That having been said, while I don't have the info, another user may be able to assist you. As this is the beginning of a long holiday weekend, with many people taking today off, if you haven't seen a reply by Monday the 4th post a simple query to this thread to pop it back up on the "new question" area. As new questions come in, the older ones scroll down, until they are on an previous page, where they tend to get missed.
    Putnam
    Certified LabVIEW Developer
    Senior Test Engineer
    Currently using LV 6.1-LabVIEW 2012, RT8.5
    LabVIEW Champion

  • Error -18004 with LabVIEW Adapter using LabVIEW Run Time Engine 7.1.1

    Hi to all,
    I am trying to use the LabVIEW Run Time Engine 7.1.1 instead of the Development System for executing VIs in TestStand with the LabVIEW adapter.
    The Problem is that I get the following error, saying that my VIs cannot be executed:
    -18004; An error occurred accessing the LabVIEW Run-Time Engine DLL.
    All my VIs were masscompiled with LabVIEW 7.1.1
    How do I manage this problem, in other words how do I get my VIs in TestStand to run with the LV Run Time Engine?
    Thanks for you help,
    - Caribe -
    PS: I configured the adapter to use the  LabVIEW Run Time Engine 7.1.1. When I check back in the dialog "LabVIEW Adapter Configuration" the selector went back to LV Runtime 7.1??? Thats weird dude!

    Hi Caribe,
    Did you find any solution to this weird behaviour? Even I am facing the same problem! If we set the adapter as LV 7.1.1 runtime engine, it changes back to LV 7.1 runtime engine.
    I am also facing -18002 error after mass compiling LV 7.1 folder and my source code folder.
    If you can share your solution, that would be of great help to me. If i couldnt find any solution, I have planned to revert back to LV 7.1 version.
     Thank you,
    Sasi

  • With Labview what do I need to run vi's on computers without Labview installed

    With Labview, how can I install my VI's on another computer to run them with runtime eng. Do I need additional software or ?

    On your development computer, click on Tools -> Build Application or Shared DLLs. Select Application and fill in the rest of the boxes with proper information (click Help button for more info). When all info is correctly filled, click on Build button. This will create an EXE file. On the other computer, install the Labview runtime engine. You can do this by using your regular Labview developer CD. Run the setup program but, when prompted for items to install, uncheck everything except the runtime engine box. Proceed with setup. This will install only the runtime engine on your target computer. Transfer your EXE file to the target computer. Run the EXE file, it should work.
    - tbob
    Inventor of the WORM Global

  • Labview 7.0 is compatable with Labview Imaq6.1 , vision builder 6.0 and Imaq run time engine 6.0.

    Sir,
    My system is PXI 8174 and i an using NI 1411 card for my application. I want to know the compatability of the softwares. Whether Labview 7 is compatable with Labview Imaq 6.1 , vision builder 6.0 and Imaq run time engine 6.0.

    Hi,
    Assuming you meant IMAQ Vision 6.1 instead of IMAC 6.1, this software was intended to run on LabVIEW 5.1, 6.0, and 6.1.  I have heard of it being used with LabVIEW 7 on occasion, so it may be possible to make it work, but this has not been tested and is not officially supported.  Vision Builder 6.0 should run; however, it was developed long before LabVIEW 7.x and will not generated code for LabVIEW 7.0 and later.  The Vision RTE version should correspond to the version of Vision you are using.  For instance, if the program was developed with Vision 6.1, the computer should have the Vision 6.1 RTE installed.  With this being said, if you plan to use LabVIEW 7, I recommend updating your other software.
    Regards,
    Ryan M.
    Applications Engineer

  • Running NI I/O Trace with Labview

    Hi All,
        So I've been having a problem with labview for a while now. It keeps crashing randomly and unpredictably. I posted on this forum in the past and someone suggested running an NI I/O trace. I went ahead and did that and I have received an error message. After running some 2000 processes I got a red line containing the below data.
    > 2788. GPIB Wait (19, 4294967295, 37236)
    > Process ID: 0x0000029C Thread ID: 0x00000238
    > Start Time: 09:49:09.947 Call Duration 00:00:00.799
    > Status: 28 (0x1C)
    I understand most of it but I don't know what status 28 means. This is the obvious standout as every other event returned status 0. Does anybody know what this means and if so how can I rectify the problem.
    Thanks for your help!

    So the definition of the status is: This column displays each API call's output status value. (For calls made to the NI-488.2 API, this is equivalent to ibsta.) More info here. If this is the value returned from the operation, I would assume is the time is waiting. Could be a timeout?
    Alejandro | Academic Program Engineer | National Instruments

  • I created an application on a machine with Labview 6.01, can I run this application on another machine that has labview 5?

    In the development center we use Labview 6.01, in the testcenter we use labview 5.
    Additionally, in the development center we use a unix version of Labview and in the testcenter a Windows version.

    You can Save with Option to save VIs as version 5.
    Unless your VIs deal with system files in UNIX or Windows (ie. Registry...)
    then you have to develop your VI specificly on that OS, since UNIX and
    Windows have different ways to deal with system files. Mostly, LabVIEW is OS
    independent. I used to have VIs developed from LabVIEW v.3 on UNIX, I can
    still open these files from LV v.4 on Windows. Now I can still work with
    these VIs on LV 6 on Windows.
    Good luck,
    Nam.
    roybra wrote in message
    news:[email protected]..
    > I created an application on a machine with Labview 6.01, can I run
    > this application on another machine that has labview 5?
    >
    > In the development center we use Labview 6.01, in the testcenter we
    > use l
    abview 5.
    >
    > Additionally, in the development center we use a unix version of
    > Labview and in the testcenter a Windows version.

  • Running 2 stepper motors with LabVIEW using RMV ST400-NT controller and driver

    Hello, I am new to programming as well as motors in general so please bare with me in my attempt to explain myself. I have a project involving laser therapy and I am attempting to control two stepper motors from Falhauber, Type AM2224-R3-AV-4.8. I will be using a RMV ST400-NT controller and driver. Original plan was to use 3 stepper motors for control in 3 axis but realized 2 axis is complicated enough. My power source is an Agilent E3630A. I am new to this whole thing and from what I have read form examples and other posts is that NI drivers seem to work best for these applications. I've written simple programs from examples, reading and watching videos. I want to know whether it's possible for these to work together using LabVIEW and also a nudge to help me get started would be much appreciated. Can someone please help guide me in the right direction, I feel a bit lost when it comes to all this. Thank you for your time and consideration.  Also, I will be using Windows 8 laptop with Labview 8.5. I have attached pics of components I will be using.
    Justo T.
    Attachments:
    photo 1.JPG ‏1150 KB
    photo 2.JPG ‏987 KB
    photo 3.JPG ‏1085 KB

    Hi jtarula,
    I want to preface this response by saying that I am mre familiar with NI controller and driver rather than the one that you have. I am assuming that you are using the dll provided by the manufacturer here:
    http://www.rmv.com/download.htm
    With these, you should be able to interface with LabVIEW using the call library function node. What the controller is capable I am uncertain of. I am certain that you should be able to since another user has commented on the use in LabVIEW before in another forum post.
    I also want to let you know that LabVIEW 8.5 is not supported on Windows 8, which means that you may run into some compatibility issues. Here is the compatibility chart.
    Paolo F.
    National Instruments
    Applications Engineer

  • Excel with Labview 6?

    I'm trying to get Excel '97 to work with Labview 6.02, but I'm always receiving error message: -2147319784: "old format or invalid type library". I modified windows registry as told in LV knowledgebase. After that I could see Excel components in ActiveX pull down menus. I have tried to run demos such as "Open Excel And Make visible.vi" but they always output the error message. I have tried this with both Windows 2000 and NT. Other programmes, for instance MS Access, seem to work fine. What is the catch?

    Anders,
    You have run into a special case of the problem that actually has a work around for it. However, you will have to contact LabVIEW technical support to obtain the temporary fix since they need to keep track of all the people with this special case.

  • Is it possible to view VIs remotely on windows 7 if VI was built with LabView 8.2?

    So I know i'm probably dealing with software compatibility issues here, BUT, I wanted to make sure every option was exhausted before considering the idea of upgrades.  
    Im using LabView full development system 8.2 on windows XP 32bit os.  Currently, I run into no issues when controling or building VIs on my computer.  Problems do occur when trying to control VIs on a remote computer with windows 7. That computer has run-time 8.2.1 installed on it.  For the most part it works best to just view the VIs, and not interact or control too much.  More specifically, the VI will freeze once interacting with a control that is intended to pop up a two button dialogue box.  I'm sure there are a lot more issues with using run-time 8.2.1 on a windows 7 computer; that one in particular is just the only one i've experienced.  
    In all efforts to avoid what could eventually be an unavoidable situation where an upgrade is necessary, is there a way to remotely control (on windows 7) a VI front panel that was built with labview 8.2?

    Thank you for the response.  Just to preface, I am fairly new to LabView so pardon my potentially "stupid" questions.  Here's my process in a nut shell:  VI programs are created on our server computer and then published for web with the "web publishing tool...".  The html page created is then put on a main page with all other created VIs and are then viewed on other computers that are part of the network via ip address.  
    I was under the impression the LabView run-time engine enabled remote computers to view and control these VIs.  Could be wrong?  After downloading and installing run-time 8.2.1 (since vi's were created with labview 8.2), those computers are able to enter the ip address and navigate to the main page to control the web published vi's.  The issue is with the computer that has windows 7.  I know run-time 8.2.1 isn't necessarily compatible with windows 7, but it does seem to run the vi on a pretty minimal level.  I run into problems on that computer when hitting particular controls that are wired to be more complex than just a simple boolean.
    Just to provide a visual, I attached an image of one of the scenarios where it will freeze up on the windows 7 computer.  This is how the VI should normally function; however, before the dialogue box even pops up after clicking a valve control, it freezes.  
    I didn't even consider VNC or Remote Desktop up to this point.  Thank you for that idea.  I'll definitely look into that as an alternative.

  • Need instructions on how to get Quanser working with LabView 7.1

    I need information on what LabView modules or addins to install in order to run Quanser (QNET Experiments release 2.2).  LabView 7.1 is loaded but we also have LabView 7.0 if needed.

    Hello JND,
    The Quanser website indicates that the QNET products are fully
    compatible with LabVIEW and NI Elvis. However, I could not find more
    information on any drivers they provide for LabVIEW, so I suggest you
    contact them directly about this. If they have drivers written for
    LabVIEW, that should be enough to communicate with the board from
    LabVIEW. In order to communicate to NI Elvis, you need to install
    NI-DAQmx and NI ELVIS drivers available at this page.
    Good luck and best regards,
    Shakhina P.
    Applications Engineer
    National Instruments

Maybe you are looking for