Labview IO instrument in Multisim 10.1?

Hello.. I'm trying to make a labview Input/Output instrument that will take an input, compare the input against a lookup table (preferably in a text file), and output the value that was looked up. I've been playing with the example labview IO template project that came with Multisim, and I am having trouble figuring out how it works. Can someone make an example that would, say, take the input, multiply it by two, and output that value just so I can see where in the block diagram the calculation is supposed to be done?
Thanks!
Mike

Mike,
What are your software versions? Depending on this you might need some additional files to assure the compatibility between LabVIEW and Multisim. Click here for more info.
Please let me know how it works.
Fernando D.
National Instruments

Similar Messages

Looking for a labview virtual instrument program we can modify

Hi, I’m looking for a canned labview virtual instrument program we can modify for the OMB DAQ 55 from Omega to measure three temps and control three DO. I have the driver at:ftp://ftp.omega.com/public/DASGroup/products/OMB-DAQ5455&56/ The driver is labviewpdaq5xsetup.exe. I have the OMB DAQ 55 from http://www.omega.com/pptst/OMB-Daq55.html with a USB interface. I am trying to set it up to control a 24V electric valve. I’d like it to measure temperatures (5 separate temps), allow a set point to be programmed for three of them and turn on and off a DO based on the temperature. PID is not required yet. Maybe in the future… We have labview 7.1 and 8.0 but my colleague prefers 7.1 Do you have an labview VI programs that you can share that will do this with the DAQ 55? If you have something that will be close, we can modify it. But starting from scratch will likely mean we can not get this done in time for a project test. Simple set point and control is all I’m looking for… I’m new (my colleague knows it better than me, but has less time) to labview and do not have the resources to learn it from scratch to figure this out. Is there something you have I could modify? Can you help. Or are there canned programs you have that will do this? Labview is the preferred language. Thanks. Attached is what Omega shared with us, it might help…it’s a screen capture from a similar program, but far from the mark.

Hi vestel,
These discussion forums are more geared for questions - not necessarily having everyone else code for you.
You have a few options if you want code.
1) Look at the shipping examples that come with LabVIEW. This will give you a starting point from which to ask questions.
2) Look at the Instrument Driver Network that exits on National Instrument's Web site. Here are all the Omega instrument drivers listed.
3) Look at the list of Alliance members who you can pay to develop your code for you. Look here.
I hope this helps,
Kevin S.
Applications Engineer
National Instruments

LabVIEW 2-output instrument into Multisim

Hi, buddys!
I'm trying to bring two waveforms into Multisim by means of project provided by Patrick Noonan here:
http://forums.ni.com/t5/Circuit-Design-Suite-Multisim/Create-a-LabVIEW-Based-Virtual-Instrument-for-...
I added in Patrick's Simple Output Instrument.vit another waveform and connected it to one more terminal added. The project builds and the new instrument adds to Multisim just fine.
The thing is that only one waveform is "working" while the other one (another output) is always zero in multisim. Though both are non-zero in correspondance with front panel.
How to make one more waveform "work"?
LabVIEW 2012
Multisim 12.0

Here they are (what is modified):

Custom Labview Instrument with Multisim

Hi,
I want to use a custom Labview Instrument (Phasor_Diagram) with Multisim 13.0:
http://www.ni.com/example/30200/en/
I copied Phasor_Diagram.llb and the folder Phasor to C:\Program Files\National Instruments\Circuit Design Suite 13.0\lvinstruments but
I can't find the Phasor Labview Instrument in my Multisim.
What is going wrong? How to get this work?
Regards Peter Stolz
Solved!
Go to Solution.

Hi Peter,
It looks that phasor instrument was built using an old LabVIEW version, I rebuit it in LabVIEW 2013.
Tien P.
National Instruments
Attachments:
Untitled Project 2.zip ‏1634 KB

Using the NI6551 Instrument in Multisim

I would like to use the Digital Waveform Generator. I have Student Version 11.0. I followed the below instructions.
Close NI Multisim if open.
Open the attached 5926_waveform_gen.zip file.
Select My Computer.
Browse to C:\Program Files\National Instruments\Circuit Design Suite 10.1\lvinstruments.
Save the NI655XGenerator.llb file from the zip file to this folder.
I don't have the same toolbar listed in this doc..
http://zone.ni.com/devzone/cda/epd/p/id/5926#toc1
Is this because I have the student versions of Multisim and Labview or am I just being obtuse?
Thanks for your help!

Hi,
If you click on the LabVIEW symbol on the toolbar in the right, you will see the LabVIEW instruments. Take a look at attached screen shot.
Regards,
Tayyab R,
National Instruments.
Attachments:
LabVIEW Instruments Toolbar.JPG ‏218 KB

Call LabVIEW Virtual Instrument through ActiveX Server from C/C++

I am trying to access a VI by C/C++ almost identical to the reference example that can be found on this site for Visual Basic. However, somehow, I am unable to succeed to use the ActiveX Call() function. The program always crashes, whatever I try. Because the Visual Basic version works without any problems, I hope someone can point me the error in the code.
Thanks!
#include "stdafx.h"
#import "LabVIEW.tlb"
#define VIPATH "D:\\Program Files\\National Instruments\\LabVIEW 7.0\\examples\\apps\\freqresp.llb\\Frequency Response.vi"
using namespace LabVIEW;
int _tmain(int argc, _TCHAR* argv[])
// Initialization
HRESULT he = NULL;
he = CoInitialize(NULL);
// Create instance of
labview application engine
_ApplicationPtr pLV;
he = pLV.CreateInstance("LabVIEW.Application");
// Create instance of virtual instrument
VirtualInstrumentPtr pVI;
he = pVI.CreateInstance("LabVIEW.VirtualInstrument"); /* ?not? mandatory */
// Get reference to a VI at location VIPATH
_bstr_t viPath(VIPATH);
_bstr_t password("");
VARIANT_BOOL resvForCall = FALSE;
long options = 0;
pVI = pLV->GetVIReference(viPath,password,resvForCall,options);
// Show front panel
pVI->FPWinOpen = TRUE;
// Call the referenced VI as subVI
_variant_t paramNames[5] = {"Amplitude", "Number of Steps", "Low Frequency", "High Frequency", "Response Graph"};
_variant_t paramVals[5] = {}; /* VT_EMPTY */
/* Fill ParamVals with values from VI */
for (int i = 0; i < 5; ++i) paramVals[i] = pVI->GetControlValue(paramNames[i].bstrVal);
/* Call VI -> !!! CRASH !!! :-( */
pVI->Call(paramNames,paramVals);
// Release references and close application
pLV->AutomaticC
lose = TRUE;
pVI.Release();
pLV.Release();
CoUninitialize();
return 0;

This may not be the easiest way. Although i have not used _variant_t. But it seems like your VARIANT type is VT_EMPTY for everything. You need to build up an array of variants with correct type, that matches the type of control you are assigning data to like VT_INT for int numeric, VT_BSTR for string control etc
VARIANT paramNamesVarArg, paramValuesVarArg;
SAFEARRAY *paramNames, *paramValues;
::VariantInit(&paramNamesVarArg);
paramNamesVarArg.vt = VT_ARRAY | VT_BYREF | VT_BSTR;
// create safearray of strings
SAFEARRAYBOUND rgsabound[1];
rgsabound[0].lLbound = 0;
rgsabound[0].cElements = 1;
paramNames = SafeArrayCreate(VT_BSTR, 1, rgsabound);
paramNamesVarArg.pparray = &paramNames;
long index = 0;
_bstr_t paramName = "Numeric";
BSTR *bstrVal;
retVal = SafeArrayPtrOfIndex(paramNames, &index, (void **)&bstrVal);
*bstrVal = paramName.copy();
//do the same method for paramValuesVarArg
::VariantInit(&paramValuesVarArg);
paramValuesVarArg.vt = VT_ARRAY | VT_BYREF | VT_I4;
rgsabound[0].lLbound = 0;
rgsabound[0].cElements = 1;
paramValues = SafeArrayCreate(VT_VARIANT, 1, rgsabound);
paramValuesVarArg.pparray = &paramValues;
VARIANT *dispVarVal;
VARIANT tempVar;
tempVar.vt = VT_I4;
retVal = SafeArrayPtrOfIndex(paramValues, &index, (void **)&dispVarVal);
*dispVarVal = tempVar;
viPtr->Call(&paramNamesVarArg, &paramValuesVarArg);
Hope it helps.
A Rafiq

Is it possible to convert a LabView .ldd Instrument Driver into a dll that can be used with MAX and visual basic?

I got the following problem. I'm using a Stanford DS360 UltraLow Destortion Function Generator, and would like to access it with the CwIVIFgen ActiveX Controll. In the driver database i found a instrument driver for LabView (ds360fg.llb). But its a llb file and i am not sure what to do.
Is it possible to convert it?
Is it possible to use it anyways?
Maybe i overread the answer, but i search the forums for quite a while now and i am not a bit wiser.
Thanks in advance
Felix

If you have LabVIEW and the application builder, a dll can be created from it but it cannot be used as an IVI driver. The only way to create an IVI instrument driver is with LabWindows/CVI. I personally don't have the time right now to create the dll but maybe if you post to the LabVIEW forum and get someone there to do it. Another other option is to hire an Alliance member to create either a dll from the LabVIEW code or to create an IVI driver from scratch.

LabVIEW Call Instrument VI

Hi,
Why I cannot use the Call Instrument VI from Labview 4.1 in the version 5.1?
The error is:
53
VI Server: Unsupported operation.
Thanks.
Denys

> Why I cannot use the Call Instrument VI from Labview 4.1 in the version 5.1?
> The error is:
> 53
> VI Server: Unsupported operation.
>
In LV5, many new capabilities were added to the VI Server. There are replacement
functions in your 5.1 vi.lib, and if you load your application with
references to
the old VIs from vi.lib, everything should map over to the new functions
automatically. If you have saved the vi.lib VIs with your source, then
I guess
that might cause a problem.
The best solution at some point will be to convert over to using the new functions
that are located in the palettes. They support property nodes and as I
said, have
lots of new functionality.
In the meantime, try loading the new VI then loading your application.
This will
automatically m
ove the calls over to the newer version. To do this,
make sure
nothing is open. Open the vi.lib/utility/victl.llb/Call Instrument.vi
file. Now
load your application. Assuming the name of the VI didn't change, your application
should have started using the correct replacement file. You may need to
do this
for other victl files that you are using.
Greg McKaskle

Labview et instruments de mesure Agilent

Salut !
Je travaille sous LabVIEW 8 et je pilote des instruments de mesures Agilent (DMM 34410A, générateur 33220A, oscillo DSO6012A et spectrum N1996A) connectés via LAN.
Y a-t-il des membres du forum qui travaillent avec ces équipements (ou proches) sous Labview ? Peut-être pourrions-nous échanger des actuces...
++
Julien

bonjour,
Je commande un GBF Agilent 33220A à l'aide de LabView et j'ai aussi des problèmes avec le close. Le VI "close" s'execute mais le GBF reste sous le control de Labview (impossible de reprendre le mode manuel sans appuyer sur le bouton "local").
De plus, lorsque j'arrete mon programme, le GBF stock la derniere valeur (surement dans un buffer) et me la renvoie à chaque relancement du programme. N'y a t il pas un moyen de supprimer la memoire du gbf pour qu'il m'envoie la valeur de fréquence que je lui envoie avec labview lors de l'initialisation de l'instrument??
Pourriez vous m'aider ??
Merci d'avance

Compatibilité labview et instruments

Bonjour,
Je suis débutante et dans le cadre d'un projet d'école, je dois utiliser une caméra thermique et développer ,sous Labview, un logiciel de traitement.
Je n'ai pas encore fait le choix de la caméra et je me demandais si toutes les caméras pouvaient être utilisées avec Labview ou s'il existait des restrictions.
La question peut paraître un peut bête mais elle m'est nécessaire ...

Bonjour,
Votre question est très large et nécessiterai que vous preniez contact avec votre représentant technico-commercial pour que vous discutiez des solutions possibles NI en terme de Vision.
Sachez globalement que la caméra n'est pas le seul élément à prendre en compte, il vous faudra une carte d'acquisition d'image (cartes NI-14xx)qui se connectera à la caméra, un driver (NI-IMAQ), probablement une bibliothèque de traitement (NI-Vision) et l'environnement de développement (LabVIEW).
Ci-dessous quelques liens utiles:
(Apprendre comment faire de l'acquisition d'image avec LabVIEW)
* Vision tutorials
http://zone.ni.com/devzone/devzone.nsf/webproducts/7d6146d8c67a832e862567f1006c29ee
(Sélectionner une caméra)
* Camera Advisor
http://sine.ni.com/apps/we/nipc.specs?action=search&asid=1102
Cordialement.
Matthieu Gourssies
National Instruments France

Why does visa write hang with Labview 2009 instrument drivers.

I'm having an issue with a code package that I'm running. The pacakge is very complex and was written by someone other than me. It runs fine while using the labview 8.5 drivers, however, when the 2009 instrument drivers are install there is a visa write call to an instrument where the software will hang up at the VISA write VI. I tried setting the timeout attribute but that makes no difference. I would expect that if the visa write did not work, that it would time out with an error instead of hanging up.
Some additional information. The instrument is an EPM which is on a GPIB bus with other instruments. When I place the EPM2000 on a serparate bus this problem goes away, but I want to be able to operate on the same GPIB bus.
Has anyone experienced a similar problem? What can I try to help troubleshoot the problem. I tried opening NI Spy but that shows no activity going on.

Hi Steve,
My apologies, when you said instrument drivers I assumed you were refering to the individual drivers for your instrument. Were you refering to the VISA drivers? If so, the latest version of these is 5.1.1 which can be downloaded here: http://joule.ni.com/nidu/cds/view/p/id/2659/lang/en.
Also are you able to communicate with this device using the test panels in Measurement & Automation Explorer? There is also a tool called NI IO Trace (or it may still be called NI-SPY in 2009) that can be opened from MAX that monitors all GPIB commands sent and received on the machine. Getting a log of the commands when the hang occurs may help to diagnose it.
It is possible this issue could be caused by opening and closing the VISA reference frequently in the code such as in a loop iteration. Is this is case in your code?
Justin D
Applications Engineer
National Instruments
http://www.ni.com/support/

How to make a multimeter in multisim using LabVIEW

Hello there, I want to make a multimeter in Multisim using LabVIEW. And I have read this article http://zone.ni.com/devzone/cda/tut/p/id/5635#toc3 before.
And now I have these questions:
1. How to measure a resistor? The Impedometer.llb in lvinstruments folder made me confusing.
2.how to measure the current? I can measure the voltage but I dont know how to measure the current.
3.What's the meaning of "instrument version" in every _multisimInformation.vi, whether I can modify it?

Hello,
A question for you: your multimeter will acquire real data (using a data acquisition board) ? or, is it just for simulation (like the Multimeter included in Multisim)?
The Impedometer.llb is a library that contains all the files for the Impedance Meter instrument in Multisim. As stated in the template, the instrument version constant is an internal reference that must not be modified.
Regards,
Fernando D.
National Instruments

LabVIEW Video Waveform Source from Video Test Image for Multisim simulation

Hi,
I want to simulate a video amplifier circuit in Multisim. I need a Composite Video Signal Source for feeding the input to the amplifier. In one of the application note I saw that LabVIEW can be used to create Video Waveform Source from Video Test Image (BMP). I've attached the sheet for reference. My questions are below:
1. Do I need to create the Video Signal Source in LabVIEW or is it already available with LabVIEW library?
2. How to call/access this Video Signal Source from LabVIEW for simulation in Multisim?
3. Any examples available?
4. Which versions of LabVIEW and Multisim supports this feature?
Any help is truly appreciated.
(Topic of the Application Note: Circuit Design Using Simulation and Virtual Instrumentation, Applications in Biomedical Engineering)
Regards,
Sinoj
Attachments:
circuit_design_simulation_and_virtual_instrumentation_page26.pdf ‏314 KB

Hi Mahmoud,
Thanks for your reply.
I searched for the VI 'Simple create composite signal from BMP image.vi' on internet (since it is named so in the Application Note), but could not find. I've some experience with LabVIEW, so I hope that once I get this VI I can plug-in to Multisim. But in order to add it to 'lvinstruments' folder of Multisim installation directory I need the DLL and LLB file (not the VI, I understand so). If these DLL and LLB files are available I think it will be easier to integrate with Multisim, otherwise I don't know what to do if I have just the VI.
Anyway attached the complete Application Note.
Regards,
Sinoj
Attachments:
circuit_design_simulation_and_virtual_instrumentation.pdf ‏2293 KB

LabVIEW instruments in transient simulation

Hi,
I'm performing some tests with an InputOutput LabVIEW Instrument that I made myself (2 in/4 out) that basically implements a simple lookup table (on the basis of two DC voltage levels it perform a 2D interpolation and then sets the 4 voltage outputs accordingly).
In the interactive simulation mode everything works great.
However, if I try to run a transient simulation, the LabVIEW instrument does not respond, it seems to ignore the two inputs so it gives zero for all the 4 parameters.
This suggests me that LabVIEW instruments are interactive-simulation objects only. Is it correct?
This would limit the benefits of this great tool!
Can anyone suggest me a way to overcome this?
I work with Multisim 11 and LabVIEW 2009.
Thanks.

Everasia,
Yes the custom LabVIEW instruments are used in interactive mode only. What other things are you looking to do in Analysis -> Transient mode? Expresssions, Post Processor data, etc?
Are you are trying to use LabVIEW as a type of I/O behavioral component?
Also, another possibility is using the Multisim API with LabVIEW (www.ni.com/labs) -
LabVIEW Multisim Connectivity Toolkit (Beta), this will allow you to create interactivity between LabVIEW controls and the Multisim simulation - you can adjust source inputs and measure probes and pause the simulation between steps.
If you would like to discuss the use case in more detail, please email me directly.
Regards,
Pat Noonan
[email protected]

How to use Extech Instruments model 407123 with Labview 7.1

I am pretty new to Labview. With the help of this forum I was able to configure my DAQpad 6020E with my Labview 7.1.
Now I am looking at using an Extech Instruments Hot Wire Thermo-Anemometer (407123) in my experiment and running it through Labview. Based on my research, I was led to believe that I should use the Instrument Assistant I/O and NI-Visa, but I am having a lot of difficulties. First off, the Thermo-anemometer is wired for RS232 and I have it connected to an RS232 to USB converter, which is then plugged into my computer. I have the driver for the converter. When I plug the thermo-anemometer into my computer, MAX reads it as a serial port and it is listed as COM3. MAX claims that the device is working properly. However, when I run Labview's Instrument Assistant I/O, and tell it to read data I get a bff0015 error and it says that the device timed out. I have tried changing the time and I still get the same error. I am assuming this means that Labview and my device are not communicating.
I have seen some mention of instrumentation drivers, but I haven't been able to find any for my particular device. I am assuming that is the root of my problem, and that if I had an instrument driver to run my device in Labview that it would work properly. So here are my questions.
1) What do I need to take data from a third party thermo-anemometer in Labview?
2) Am I correct in thinking I need some sort of instrument driver? And if so, where could I find one (I have already searched for one and did not find it)?
3) Is it possible and practical to take data through Labview from a DAQpad and a third party instrument at the same time?
4) Are there any guides or tutorials I could use that may show me how to accomplish what I'm trying to do?
Thanks.
Solved!
Go to Solution.

I've been trying numerous things to get this to work, and I've had little luck in getting exactly what I want. I have been able to get data from some example VI's designed for serial read, and I was able to tweak them some, but this data seems to be only able to be saved to a .txt file. I want the data from my anemometer to be read along with the time it was read and stored in a spreadsheet.
Instrument I/O Assistant appears to have exactly what I need to do this, but I can't get it to work. I keep getting the bff0015 error, which is that the device timed out before the operation completed. I don't understand why it is doing this, or how to stop it, because I am able to get data from the device otherwise. In fact, following these steps I can see the exact data I want:
1. Open Instrument I/O Assistant
2. On "Select Instrument" I select the correct port and then click "properties"
3. At the top corner of the window I click "Open VISA Session"
4. Once there, I go to the "Basic I/O" tab. Within that tab I click the "Read" tab.
Please see attached screenshots if you want to see what I'm talking about below.
At this point I can read the data from my device. The default count value is 1024 bits. If I click "execute" the device is read and I can read the data in the textbox that says "buffer." However, my device only makes one 16-bit reading every 1.6 seconds, so I have to let the device sit for some time before it can fill the buffer up with 1024 bits. If I don't, the reading takes place, I can see all of my data in the buffer, but the "Return Count" value on the screen is something significantly less than the "Count" value. This makes sense because the buffer did not have time to fill. Needless to say, the "Return Value" says "bff0015" which means it would return the time-out error.
If I wait for the full time for the buffer to fill, OR if I change the "count" value to something significantly lower, say... 32 bits, the buffer "fills" much faster, the "return count" count is correct, and the "return value" reads "3FFF0006" which I assume is a standard code meaning everything went correctly. I also notice that if I wait long enough, the buffer will continue to fill, and I can click "Execute" many times rapidly and get readings instantly. I can tell that the program is just reading data stored in the buffer when it doesn't take a second to perform the reading, and if I continue to click "Execute" rapidly, I will eventually expend the data stored in the buffer and I will start to see the "fresh" readings again.
So here is my question. How do I lower the expected "count" value in the actual "Instrument I/O Assistant"? I can do it in the "Open VISA session" under properties, but the only thing I can change in the Instrument I/O Assistant is the timeout value, but even when I set the value to 5 minutes, I still get the time out error. What else can I do?
Attachments:
Instrument IO view select.pdf ‏119 KB
Instrument IO view read.pdf ‏125 KB

Labview IO instrument in Multisim 10.1?

Similar Messages

Maybe you are looking for