Labview 6 VS instrument wizard of labview 5.0

I would like to know if there is a way I could decide the VISA I'm using in labview 6.0 just like in labview 5.0 with the instrument wizard?
Thanks to anyone

The easiest way to find out what version of VISA you have is to open up MAX and look at the version number under the Software listing. You can also look at the VISA Interactive Control help menu About screen. If you want to be able to query this programmatically from LabVIEW, you can probably do it by querying the registry. The registry entry is under HKEY_LocalMachine\Software\National Instruments\NI-VISA. There is a "current version" listing that should give the infromation.

Similar Messages

No longer able to import CVI Instrument Driver in LabView 2010

Hello,
I used to be able to download the Import CVI Instrument Driver Wizard in LabView 2009, but there is no wizard for 2010?
I also tried importing the driver with the shared library import, but then Binary, Slides and Rings do not come up with their values i.e. if my slide in CVI has 3 positions :
Description      Value
Item 1                 1
Item 2                 2
Item 3                 3
or if my Binary has
Description      Value
On                        1
Off                        0
they do not import the description into LabView 2010?
I tried copying the directories created by the 2009-wizard to the directories of 2010 i.e.:
from     C:\Program Files\National Instruments\LabVIEW 2009\resource\CVIFpConv
to          C:\Program Files\National Instruments\LabVIEW 2010\resource\CVIFpConv
and
from     C:\Program Files\National Instruments\LabVIEW 2009\project\_DriverCtoLV
to         C:\Program Files\National Instruments\LabVIEW 2010\project\_DriverCtoLV
and the wizard loads and runs until I specify a .fp file and then I get the error in the jpeg attached. When I try to open the block diagram (FC_RFL_Initialize.vi), it says you need a password to view it, so that stops my debugging.
Attachments:
Error using Instrument Driver Import Wizard in LabView 2010.JPG ‏88 KB

HI,
I downloaded the wizard and when I tried to import a driver I got this message shown below...(labview 2010)
Thanks...Ness
Attachments:
Error message.JPG ‏140 KB

How do I use "LabVIEW dll import wizard" to import NETAPI32.dll

I am trying to use the LabVIEW dll import wizard for the first time. I am not very familiar in C-coding so this might be a good help instead of configuring CallLibraryFunction nodes myself.
I want to import NETAPI.dll. I am interested in several functions in that dll, but my main priority is the funtion NetUserGetInfo(). On MSDN I have found that the header file for the mentioned function should be: lmaccess.h (include lm.h).
My problem is this:
The shared library contains 317 function(s). But no function is found and recognized in the header file. The following function(s) cannot be wrapped. If you want to import these functions, please review the warning messages next to the functions below. You will need to fix the problems before you can continue with the wizard.
The function cannot be imported into LabVIEW. This might be caused by one of the following problems:
The function is not declared in the header file but is exported in the library.
Check the header file to make sure it contains declarations of the function.
Undefined symbols can prevent the wizard from recognizing functions and parameters. To correct this problem, check the header file to determine if you must add predefined symbols. Click the Back button to return to the previous page of the wizard to add a predefined symbol (for example, "NIAPI_stdcall = __stdcall" or "NIAPIDefined = 1").
MIDL_PASS;_STDCALL_SUPPORTED;__cplusplus;
Any suggestions how I can solve my issue?

astrid wrote:
I am trying to use the LabVIEW dll import wizard for the first time. I am not very familiar in C-coding so this might be a good help instead of configuring CallLibraryFunction nodes myself.
I want to import NETAPI.dll. I am interested in several functions in that dll, but my main priority is the funtion NetUserGetInfo(). On MSDN I have found that the header file for the mentioned function should be: lmaccess.h (include lm.h).
My problem is this:
The shared library contains 317 function(s). But no function is found and recognized in the header file. The following function(s) cannot be wrapped. If you want to import these functions, please review the warning messages next to the functions below. You will need to fix the problems before you can continue with the wizard.
The function cannot be imported into LabVIEW. This might be caused by one of the following problems:
The function is not declared in the header file but is exported in the library.
Check the header file to make sure it contains declarations of the function.
Undefined symbols can prevent the wizard from recognizing functions and parameters. To correct this problem, check the header file to determine if you must add predefined symbols. Click the Back button to return to the previous page of the wizard to add a predefined symbol (for example, "NIAPI_stdcall = __stdcall" or "NIAPIDefined = 1").
MIDL_PASS;_STDCALL_SUPPORTED;__cplusplus;
Any suggestions how I can solve my issue?
Sorry I forgot the attachment, but here it is.
Attachments:
NETAPI32.doc ‏103 KB

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

Has anyone tried to write a wizard in labview?

Hi,
We are planning a new GUI for our hardware, and we want to implement a Wizard, with next and back buttons. Our old GUI is implemented in Labview, and we had lots of database problems (globals, memory etc.). Is there a way to implement a wizard in Labview with a database that can be updated easily (not a structure - everytime you add something everything changes, a file seems slow and cumbersome, a functional global - would it work for a large amount of data?) and will prevent race conditions (part of the program trying to write the same time as another)?
Any ideas would be welcome!
Thanks,
Danielle
"Wisdom comes from experience. Experience is often a result of lack of wisdom.”
― Terry Pratchett

Danielle,
i didn't say that a FGV is not good for the task. I only doubt that a single FGV will do the job.
dsavir wrote:
[...]because we always adding new capabilities to our hardware[...]
Does that require complete new elements in your datastructure? If yes, it is very hard to solve it.
I asuyme that most changes can be captured by using "intelligent" elements in your datastructure like enums and typified clusters.
Bringing up a very important point: In situations like this, it is imho mandatory to create good typedefinitions in order to keep proper versioning.
Working with SCC helps a lot, too, because you can track all changes made over time very easy, and switching back is possible as well.
Regarding the queue-question:
There are many good examples/tutorials and posts available, so please do a short search.
I recommend you to start here.
hope this helps,
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

HP 54501A - Instrument Driver for LabView v.7 or v.8

Hi all,
I'm looking for HP 54501A - Instrument Driver for LabView v.7 or v.8. I have NI gpib/usb controller installed, but cannot control the scope via Labveiw.
The link I found at NI web site within drivers section seems to be broken so I couldn't download it!
Please, anyone, suggest/help!

The link you were given works for me. You can try it again. The given link brings you to a page where the CVI and LabVIEW drivers are listed. the direct link to the LabVIW driver is http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=E3B19B3E9455659CE034080020E748... .

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

Why can't the Instrument Wizard detect my GPIB instruments?

My system has the AT-GPIB/TNT card. I can detect the GPIB instrument connected to the card with "Measurement & Automation" but when I go into Labview Instrument Wizard and try to find the GPIG instrument, all I see is Serial ASRL1 and ASRL2. What can I change so that I can detect the GPIB instruments in Instrument Wizard? I've tried everything. I have NI 488.2 v1.60 installed and NI VISA v2.01. Any help would be appreciated. Thanks!

Make sure that you check the box next to "GPIB" on the second screen of the instrument wizard. Also, make sure that what you are seeing in Measurement and Automation Explorer (MAX) is the most recent case (refresh your screen). It is possible that the instrument is offline, but since MAX doesn't automatically refresh everytime a change is made, it may appear that the instrument is still being detected.
The following link may help.
http://zone.ni.com/devzone/conceptd.nsf/2d17d611efb58b22862567a9006ffe76/8e2f0a10f99519268625680400644435?OpenDocument
Kim L.
Applications Engineer
National Instruments

Convert VI llb from LabVIEW 5 for use in LabVIEW 8.6

Hi Everybody!
Firstly, I'd like to say how much I have enjoyed working for NI and especially supporting the online community in my spare work time. I have to say it is a great place for NI, long term users, new users and everything else LabVIEW - and you guys have fun! Excellent.
I am now back at university and I am looking to use LabVIEW for some robotic work. During my research I have found some manufacturer's VIs for the hardware: however their 'latest' version appears to be in LabVIEW 5.
Would someone be so kind to convert my VIs into at least LabVIEW 6, or up to LabVIEW 8.2.1 (Last version that can open LabVIEW 5 VIs) that would be great. My LabVIEW 8.6 should be able to open VIs saved in LabVIEW 6 or greater. (Obviously not LabVIEW 2009!)
Reference: How to Upgrade or Revert a VI to a Different Version of LabVIEW
Thanks ever so much in advance (I miss the day I had every version of LabVIEW - and NI software on my machine!)
Regards,
James Hillman
Message Edited by Hillman on 10-04-2009 10:16 AM
Kind Regards
James Hillman
Applications Engineer 2008 to 2009 National Instruments UK & Ireland
Loughborough University UK - 2006 to 2011
Remember Kudos those who help!
Solved!
Go to Solution.
Attachments:
Koala_PC.zip ‏328 KB

Mass compile in 7.1
Felix
www.aescusoft.de
My latest community nugget on producer/consumer design
My current blog: A journey through uml
Attachments:
Koala_PC.zip ‏274 KB

An error occurred loading VI. LabView load error code 1: LabView load error code %ld: %p"

I have been developing a VI file that has
been working fine, until now. I am using 8.6.
Every time I attempt to open this file
I keep getting:
How do I fix the error code:
Labview: Memory is
full.
An error occurred loading VI. LabView load error code 1:
LabView load error code %ld: %p”
On a separate dialog:
“Not enough memory to complete this
operation.”
I ran VI analyzer which told that the
VI:
One or more errors occurred during
analysis.
Testing errors tab – Vi not loadable
and my file name. At the bottom in the error description I got:
“Error 74. Memory or data structure
corrupt. <my file path> and <file name>.”
Could not be opened.
Is there anything I can do to recover
the file?

Hi kevin_khan,
I went ahead and tried to open it and got the error attached.
Peter T
Applications Engineer
National Instruments
Attachments:
test.png ‏14 KB

LabVIEW load error code 1: LabVIEW load error code %Id: %p

One of my VI crashed while trying to save some data to file, I then tried to save the VI afterwards, but message with Out of Memory popped up again and the IV closed down. So now I can´t open my VI, then I try I get the "LabVIEW load error code 1: LabVIEW load error code %Id: %p" message and I have been given no opportunity to recover an older version of the VI then I close down and open LabVIEW again!!! So my VI is lost or what?
This is a huge problem for me, hope someone can help...
Regards
Jesper

Hi Jesper
For the future you should be good with LabVIEW 2012 (Normally realeased after NI Week in Austin in beginning of August). From what I know about this problem it have not been mentioned to be solved in a fixpack before release of LabVIEW 2012.
If you are reading in large files that uses more memory than avaliable and do wan't to avoid LabVIEW from crashing then you could add more RAM to your PC. If you are using Windows 32-bit you could try to edit the boot.ini file for Windows to allow Windows to allocate more memory to LabVIEW as explained in the following article:
Extending Virtual Memory Usage for 32-bit Windows
http://zone.ni.com/reference/en-XX/help/371361H-01/lvhowto/enable_lrg_ad_aware/
You could also try upgrading to Windows 64-bit this will allow much larger memory operations, and Windows 64-bit will let LabVIEW allocate more memory.
To use Source Code Control on your computer you will need:
1) A Source Code Control server with space to store the backup VI's and previous versions on (this can be your own PC). All Source Code Control providers that follow the Microsoft Source Code Control API. We have a list of tools that we have been tested that can be found here (note that some is free and other is not):
Which Third-Party Source Control Providers Can I Use with LabVIEW 8.0 and later?
http://digital.ni.com/public.nsf/websearch/26EC5904169430CE8625706E00743997?OpenDocument
2) After installing the server you need to configure LabVIEW to communicate with this server. In the article below under the section "Configuring LabVIEW to Call the Microsoft SCC API" you can see how to do this:
Software Configuration Management and LabVIEW
http://zone.ni.com/devzone/cda/tut/p/id/4114
3) You are good to go. Source Code Control uses the two most know functions "Commit / Check out." When you Check out a document you will be able to edit it, and when you then commit the changes then it will be saved with a new version number on the server. For each commit you will be able to select "Revert to previous version" to go back and restore a previous commited VI. You can use these functions on the VI it self or as I prefer from the Project Explorer.
Bisides the advantage of being able to restore previous versions, Source Code Control is also a great tool if your are multiple users working on the same project. You will i.e. be able to be 2 or more developers working on the same VI at the same time and then merging your changes to one VI when you are finished.
Best Regards
Anders Rohde
Applications Engineer
National Instruments Denmark

How can I call a LabVIEW executable from within another LabVIEW executable?

I have a customer requirement for two LabVIEW executables. Based on their current setup, they need to run executable "A" or "B", both of which are under independent revision control. I have created a third "selection" executable that allows the operator to choose between one of the two, but I am receiving errors when I attempt to call a LabVIEW executable from within a LabVIEW executable using either the "System exec" VI or the "Run Application" VI. If I call a non-LabVIEW executable (such as Windows Explorer) everything works fine.

> I have a customer requirement for two LabVIEW executables. Based on
> their current setup, they need to run executable "A" or "B", both of
> which are under independent revision control. I have created a third
> "selection" executable that allows the operator to choose between one
> of the two, but I am receiving errors when I attempt to call a LabVIEW
> executable from within a LabVIEW executable using either the "System
> exec" VI or the "Run Application" VI. If I call a non-LabVIEW
> executable (such as Windows Explorer) everything works fine.
As with the other poster, I suspect a path problem. You might try the
path out in a shell window, and if it works, copy the complete absolute
path to LV to see if that works. LV is basically passing the comma
nd to
the OS and doesn't even know what is in it, so you should be able to get
it to work.
The other poster commented on subpanels, which is a good suggestion, but
without going to LV7, an EXE can have open more than one VI. You can
use the VI Server and the Run method to fire up another top-level VI.
The decision is whether you want both to be in unique processes.
Greg McKaskle

How can i use labview.tlb to control Labview from an external application?

Hi,
I've been told by a labview engineer that i could use the file
labview.tlb located in the labview install folder to control labview
from an external application (in my case, a C# app). I'm using Labview
6.1 under Windows 2000. This article confirms that:
"ActiveX and LabVIEW"
http://zone.ni.com/devzone/conceptd.nsf/webmain/5401BE584FBAEECE862567C2006D36C7?opendocument
But i've not been able to find out how to use this file to achieve
what i want. I just want to be able to open/close labview, open/close
a vi, start/stop a vi, hide/show a vi from a C# application. The above
web page talks about activex but i really don't see the realtion
between activex and that labview.tlb file.
Is there so
mebody around who knows how to use that file? Why does NI
tell us that it's possible to do what i want to do but doesn't explain
how (or hides this info very well)?
Thanks

Hi,
> Hi I am fighting a similar problem and so far I found this: Calling
> LabVIEW from C++ Using ActiveX
>
> http://sine.ni.com/apps/we/niepd_web_display.DISPLAY_EPD4?>p_guid=B45EACE3E21356A4E034080020E74861&p_node=DZ52051&p_submitted=N&p_rank=&p>_answer=&p_source=External
Thanks for the link, i actually already found this link before. I've
found yesterday how to use Labview.tlb, just add it to the references
of the project, it was probably too easy for me at that time:-) But
now, i'm still stuck as there is no doc about using the interfaces and
classes of this activex to control labview.
The example given on your link is made is C++ and for some reasons,
the wrapper generated for Labview.tlb when i added it to my c# project
doesn't seem to expose the same
interfaces and classes as the one used
in the C++ example. I therefore can't use the C++ example in C#.
I've tried to do something like:
LabVIEW.ApplicationClass a = new LabVIEW.ApplicationClass();
Just this line causes labview to launch but then immediately throws an
exception: "Query interface for interface LabVIEW._IApplication
failed".
Does somebody knows how to use that control in C#/VB.NET ?

Problems with project when switched from Labview 8.2.1 to Labview 10

Hi everyone,
I recently switched from Labview 8.2.1 to Labview 10.
Before I can run the project I get the error which you can see in the attachment.
(The project is running well in Labview 8.2.1)
I did already check if variables end with a space, but none of them are.
The variables are also without any slashes, so that couldn't be the problem either.
Does anybody has any idea what the problem can be, please let me know.
I hope to hear from some of you soon.
Regards,
Kenny
Attachments:
Error Labview 10.JPG ‏19 KB

Your other post in the other thread indicates you've looked at that thread. Based on that have you checked your variable names to see if any of them are multi-line? The error message is basically telling you that you have illegal characters. A carriage return (\r) or a new line (\n) is an illegal character.

Labview 6 VS instrument wizard of labview 5.0

Similar Messages

Maybe you are looking for